Recruitment Funnel Map

Put real numbers on each stage from first reach to accepted offer, so the hiring debate is about one stage and its cause instead of the latest anecdote. Then change that stage before the next hire.

The funnel itself is practice, not research: process counting applied to hiring. Inclusion theory is well developed (Shore et al., 2011), while the effect of specific diversity initiatives varies (Kalev, Dobbin & Kelly, 2006; Bezrukova et al., 2016). Legal references are to the Swedish Discrimination Act, the EU pay transparency directive and the German Works Constitution Act. Stage timings and thresholds on this page are rules of thumb.

Use it when:

• A hire took far longer than planned, or ended with no accepted offer.
• You hire for the same kind of role regularly and want to know which stage to improve.
• You suspect the process loses certain candidates, or good candidates, at one particular point.

Skip it when:

• You have not yet designed the process for a new role: start with 4.7 Hiring & Onboarding Checklist.
• The question is whether your interviews and tests pick the right people: use 4.16 Selection Quality Scorecard.

A recruitment funnel is working craft borrowed from any process you can count. Each stage has a volume, a conversion rate and a duration, so instead of arguing about whether hiring is broken, you can point to where candidates disappear and ask why there. That matters because the fixes differ completely by stage: a weak ad, a screen that filters out the wrong people, a slow process and an unattractive offer all look the same from a distance, as "we cannot find anyone".

Research enters most directly through inclusion. The theory of inclusive work groups is well developed: people need both to belong and to be valued for what makes them distinct (Shore et al., 2011). But which interventions actually change who gets hired is far less settled, which is an argument for measuring your own funnel before importing someone else's fix. A group that thins out at one stage points at that stage, often the interview, rather than at the pipeline as a whole.

The limit: one hire gives small numbers. Read a single funnel as a set of questions, and trust patterns only across several hires.

Name the role and what success would have looked like, so the funnel has something to be measured against.

Strong answer: "Quality technician, one hire, wanted a start within ten weeks of posting and at least three qualified candidates at final stage. Hiring manager: production manager."

Role and number of hires:

Target time from posting to start:

Hiring manager (role) and who ran the process:

Illustrative example: the roles, the company and all numbers are made up.

A food producer in western Finland hires a quality technician. The post goes up in March; ten weeks later there is still no one.

Section 2: 64 applications, 12 passed screening, 8 first interviews, 4 at the final stage (a lab task), 1 offer, 0 accepted. Offer on day 38.

Section 3: the screen removed 52 applications, but most lacked the required food safety training, so that drop is healthy. The real loss is at the end: the one offer came eleven days after the final interview, and the candidate had accepted another job on day 33.

Section 4: the wait came from two separate sign-offs. Two candidates had emailed to ask for status.

Section 5: bottleneck is speed after the final stage. Offer approval is now agreed before the final interview, and every candidate hears back within three working days. On the next hire for the same role, the offer goes out two days after the final stage and is accepted.