Running a Candidate Pipeline Without Losing People to Delays

Recruitment is unusual in having two sets of people who can both stall the process. Candidates drop out because they are waiting. Clients delay because hiring is rarely anyone only job. A candidate pipeline managed without equal attention to the client side produces a great deal of activity and few placements.

The practical consequence is that a recruiter working day should be split between advancing candidates and advancing clients, and that both should appear on the same working list. Systems that track only candidates make the client side invisible, and the client side is where the delay usually originates.

The submission trap

Holding strong candidates back to submit a complete shortlist of three is a common habit and usually costs placements. The candidate found on Monday waits until Thursday, by which time they have interviewed elsewhere. Submit good candidates when you find them, and explain to the client that more will follow. Clients rarely object to receiving a strong candidate early.

Screen against written requirements agreed with the client, covering the must-haves, the nice-to-haves, the salary band, the location or remote arrangement, and the expected joining timeline. Without that document, screening becomes an interpretation of a conversation, and the mismatch surfaces two interviews later when the client says something about the role that nobody wrote down.

Capture notice period, current and expected compensation, other active processes, and location constraints at the first candidate conversation. These are qualification facts. Discovering a three month notice period after the client has committed to a start date is a process failure rather than bad luck.

The single most effective retention technique in recruitment is telling candidates what is happening on a schedule, including when nothing is happening. Set the expectation at each step: you will hear from me by Thursday. Then contact them on Thursday, even if the message is that the client has not yet responded and you are chasing again.

As an illustrative example, a candidate who receives three brief honest updates during a two week wait is far more likely to still be engaged than one who receives silence followed by an apologetic call, even though the underlying delay is identical. The delay is not what loses candidates. The uncertainty is.

Treat this period as an active stage with scheduled contact rather than as a formality. A light sequence works well: confirmation and congratulations, documentation early rather than at the end, an introduction to the future manager, a check in the middle of the notice period, and contact in the final week before joining.

Surface the risks before the offer rather than after. Asking a candidate directly what their current employer is likely to do when they resign, and whether their family supports the move, produces honest answers and gives you time to work with them. Discovering a counter-offer on the resignation day leaves you with nothing but persuasion.

Track time in stage at every step and review it weekly. In recruitment, unlike most sales processes, the primary cause of loss is elapsed time rather than persuasion, which means the single most valuable report is the one showing where days are being spent. Combine it with drop-off by stage and reasons, and the picture is usually unambiguous: either the shortlists are wrong, or the process is too slow, and the response to each is entirely different.

Related reading: industry pages, pipeline management, the dialer, WhatsApp CRM, features, and use cases.