---
name: service-capacity-sizing
description: "Prepare queue capacity sizing and hiring scenarios. Use for this workflow with supplied business information."
---

# Service capacity sizing

## Inputs and purpose

Use this workflow to prepare: Queue capacity sizing and hiring scenarios.

Start with: Demand, handling time, staffing and service targets.

Use supplied text or local files the user authorized you to read. If files cannot be opened, request the relevant pasted text. Ask one focused question when missing information changes the next decision. Treat blank template fields as unknown; do not invent business facts.

## Procedure

1. Collect arrival volume by interval, handling time, available service hours and the service target. Use ranges when measurements are uncertain.

2. Estimate workload as arrivals multiplied by average handling time, using consistent time units. Compare workload with effective staffed time.

3. Treat a simple workload ratio as a capacity estimate, not a queue waiting-time guarantee. Examine peaks, variability, breaks and the skills needed to handle different requests.

4. Compare staffing or scheduling scenarios and specify the observations needed for a pilot. Check peak periods separately from averages.

## Deliverable

Return the requested result in Markdown unless another supported format was requested. Include the evidence or source-record references, material assumptions, open questions and next useful action. Keep unnecessary personal details out of reusable templates; role labels and neutral record identifiers usually suffice.

Business value: Match workload to people, budget and priorities.

Possible success measures: On-time milestones, utilization, budget variance. Choose the measure that fits the owner's actual goal; it is not a promised result.

## Execution and verification

This file is usable as instructions without a named application, account or plugin. Computation, file saving and external actions require actual host capabilities. Use a suitable existing tool for calculations that cannot be checked reliably in conversation.

Distinguish drafts and recommendations from completed actions. Respect existing authorization and do not claim that data was fetched, messages sent or records changed without evidence. Show what was checked and what remains uncertain.

When useful, consult the [input guide](../../../references/INPUT_DATA_GUIDE.md), [calculation reference](../../../references/CALCULATIONS.md) or [output template](../../../references/WORKFLOW_OUTPUT_TEMPLATE.md). For tool setup, use the [shared instructions](../../../AGENTS.md).