Should you give feedback to a rejected candidate?
Yes, to candidates you interviewed; send the outcome alone to everyone else. Feedback isn't owed. Our advice is to give an interviewed candidate two or three honest sentences with the outcome, and a clear no to someone you screened on a CV. Decide the rule once per role and apply it to every candidate at the same stage.
The wording for each mail is in the regret mail templates. The recruitment agency screening playbook covers where rejections come from. This guide covers the decisions around the mail: who gets feedback, what it leaves out, and when it goes.
Who gets feedback, and who gets only the mail?
This is our own rule of thumb, not a standard. Stage by stage:
| Where the candidate stopped | What they get |
|---|---|
| Applied, or screened on a CV | The outcome mail only |
| Answered the interview | The outcome, plus two or three sentences of feedback |
| Reached the client | A call from you, with the client's view only if the client has agreed to share it |
Source: our own rule of thumb, not a standard · 18 Nov 2026
What about the legal risk?
Legal risk is the commonest reason given for staying silent, and the sources below don't show it is large. Workable (Sep 2023) warns that written feedback needs extra care, because word choices can read as discriminatory, and says a phone call lowers that risk at the cost of more time. interviewing.io's author, in an undated post, reports finding no case where constructive feedback to a rejected engineering candidate led to litigation, after searching Lexis Nexis and speaking to labour lawyers, and notes that settled cases are hard to find.
None of this is legal advice, and none of these sources is about Indian law. If your agency has a policy, it comes first. Past that, tie every sentence to the role's requirements, leave out anything personal, and keep the reason for the decision in your own records.
Why does candidate experience matter to a recruitment agency?
Our advice is to treat candidate experience as part of an agency's work: tell every candidate the outcome, and tell interviewed candidates what their answers showed against the role. It costs a few sentences, and you control it.
Clients raise the same gap from their side. More than a quarter of the businesses polled in a survey shared by Silver Swan Recruitment, a recruitment agency, named lack of feedback as their top problem with recruitment agencies (HR Dive, 17 Dec 2019; sample size not stated). That is clients' feedback from agencies, not candidates', and it is old, so read it as a sign of the same gap, not a measure of it.
An agency also has two audiences, the candidate and the client who made the call, and usually doesn't own the reason. The client does. What you can say in your own words is what the answers showed against the role's requirements. The client's view of the person stays with the client unless they've agreed to share it. This is our own advice; none of the sources we read covers it.
For the candidate, a good process is one message when you decide, written for someone who has interviewed, with the same wording rules for everyone at that stage. Recording why each candidate was rejected, so you can fix the stage that let them through, is in the recruitment agency screening playbook.
What should candidate feedback say, and what should it leave out?
Candidate feedback should say one thing they did well, then one or two gaps, in terms of the role and from what they said in the interview. It should leave out scores, other candidates, the client's opinion, the reason for the decision and anything about the person rather than the answers.
A gap is not the reason for the decision. A gap is what the answers showed ("your follow-up was reactive"). The reason is why you rejected them ("these are core requirements, so we are not moving forward"). Say the first and leave out the second.
Say
- One specific strength they showed.
- One or two gaps, in the role's terms, each tied to something they said. A gap the candidate can't tie to an answer reads as an opinion.
- The outcome, once.
Leave out
- A score or a rank. It invites an argument about the arithmetic and means nothing outside your own scoring.
- Other candidates. Comparison doesn't help the candidate improve, and Workable lists it as something to avoid.
- The client's view of them, unless the client agreed to share it.
- The reason for the decision. The decision sentence already says it, and a reason invites a rebuttal.
- Anything personal: age, gender, background, accent, appearance or health.
- A promise of future roles you don't mean to keep. Workable warns that false hope backfires.
- How the interview was monitored.
Notes beat memory
Feedback is only as good as what you wrote down while the interview was fresh. Notes written against the criteria of an interview scorecard are what the two or three sentences are made from.
When and how should you send candidate feedback?
Our advice is to send the outcome the day you decide, with the feedback in the same message. A candidate waiting for an answer is the part of the experience you can most easily fix. Use a short email for most candidates, and a call for anyone who reached the client or asks you to explain.
If you are still waiting on the client, say so: "we're still waiting on the client" is itself a message to send. An email scales. A call is for the few who reached the client or who write back to ask. Workable's caution that written feedback needs more care is the reason to keep emails short and tied to the role.
If they reply asking why, reply once, in the same terms, and don't reopen the decision. That, too, is our own advice.
How Recagn does this
Recagn is our product. After an interview, Recagn can draft the two or three sentences of feedback from its reasoning on each criterion, and you read, edit and confirm them before anything goes. The draft is a start, not a finished message: the one below breaks its own instruction, and you would cut a line.
Read the tags: only the feedback paragraph is the AI's draft, written from the reasoning above it; the rest is Recagn's fixed template.
Who isn't going forward
- The rule
- Lowest weighted score: sum of weight times score over the scored criteria, divided by the sum of those weights. A tie goes to the earlier candidate id. A Candidate whose bucket is qualified is never rejected.the worked example's rule, standing in for you
- Debashish Mahapatra
- 1.15 out of 5 · Recagn recommends Disqualified · rejected by the rulereport
- Nisha Pillai
- 4.00 out of 5 · Recagn recommends Qualifiedreport
What the draft is written from
- B2C Sales & Conversion
- The candidate has no sales ownership or conversion responsibility. The role-play pitch is a generic one-line product assertion with no discovery, tailoring, or close. They explicitly confirm no sales targets and no closing experience, describing only data-entry and support roles. This maps directly to anchor 1.Recagn's reasoning, per criterion
- Counselling & Needs Discovery
- The pitch is a one-size-fits-all script with no attempt to understand the prospect's role, goals, or constraints. The discovery answer does not list a single discovery question; it only describes jotting names to call back later. No needs discovery whatsoever, matching anchor 1.Recagn's reasoning, per criterion
- Objection Handling & Persuasion
- Faced with a price/competitor objection, the candidate offers only a flat assertion that the course is better, with no technique to isolate the concern, reframe value, or create urgency. They explicitly admit no experience. This is the give-up/defensive level of anchor 1.Recagn's reasoning, per criterion
- Follow-up Discipline & Pipeline Management
- No follow-up cadence, no lead prioritisation, and no CRM experience. Relying on calling back 'when I remember' is reactive and system-less, with no method to prevent leads slipping through. This matches anchor 1.Recagn's reasoning, per criterion
- Communication & Confidence
- Language is understandable and grammatically correct, but the delivery lacks confidence, structure, and persuasive content. The written follow-up task was not even attempted correctly — instead of a re-engagement message, the candidate answered about location and intent. This lack of structure and task relevance keeps it at anchor 2.Recagn's reasoning, per criterion
The email
- Subject
- An update on your application: Inside sales / admissions counsellorRecagn's fixed template
- Heading
- YOUR APPLICATIONRecagn's fixed template
- Greeting
- Hi Debashish Mahapatra,Recagn's fixed template
- Decision
- Thank you for taking the time to interview for Inside sales / admissions counsellor (An EdTech company in Pune). We won't be taking your application forward for this role. We'll keep your details in case something closer fits.Recagn's fixed template
- Feedback
- Some feedback from your interview: Your language came across as clear and easy to understand, which is a solid foundation for a client-facing role. That said, the interview highlighted two areas that were not yet at the level needed for this position: in the sales and objection-handling scenarios, your answers focused on general assertions rather than exploring a prospect's specific needs or addressing their concerns with tailored reasoning, and your approach to following up with leads was more reactive than structured, without a consistent method to track and prioritise contacts. These are core requirements of the role, so we are not moving forward at this time.AI draft, unedited
- Sign-off
- Best wishes, Orchard Talent Partnersinvented agency
- Footer
- Sent by Orchard Talent Partners via Recagn. Replies to this address aren't read. Opt out https://recagn.app/optout/example of emails from every recruiter on Recagn.example link
The draft is written only from Recagn's notes on each criterion. It never sees scores, rankings, other candidates or how the interview was monitored. Its last sentence, "These are core requirements of the role, so we are not moving forward at this time", gives the reason the draft is told to leave out, and repeats the decision. That is the line between a gap and a reason, crossed. So read every draft against the Leave out list before it goes.
Nobody reviewed or sent this one. In Recagn, nothing goes until you press Send in 10 min, and you can cancel it for those 10 minutes. The whole email, and the sentence to cut, are walked through on the regret mail template page.
Drafting the feedback comes off your plate. Who is rejected, and what they're told, stays yours. Recagn recommends. Only you can reject a candidate.
Where the decision sits in the flow is in how Recagn works.
Questions people ask
Should AI write candidate feedback?
Only as a draft you read first. Recagn drafts two or three sentences from its reasoning on each criterion, never from scores, rankings or how the interview was monitored, and tags it as an AI draft until you edit or confirm it. The example on this page shows why: the draft gave a reason it was told not to give.
Do rejection email templates tell you to give feedback?
Two vendors' pages do, in general terms. Keka's rejection email page says to offer constructive feedback "if appropriate", and one of its ten templates invites the candidate to contact the company if they want feedback on the interview. Hyring's rejection letter page says brief, constructive feedback is encouraged when possible, should be factual, non-discriminatory and tied to job-specific criteria, and that some organisations avoid detail to limit legal risk, so check your HR policy first. We read both on 18 Nov 2026.
Does Recagn charge for rejection emails or AI feedback?
Neither uses a credit. Recagn sends the rejection email when you press Send, after a 10-minute wait you can cancel, and the AI draft is something you ask for on the interviewed candidate.