{{ summaryTitle }}
{{ summaryValue }}
{{ summaryLine }}
{{ badge.label }} {{ badge.value }}
candidates
candidates
candidates
candidates
offers
hires
accepted
declined
{{ workflowFeedback }}
Use only documented targets for a comparable role and reporting definition.
%
%
Stage display labels
Change report wording only; the six-stage order and calculations stay fixed.
StageCountShare of appliedPass-throughDrop-offCopy
{{ row.label }}{{ number(row.count, 0) }}{{ percent(row.share_percent) }}{{ row.conversion_available ? percent(row.conversion_percent) : 'End stage' }}{{ row.conversion_available ? (row.increases ? 'Count increase' : percent(row.drop_off_percent)) : 'End stage' }}

Data readiness

{{ reviewHeadline }}

Offer response

{{ offerReview }}

Funnel checks

  • {{ item }}

Interpretation boundary

These aggregate rates locate candidate loss and incomplete records. They do not establish sourcing quality, interview fairness, candidate experience, or quality of hire without additional evidence.

Correct the input issue to render the funnel chart.

{{ exportAnnouncement }}

Cost Per Hire Calculator Calculate cost per completed hire from aggregate or itemized recruiting costs, then compare spend mix and performance against your target.
Employee Turnover Rate Calculator Calculate employee turnover for a defined period, compare separation categories, and catch denominator or headcount reconciliation problems.
Employee Total Cost Calculator Estimate the full annual employer cost of a role from pay, benefits, payroll burden and support costs with monthly and productive-hour views.
Salary Raise Budget Calculator Plan salary raises by employee row or pooled salary base, with fiscal-day proration, employer burden, budget fit, and scenario comparisons.

A recruiting funnel turns a sequence of candidate counts into evidence about where a hiring process narrows. The end-to-end hire rate describes the overall yield, while stage pass-through and drop-off rates locate the transitions that deserve investigation. Those rates become useful only when every count describes the same role, population, status definition, and reporting window.

The funnel is ordered. Candidates move from application through screening and interviews to offer and hire, but real applicant-tracking data does not always decline neatly. A later count can exceed an earlier one when teams merge requisitions, skip stages, change reporting dates, or count events rather than distinct candidates. That increase is a data-reconciliation signal, not a valid negative drop-off.

MeasureUseful questionImportant limit
Pass-throughWhat share reached the next stage?The reason for loss is not shown.
Hire rateHow many applicants became hires?Source mix and role difficulty change the rate.
Offer acceptanceWhat share of the offer denominator was accepted?Pending or mismatched responses can distort the result.
Time to fillHow many calendar days passed from open through filled?The start and finish definitions must stay consistent.

A large drop-off does not prove that a stage is inefficient or unfair. A selective step may be doing its intended job, while a smaller loss can still hide delay, poor candidate experience, or uneven decisions. Funnel metrics point to where deeper evidence is needed; they do not supply the cause or measure quality of hire.

Offer responses need their own consistency check because accepted offers, declined offers, issued offers, and completed hires can belong to different operational moments. A rate should not be compared across teams until those definitions and windows are aligned.

How to Use This Tool:

Build one aligned aggregate report before comparing rates or internal targets.

  1. Enter the six ordered stage counts from Applied through Hired. Use distinct-candidate counts under one consistent scope.
  2. Add accepted and declined offer responses from the same offer window. Pending responses are inferred from issued offers minus classified responses.
  3. Supply both Role opened and Role filled dates when inclusive time to fill is needed. Leave both blank when the dates are not comparable.
  4. Compare internal targets only when they are documented for a similar role and definition. Custom stage labels change report wording, not stage order or arithmetic.
  5. Resolve count increases and incomplete or excess offer responses before using the funnel for cross-role or trend comparisons.

Interpreting Results:

Start with Review. A clear review means stage counts never increase and issued offers have complete accepted-or-declined coverage. It does not certify the underlying applicant-tracking data or the quality of the hiring process.

The largest drop-off identifies the greatest percentage loss among valid declining transitions. Examine that transition with source, queue time, interviewer capacity, decision reasons, and candidate feedback. Percentage loss and absolute candidate loss answer different questions, especially when early stages are much larger than late ones.

  • An unavailable hire rate means the Applied count is zero.
  • An unavailable offer acceptance rate means both issued offers and classified responses are zero.
  • An internal target is missed only when the calculated rate is strictly below the entered threshold; equality clears the comparison.
  • Aggregate conversion rates cannot establish selection fairness, candidate quality, or quality of hire.

Technical Details:

Each transition uses the current stage as its denominator and the following stage as its numerator. A zero current-stage count makes that transition unavailable. Counts are not silently forced into descending order, so a later-stage increase remains visible for reconciliation.

Formula Core

The core ratios preserve the difference between stage conversion, overall funnel yield, and offer-response coverage.

conversioni=counti+1counti×100 drop-offi=100−conversioni hire rate=hiredapplied×100
offer denominator=issued offers when issued is above zero; otherwise accepted plus declined offer acceptance=acceptedoffer denominator×100 response coverage=accepted+declinedissued offers×100

Applications per hire is Applied ÷ Hired and is available only when Hired is greater than zero. Time to fill uses proleptic Gregorian calendar dates and counts both endpoints, so a role opened and filled on the same date has a one-day time to fill.

Rule Core

ConditionResult
Next-stage count > current-stage countFlag a stage increase and exclude that transition from largest-drop-off selection.
Accepted + declined < issued offersFlag incomplete offer responses and show the remaining count as pending or unclassified.
Accepted + declined > issued offersFlag responses that exceed issued offers.
Hires > accepted offers, when accepted > 0Flag a likely scope or status mismatch.
Calculated rate < enabled internal targetFlag the target miss. Equal values are not misses.

For a 100 → 50 → 25 → 10 → 5 → 2 funnel, the hire rate is 2%, or 50 applications per hire. The phone-to-final and offer-to-hire transitions each lose 60%, while 4 accepted and 1 declined response over 5 issued offers gives 80% acceptance and 100% response coverage.

Limits of Funnel Metrics:

The calculations use aggregate counts and user-supplied dates. They do not track candidates, schedule interviews, supply industry benchmarks, test selection fairness, or predict employee performance.

  • Compare funnels only after aligning role family, location, seniority, candidate source, stage definitions, and reporting window.
  • Investigate large losses with qualitative and time-based evidence rather than assuming the percentage identifies a cause.
  • Keep personally identifiable candidate information out of the role label and stage labels; the calculation needs counts, not names.