Generate: Business HR — Rejection Letter

Create clear, consistent rejection letters in minutes

Use ready-to-send templates tailored to screening stage, interview outcome, or internal candidates. Output uses merge-ready tokens, tone presets (concise, warm, constructive), and export formats for ATS or bulk email workflows.

Try the generator See template examples

Save time, protect your brand

Why use a rejection-letter generator

Writing rejection emails that are timely, consistent, and legally safe is a common pain for hiring teams. This generator provides HR-focused templates and guided prompts so you can produce professional rejections fast, maintain a consistent employer brand, and reduce risk by avoiding problematic phrasing.

Consistent tone across recruiters and hiring managers
Editable placeholders for ATS and mail-merge workflows
Guidance to keep feedback constructive and legally prudent

Practical starting prompts

Prompt clusters — ready prompts you can copy

Select a prompt cluster that matches the interview stage, candidate type, and desired tone. Each cluster includes tokenized placeholders you can map to your ATS export or CSV.

Short professional decline after phone screen
Warm decline after final interview with constructive points
Concise automated rejection for high-volume roles
Internship-specific supportive decline and next steps
Internal candidate decline with development guidance

Short phone-screen decline

One-line reason, thanks, and soft next step. Tokens: {{candidate_name}}, {{role}}, {{date}}

Prompt: Write a concise rejection after a phone screen. Use tokens {{candidate_name}}, {{role}}, {{date}}. One-line reason + thanks + invitation to connect on LinkedIn.
Tone preset: concise

Warm final-interview decline

Provide 2–3 constructive points and keep emphasis on fit. Tokens: {{candidate_name}}, {{role}}, {{interview_date}}

Prompt: Create a warm decline after the final interview. Include two constructive development suggestions; emphasize role fit rather than performance flaws.
Tone preset: warm/constructive

Bulk automated rejection for high-volume roles

Neutral, brief wording suitable for mail-merge. Avoid personalized feedback.

Prompt: Generate a neutral automated rejection for high-volume hiring. No personal feedback. Include line on record retention and how to update contact preferences.
Includes CSV mapping guidance in the Export & ATS section

Localization cluster

Translate and adapt tone for Spanish (ES), French (FR), German (DE). Prefer local formality and date formatting.

Prompt: Translate the selected template to Spanish (ES), adapting formality and date format to DD/MM/YYYY.
Recommendation: Use local salutations and formal registers for senior candidates in DE and FR

GDPR / EEA-aware phrasing

Short guidance to avoid legal overpromises while respecting privacy rights.

Prompt: Produce GDPR-aware rejection text that states how long application records are retained and how to submit a data request without providing legal advice.
Avoid definitive legal guarantees—refer to company privacy policy instead

Tokens & extractability

Templates optimized for ATS and mail-merge

Each template uses clear, machine-readable placeholders so you can map CSV columns or ATS fields directly. Keep template copy in a separate template library in your ATS or HR portal for consistent bulk sends.

Common tokens: {{candidate_name}}, {{first_name}}, {{last_name}}, {{role}}, {{hiring_manager}}, {{interview_date}}
Keep tokens in header comment lines or a dedicated template field for safe parsing
Export messages as per-row text column or as merged email drafts

Sample token mapping (CSV)

How to map CSV headers to tokens for bulk generation and audit.

CSV: candidate_first,candidate_last,email,role,interview_date
Map: {{first_name}} -> candidate_first, {{last_name}} -> candidate_last, {{role}} -> role, {{interview_date}} -> interview_date
Bulk output: one message per row plus an audit CSV that records template_id and send_status

Mail-merge best practices

Avoid sending partially personalized content; test with a small sample first.

Run a 5–10 message dry run to verify token substitution and date formats
Include an unsubscribe or contact-preference line if sending mass emails

Adapt for global candidates

Localization & tone guidance

Localization covers both language and cultural norms (formality, titles, date formats). Provide tone presets that are suitable per region and candidate seniority.

Spanish (ES): prefer formal 'Estimado/a' for senior roles; use DD/MM/YYYY dates
French (FR): use formal register for external senior candidates; avoid literal translations of English idioms
German (DE): formal 'Sehr geehrte/r' for seniors; match local title conventions

Compliance-minded phrasing

Avoiding biased or legally risky phrasing

Use neutral, role- or fit-based reasons rather than personal attributes. Include constructive, non-specific feedback when appropriate and avoid mentioning protected characteristics or unverifiable claims.

Prefer: 'We selected a candidate whose experience more closely matches this role.'
Avoid: references to age, health, family status, or other protected characteristics
When giving feedback, link to observable behaviors or skills (e.g., coding task, leadership examples) rather than personality labels

Implementation steps

How to use these templates in your workflow

These are practical steps to add the generator into common HR workflows—manual send, ATS merge, or bulk email platforms.

Manual send (small hiring teams)

Copy the template, replace tokens manually or with a simple find/replace, and send via your email client.

Choose appropriate tone preset
Replace tokens like {{candidate_name}} and {{role}}
Save a copy in the candidate record

Bulk send (CSV/ATS)

Map CSV columns to tokens and generate per-row messages. Keep an audit log for compliance and reporting.

Export candidate list from ATS to CSV with consistent headers
Map CSV headers to template tokens and run a dry test batch
Save the audit CSV with template_id, send_timestamp, and send_status

Internal candidate communications

Use a distinct internal template to acknowledge contributions and provide next steps.

Acknowledge recent contributions and learning opportunities
Offer concrete development or reapplication timeline
Avoid mixing external and internal templates to preserve confidentiality

FAQ

How do I personalize feedback without creating legal risk?

Personalize feedback by focusing on observable skills and interview behaviors (e.g., 'more experience with X', 'strong on collaboration but needs deeper technical exposure in Y'). Avoid statements about personal attributes. Keep feedback concise, factual, and avoid comparisons to specific named candidates.

What phrasing avoids discriminatory or biased language?

Use role-fit language: 'We selected a candidate whose experience better matches this role.' Avoid references to age, family status, disability, national origin, religion, gender identity, or other protected traits. When in doubt, stick to neutral, competency-focused descriptions.

Can I bulk-generate rejections from a candidate list or ATS export?

Yes. Export a CSV with consistent headers, map CSV columns to tokens (for example, {{first_name}} -> first_name), run a small dry batch to verify substitutions, then generate per-row messages. Keep an audit CSV that records template_id and send_status for compliance.

How should I word rejections for internal candidates differently?

Internal candidate letters should explicitly acknowledge contributions, explain the decision drivers respectfully, and provide clear next steps and development options. Offer timelines for re-application and identify growth areas—avoid making internal messages identical to external rejections to preserve morale.

What is best practice for multilingual rejections and localization?

Translate and adapt templates rather than performing literal translations. Adjust formality level according to local norms, use local date formats, and have a native reviewer or localization tool check phrases that convey tone. Maintain a separate localized template library in your ATS or HR portal.

How long should we keep rejection communications and what should HR log for compliance?

Retention periods vary by jurisdiction. Log the template used, send timestamp, and minimal correspondence record in the candidate file. Refer applicants to the company privacy policy for data-retention details and provide a clear contact method for data requests.

Can I include brief, constructive feedback — and how specific should it be?

Yes, include brief, constructive points that reference observable skills or interview outcomes. Keep specifics limited to a few actionable items (e.g., 'gain familiarity with X', 'additional experience with Y framework'), and avoid highly granular performance critiques that could be misinterpreted.

Is there a recommended tone for early-stage vs final-stage rejections?

Early-stage rejections are typically concise and neutral. Final-stage rejections benefit from a warmer, more constructive tone and — where appropriate — short development suggestions. Match tone to candidate effort and stage to preserve brand and candidate experience.

PricingPlans and features for HR teams and hiring workflows.
ComparisonSee how template and export features compare to other HR communication tools.
BlogGuides on candidate experience, tone testing, and localization best practices.
AboutHow the generator is designed for HR workflows and extractability.