Fourteen Days of Decay: The Case for Measuring Speed-to-First-Contact

Recruiting teams track a lot of numbers. Time-to-fill, cost-per-hire, source-of-hire, quality-of-hire. Somewhere in that spreadsheet is a metric that predicts whether your best applicants ever become your best hires — and chances are, you aren't measuring it.

Call it speed-to-first-contact: the elapsed time between the moment a candidate submits an application and the moment a human being at your company meaningfully responds. Not an autoresponder. Not a status update. An actual touchpoint that tells the candidate where they stand.

The data problem here isn't complicated. Candidate interest has a half-life, and it's short. A job seeker who applies on a Tuesday is at peak enthusiasm that day. By the following week, they've applied to four other roles, taken two screening calls, and possibly received an offer. By day fourteen, your company has become a footnote in their search — and if a competitor moved faster, your outreach now competes against a signed offer instead of silence.

The Decay Curve Nobody Plots

Think of applicant enthusiasm the way a marketer thinks about lead temperature. The moment someone applies, they've raised their hand. That hand stays up for a while, but it doesn't stay up indefinitely. Every day of silence lowers the odds that a first-round conversation converts, and it raises the odds that the candidate accepts the next reasonable offer that comes along.

This dynamic is especially punishing in the US labor market, where the majority of employed job seekers are passive-to-active transients — people testing the water, not desperately paddling. These are exactly the candidates you want, and exactly the ones with the least tolerance for a black-hole application process. A software engineer in Austin or a registered nurse in Ohio doesn't need your job; they're entertaining it. Entertainers walk away quietly.

What makes the metric so powerful is its simplicity. Unlike quality-of-hire, which requires months of hindsight, speed-to-first-contact is observable in real time, attributable to specific process steps, and immediately fixable. It's one of the few recruiting KPIs where improvement can be implemented this week.

Why Fourteen Days Is the Practical Ceiling

Two weeks isn't a magic number pulled from a vendor whitepaper. It reflects how long a typical active candidate stays in open-market mode before either committing elsewhere or deprioritizing the search. Within that window, three phases matter:

Days 1–3: The acknowledgment window. Candidates expect confirmation that their application landed. A personalized acknowledgment — even a two-line note from a recruiter — outperforms a generic confirmation email because it signals a process, not a form letter.

Days 4–10: The triage window. This is when screening decisions should happen. A candidate who hasn't heard anything by day ten starts assuming rejection and adjusts their behavior accordingly — including accepting competing offers they might otherwise have declined to wait on.

Days 11–14: The recovery window. If you've fallen behind, this is your last realistic chance. A late but substantive outreach — an actual scheduling invitation, not a canned "we received many applications" note — can still salvage a portion of decaying candidates. Past this point, recovery rates fall off a cliff.

Building the Metric Into Your Operation

Measuring speed-to-first-contact requires no new software. Pull timestamps from your applicant tracking system: application date versus first meaningful recruiter activity. Segment by role family and requisition volume. The average will embarrass someone, and that's the point.

Once you can see the number, three tactics reliably move it:

Automate the floor, humanize the ceiling. Set an automated acknowledgment that goes out within hours, but write it like a person and set expectations: "A member of our recruiting team reviews applications within three business days." Automation should buy you time, not replace the human contact that follows.

Institute recruiter triage blocks. Treat new applications like inbound sales leads. Block ninety minutes every morning for application review — no meetings, no sourcing, just triage. Teams that do this routinely cut first-contact times from weeks to days without adding a single recruiter.

Get hiring managers to commit in stages. Most delays happen after the recruiter's initial screen, when the file sits with a hiring manager who has "a lot going on." Solve this at kickoff, not at crisis point. Ask managers to commit to 48-hour review turnaround for screened candidates as a condition of opening the requisition. Make the commitment explicit and put it in the service-level agreement you set at intake.

A Word of Caution About the Wrong Kind of Fast

Speed-to-first-contact is a means, not an end. The goal is a fast, substantive touchpoint — not a rushed one. A templated outreach fired off in four hours that says nothing and asks nothing is metric gaming, and candidates can tell the difference. Pair speed with specificity: reference the role, the candidate's background, and the next concrete step.

It's also worth watching the metric in combination with downstream outcomes. If first-contact speed improves but screen-to-onsite conversion drops, your triage may be prioritizing speed over fit. The KPI should live alongside pass-through rates and candidate satisfaction signals, not instead of them.

Start With Last Quarter's Applications

If you want a fast internal case study, run the numbers retroactively. Take every application from the past quarter, calculate time-to-first-contact, and cross-reference with offer-accept and withdrawal rates. In most organizations, the pattern is unmistakable: candidates contacted within a week convert at a meaningfully higher rate than those contacted later — and withdrawn candidates cluster heavily in the two-week-plus bucket.

That analysis takes an afternoon. The process changes it points to take a sprint. And the payoff — more of your best applicants actually becoming your hires — compounds on every requisition you open afterward.