Hiring Stage Count Reconciliation

Reconcile recruitment funnel counts without confusing event counts with unique candidates. The download provides a specific review process. It does not make decisions or act in an account.

What to provide

Approved candidate IDs, stage events, period, duplicate-event policy and stage definitions.

How it works

1. Match candidate IDs and preserve re-entry events rather than deleting them silently.
2. Report unique candidates and event counts separately for each stage.
3. Use one defined cohort before calculating stage-to-stage rates; mixed periods block comparison.
4. Return a funnel reconciliation and data gaps. Do not update ATS stages or reject applicants.

The output

stage | event count | unique candidates | cohort basis | re-entry count | valid transition rate

Worked fictional example

Fictional A interviews twice and B once: three interview events, two unique candidates. With four cohort applicants, candidate interview rate50%, not75%.

Checks and limits

Preserve source versions and original values. Unknowns stay unknown. Use a qualified reviewer for regulated, legal or hiring decisions. No send, share, account change, schedule, ledger update or payment is authorized. No live account test is claimed.

More recruiters workflows · How-to guides

Method: reviewed source. Demand lead: GSC recruitment pipeline/hiring cluster; distinct from delay register. These are site-query cluster impressions and method evidence, not exact new-topic monthly search volume or a traffic promise. Checked October 4, 2026.