Hiring funnel calculator for conversion and capacity

Enter counts for one role or a clearly defined group of comparable vacancies. Use the same application cohort throughout: applications received, applications screened, applicants interviewed, applicants offered a role and hires. Each count means people who reached that point at least once, not the number currently sitting in a stage. The example begins with 200 applications and ends with four hires.

Add the average sessions per interviewed applicant, minutes per session and interviewers per session. The tool estimates interview sessions and combined interviewer hours. It excludes screening, scheduling, preparation and debrief time. If those matter to your capacity plan, estimate them separately. A panel of two people in a 45-minute session uses 90 interviewer minutes even though the candidate attends for only 45 minutes.

Change any field to recalculate. Counts must be whole numbers from zero to 1,000,000 and must stay the same or decrease through the funnel. Workload assumptions accept decimals within the stated limits. Blank or invalid inputs withhold the result. A stage with no entrants has no conversion rate. Reset restores the fictional example; it does not recover your previous inputs.

Choose a role, location, entry window and reporting cutoff. For example, take applications received for one support vacancy during June, then observe those applications until the vacancy closes in August. Write those dates beside your internal analysis. The calculator has no date fields, so it cannot check whether your counts describe the same population. The person preparing the figures must do that check.

Do not divide offers made this month by interviews held this month when those events concern different applicants. That period activity ratio answers a different question from cohort conversion. Likewise, a snapshot showing 20 people currently in interview does not mean that only 20 people have ever reached interview. Use historical reached-stage counts for this model and keep an in-progress cohort labelled provisional.

Decide how to handle repeat applications, reopened records and transfers between vacancies. For a single vacancy, count each application once at each reached stage. For several roles, the same person may have separate applications, so describe the unit as applications rather than unique people across the company. Keep direct sourcing and referral entry routes separate if they bypass a stage.

Stage conversion equals the number reaching the next stage divided by the number reaching the preceding stage, multiplied by 100. With 200 applications and 80 screened, application-to-screen conversion is 80 ÷ 200 × 100 = 40%. With 20 interviewed from those 80, screen-to-interview conversion is 25%. Every rate needs both a numerator and its matching denominator.

Overall application-to-hire conversion is hires divided by applications, multiplied by 100. Four hires from 200 applications gives 2%. Multiplying the four adjacent rates also produces 2% in this strictly nested example: 0.40 × 0.25 × 0.40 × 0.50 = 0.02. Calculate with unrounded values; display rounding can make a manually multiplied result differ slightly.

Interview sessions equal interviewed applicants multiplied by average sessions per applicant. Combined interviewer hours equal sessions multiplied by minutes per session, divided by 60, then multiplied by interviewers per session. These are arithmetic planning relationships. They do not determine how many interviews a role needs or how long any individual candidate should spend in the process.

All figures here are fictional. Suppose one completed application cohort contains 200 applications, 80 screened, 20 interviewed, eight offered a role and four hired. The adjacent rates are 40%, 25%, 40% and 50%. Overall conversion is 2%. These numbers demonstrate the method; they are not a recruitment benchmark, a CapoFine customer result or a recommended selection threshold.

Assume each interviewed applicant attends two sessions, each lasts 45 minutes and two interviewers attend every session. Twenty applicants × two sessions gives 40 sessions. Forty × 45 ÷ 60 × two gives 60 combined interviewer hours. Candidate-facing session time totals 30 hours. The difference comes from counting both panel members’ time, not from additional meetings.

Now hold stage counts constant and reduce the average panel from two interviewers to one. The workload estimate becomes 30 hours. That calculation does not establish that a smaller panel provides enough evidence or an appropriate candidate experience. The hiring owner must review interview coverage and responsibilities before changing the process. A lower workload figure alone cannot justify removing a necessary conversation.

If the panel stays at two but sessions average 60 minutes instead of 45, the estimate becomes 80 hours. This gives the hiring lead a concrete discussion: can the team provide 80 interview hours in the planned window, and which people can attend? Add preparation and debrief separately before treating that result as a staffing commitment.

For a planning scenario, suppose the team wants eight hires and cautiously reuses the fictional cohort’s rates. Eight hires at a 50% offer-to-hire rate implies 16 offered applicants. At a 40% interview-to-offer rate, that implies 40 interviewed applicants. At a 25% screen-to-interview rate, it implies 160 screened applications. At a 40% application-to-screen rate, it implies 400 applications.

The same two-session, 45-minute, two-interviewer assumptions give 120 combined interviewer hours. This backward scenario is explained here rather than automatically forecast by the calculator. You can enter its stage counts to check the arithmetic. Reusing historical rates assumes comparable roles, sourcing, criteria, timing and candidate behaviour. It does not guarantee that 400 applications will deliver eight hires.

Convert hours to availability only after owners agree what they can provide. If one interviewer can allocate six hours per week for five weeks, that is 30 hours. A 120-hour requirement would consume four such allocations. Those are capacity equivalents, not automatically four interchangeable people: specialist interview coverage, leave and calendar overlap may still prevent the proposed schedule.

When working backward produces fractional counts, round each required stage upward before calculating the preceding stage. A plan for a whole person cannot use a fraction of an offered applicant. Keep the original rate assumptions visible and test a less favourable scenario. Do not silently round down to make a headcount target look easier to reach.

A lower rate can have several explanations. The role may attract a different applicant mix, a job description may be unclear, availability may have changed or the cohort may still be open. Start with the underlying records and ask what happened at the handoff. Check whether candidates withdrew, hiring criteria changed, decisions remained pending or stage history was incomplete.

CIPD’s recruitment introduction describes a process spanning role definition, attracting applicants, managing applications and selection, and appointment. Its public summary also connects resourcing with workforce needs. That supports reviewing the wider process; it supplies no target conversion rate for this calculator. Use your role context and evidence before deciding which change to investigate.^[1]

A high conversion rate is not automatically a good outcome. It might reflect a strong matched audience, a very narrow sourcing route or a missing recorded stage. A low rate is not automatically poor recruiter performance. Ask the hiring owner what evidence supports each decision, whether candidates received clear information and which process issue the team can actually change.

This calculator uses applicants offered a role as the offer count and actual hires as the final count. In this model, a hire is a person who started employment. Count a revised offer to the same applicant once. If your organisation reports accepted offers instead, calculate and label that separate rate in your own records rather than relabelling it a completed hire.

The offer-to-hire rate can therefore include both declined offers and accepted offers that did not lead to a start. It is not necessarily the offer acceptance rate. To study acceptance, divide accepted offers by offered applicants using the same cohort. To study starts, compare starts with accepted offers. These additional cuts help locate the handoff requiring attention.

Wait for outstanding offers and future starts to resolve before calling the cohort complete. In an active campaign, four hires from eight offered applicants could become six hires later. The original 50% would then have been a provisional observation, not a final result. Record the cutoff and unresolved cases so readers can tell why a figure changed.

Keep the interview plan tied to the role. Identify what each session should establish, who should attend and who owns the follow-up. Avoid adding meetings merely because the calendar has space, or removing them simply to improve the workload estimate. Count preparation and post-interview feedback in the wider plan even though this tool calculates session attendance only.

The US Office of Personnel Management describes structured interviews as using predetermined questions and a common rating approach. This is methodological context for consistent interviewing, not a claim that this calculator evaluates candidates. A post-interview scorecard can help your team record role-related evidence and discuss gaps with the responsible hiring manager.^[2]

Use the interview scorecard template when the issue is inconsistent feedback. The funnel calculator addresses counts and workload, while the scorecard addresses recorded interview evidence. Neither determines who should advance or receive an offer. Keep hiring decisions with the people accountable for the role and the organisation’s approved selection process.

Zero is a valid count when it is known. If 200 applications produced no screens, application-to-screen conversion is 0%. If there were no screened applications, screen-to-interview conversion is unavailable because there is no denominator. The tool preserves that distinction. Entering zero for unknown history would create a false observation, so leave uncertain inputs unresolved until the owner can verify them.

An increase from 20 interviewed applicants to 25 offered applicants is inconsistent with this nested funnel. It may reflect a direct-offer route or a data error. The calculator withholds results rather than presenting a rate above 100%. Analyse the bypass route separately or define a different model; do not change the counts merely to fit the tool.

Average sessions and panel sizes can be fractional because they summarise differing schedules across interviewed applicants. The tool multiplies those averages as a simplified estimate. If longer sessions also have larger panels, multiplying separate averages may misstate total hours. For a precise workload total, sum duration multiplied by attendees for each actual session in your approved planning records.

Hire supports configurable hiring stages, candidate communication, interview scheduling and structured feedback after interviews. If your review reveals a handoff problem, bring one fictional vacancy and the person who owns that step to a Hire discussion. For example, show where interview feedback is missing before a manager can review the candidate. Confirm how that work would be handled in your workflow.

Keep the calculation separate from any software benefit claim. Recording a process in an ATS does not prove that conversion will increase or interviews will take less time. Agree what you will observe during a bounded pilot, which records will support the comparison and who will check whether the role and candidate audience remained comparable.

The ATS implementation guide can help scope that pilot. Review Hire plans for the required workflow, package and implementation scope. Bring the stage definitions, cohort boundary, unresolved cases and workload assumptions to the conversation, so the next decision concerns a specific recruitment problem and the people responsible for it.