The Hiring Pipeline Playbook.

A dashboard answers “how is hiring going?”. A pipeline answers “what is the next decision?”. The first is comforting. The second is useful.

Every team that grows past ten hires lives or dies on the clarity of its pipeline. Ambiguous stages produce ambiguous reports, ambiguous reports produce slow decisions, slow decisions lose the best candidates. The goal is not elegance. The goal is that two hiring managers never have to argue about what “shortlisted” means.

Rook Recruit ships with four system stages that are position locked by design: New, Screening Rejected, Shortlisted, and Joined. These are the spine. You cannot rename or reorder them. The three middle system stages (Interviewing, Offer Extended, Offer Declined) are fixed for now and may be re-ordered in the future.

Around the spine, custom stages hold the shape of your actual process. Phone Screen. Take Home. On-Site. Founder Chat. Reference Call. Anything that is unique to your team belongs here.

The reason the spine is locked is that it makes reports comparable. When “Shortlisted” means the same thing in every workspace, funnel metrics survive reorganizations. When it does not, numbers drift and trust erodes.

1. Every stage answers a question. “Is this candidate serious?” “Can they do the job?” “Do they fit the team?” “Are we their first choice?” If a stage does not answer a question, it is a queue, not a stage.

2. No more stages than interviewers. Each stage should have a named owner. If you have five stages and two people, three of them will be ignored.

3. The shortlist is not a holding pen. Candidates sit in Shortlisted for at most a week. Longer and they go cold. Move or drop, do not hold.

4. Reject fast. “Screening Rejected” is not a failure of the process, it is the process working. Measure time to reject as seriously as time to hire.

Apply-to-Shortlist rate. What fraction of applicants clear screening? High rates suggest a narrow job description. Low rates suggest the description is drawing the wrong crowd.

Shortlist-to-Offer rate. What fraction of shortlisted candidates receive offers? This is the honest quality signal — the difference between “good on paper” and “would hire again”.

Time in stage (p90). Median time hides the tail. The ninetieth percentile is where candidates quietly ghost. Pay attention to the longest 10%.

Offer acceptance rate. If offers are accepted above 85%, great. Below 70%, the interview experience is probably leaking. Fix the loop, not the offer letter.

Every stage in the Rook pipeline carries the match score and social score on the face of the card. No clicks required to see where a candidate stands against the role.

Moves are live. Drag a card from Shortlisted to Interviewing and the candidate timeline, the calendar, the interview brief, and the notification queue update at once. Two people dragging at the same time does not corrupt state — moves merge and the history shows both hands.

One candidate can sit in two pipelines at once. Context is not lost when a person is considered for two roles. Forks keep both threads alive.

• Stage creep. Stages accumulate every time a hire goes badly. Audit quarterly — if a stage has not answered a question in the last twenty hires, delete it.
• Unowned queues. A stage without a named owner is a hole candidates fall into. Every stage needs someone to defend its definition.
• Different meanings per role. “On-Site” on the engineering team can be a half-day loop. On the design team it is a portfolio walkthrough. Per-role custom stages are fine, but the system stages must stay aligned.
• Treating the pipeline as a spreadsheet. Spreadsheets do not have notifications, do not broadcast moves, and do not merge concurrent edits cleanly. A pipeline is not a spreadsheet with columns.

Hiring is not a funnel, it is a flywheel. Candidates who receive a thoughtful rejection become future applicants, future sources, and future customers. The pipeline is not complete until every candidate has been closed — either hired or honestly thanked. Rook logs both equally.