Capacity Planning Cycle

The capacity planning cycle: six stages on a repeating business-day calendar, with the clearing stage netting moves against deficits before requisitions open.

Capacity Planning Cycle is the recurring monthly process by which a workforce operation refreshes its staffing outlook, computes projected surplus or deficit for each business unit, and converts the gap into governed decisions — internal moves first, external requisitions second. Where Capacity Planning Methods covers the analytical techniques of capacity planning (how required staff is computed), the capacity planning cycle covers the operating process wrapped around those techniques: who refreshes what, on which business day, what gets locked, and how the resulting decisions flow to recruiting, finance, and operations leadership. The cycle is the mechanism that turns capacity planning from an annual budgeting exercise into a monthly operating discipline.

Naming and lineage

The process described on this page has no single codified industry name. Practitioner and vendor literature refers to fragments of it as the "capacity planning cycle," the "monthly reforecast," the "headcount planning cycle," or informally as "workforce S&OP" (a borrowing from sales and operations planning, discussed below), but no standards body, analyst firm, or vendor has established one term spanning the full loop from outlook refresh through requisition decision. Contact-center operations teams frequently carry an internal house name for it (variants of "the monthly process" are common), which is one symptom of the naming gap.

The closest codified ancestor is sales and operations planning, the cross-functional monthly process by which manufacturing firms balance aggregate demand against aggregate supply and commit the organization to one set of numbers. (The supply-chain literature abbreviates the term to S&OP; this page avoids the abbreviation, which workforce readers routinely collide with the unrelated standard operating procedure.) The canonical cycle runs five steps — data gathering and product review, demand review, supply review, pre-meeting reconciliation, and an executive meeting that is explicitly a decision meeting rather than a status review — repeated monthly over a rolling horizon of roughly 18 months. Integrated business planning later extended the discipline by tying the balanced plan to the financial plan and strategy rather than stopping at demand-supply balance.

The capacity planning cycle is sales and operations planning's structure applied to workforce supply: demand review becomes the forecast refresh, supply review becomes the roster roll-forward, reconciliation becomes the clearing stage, and the executive meeting produces a locked plan of record. The lineage is worth stating because it imports that discipline's governance machinery — a published calendar, named owners, escalation thresholds, and one committed set of numbers — rather than only its arithmetic.

Process decomposition convention

The sections that follow use a three-level decomposition, anchored to APQC's Process Classification Framework (PCF), the cross-industry standard that decomposes enterprise processes across five levels: Category (Level 1), Process Group (Level 2), Process (Level 3), Activity (Level 4), and Task (Level 5). In PCF terms, workforce processes sit under Category 7.0 (Develop and Manage Human Capital), with planning under process group 7.1 and redeployment under 7.6; the capacity planning cycle described here is a Level 3 process, its six stages are Level 4 activities, and the work instructions inside each stage are Level 5 tasks.

For wiki purposes the convention is stated as L1/L2/L3 process levels:

• L1 — the cycle: the six-stage view in one diagram. Fully generic; documented on this page.
• L2 — the stages: the activity decomposition of each stage. Generic in structure; documented on this page, though some activities (the constraint registry, the calendar offsets) are parameterized rather than fixed.
• L3 — the work instructions: task-level detail — which system produces the roster extract, who runs the clearing computation, the exact escalation thresholds. L3 is necessarily organization-specific and is therefore out of scope for a reference wiki; organizations implementing the cycle author their own L3 against the L2 skeleton.

The process levels also carry a second, older reading among operations practitioners — a documentation hierarchy rather than a classification one. The quality-management documentation pyramid, formalized in the 1994 edition of ISO 9001 and carried forward as guidance since (quality manual → procedures → work instructions → records), taught a generation of operations leaders to document a process as a ladder of distinct artifacts: an overview sheet, then a flowchart, then step-by-step instructions, then an assembled operating manual. Contemporary business-process-mapping practice publishes essentially this ladder as "process mapping levels," while noting that no universal agreement or governing body exists — a widely taught convention with an ISO lineage rather than a codified standard. The two axes are complementary, and they align here: L1 is the process's overview artifact (the six-stage view), L2 is its flowchart tier (the stage decomposition), L3 is its work-instruction tier, and the operating manual is what an implementing organization assembles from all three.

The "L1/L2/L3" shorthand is common consulting usage and is not itself standardized; where precision matters, the APQC level names are the anchor. Note also the collision hazard within this wiki: "Level" in WFM Labs Maturity Model contexts denotes organizational maturity (as in Level 1 Process Templates), an unrelated scale. Process-decomposition levels are always written L1/L2/L3 on this page to keep the two apart.

The cycle at L1

At the top process level (L1), the cycle is six stages executed once per month on a business-day calendar:

#	Stage	Core question	Primary output
1	Demand refresh	What work is coming, given what changed?	Updated volume and AHT outlook by unit and month
2	Supply roll-forward	Who will actually be here to do it?	Projected available FTE by unit and month
3	Requirement and gap	How big is the mismatch, where, and why?	Surplus/deficit view by unit by month, with drivers
4	Clearing	Can surpluses cover deficits before anyone hires?	Feasible-move set, residual hiring need, named binding constraints
5	Lock and decide	What does the organization commit to?	Locked plan of record; approved moves and requisitions
6	Execute and learn	Did the plan and the decisions hold?	Requisitions and moves in flight; variance and accuracy feedback

Each stage is decomposed at L2 in the sections that follow. The stages are sequential within a month but the cycle is continuous: stage 6 of one month's cycle feeds stage 1 of the next.

L2 stage decomposition

Stage 1: Demand refresh and driver injection

The demand outlook is rebuilt monthly using a driver-based decomposition: a business driver multiplied by a contact rate yields volume, and volume multiplied by AHT yields workload. The driver layer sits underneath, not instead of, standard time-series structure — trend, seasonality, and calendar effects still apply to the driver-implied baseline. AHT is maintained as a distinct forecast object because its drivers (self-service deflection, tenure mix, product complexity) differ from volume's.

The stage has two distinct activities:

• Standing refresh — driver actuals are updated (subscriber counts, policyholder counts, client transaction levels), forecast accuracy for months now in actuals is scored, and the statistical baseline is re-fit.
• Driver injection — known business events are entered as explicit adjustments the month they become known: a won or lost account, a product launch, a marketing campaign, a regulatory deadline. Injection is a cross-functional act — sales, marketing, and product bring the events; the forecaster models them. Events carry ramp profiles rather than step changes: a newly won account reaches steady-state contact volume over a defined onboarding curve.

Forecasting literature consistently describes the injection practice but has not formalized it as a named process step; the capacity planning cycle names it deliberately: a named step carries an owner and a calendar milestone, which the injection practice otherwise lacks.

Stage 2: Supply roll-forward

The current roster by unit and skill is projected forward month by month: planned and observed attrition, known departures, hires already in the pipeline, and planned transfers. Two modeling disciplines matter:

• Ramp as a curve, not a step. New hires carry elevated AHT and elevated shrinkage through a defined ramp window before reaching tenured productivity, so a hired head and a productive head are different quantities at different dates.
• Pipeline attrition modeled separately. Attrition during recruiting and training differs from steady-state attrition; blending them systematically understaffs the ramp period.

The output is projected available FTE by unit by month, with new hires and transfers counted at their ramp-discounted effective fraction rather than as whole heads.

Stage 3: Requirement calculation and the surplus/deficit view

Workload is converted to required staff using the methods appropriate to the operation's maturity and channel mix — deterministic Erlang-derived staffing, probabilistic planning, or simulation (see Capacity Planning Methods and Demand calculation). Requirements are grossed up for shrinkage and occupancy and expressed as required FTE by unit by month. Requirement and supply must share one currency for the subtraction to mean anything; the convention here applies shrinkage and occupancy exactly once, on the requirement side, and ramp discounts exactly once, on the supply side.

The stage's defining artifact is the surplus/deficit view: required minus available, by unit, across the rolling horizon. Two presentation standards distinguish a usable view from a spreadsheet dump:

• Every surplus or deficit carries its drivers — what changed since the previous month's lock, and why.
• The view is produced at more than one service-level scenario, so the decision forum sees the sensitivity of the gap, not a single point.

Stage 4: Clearing — netting surplus against deficit

Before any requisition opens, each deficit passes through a clearing stage: projected surpluses elsewhere in the organization are tested against it, and only the residual that cannot be covered by feasible moves becomes a hiring request. The terminology borrows deliberately from financial market infrastructure, where netting is the offsetting of obligations between parties so that only net positions require settlement, and clearing is the broader process that wraps netting — matching positions, computing net obligations, and instructing settlement. In workforce terms: the netting computation offsets one unit's deficit against another's surplus; the clearing stage is the whole monthly event in which all units' outlooks land together and the offsets are found, approved, and instructed. The Workforce Broker describes the organizational design — a brokered clearing function spanning otherwise-separate books of work — that this stage presupposes at scale, including the fungibility dividend — the gap between gross hiring requests and net post-clearing hires — as the clearing function's reportable monthly quantity.

Clearing is a constraint-based matching problem, and the constraints must be explained, not merely enforced. A typical constraint registry includes: skill and proficiency, language, licensing and regulatory scope, legal entity and employment vehicle, client-dedication commitments, geography and time zone, contractual outsourcing commitments, and move ramp — a transferred employee carries a ramp curve like a new hire's, though usually shorter and cheaper. For every deficit, the stage outputs the feasible-move set, the residual hiring need, and the binding constraint named for each move that was considered and rejected. Human-capital research documents the adjacent practice — internal talent marketplaces that surface internal candidates before external requisitions — but describes the matching mechanism rather than a governance sequence; no external standard yet names the netting step, which is why this page defines it.

Stage 5: Lock and the decision forum

The lock stage mirrors the two-tier meeting structure of sales and operations planning:

• A pre-reconciliation working session resolves what can be resolved below the executive level and frames what cannot — each unresolved item arrives at the executive forum as a decision with options and a deadline, not as an open discussion.
• The decision forum is a decision meeting, not a review. Its output is the plan of record: one locked set of numbers — the forecast, the approved moves, the approved requisitions — that recruiting, finance, and operations all execute against.

Pencils-down (the lock) freezes the target month's forecast on a published business day. After lock, changes are variances that travel an exception path with sign-off, never silent edits. Escalation thresholds are defined in advance: a change larger than the threshold moves the decision up a level automatically.

Stage 6: Execution and feedback

Approved requisitions flow to recruiting with need-by dates back-computed from the source-plus-train-plus-ramp lead time; approved moves flow to the units and, where one exists, the internal marketplace. Finance reconciles the locked plan against budget, including the cost asymmetry between hiring and moving. The locked month feeds downstream scheduling, and each new cycle opens by scoring the previous locks: forecast accuracy attributed separately to the driver layer, the contact-rate layer, AHT, and the supply assumptions, so error is assignable to a model rather than to "the forecast."

The business-day calendar

The cycle runs on business-day (BD) milestones rather than calendar dates — a convention borrowed deliberately from finance month-end close calendars, where deadlines expressed as offsets from month-end (BD+2, BD+4) survive monthly reuse across weekends and holidays. The borrow is a design choice: BD notation is standard in accounting close processes but is not an established workforce-planning convention.

A reference calendar, with the lock at BD+7:

Business day	Activity
BD+1–BD+3	Actuals close; accuracy scoring; driver refresh; driver injection
BD+4–BD+5	Supply roll-forward; requirement calculation; surplus/deficit draft
BD+6	Clearing run; pre-reconciliation; decision paper prepared
BD+7	Pencils-down: target month locked
BD+8–BD+10	Decision forum; approvals; requisitions and moves instructed

Two parameters of the calendar are derived, not conventional:

• The lock offset — how far ahead the locked month sits — must cover the cumulative lead time it protects, a heuristic inherited from master scheduling, where the frozen zone of a schedule is sized to the longest cumulative lead time of the process it feeds. If sourcing a class, training it, and ramping it takes sixteen weeks, a cycle running in month M locks month M+4: a September cycle locks January. Lock offsets of roughly two to four months are the practical consequence wherever source-to-productive time runs ten to sixteen weeks.
• The cadence itself should be justified by volatility rather than asserted. Monthly is the defensible floor where demand is event-driven — where individual account wins and losses move volume more than seasonality does — and may be relaxed in highly stable environments.

The calendar is itself a governance artifact in the sales-and-operations-planning tradition: dates published well in advance, a named owner, and named backups per seat. Within the rolling horizon (18 months is the common default in sales and operations planning), each target month passes formal checkpoints at three, two, and one months before its lock — the review discipline ICMI describes as revisiting the long-range plan at fixed distances rather than once a year.

Driver models by business type

The cycle is invariant across industries; the driver layer is not. Three archetypes illustrate the range:

Archetype	Driver	Character	Cycle implication
B2C subscription (telecom, streaming, utilities)	Subscriber count	Smooth, continuously observable, trendable	Standing refresh dominates; injection is rare
Policyholder book (insurance, banking)	Policies or accounts in force, by segment	Segment-level trends plus a book-growth overlay	Standing refresh plus periodic growth-assumption review
B2B client book (managed travel, BPO, managed services)	The client roster itself: wins, losses, ramps, per-client transaction levels	Lumpy and event-driven; individual account changes exceed seasonal amplitude	Driver injection dominates; monthly cadence is the floor; clearing matters most, because client-level volatility routinely puts one unit up while another is down

The B2B client-book archetype is the stress case for the whole cycle: demand arrives as discrete, dated events rather than drift, so the process must incorporate an account win the month it is signed — with a ramp profile and, where volume is dedicated, a unit assignment — rather than discovering it in trailing actuals.

Failure modes

Four failure patterns recur in implementations of the cycle:

• Lock erosion — post-lock changes travel informally instead of through the exception path. The plan of record stops being one set of numbers, and the decision forum degenerates into re-litigating the forecast rather than deciding against it.
• Advisory clearing — the clearing stage produces recommendations that no one is obliged to answer. Units open requisitions while surplus idles elsewhere, and the fungibility dividend is never reported, removing the evidence that clearing pays for itself.
• Injection lapse — the cross-functional feed decays; account wins and losses are discovered in trailing actuals months after signature, and the forecast takes the blame for what is a process failure.
• Blended currency — shrinkage or occupancy applied to both sides of the surplus/deficit subtraction, or to neither, producing gaps that are artifacts of arithmetic rather than of staffing.

Maturity Model Position

• Level 1–2: the cycle typically does not exist as a named process. Capacity decisions are made annually at budget time and adjusted reactively; requisitions open unit by unit with no clearing stage. The first step up is cadence — any repeatable monthly refresh with a documented lock, even in spreadsheets.
• Level 3: the cycle runs as described at process levels L1 and L2 — monthly cadence, business-day calendar, a surplus/deficit view with drivers, and a decision forum with a plan of record. Clearing is manual and advisory.
• Level 4: clearing becomes a governed gate with a constraint registry and named binding constraints; forecast error is attributed by layer; the fungibility dividend (gross requests minus net hires) is reported monthly. Probabilistic surplus/deficit views replace single points.
• Level 5: the clearing computation is continuous rather than monthly-batch, with the monthly forum retained for commitment and governance; driver injection is fed directly from CRM and sales-pipeline systems.

See Also

• Capacity Planning Methods — the analytical techniques the cycle orchestrates
• The Workforce Broker — the organizational design behind the clearing stage
• WFM Processes — the three-pillar process architecture and planning horizons
• Systems Thinking — the discipline the cycle operationalizes, with this process as its worked example
• Forecasting Methods — the demand side in depth
• Recruiting Pipeline and Capacity Planning — the requisition hand-off
• Multi Site and Network Capacity Planning — network-level allocation
• Demand calculation — converting workload to required staff
• Shrinkage · Occupancy · Average Handle Time