Speed
The first-contact clock: why good candidates disappear before shortlisting
The fastest response does not need to be a polished shortlist. It needs to be a credible signal that a real recruiter has seen the candidate — before somebody else gets there.
HireOS · · 5 min read
Most recruitment teams measure time to submit. It is a sensible metric, but it starts one beat too late.
The first clock begins when a good candidate applies, replies to an outreach message, or is forwarded by somebody the client trusts. From then on, the candidate is deciding whether this role is real, whether the recruiter has understood them, and whether there is a better conversation to take first.
They are not waiting patiently while the CV sits in a shared inbox.
A shortlist is not the first move
There is a habit in agency recruitment of treating a response as complete only when it is perfect: every CV read, every note written, every candidate compared, and a client-ready shortlist prepared. That protects quality, but it quietly turns a four-minute task into a two-day silence.
The candidate does not need a finished shortlist on day one. They need an informed human response: I have looked at your background. This is the part of the brief that fits. Here is what I need to check before I put you forward.
That response does three useful things at once:
- It tells the candidate they are not one of a hundred unseen applications.
- It surfaces availability, salary, notice period, and deal-breakers before the desk invests another hour.
- It gives the recruiter permission to keep evaluating the batch without losing the people at the top of it.
None of that means submitting somebody before they are properly assessed. It means separating contact from commitment.
Why the delay compounds
The first delay is usually ordinary. A recruiter is in interviews. A manager wants a tighter brief. The CV arrived after lunch on a Friday. But the delay compounds because every quiet hour makes the next action less likely to happen.
Candidates send their CV to more than one agency. They reply to more than one message. The first recruiter to have a specific conversation creates momentum; the second is now asking a person who has already started imagining another role to go backwards.
This is especially sharp for candidates who are genuinely in demand. The person with a rare skill, a sensible salary expectation, and a clean reason for moving is not available for a leisurely process. They may not take the first job they hear about, but the first competent interaction changes who gets their attention.
The useful internal measure is therefore not just time to submit. Track the time from a candidate entering the process to a meaningful first touch. If it is consistently measured in days, the desk has a queueing problem — even if the finished shortlist looks good.
Build a two-speed workflow
The practical answer is a two-speed workflow.
Speed one is triage. Against a written rubric, identify the candidates with enough evidence to merit a conversation. This should be fast and deliberately reversible. You are not rejecting the rest; you are deciding whose clock should not be allowed to run.
Speed two is judgement. Read the relevant CVs properly. Test the career story, the context behind the titles, the things that never appear neatly in a PDF. Decide who you would stand behind with the client.
The mistake is trying to perform speed two on every application before allowing speed one to happen. It feels thorough, but it creates a batch process around a market that moves one person at a time.
An explicit rubric makes the distinction safe. A recruiter can see that someone appears to meet the essential criteria and start a conversation, while still having the evidence and the final call in front of them before any submission.
What “meaningful” actually means
An automated acknowledgement does not stop the clock. Neither does “thanks, we will be in touch if suitable.” Candidates have learned to read both as a polite no.
A meaningful first touch has three ingredients:
- One detail that shows the recruiter saw the person, not merely their email address.
- One clear description of the opportunity or the uncertainty to resolve.
- One low-friction next step, with a time attached.
For example: “Your recent migration from on-premise Java to AWS is relevant to the platform work here. I need to check how hands-on you were with the Kafka side and whether the two-day office pattern works for you. Could we speak for ten minutes today or tomorrow morning?”
It is not clever copy. It is evidence of attention, and that is what candidates are evaluating.
The guardrail: do not confuse fast with careless
Faster contact becomes dangerous when it is based on a weak or invented signal. Do not tell somebody they are an excellent fit before a recruiter has checked the essentials. Do not invite them to a process you cannot explain. And do not make a candidate repeat their history because the first message was sent before anyone read it.
The point is not to automate enthusiasm. It is to remove the mechanical wait between a clear piece of evidence and a human conversation.
That is where a good screening workflow earns its keep. It gives the recruiter the handful of candidates whose clock matters now, plus the source material to say something real when they call. The recruiter still decides whether there is a match. They just get to decide while the candidate is still listening.
Look at the last role your desk filled. Find the best candidate, then find the time their CV first appeared. If the gap to a real conversation is longer than a working day, there is probably revenue hiding in that queue.