Annual Strategic Workforce Planning Cycle (generic process)

Annual Strategic Workforce Planning Cycle (generic process) is the generic process card, GP-101, for the once-a-year cycle by which a workforce function turns the enterprise plan into a long-range demand envelope, a supply posture, a hiring plan and a budget submission, and locks the result as the baseline plan of record that the monthly cycle refreshes inside. What strategic planning produces and the methods it draws on are on Strategic Workforce Planning; the events of the year and their sequence are on Workforce Planning Calendar and Annual Planning Cycle; the long-range forecast is the first step of the Three-Step Forecast Build and its lock is the budget submission on Forecast Lock Process. None of that is restated here. This card carries the operating process, who does what in which month, with the L0 profile, the variant classes, the L3 job aids and the automation candidates. It is part of Process Standardization and sits under the long-range planning section of the function catalog in Anatomy of a ROC Standard.

The cycle's defining rule is one of sequence: the volume forecast precedes the headcount model, the headcount model precedes the budget submission, and the approved budget precedes any hiring authorization, because a step taken out of order compounds its error across the fiscal year. Its structural ancestor is the annual business plan of the sales-and-operations-planning tradition, which the monthly cycle then works inside.

Process profile

The profile extends the L0 identity fields of Process Decomposition (L0–L3) with the process-level facts a standards committee needs before any step is drawn. Local values are held by the deploying function and marked SET LOCALLY.

Field	Generic value
Card	GP-101 · local card id assigned by the standards committee at deployment
Class	strategic, in the catalog's four-class vocabulary (strategic · real-time · both · supporting); the annual row of Decision Rights by Planning Horizon
Trigger	the fiscal calendar: the cycle opens when finance publishes the budget timetable, a fixed number of months before the fiscal year (SET LOCALLY; nine to twelve months is typical [A])
Cadence	annual, with quarterly checkpoints that may reopen named assumptions; the horizon runs beyond the fiscal year (SET LOCALLY; twelve to thirty-six months is typical [A])
Scope in	the long-range demand envelope by month and client portfolio; the supply posture (supply nodes, sourcing mix, partner seats); the hiring plan and class calendar; the scenario set; the budget submission; the lock calendar and the baseline plan of record
Scope out	the monthly refresh (GP-102); the forecasting method (Three-Step Forecast Build); a single placement decision (GP-401); recruiting after a class is authorized; the schedule bid
Inputs	the enterprise plan and its drivers; last year's envelope and its variance; the long-horizon supply forecast (GP-105); the collision calendar; finance's envelope guidance; the network design; the definitions register
Outputs	the signed envelope (volume, handle time, shrinkage and staffing by month and client portfolio); the submission and the approved headcount; the hiring plan with class dates; the posture; the scenario register; the lock calendar; the baseline plan of record
Upstream	enterprise strategy and finance; the placement function (network design, constraint register); human resources (bid calendar, compensation assumptions); the supply forecast
Downstream	the monthly cycle; recruiting (class calendar); training (cohort schedule); finance (the committed cost line); placement (seat commitments); scheduling (bid timing)
Resources	a long-range capacity model; the roster of record; a scenario set; the committee calendar; finance's budgeting format. Platforms are named at L3, never here
Decision points	is the requirement inside finance's guidance? which scenario is the plan of record? does the posture add or exit a supply node? is the submission approved, cut or returned? does a quarterly variance exceed the band?
Authority tier	stage work at tier 1 (forecaster, planner inside the cycle calendar); the client-portfolio inputs to the envelope signed at tier 2 by the planner who owns each; the plan case, the posture, the budget signature and the lock of the envelope, which is the long-range lock of Forecast Lock Process, at tier 4 (function head); a supply node added or exited, and the budget approval itself, at the executive sponsor by exception
Risk and compliance flags	the approved headcount binds for a year; a site decision carries consultation duties in several jurisdictions; a hiring or reduction plan may have to be presented to a works council; partner seats bind under contract; an [A] attrition rate reaches this cycle only with a range beside it or a tier-4 logged acceptance, under Human Gates and Number Grades
Variant-prone steps	the calendar offsets per fiscal year; the consultation step; notice periods on partner seats; the format finance requires
Automation candidates	four L2 sub-steps (four ranks), listed below

L1 flow

Months are counted back from the first day of the fiscal year; the offsets are SET LOCALLY and published in the cycle calendar. One owner per step; owners are seats.

1. Open the cycle: publish the cycle calendar with an owner per step, the partner input deadlines and the lock calendar for the coming year (standardization lead).
2. Score last year's envelope against actuals by layer (volume, handle time, shrinkage, supply) and log the lessons (forecaster).
3. Collect the drivers of the enterprise plan (growth, launches, migrations, automation deflection, exits) from the business partners by the input deadline (planner).
4. Build the long-range demand envelope by month and client portfolio as the first step of the three-step build (forecaster).
5. Roll supply forward on the long horizon through GP-105 (supply planner).
6. Compute the staffing requirement by month and client portfolio and the gross hiring need by class, ramp-adjusted (planner).
7. Decision: does the requirement sit inside finance's envelope guidance? If no, step 8 adds a reduction case to the set (planner).
8. Build the scenario set: a conservative, a plan and a stressed case, each with its cost and service outcome, plus the reduction case when step 7 called for one (planner).
9. Choose the plan case with a stated reason (function head).
10. Set the sourcing and location posture from the placement lead's proposal of supply node and seat changes against the gap and the constraint register. Decision: does the posture add or exit a supply node? If yes, the executive sponsor decides by exception; if no, the function head decides (function head).
11. Decision: does any jurisdiction in scope require consultation before a hiring or reduction plan is committed? If yes, run the consultation step; if no, record that none applies (works-council liaison).
12. Submit the budget: sign the submission the planner assembled in finance's format; finance approves, cuts or returns (function head).
13. Decision: approved as requested? If cut or returned, re-run steps 6 to 10 inside the approved envelope for one iteration (SET LOCALLY) (planner).
14. Lock and publish: the function head signs the lock of the envelope, the long-range lock, stamped as the long-range vintage, on the client-portfolio inputs the planners have signed; the hiring plan, class calendar, posture and lock calendar are published to recruiting, training, placement, scheduling and the monthly cycle as the baseline plan of record (function head).
15. Quarterly checkpoint: compare year-to-date actuals with the envelope. Decision: does the variance exceed the band (SET LOCALLY)? If yes, reopen the named assumptions as a variance on the long-range lock (Forecast Lock Process); if no, note and continue (planner).

L2 step table

Generic sub-steps only; the deploying function adds the columns Process Decomposition (L0–L3) leaves open. Durations are typical business days [A], SET LOCALLY.

Step	Sub-step	Owner (seat)	Inputs	Outputs	Duration	Automation candidate	Documentation join key
1	1.1 Publish the cycle calendar, owners and input deadlines	standardization lead	finance's timetable	the cycle calendar	2 BD	N	cycle calendar
2	2.1 Score last year's envelope by layer; log lessons	forecaster	last year's vintage, actuals	scoring sheet, lesson log	3 BD	Y	prior-year scoring template
3	3.1 Collect and grade each driver; enter events on the collision calendar	planner	partner submissions	the graded driver list	10 BD	N	driver intake form
4	4.1 Run the long-range baseline	forecaster	the driver list, history	the baseline	3 BD	N	long-range build instruction
4	4.2 Apply driver and event adjustments with reasons	forecaster	the baseline, the calendar	the envelope draft	2 BD	N	long-range build instruction
5	5.1 Call the supply roll-forward on the long horizon	supply planner	the roster, the curves	the supply vintage	3 BD	Y	GP-105 hand-off
6	6.1 Compute requirement and hiring need by class	planner	envelope, supply vintage, register	requirement and gross-hire table	2 BD	Y	requirement computation instruction
7	7.1 Test the requirement against finance's guidance; flag a reduction case if outside	planner	the table, the guidance	inside or outside; the flag	1 BD	N	envelope test
8	8.1 Assemble the scenario set, with the reduction case where flagged	planner	the envelope, the levers, the flag	the scenario register	3 BD	Y	scenario register layout
9	9.1 Choose the plan case with a stated reason	function head	the scenario register	the plan case	1 BD	N	scenario register layout
10	10.1 Propose supply node and seat changes	placement lead	the gap, the constraint register	the posture proposal	5 BD	N	posture proposal template
10	10.2 Decide the posture; route a supply node add or exit to the executive sponsor	function head	the proposal	the posture; an escalation	2 BD	N	posture proposal template
11	11.1 Run the consultation step where required	works-council liaison	the hiring or reduction plan	the consultation record	SET LOCALLY	N	consultation pack
12	12.1 Assemble the submission in finance's format	planner	requirement, posture, plan case	the submission pack	3 BD	N	budget submission pack
12	12.2 Sign and submit	function head	the submission pack	the signed submission	1 BD	N	budget submission pack
13	13.1 Record the approval, cut or return; open a re-run if cut	planner	finance's decision	the approved envelope	1 BD	N	budget submission pack
14	14.1 Sign the lock of the envelope on the signed client-portfolio inputs; stamp the vintage	function head	the approved envelope, the planners' signed inputs	the locked vintage	1 BD	N	lock pack
14	14.2 Publish the plan of record to the downstream functions	standardization lead	the locked vintage	the baseline plan of record	1 BD	N	lock pack
15	15.1 Compare year-to-date with the envelope; test the band; raise a variance on the long-range lock if breached	planner	actuals, the envelope	checkpoint note; a variance entry	2 BD	N	quarterly checkpoint template

Variants

The known variant classes for this process, recorded per Standard and Variant in Process Documentation:

• Statutory. A jurisdiction that requires consultation with a works council before a hiring plan, a reduction or a site change is committed takes a variant row at step 11, owned by the works-council liaison and approved by the function head. A record-keeping period for the submission is a parameter, SET LOCALLY.
• Contractual. Partner seats with notice periods or minimum commitments constrain the posture step through the constraint register; the step is parameterized, so the constraint is SET LOCALLY and takes no variant row.
• Structural. A unit with no long-range model that builds its envelope in a spreadsheet varies step 4 under a row with a review date each cycle until a model exists. A different fiscal year changes only the calendar offsets, which are parameters.
• Transitional. A unit from a predecessor organization still budgeting on its own cycle keeps it under a variant row until its first shared fiscal year, dated by the standards committee; the row's automation effect reads blocks against ranks 1 and 3 for that unit.

L3 register

A localizing team writes these job aids against the generic L2; names only, the content is the function's. The band a quarterly variance may sit in and the number of re-run iterations are L3 values marked SET LOCALLY in the L2 row.

Job aid	Anchored to	Form
The cycle calendar of fiscal offsets, owners and partner deadlines	steps 1 and 14	work instruction
The driver intake form and grading rule	step 3	work instruction
The prior-year scoring template and lesson log	step 2	work instruction
The long-range build instruction (engine, resolution, adjustment reasons)	step 4	work instruction; method on Three-Step Forecast Build
The requirement and hiring-need computation	step 6	work instruction; arithmetic on Capacity Planning Methods
The scenario register and choice record	steps 8 and 9	playbook; method on Scenario Planning and Contingency Staffing
The posture proposal template (add, grow, shrink, exit)	step 10	playbook
The consultation pack	step 11	work instruction
The budget submission pack in finance's format	steps 12 and 13	work instruction
The quarterly checkpoint template	step 15	work instruction
The envelope-breach exception path	step 15	runbook

Automation candidates

Flagged at L2 per the method on Process Decomposition (L0–L3); released per class of action on a published catch rate per Human Gates and Number Grades, never on a maturity label. The list is ordered by how easy a catch rate is to publish, and every row marked Y above appears in it.

1. Prior-year scoring (2.1): a computed comparison of a stored vintage with actuals; first because the right answer is known the moment actuals close, so every miss is countable.
2. The supply roll-forward on the long horizon (5.1): the deterministic query GP-105 releases first, run on a longer horizon; it ranks after scoring because its catch rate is published on GP-105's cadence, not this cycle's.
3. The requirement and hiring-need computation (6.1): deterministic given the definitions register and the ramp curves; it ranks after the roll-forward because an error in its inputs, which the overseer checks, is only visible once the roll-forward's own rate is known.
4. Scenario-set assembly (8.1): the model runs the cases; it ranks last because a wrong case is only caught at the choice in step 9, a human step whose verdicts accumulate once a year.

The signatures are never candidates: the lock of the envelope (14.1) and the budget signature (12.2), both the function head's, commit people and money, and a signature is a human act by definition. The posture decision (10.2) is not a candidate because a supply node added or exited commits the function to a jurisdiction and a workforce whose consequences are not in the model's data, and the consultation step (11.1) is a legal act. The envelope rests on a long-horizon forecast whose uncertainty grows with the horizon, which is why the cycle carries a scenario set rather than one number.

Maturity Model Position

Four scales on this wiki use the word level; the launch page states which is which. On the WFM Labs Maturity Model™ a function that runs the cycle on a published calendar and submits a headcount built from a volume forecast rather than from last year's headcount is at Level 2; one that builds a scenario set, puts a plan case on record and has released ranks 1 and 2 above on a published catch rate is at Level 3; one whose envelope is the machine-readable object described in Long-Term Planning Agents and the Plan of Record, refreshed at each quarterly checkpoint without a rebuild, is at Level 4.

See Also

• Process Standardization — the hub and the inventory this card belongs to
• Workforce Planning Calendar and Annual Planning Cycle — the events of the year and their sequence
• Strategic Workforce Planning — what the long horizon produces and the methods it uses
• Three-Step Forecast Build — the long-range step and the envelope it produces
• Forecast Lock Process — the budget submission as the long-range lock
• Monthly Capacity Planning Cycle (generic process) — the cycle that refreshes inside this envelope
• Supply and Attrition Forecasting (generic process) — the supply roll-forward that step 5 calls
• Decision Rights by Planning Horizon — the annual row and the envelope's accountable body
• Standard and Variant in Process Documentation — how the variants above are recorded
• Wiki:Packs/Process Decomposition — the pack that localizes this card (CP-OPS-001)