Requisition Forecasting

Four streams, kept separate because they behave differently. Growth headcount comes from the operating plan: which teams are funded to expand, by how much, and in which quarter. Backfill demand comes from observed leaving patterns by team, role family and tenure band, which is a population view rather than a prediction about named individuals. Seasonal cycles supply timing, including graduate intakes, fiscal year starts, and product or delivery cycles that reliably push hiring into particular months. Known events sit on top: funding rounds, contract wins, site openings, planned restructures. Lead time per role family converts all of it into a start-sourcing date, since a scarce specialist search has to begin far earlier than a volume role to land in the same month. A forecast that supplies counts without dates cannot be resourced.

Horizon and purpose. Workforce planning asks what capabilities an organization will need over the coming years and how to obtain them, weighing building skills internally, hiring them, borrowing them through contractors, or redesigning the work so the need changes shape. Requisition forecasting is the near-term operational layer underneath that: given the direction already agreed, how many requisitions will actually open in the next couple of quarters, in what order, and whether the recruiting team can absorb them. One sets direction and usually belongs to HR and finance leadership. The other schedules work and belongs to talent acquisition. They also fail differently. Weak workforce planning leaves an organization without a capability. A weak forecast leaves recruiters starting from zero on the day a requisition opens, which surfaces as slow time to fill rather than as a strategy problem.

Publish ranges and confidence tiers instead of single numbers, then re-forecast on a fixed rhythm. A workable structure sorts demand into committed roles that are approved or certain to be, probable roles tied to plans that are agreed but unfunded, and speculative roles that depend on an event which may never happen. Resource the committed tier properly, prepare pipelines for the probable tier, and do nothing but watch the third. Rolling the forecast forward monthly or quarterly matters more than getting the first version right, because plans move and a forecast nobody revises is quietly abandoned within a quarter. Comparing forecast against actual openings is what calibrates the next round, and recruitment analytics software turns that comparison into something routine rather than a manual exercise somebody eventually stops doing.

Work ahead of demand instead of behind it. Knowing that a role family repeats every quarter justifies building a talent pool for it now, so the first shortlist appears days after the requisition opens rather than weeks. Recruiter assignment can be staggered on purpose, supplier or panel engagement can be arranged before the crunch instead of during it, and advertising budget can be committed when rates are favourable rather than when desperation sets in. The forecast also creates the one conversation recruiting teams struggle to start. Showing a leadership group that projected demand exceeds available coverage, with dates attached, persuades far better than reporting that everyone is busy. A rough forecast that turns out partly wrong still beats none, because it makes the assumptions visible enough to argue about.