A candidate has been in your "Interview" stage for five days. A panelist promised a scorecard. You haven't heard from them. You don't actually know if they opened the form or just ignored it.
This is the silent failure in hiring that most tools miss.
We run all our hiring on Recruiter — our own product. So when we built the system, we had to solve this first, for ourselves.
The problem we kept hitting
In a typical hiring round, a candidate moves from resume review into interviews. The panel scores them. Based on those scores, you either advance them or reject them. Straightforward, right?
Except it isn't, because most of the time, what you think is happening isn't what's actually happening.
A panelist might open the scorecard modal and then get interrupted. Or forget they started it. Or decide privately that the candidate isn't for them and just… not fill it out. Meanwhile, you're looking at your "Interview" stage and seeing that candidate sitting there, thinking they're being evaluated, when really they're just parked.
The candidate, meanwhile, is waiting to hear back. After a week of silence, they apply elsewhere and accept an offer. You never reach out because you thought they were still in your pipeline.
When we audit our own hiring, we see this pattern constantly: candidates stall not because the interview went poorly, but because the signal from the panel never actually arrived.
Why "looks like it's being handled" is dangerous
Recruiting tools typically show you:
- Candidate is in Interview stage: ✓
- Panelist was invited: ✓
- Panelist opened the email: ✓ (if tracking is on)
What they don't show:
- Did the panelist actually fill out the form?
- Did they hit submit, or just close the tab?
- Is the candidate stuck because the panel is slow, or because the panel never committed?
You can't tell the difference. So candidates languish while you assume the process is moving.
The fix isn't to pester panelists more (they already have too many things demanding their attention). The fix is to know, with certainty, whether the action actually completed.
What we built to solve it for ourselves
We added Action Confirmation to Recruiter: an optional flag on any round that says "verify this scorecard was actually filled out and submitted, not just opened."
When a panelist completes their scorecard in a round with Action Confirmation enabled, Recruiter records that definitively: the action is confirmed. On the Merit List (where you see round results), you can see which panelists confirmed vs. which are still pending.
Two modes:
- Explicit failure only: alert me only if a panelist explicitly tells me they couldn't complete the scorecard. Right for a round where most panelists will score, and a few edge cases might not.
- Every execution should confirm: also alert me if a panelist was supposed to confirm but never reported back. Right for a round where you're expecting everyone to score, so silence itself is a signal something went wrong.
We use the second mode. When a panelist hasn't confirmed within 24 hours, we know it's not radio silence—it's information that the scorecard was never actually submitted.
What changed when we actually used it
Once we turned it on, we discovered our assumption was wrong. We thought ~95% of invited panelists would complete their scorecards. Reality was closer to 80% within a reasonable window.
That's not because our panelists are flaky. It's because scoring is someone else's priority. A founder doing hiring is great at hiring, but they're not great at remembering to file the scorecard while they're fighting a production incident. A hiring manager is juggling their team and their own work.
The absence of certainty is what kills the candidate experience. Once we could see which panelists had confirmed, we could intervene early:
- If your strongest candidate is in Interview but only 1 of 3 panelists has submitted, you can nudge the others now, not five days later.
- If a panelist confirmed but then the candidate waited another week, you know the delay isn't on the panel—it's on your decision-making or scheduling.
- If a panelist never confirms, you can either extend the round timeline or move the candidate forward without that feedback instead of leaving them in limbo.
Why this matters beyond your hiring round
The core insight is simple: absence of a signal is not a signal of absence.
A panelist who didn't complete a scorecard doesn't mean "the candidate isn't ready"—it means "the panel didn't execute." One is a decision; the other is a process failure. Confusing them is how candidates disappear while you think they're still in your pipeline.
This is true for any workflow where the human action is soft and asynchronous. Hiring is just the clearest case because the cost of getting it wrong is real and visible: a great candidate takes another offer, your team doesn't ship, you're understaffed six months later.
We built this because we were losing candidates to our own process. Now we can see where the bottleneck actually is.
If you're running hiring rounds and candidates keep stalling out, this is worth looking for: not "why isn't the panel scoring faster," but "do I actually know whether the panel committed to scoring at all?"
You can monitor your own Recruiter hiring pipeline here: https://roster.opsveritas.com
Curious about how we watch our own pipelines? We use the same Action Confirmation pattern for every async task in our hiring workflow—scoring, scheduling confirmations, offer acknowledgments. The logic is always the same: verify the action completed, not just that it was started.
Top comments (0)