This article draws on the Vitaver Playbook’s practice of measuring progress through concrete outcomes and assigning an owner to the next step.
Define the result before counting activity
Write down what the person must accomplish, when they need to start, and which conditions they must meet to perform the work. For a database migration, that might mean someone who can rehearse a cutover and rollback before a scheduled release. The hiring manager owns that outcome. The recruiter owns producing candidates who meet the agreed requirements. Name the person who owns each remaining step, including any approvals or access that could delay a start.
Map the search from submission to start
Track unique candidates through submission, interview request, interview conducted, offer, acceptance, and actual start. Record the date each person enters a stage and the reason they leave it. Count a candidate only once per stage for the same requisition. Keep unresolved cases visible, with their age and next action, so people waiting on a decision are distinguishable from people who withdrew or were declined.
Compare each step with the step before it for the same group of candidates. If four of eight completed interviews led to offers, record four out of eight alongside the percentage. Keep repeat interview rounds visible as elapsed time, since counting them as new candidates distorts the comparison. A few cases can point you toward the records to inspect. Use those records to decide whether a process problem is recurring.
Follow the evidence to the bottleneck
- Submissions rarely become interviews. Ask the recruiter and hiring manager to review two declined profiles together. Compare each rejection with the original essentials. If the manager expects recent production cutover experience and the brief only asks for database administration, correct the brief and ask for specific evidence in the next submission.
- Interviews are requested and then sit unscheduled. Check the timestamps on invitations and responses. If qualified candidates are waiting for a panel, give scheduling to a named coordinator and reserve interview times before the next set of submissions.
- Interviews happen and feedback is inconsistent. Compare the actual questions and reasons for rejection. Ask candidates the same core questions about the work and judge the answers against the same standards. The U.S. Office of Personnel Management describes this method in its structured interview guidance.
- Offers seldom become acceptances. Ask candidates what led to the decision and compare the written offer with what they heard earlier. If several candidates cite a schedule or rate that changed late, confirm the terms before interviewing the next group. If the terms were clear throughout, use the feedback to decide whether to revise them or narrow the search.
- Accepted offers stop short of a start. Trace the handoff between acceptance and day one. Confirm who controls each approval, credential, device, or start date. Tell the candidate who owns the next step and when to expect an update.
Use the review to make one decision
Suppose 12 candidates were submitted for a migration role, eight received interview requests, three completed interviews, and one accepted an offer. Four qualified candidates withdrew before the panel could meet and one is still waiting. The five cases between interview request and interview are the first ones to look at. If the withdrawal notes confirm scheduling delays, give the coordinator two reserved interview windows and check whether the next candidates get a confirmed slot sooner. If the notes instead show that candidates learned about a mandatory on-site requirement late, put the requirement in the first conversation and verify that it was understood.
At the next review, compare the same stage for the next group and check that candidates still meet the technical standard. Record the fix, the owner, and the date you’ll review it. With one open requisition, even an informal log can tell you more than a monthly total of résumés sent.