Capability
Zero ghosting and talent report cards
Ghosting is not a failure of manners. It is what happens when giving feedback is manual, unrewarded and slightly risky, so we made it automatic instead.
Zero ghosting means no talent is left without an answer. On CalHire, every talent who is declined automatically receives a report card: where they placed against the role’s requirements, which skills were strongest, and what would most improve their next application. It is generated from the same scores the company used, sent without the company having to remember, and written in growth terms rather than as a verdict.
Last reviewed
The short version
- Every declined talent is told. It is enforced by the platform rather than left to a recruiter’s to-do list.
- The report card is built from the same scores that drove the decision, so it cannot contradict it.
- The word "rejected" does not appear in talent-facing copy anywhere in the product.
- Feedback is about skills and evidence, never about the person, which is also what keeps it legally safe to send.
Why ghosting happens, and why exhortation does not fix it
Most recruiters do not enjoy ghosting people. It persists because the incentives are stacked against the alternative. Writing individual feedback for two hundred applicants is hours of unpaid work at the end of a process that has already closed. Legal teams, not unreasonably, worry that specific feedback creates specific exposure. And nothing bad visibly happens to the company that stays silent, at least not on a timescale anyone measures.
So the honest way to fix it is not to ask people to try harder. It is to make the feedback a byproduct of a decision that has already been made, and to make it structurally safe to send.
Both fall out of scoring against declared skills. The company has already produced the material: component scores, weights, where this talent sat relative to the role’s requirements. Turning that into a report card costs nobody an hour, and because it describes measured performance against stated requirements, it is the kind of feedback that is defensible rather than the kind that invites an argument.
What is in a report card
Where they stood
Their composite and component scores against what the role required. Not a rank against other talent, which tells them nothing actionable and reveals things about other people.
What was strongest
The skills that scored well. Worth saying plainly: most people have never been told which parts of their application worked.
What to work on
The specific gap that most affected the outcome, framed as something to develop rather than something they lack.
What happens next
When their verified score expires, when they can retake, and that their profile stays live for other roles. A decline for one job is not an exit from the platform.
The language rule
The word "rejected" does not appear anywhere a talent can read it. This is enforced in the product rather than left to whoever writes the next email template.
It is not squeamishness. A rejection is a statement about a person; a decline is a statement about a match between a person and one role. The second is both kinder and more accurate, because it is what actually happened. A talent who was strong but third for a role with one opening has not been found wanting in any sense the word "rejected" implies.
Small vocabulary choices compound at volume. A company that declines two thousand people a year with a form letter has generated two thousand small experiences of being dismissed. The same two thousand people, told where they stood and what would help, have had an experience that is at worst neutral. Some of them apply again with a better score, which is the only part of this that shows up in a hiring funnel.
How it works in practice
- 1
You decline a talent
One action in the pipeline, attributed to you, recorded in the audit trail. Nothing extra to write.
- 2
The report card is generated from existing scores
Component scores, weights, and role requirements are already in the system. Nothing is invented for the report, which is exactly why it cannot contradict the decision.
- 3
It is sent automatically
Through the notification engine, on your behalf, to a talent who is still anonymous to you. No inbox, no forwarding, no name required.
- 4
The talent can act on it
Retake after the cooldown, target the gap, or apply elsewhere with the same verified profile. Their next application starts from information rather than from guesswork.
What this does not do
It does not explain the parts of a decision that were not scored. If you declined someone for a reason outside the assessment, the report card will not mention it, because the platform will not put words in your mouth about a judgement it did not observe.
It is not a conversation. A talent cannot reply and argue their way back into a pipeline through the report card. What they can do is appeal a score, which is a separate flow with a human reviewer at the end of it.
It cannot make a decline welcome. Feedback makes rejection informative, not pleasant. Some talent will read a report card and be more frustrated than a silent decline would have left them, because now the gap has a name.
It does not apply to talent who withdraw or never complete an assessment. There is nothing measured to report on, and manufacturing feedback from an incomplete process would be worse than sending none.
Questions people actually ask
Can we turn report cards off?
Is giving feedback a legal risk?
Does the company write anything?
Does a talent see how they ranked against others?
What if a talent disagrees with their score?
How quickly is the report card sent?
Related
Where this connects to the rest of the platform.
Composite scoring and blind ranking
A job score you set the weights for, defaulting to 35 percent vetted score, 40 percent the job’s own interview and 25 percent match. It orders a list. It never makes a decision.
Vetted assessment
One vetted assessment produces a skills profile a company can check, instead of a resume they have to take on trust.
AI governance, bias auditing and the audit trail
Adverse-impact analysis on the four-fifths rule, a hash-chained audit trail, talent appeals, and DSAR handling. The evidence exists before anyone asks for it.
Read the reasoning
The evidence and the argument behind what is on this page.
Why candidates get ghosted, and how to actually stop
Ghosting is almost never malice. It is what happens when closing the loop is optional, unowned and manual. The four structural causes, and the fix for each.
ReadHow to write rejection feedback that is actually useful
Most rejection feedback is either a form letter or a risk. How to write something specific and safe, using the scores you already have.
ReadTime-to-hire is a throughput metric. Quality-of-hire is the one that matters
Speed metrics are easy to collect and easy to game. How to measure whether your hiring decisions were any good, and which metrics to pair with which.
ReadHow to get hired without a degree
A practical guide to competing on demonstrated skill: what to build, how to describe it, which employers to target, and how to handle the question directly.
ReadSee a verified pipeline for one of your roles
Post a role free and review anonymous, skill-ranked talent. No card, no sales call to get started.