Rejection Letter

Rejection Letter

When to Use

Use this skill when the user needs to compose a formal decline of someone's application, bid, proposal, or request -- where the recipient invested meaningful time or effort and the communication needs to preserve goodwill, protect the sender's reputation, and deliver a clear, legally appropriate decision.

Trigger scenarios:

• A recruiter or hiring manager needs to notify a job candidate (screened by phone, interviewed once, or advanced to final rounds) that they were not selected
• A procurement or operations team needs to decline a vendor bid or RFP response after evaluation
• A business development or executive team needs to reject a partnership proposal, licensing offer, or joint venture request
• An internal decision-maker needs to decline an employee's budget request, project proposal, or internal transfer application
• A grant committee, accelerator program, or editorial team needs to decline an applicant who submitted a formal submission
• A department head needs to reject a consulting firm's proposal after a paid scoping engagement
• A nonprofit needs to decline a sponsorship request or collaboration offer from another organization

Do NOT use this skill when:

• The user needs a general professional letter with no specific decline element -- use business-letter instead
• The communication involves a complaint, grievance, or interpersonal conflict -- use conflict-resolution-email instead
• The user needs to address an underperforming employee -- use pip-writing instead
• The communication involves contract termination, service cancellation with financial penalties, or legal notice of breach -- these require legal counsel, not a writing skill
• The user is declining a social invitation or informal request -- this skill is for formal business contexts only
• The communication is a collections notice or financial dispute response -- these carry regulatory requirements beyond the scope of this skill
• The user needs to negotiate revised terms rather than issue a clean rejection -- a counter-proposal format is more appropriate

Process

Step 1: Gather Context Before Writing Anything

Ask the user for the following before drafting. Missing any of these leads to a letter that must be revised or that creates unintended legal or relationship risk.

• Recipient identity: Full name, title (if known), and the capacity in which they applied (candidate, vendor, partner, internal employee, etc.)
• What was rejected: The specific role title, proposal name, bid reference number, or request type -- use their exact language back to them in the letter
• Stage of relationship: Initial application (no interview), phone screen, one or two interviews, final-round finalist, shortlisted vendor, or post-paid-engagement rejection. This is the single most important calibration factor.
• Stated reason for rejection: What actually drove the decision -- budget, qualifications, fit, timing, competitive selection, internal shift in direction. The user may or may not want this reflected in the letter.
• Legal constraints: For job rejections, ask whether HR has cleared any specific reason language. For vendor bids in government or regulated industries, ask whether procurement rules restrict what can be disclosed.
• Future relationship intent: Does the sender want to preserve a future hiring/vendor/partnership pipeline? Is this a genuine "not now" or a permanent "no"?
• Tone register: Warm and human (startup, small business, personal relationship with recipient), professionally warm (most corporate contexts), or formally neutral (regulated industries, legal sensitivity, mass rejections)
• Delivery format: Email (most common), formal letter on letterhead (vendor bids, grant rejections, government procurement), or letter attached to email

Step 2: Determine the Depth of Explanation Required

The stage of the relationship is the primary driver of how much you say. Apply this framework:

Tier 1 -- Early stage (unsolicited inquiry, initial application, no interview, automated screening):

• No detailed reason required or expected
• Generic decline acceptable: "After reviewing all submissions, we have moved forward with other candidates"
• Do not fabricate specifics you do not have
• Length: 3-4 sentences total

Tier 2 -- Mid stage (one interview, one proposal review meeting, single RFP round):

• Acknowledge the specific interaction by name or date
• Provide a brief, general reason: "We are moving forward with a candidate whose background is more closely aligned with the technical requirements of this role"
• Reference one specific strength or element of their submission
• Length: 4-6 sentences, one short paragraph

Tier 3 -- Late stage (final-round candidate, shortlisted vendor, partner who invested weeks of work, post-paid-engagement rejection):

• Full acknowledgment of their time investment, including specific elements of their work
• Clear and honest (but legally reviewed) reason for the decision
• Genuine specific feedback on what was strong -- not flattery, but accurate observation
• An explicit next step: feedback call offer, stay-in-touch ask, future opportunity mention
• Length: 3-4 paragraphs, up to one page

Tier 4 -- Post-paid engagement (you hired a consultant, ran a paid pilot, or completed a trial period):

• Acknowledge the completed work explicitly
• Be especially careful with the reason -- the recipient may be in a position to dispute characterizations of their work
• Offer a reference or testimonial if the work quality genuinely warrants it
• Consider whether a phone conversation should precede the written rejection

Step 3: Construct the Opening -- Acknowledge Before Declining

The opening sentence must do two things: thank the recipient for something specific, and signal what the letter is about without using the word "unfortunately" as the first word.

What to reference specifically:

• For candidates: the role title and the specific interview stage ("your time meeting with our product team on March 4th")
• For vendors: the proposal title, bid number, or the specific meeting where they presented
• For partners: the proposal document, the introductory call, or the specific collaboration scope discussed
• For internal requests: the project name, the team's effort to prepare the submission

Openings to avoid:

• "We regret to inform you..." -- dated, cold, signals bad news immediately without any warmth
• "Unfortunately, after careful consideration..." -- "unfortunately" as the first word is a cliché that reads as impersonal
• "Thank you for your interest in [Company]" -- acceptable but generic; specificity is always stronger
• Excessive praise before the decision -- anything more than one sentence of acknowledgment before the rejection feels like stalling

Step 4: Deliver the Decision -- Clearly and Without Ambiguity

The decision statement must appear by the second or third sentence of the letter. This is not optional. Recipients who have to read through an entire paragraph before finding the "no" feel manipulated.

Decision statement construction rules:

• Use active, clear language: "We have decided to move forward with another candidate" not "It appears we will be going in a different direction at this juncture"
• Do not use "at this time" unless the door is genuinely open in the near future -- this phrase is widely recognized as a false softener and damages credibility
• Do not name the competing candidate, vendor, or proposal -- this creates comparison-based grievances and legal risk
• For internal rejections, "After reviewing the proposal with leadership, we will not be moving forward with this initiative" is appropriate -- do not attribute the decision to a single person if it was collective
• The phrase "We have decided to pursue a different direction" is appropriate when the rejection is based on internal strategy shifts rather than the recipient's shortcomings

Common decision statement templates by context:

• Job candidate: "After careful consideration, we have extended an offer to another candidate whose experience more closely aligns with the current needs of this role."
• Vendor/RFP: "Following our evaluation of all submitted proposals, we have selected a different vendor for this engagement."
• Partnership proposal: "After reviewing your proposal with our leadership team, we have decided not to move forward with a partnership at this time." (Use "at this time" here only if you mean it.)
• Internal budget request: "After review, we are not able to approve this budget allocation for the upcoming quarter."
• Grant/accelerator: "After reviewing all applications, we are unable to offer you a position in this cohort."

Step 5: Provide the Reason -- Calibrated, Honest, and Legally Safe

The reason is the most legally and relationally sensitive element of the letter. The level of specificity must match the tier from Step 2.

What is safe to say:

• Competitive selection ("the submitted proposal more closely aligned with the specific technical requirements of this project")
• Budget or capacity constraints ("the project scope has shifted and we are unable to proceed with external support at this time")
• Timing or strategic direction ("our current priorities have shifted in a direction that does not align with this partnership")
• General fit ("we were looking for a profile with deeper experience in enterprise SaaS environments")

What is NOT safe to say in writing:

• Any language that could imply illegal discrimination (age, background, appearance, family status)
• Specific comparative claims ("the other candidate had X years more experience") -- this invites rebuttal and creates legal exposure
• Characterizations of the recipient's work quality as flawed, insufficient, or below standard -- even if true, say "the fit was not right for this role" rather than "your experience level did not meet our requirements"
• Promises about future consideration you cannot keep

For HR-regulated job rejections: Default to: "We have moved forward with a candidate whose background more closely matches the specific needs of this role at this time." Do not specify which requirements were unmet unless HR has explicitly approved the language.

Step 6: Write the Acknowledgment -- Specific, Earned, and Genuine

Every rejection at Tier 2 or above must include one genuine acknowledgment of something specific the recipient did well, submitted well, or demonstrated clearly. This is not flattery -- it is accurate reporting of what was actually strong.

How to extract specifics from the user:

• Ask: "What was genuinely impressive about this candidate/proposal/submission?"
• Ask: "What would you tell a colleague about this person's strengths?"
• Ask: "What made this a hard decision?"

What to avoid:

• "Your qualifications were impressive" -- too vague, reads as filler
• Praising something that contradicts the rejection reason -- if you're rejecting them for lack of enterprise experience, do not praise their "extensive experience"
• Mentioning weaknesses in the acknowledgment section -- even constructive criticism belongs only in a separate feedback offer, not embedded in the rejection letter itself

Strong acknowledgment examples:

• "Your proposal's phased implementation approach was the most clearly structured of those we reviewed, and the team specifically noted the risk mitigation section."
• "Your work sample on the customer journey redesign demonstrated exactly the kind of systems-level thinking we look for."
• "The commercial terms you outlined were competitive and well-constructed."

Step 7: Write the Close -- Only Offer What You Will Actually Deliver

The closing of a rejection letter determines whether the relationship is preserved or damaged. Three closing types exist:

Close Type A -- Permanent, Clean No: For situations where there is genuinely no future opportunity and offering one would be false hope.

• "We wish you every success in your search and appreciate the professionalism you brought to this process."
• Do not offer to "keep them in mind" or "stay in touch" if you will not.

Close Type B -- Genuine Future Pipeline: For candidates, vendors, or partners you would genuinely consider for future opportunities.

• Be specific about what the future opportunity might look like: "We anticipate opening a consumer product design role later this year and would welcome the opportunity to reconnect when that role is posted."
• Offer a specific, time-bounded action: "Would it be alright if I reached out in Q3 when we revisit this?"
• Ask for permission before assuming continued contact is welcome.

Close Type C -- Feedback Offer: For Tier 3 and Tier 4 rejections where the recipient invested significant time and feedback would be genuinely useful.

• Offer a phone call, not written feedback -- written feedback creates a permanent record of characterizations that can be disputed, shared, or used in legal contexts
• Make the offer conditional on their interest: "If a brief call to share observations from the interview process would be helpful, I would be glad to schedule one."
• Only offer if you have the time and intention to actually do it -- an offered feedback call that never materializes is worse than no offer

Step 8: Review for Legal, Tonal, and Relational Risk

Before presenting the draft to the user, run through this checklist:

• Decision appears within the first 2-3 sentences after the greeting
• No language that implies the decision is temporary when it is not
• No comparative language naming or characterizing competing submissions
• No legally sensitive characterizations of qualifications, age, background
• Acknowledgment is specific and accurate -- not generic or contradictory
• Close only offers what the sender will actually follow through on
• Tone matches the relationship stage and industry context
• Length is appropriate to the tier (Tier 1: under 100 words; Tier 2: 100-150 words; Tier 3: 150-250 words; Tier 4: 200-300 words with optional phone call recommendation)
• Letter reads as written by a human, not a template

Output Format

Present the letter with a brief preamble explaining any choices made, then the full letter.

[PREAMBLE -- one or two sentences explaining the tone calibration and any 
choices made, e.g., "I kept the reason general given the early stage of this
application" or "I recommended a feedback call rather than written feedback
given the post-pilot context."]

---

[DELIVERY METHOD NOTE, if relevant: e.g., "Send as an email from the hiring
manager directly, not from a recruiting system, given the final-round context."]

---

Subject: [Role/Proposal/Request Name] -- [Company Name] Update
[Include for email delivery. Subject line should be specific, not "Regarding
Your Application." Specific subject lines signal respect and improve open rates.]

Dear [Full Name / First Name based on existing relationship],

[Opening -- one sentence acknowledging the specific thing they submitted, 
attended, or invested in. Reference the role title, proposal name, or 
interaction by date.]

[Decision statement -- clear, one sentence, within the first two sentences 
after the greeting. No "unfortunately" as the first word.]

[Reason -- 1-2 sentences, calibrated to tier. For Tier 1, this may be omitted. 
For Tier 3, this should be a genuine, honest general explanation that does not
create legal exposure or invite rebuttal.]

[Acknowledgment -- 1-2 sentences referencing something specific and genuine
about the submission, presentation, or candidate. This section is omitted for 
mass/Tier 1 rejections.]

[Constructive close -- one of three types: clean farewell, genuine future 
pipeline with specific details, or feedback call offer with conditional framing.
Never offer more than one future action to avoid ambiguity about what comes next.]

[Sign-off: "Best regards," "Warm regards," or "Sincerely," based on relationship 
warmth -- "Warm regards" for candidates and partners, "Sincerely" for formal 
vendor/government contexts],

[Sender Full Name]
[Sender Title]
[Company Name]
[Phone number, if feedback call was offered]

Rules

1. Deliver the decision within the first two sentences after the greeting, always. Recipients who have invested time in a process deserve clarity immediately. Every sentence before the rejection increases anxiety and erodes trust when the decision finally arrives.

2. Never use "at this time" unless the door is genuinely open within a visible timeframe. This phrase is universally recognized as a false softener. If you use it when the door is actually closed, the recipient will find out and the sender's credibility is damaged permanently. Reserve it for situations where a specific future window exists.

3. Never name or characterize the competing candidate, vendor, or proposal. "We selected a candidate with deeper enterprise experience" is safe. "We selected a candidate with more experience than you" is not. Never reference names, company names, or specific comparative metrics.

4. Never write specific skill-based rejection reasons for job candidates without HR clearance. The risk is not the written reason itself -- it is the inaccuracy of that reason, which can be challenged in an employment dispute. Vague-but-accurate ("not the right fit for this role at this stage") is legally safer than specific-but-potentially-inaccurate ("lacked Python experience").

5. Never offer written feedback for Tier 3 or Tier 4 rejections. Written feedback creates a permanent comparative record. Offer a phone call. If the user insists on written feedback being included, flag this risk explicitly before drafting.

6. Never exceed one page (approximately 300 words) for any rejection letter. Longer letters signal that the sender is overexplaining, apologizing, or covering something. Brevity is a form of respect.

7. Never open with "We regret to inform you" or "It is with regret that..." These phrases are so overused they have become signals of impersonal, template-driven communication. They undermine the entire effort of a warm rejection.

8. Always use the recipient's specific name in the salutation. "Dear Hiring Candidate" or "Dear Applicant" is never acceptable in any tier. Even mass rejections should have the recipient's first name populated via mail merge.

9. Always match the sign-off to the sender's actual relationship with the recipient. A CEO who has never spoken to the candidate should not sign a rejection letter as if they have a personal relationship. The letter should come from the person who actually interacted with the recipient most directly.

10. Always flag to the user if their stated reason contains legally sensitive language before including it in the draft. Phrases like "overqualified" (can imply age discrimination), "not a cultural fit" (can imply discriminatory exclusion), or "we were looking for more energy" (can be read as ageist or ableist) must be surfaced and reworded before inclusion.

11. Never fabricate specifics you were not given. If the user cannot provide a genuine strength to acknowledge, write a Tier 1-style letter without the acknowledgment section rather than inventing praise. Invented specifics can be disproved and damage the sender's credibility.

12. For government procurement and regulated vendor rejections, ask whether a debriefing process is required. Many government procurement frameworks legally require offering a debriefing to unsuccessful bidders. The rejection letter in these contexts is not the end of the process -- it is the beginning of a formal debriefing right.

Edge Cases

Rejecting a Final-Round Candidate Before They Learn They Did Not Get the Job from Another Source

Speed is ethically mandatory. If there is any chance the selected candidate might post on LinkedIn, or that someone inside the organization might mention the hire externally before the rejected candidates are notified, the rejection letter must go out simultaneously with or before the offer acceptance. Delay in this scenario is a reputational hazard for the employer. Recommend the user send the rejection within 24 hours of offer acceptance, not after the selected candidate's start date.

The User Wants to Reject Someone but the Decision Is Not Final

Do not write a rejection letter if the decision is genuinely still open. Instead, write a status update: "We are still in the final stages of our review and expect to have a decision by [specific date]." Writing a rejection that is later reversed is far more damaging to the relationship than a delayed decision. Push back on the user if they are trying to use a rejection letter to manage expectations before a decision is actually made.

Rejecting a Vendor After a Paid Pilot or Paid RFP Process

This is the highest-stakes rejection scenario. The vendor has invested real money, the work product exists and may be disputed, and the relationship may continue in other forms. Handle as follows: (1) recommend the user make a phone call before sending the written rejection, (2) in the letter, acknowledge the completed work by specific deliverable name, (3) do not characterize the quality of the work -- say "the fit with our current direction" not "the output did not meet our expectations," (4) offer a reference or case study acknowledgment if the work genuinely warrants it, and (5) if the rejection may prompt a billing dispute, loop in legal before sending.

The Recipient Is a Current Customer, Partner, or Community Member

When rejecting an application, proposal, or bid from someone with whom you already have an ongoing relationship, the rejection letter must explicitly acknowledge and affirm that relationship. "While we will not be moving forward with this proposal, we value our ongoing partnership with [Company] and look forward to continuing [specific existing engagement]." Failure to do this creates the impression that the entire relationship is being terminated.

Mass Rejection Waves (20+ Candidates at Once)

Never send a truly generic mass rejection. At minimum, the email must be personalized with: (1) the recipient's first name, (2) the exact role title they applied for, and (3) if any phone screen occurred, a reference to that interaction. Use a mail merge system that populates these fields, not a BCC blast. For candidates who were screened by phone, send a manually written Tier 2 letter -- they have earned more than a form letter. Employer brand research consistently shows that rejected candidates' perception of a company is determined almost entirely by the quality of the rejection they received.

The User Wants to Reject Someone Who Has Been Difficult, Aggressive, or Has Made Threats

Do not add emotional language, defensive tone, or additional explanation to a rejection involving a difficult recipient. The correct response is a shorter, more formal letter -- not a longer one. Remove any acknowledgment of strengths (it will be received as sarcastic or false), use formal salutation and sign-off ("Sincerely" not "Warm regards"), and do not offer feedback or future contact. If the recipient has made explicit threats, recommend the user consult HR or legal before sending any written communication.

Internal Proposal Rejection (Employee or Team)

Internal rejections carry unique risks: the rejected party continues to work for the organization, may feel devalued, and the rejection may affect their engagement and retention. Best practices: (1) the rejection should be delivered verbally by the direct manager first, with the written communication serving as a formal follow-up, (2) the written version should acknowledge the effort of the team by name if a group prepared the proposal, (3) offer a specific next step -- a meeting to discuss alternative approaches, a revised scope, or a timeline for resubmission -- rather than a clean close, (4) do not explain the decision in terms of resource competition with other teams, as this breeds internal resentment.

Example

User input: "I need to reject a vendor named Meridian Analytics who submitted a proposal for our customer data platform project. They made it to the final two and we spent about six weeks evaluating them including a three-hour product demo and a technical deep-dive call with their engineers. We went with a different vendor because the other vendor had a native integration with our Salesforce environment that Meridian would have needed custom work to achieve. Meridian's proposal was actually excellent -- their data modeling approach was the best we saw. We'd genuinely consider them for future analytics work. I'm the VP of Technology Partnerships."

AI assistant preamble:

This is a Tier 3 rejection -- a final-round vendor who invested six weeks and two substantial engagements. The letter acknowledges the process depth, gives an honest and legally safe technical reason (integration fit, not capability), specifically names their strongest contribution (data modeling), and opens a genuine future pipeline with specificity. I have not offered written feedback since the vendor could use written characterizations of their work in competitive contexts. I have recommended a phone call precede this letter, which is standard for late-stage vendor rejections of this depth.

Delivery note: Strongly recommend a brief phone call from you to their account lead before this letter lands. The letter can follow the same day as confirmation. A six-week evaluation ending in a written-only notification can feel impersonal and may close the door on the future relationship you want to keep open.

Subject: Customer Data Platform Vendor Selection -- Meridian Analytics

Dear [Account Lead First Name],

Thank you for the depth of engagement your team brought to our customer data platform evaluation over the past six weeks -- particularly the thoroughness of your technical deep-dive session and the quality of the materials your engineering team prepared.

After completing our final evaluation, we have decided to move forward with a different vendor for this engagement. The determining factor was native integration with our Salesforce environment, which was a hard infrastructure requirement for our current architecture. Achieving equivalent functionality with Meridian's platform would have required a custom integration layer that introduced timeline and risk considerations we were not able to absorb in this project cycle.

I want to be direct: this was a genuinely close decision, and Meridian's data modeling architecture was the strongest we reviewed across all submissions. Your proposed approach to customer segment hierarchy and attribution modeling reflected a level of analytical sophistication that set the proposal apart.

We view this as a matter of fit for this specific project, not a reflection of Meridian's platform capabilities. We are already anticipating a standalone analytics modernization initiative in H2, and I would like to reconnect with your team when that scope is defined -- likely in Q3. Would you be open to a brief call in late June to explore whether there might be a fit there?

Thank you again for the professionalism and rigor your team brought to this process.

Sincerely,

[Sender Full Name] VP of Technology Partnerships [Company Name] [Direct phone number]