Workload capacity plan

Download Markdown ↓

Inputs and purpose

Use this workflow to prepare: Capacity gaps and staffing/prioritization scenarios.

Start with: Project workload, people availability and planning horizon.

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. List committed work by deliverable, due period, required skill and remaining effort. Separate firm commitments from possible demand.

  2. Calculate usable capacity as scheduled hours minus leave, recurring duties and an explicit contingency allowance. Do not equate headcount with interchangeable capacity.

  3. Place work against the required skills and periods; show overloads and dependencies. Compare sequencing, reduced scope, redistribution and additional capacity.

  4. Return a feasible allocation and the first decision needed. Check that one person's hours are not assigned twice and that each scenario meets its stated service commitments.

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, calculation reference or output template. For tool setup, use the shared instructions.

Plain-text instructions