Headcount forecasting and roll-forward
Project headcount by team and month from the approved plan, adjusting for hiring lag, attrition and backfill policy.
varies by archetype
1The task exists in this business archetype but behaves differently. The note is the point of the edge: it must say how it differs, not merely that it does.
Headcount is capacity and therefore revenue, not merely cost. The hiring plan is the revenue plan, and a hiring miss becomes a revenue miss inside the same period rather than a favourable cost variance.
must happen before
1A hard sequencing dependency: the target cannot correctly start until the source is done. The note gives the reason.
Headcount is the largest and least reversible cost line, so the plan is built around the hiring plan rather than the other way round.
produces
1The modeling object or downloadable deliverable the task creates.
consumes
3A canonical data object the task needs as input.
owned by
1The business-partner org unit accountable for the task.
runs in
1The end-to-end shared-services process the task sits inside.
serves
1The verb-level intent the task exists to satisfy.
performed in
2Software the task is actually carried out in.
Relationships pointing at this node.
performed by
1A job title someone actually holds does this work.