Recruiting forecast model: working backward from hires to sourcing targets

A recruiting forecast model starts from the number of hires a business actually needs and works backward, through each stage of the funnel, to the number of applicants or sourced candidates required to get there. Most recruiting teams do this instinctively for one role at a time; a written model does the same arithmetic in a way that can be checked, reused across the headcount plan, and updated as real conversion rates come in. Below is the model, worked through with the full arithmetic for two invented scenarios.

The two directions this model runs

A forecast model answers one of two questions, and it matters which one you are asking:

• Forward: given how many applicants or leads you expect, how many hires will that produce? Useful for checking whether current sourcing volume is on track.
• Backward: given how many hires the business needs, how many applicants or leads does sourcing need to produce? Useful for setting a sourcing target before the hiring window starts.

Both directions use the same conversion rates; only the arithmetic's starting point and direction change. The backward direction is usually the more useful planning tool, since it turns a headcount target into an actionable sourcing number before you are already behind.

The forecast model, backward from hires needed

Step 1: Hires needed = Attrition-driven replacements + Growth-driven additions
         (from your headcount plan)

Step 2: For each funnel stage, get your own historical conversion rate:
         Applicant -> Screen rate        [ ]%
         Screen -> Onsite/interview rate [ ]%
         Onsite -> Offer rate            [ ]%
         Offer -> Accept rate            [ ]%

Step 3: Work backward, dividing hires needed by each rate in turn:
         Offers needed   = Hires needed / Offer-accept rate
         Onsites needed  = Offers needed / Onsite-to-offer rate
         Screens needed  = Onsites needed / Screen-to-onsite rate
         Applicants needed = Screens needed / Applicant-to-screen rate

Step 4: Compare Applicants needed to your current sourcing/application volume.
         Gap = Applicants needed - Current volume
         If Gap > 0: increase sourcing spend, channels, or lead time before the role opens.

Worked example: a single hard-to-fill role

An invented scenario: a business needs to fill one senior data analyst role. This is the same arithmetic as a high-volume plan, just with hires needed set to 1, which is useful precisely because it shows the model works the same way regardless of scale.

This role needs roughly 50 applicants in the pipeline to reliably produce one hire, given this team's own historical conversion rates. Rounding offers needed up from 1.33 to 2 matters: a plan built on exactly 1.33 offers has no margin if the first offer is declined, which is common enough at a 75% acceptance rate that the model should plan for it rather than treat a single offer as a sure thing.

Worked example: a high-volume hiring plan

A second invented scenario: a customer support team needs 20 hires this quarter, with different historical conversion rates because the role and sourcing channel are different.

This plan needs roughly 178 applicants for the quarter. If current application volume for this role and channel is running at 120 for a comparable period, the gap is 178 − 120 = 58 additional applicants needed, which is the number to act on: more job board spend, an additional channel, or a longer sourcing lead time before the roles need to be filled, not a vague sense that "we should probably post more."

Where the conversion rates come from

Every rate in this model has to come from your own applicant tracking system's history for a similar role, level and sourcing channel, not from a published benchmark. Pull the last two to four closed requisitions of the same type, count candidates at each stage, and calculate the rate directly:

Screen-to-onsite rate = Candidates who reached onsite / Candidates screened

Example: 13 candidates reached onsite out of 20 screened
Screen-to-onsite rate = 13 / 20 = 0.65 = 65%

If you do not have enough closed requisitions of a similar type to calculate a reliable rate, say so on the forecast explicitly and use the closest comparable role type you do have data for as a placeholder, flagged as such, rather than presenting a guess with the same confidence as a calculated rate.

Building in a withdrawal rate

The stage-to-stage rates above already capture some candidate withdrawal implicitly, but a separate withdrawal rate is worth tracking on its own when candidates drop out late in the process, since a late withdrawal costs more sourcing and interviewing time than an early screen-out. Track it as: withdrawals after onsite but before offer, divided by total candidates who reached onsite. A high late-withdrawal rate usually points to a slow process or a compensation mismatch discovered too late, not a sourcing problem, and the fix is different from adding more applicants at the top of the funnel.

Using the model to set sourcing lead time

Once the applicants-needed figure is known, compare it to how many applicants your current channels produce per week for this role type to estimate how many weeks of sourcing lead time the role needs before its target start date. A role that needs 178 applicants and typically receives 15 per week from current channels needs roughly 178 ÷ 15 ≈ 12 weeks of sourcing time before the onsite stage can even begin, which should feed directly into hiring plan template's timeline math rather than being treated as a separate estimate that might not agree with it.

Running the model forward to check current pace

Mid-quarter, the same rates run in the other direction answer a different question: at current sourcing volume, how many hires is the pipeline actually on track to produce? Take current applicant volume and multiply forward through the same conversion rates, instead of dividing backward from a target.

Screens expected  = Current applicants x Applicant-to-screen rate
Onsites expected  = Screens expected x Screen-to-onsite rate
Offers expected   = Onsites expected x Onsite-to-offer rate
Hires expected    = Offers expected x Offer-accept rate

Using the high-volume example's rates with 120 current applicants: screens expected = 120 × 0.35 = 42; onsites expected = 42 × 0.65 = 27.3; offers expected = 27.3 × 0.60 = 16.4; hires expected = 16.4 × 0.85 = 13.9, roughly 14 hires. Against a target of 20, this is the same 58-applicant gap found working backward, arrived at from the other direction, which is a useful check that the two calculations agree before you act on either one.

Common mistakes and the fix

What this model does not tell you

A forecast model tells you how many candidates you need at each stage; it says nothing about whether the roles are being prioritized correctly once they are open, or whether a stalled requisition needs attention before it affects the numbers here. Pair it with how to prioritize open requisitions once the sourcing target is set, since a well-forecast role that never gets worked will miss its hires-needed figure regardless of how accurate the funnel math was.