The message is the last step, not the decision
A reusable rejection template can make communication more consistent. It cannot decide who should be rejected or turn an incomplete review into a defensible outcome. Before sending, an authorised person should have reviewed the role criteria and source evidence, handled material uncertainty, selected the outcome, and recorded who owns it.
Acas notes that candidates may ask for the reason, recruitment rules, or feedback, while employers should decide what they can accurately provide in their context. The European Data Protection Board emphasises accuracy and data minimisation when organisations process personal data. Together, these are useful operational prompts: communicate the outcome clearly, but do not paste every internal observation into the candidate message.
This guide is practical guidance, not legal advice. Employment, equality, privacy, feedback, retention, and accommodation duties vary by market and circumstance. Confirm the process with the appropriate local advisers.
Four records that should not become one
1. Decision rationale
Keep the approved requirement, source evidence, unresolved uncertainty, reviewer action, selected outcome, owner, and time in the decision record. Do not use an AI score as the reason and do not invent a reason after the status changes. The five-part shortlist record can also be used for a non-progression decision.
2. Candidate-facing message
The email should identify the role, state the outcome without euphemism, thank the candidate, and explain any next step or reply route. Include detailed feedback only when a person has reviewed it, the organisation supports it, and the wording is appropriate for that candidate and market.
3. Internal note
Internal context may include handover details, a question requiring HR review, or an accommodation request that still needs an owner. Keep it in the appropriate controlled record. It is not a hidden extension of the rejection email and should not contain irrelevant speculation or copied sensitive detail.
4. System record
Record the operational facts needed to understand the send: recipient, subject, sender, time, message identifier, and available delivery events. A sent or delivered event does not prove that the candidate read or understood the message. Bounce and complaint events need an owned follow-up process.
A locale-adaptable rejection template
Subject: Update on your application for [role]
Hello [candidate name],
Thank you for the time you invested in applying for [role] and for [interview or relevant stage, if applicable].
After reviewing your application, our recruitment team has decided not to progress it to the next stage.
[Optional reviewed feedback: one concise, job-related point that the organisation is prepared to explain consistently. Omit this paragraph when it is not supportable or appropriate.]
If you need an accommodation related to this communication or have a question about the process, contact [owned channel].
Thank you again for your interest in [organisation].
Kind regards, [named person or recruitment team]
Adapt the tone, salutation, formality, and reply expectations for the locale. Do not translate idioms literally. Do not promise reconsideration, future contact, deletion, detailed feedback, or a response time unless the operating process can deliver it.
Worked example: remove unsupported detail
Unsupported: “Our AI found that you were not a cultural fit and other candidates scored better.”
This attributes the outcome to software, introduces an undefined criterion, and gives the candidate no reliable human contact.
Send-ready: “After reviewing your application against the requirements for the production supervisor role, our recruitment team has decided not to progress it. Thank you for the examples you shared during the interview. If you have a question about the process or need an accommodation related to this communication, reply to this email and our recruitment team will review it.”
The revised version states the human-owned outcome and a usable route. It does not claim that the process was fair, legally compliant, or error-free.
Send-review checklist
- An authorised person selected the rejected status after reviewing the relevant evidence.
- The decision record identifies the criterion, uncertainty, outcome, owner, and time.
- Candidate name, address, role, stage, and content locale are correct.
- Subject and body state the outcome clearly and respectfully.
- Optional feedback is job-related, reviewed, supportable, and consistent with internal records.
- No AI score, protected characteristic, speculation, or unnecessary personal detail appears in the message.
- The reply, feedback, privacy, and accommodation routes have named owners.
- The sender and reply-to address are monitored and correctly configured.
- An authorised person has inspected the final preview before confirming send.
- Bounce, complaint, or reply handling has an operational owner.
Skilltage guidance and product boundary
Skilltage guidance: require a human reviewer to select the rejected status before a rejection email can be prepared. Skilltage renders the organisation's configured rejection template in the recruitment case's content locale, shows the subject and body in a confirmation preview, and sends only after an authenticated user confirms. The system keeps lightweight sent-email metadata. When Skilltage's SES delivery path is used, the interaction timeline may also show delivery, bounce, or complaint events; organisation SMTP sends do not create the same provider feedback events.
This workflow keeps communication recruiter-controlled. It does not validate the hiring decision, guarantee delivery, prove that a candidate received or understood the message, or establish compliance. Templates should be reviewed whenever the recruitment process, market, sender configuration, or candidate response route changes.
Next step
Take the current rejection template and mark which sentence belongs to the decision record, candidate message, internal note, or system record. Remove any sentence that has no clear owner or support. Then compare the underlying human decision with the evidence-first screening boundary and check that the candidate-facing process matches the candidate transparency framework.