How to Write a Letter of Dismissal: A Manager's Guide

You've been asked to terminate someone, and your first instinct is to search for a template. That's understandable. But if you're looking up how to write a letter of dismissal, you're usually already in the riskiest part of the process.

The hard truth is that the letter itself rarely saves a weak termination. A clean template can't fix missing warnings, inconsistent dates, or a manager who says one thing in the meeting and writes something else in the file. What protects the company, and equally treats the employee fairly, is a process that holds together before, during, and after the letter is issued.

That matters even more in small and midsize companies. You may not have in-house counsel, a full HRBP team, or a formal employee relations function. You still need a dismissal letter that is factual, complete, and defensible. You also need a delivery process that proves the employee received the notice and understood the practical next steps.

Before You Write Legal and Documentation Checks

A manager tells you, “I know this employee needs to go. I just need the letter.” That is the point where HR has to slow the process down.

A dismissal letter records a decision that should already be supported by facts, policy, and approvals. If the file is thin, inconsistent, or missing key dates, the letter becomes evidence against the company instead of evidence for it.

SHRM makes the same point in its termination best practices. The termination review should be documented and the decision finalized before the meeting. It also warns against three patterns that create risk fast: terminating an employee with a documented history of satisfactory performance, relying on subjective judgments with no written support, or making the call based only on conflicting accounts with no corroboration.

Build the file before you build the letter

Start with the record, not the wording.

Pull the documents that show what happened, what standard applied, what the employee was told, and what the company did in response. For a performance termination, that usually means reviews, coaching notes, written expectations, and any performance improvement plan. For misconduct, it may include witness statements, screenshots, attendance logs, investigation notes, or policy excerpts. You also need the core employment documents: offer letter, handbook acknowledgment, compensation terms, and any agreement that affects notice, severance, commissions, confidentiality, or restrictive covenants.

Read the file like an outsider would. Do the dates line up? Did the manager document concerns before recommending termination? Does the record show the employee had a fair chance to correct the issue, if your policy requires that?

If the answer is no, stop and fix the process before anyone drafts the letter.

I have seen managers try to fill gaps with phrases like “ongoing attitude issues” or “not a fit.” Those phrases do not hold up well in a review. Specific facts do. A neutral reviewer should be able to understand the basis for termination without needing the manager in the room to explain what they meant.

Check policy, contract, and legal fit

The next review is less about frustration and more about alignment. The reason, timing, and process have to match the employee's status and the company's own rules.

Check four things before you write:

• Policy alignment Confirm whether your handbook requires progressive discipline, an investigation, a final warning, leadership approval, or HR signoff. If the written policy says one thing and the file shows another, expect that gap to be challenged.
• Contract and pay obligations Review any terms on notice, severance, commissions, bonus treatment, accrued leave, final pay timing, and post-employment restrictions. A dismissal letter should reflect those terms accurately, not summarize them from memory.
• Protected activity or sensitive timing If the employee recently requested leave, raised a complaint, reported harassment, asked for an accommodation, or participated in an investigation, pause and get senior HR or legal review. The facts may still support termination, but the file must show a clear, independent business reason and consistent handling.
• Consistency with comparable cases Compare this situation with similar cases in your organization. If one employee received coaching and another is being terminated for comparable conduct, you need a documented reason for the difference.

Managers new to terminations often underestimate how quickly a routine case can turn into an unfair dismissal risk when the company cannot show consistency, policy compliance, and a supported rationale.

Get a second review before the meeting

No one should draft or deliver a dismissal letter alone if there is any avoidable uncertainty in the file. In a large company, that second review may come from employee relations or counsel. In a small or remote team, it may be the head of HR, an outside advisor, or the next-level leader who was not directly involved in the dispute.

That reviewer should test the case with blunt questions:

• Can we prove the stated reason with documents, not impressions?
• Do the dates, warnings, and policy references match across the file?
• Is this performance, misconduct, redundancy, or another category, and does the paperwork support that category?
• Have payroll, benefits, system access, and company property steps been coordinated with the termination date?
• If this employee disputes the decision tomorrow, will the file read as fair, consistent, and complete?

Many preventable mistakes surface at this stage. The manager may call it a performance issue, but the record reads like misconduct. Payroll may be working from a different end date than the one in the draft letter. A remote employee may need courier instructions for company equipment, yet no one has assigned that task. Those are not minor details. They affect legal exposure, final pay compliance, and basic credibility.

A defensible dismissal letter starts well before the document itself. It starts with a file that can withstand review, a decision that matches policy, and an execution plan that holds together on the day of termination and after.

The Anatomy of a Legally Sound Dismissal Letter

Once the file is ready, the letter itself should be simple. Not casual. Not cold. Simple.

The best dismissal letters follow a clear structure because each part serves an operational purpose. They tell the employee what decision has been made, when it takes effect, why it happened, and what happens next. They also create a written record the company can stand behind later.

Start with the core notice

Open with the employee's identifying details and a direct statement that employment is ending.

“This letter confirms that your employment with [Company] is terminated effective [date].”

That opening matters because ambiguity causes problems fast. A letter that wanders through background before stating the decision invites confusion, especially if the person is upset.

Include:

• Employee identity: full name, job title, and often department
• Date of the letter
• Effective termination date
• Whether the end is immediate or after a notice period

If your organization uses a notice period, make sure the letter reflects exactly how that period is being handled. Don't assume managers and payroll are using the term the same way.

State the reason clearly, but without editorializing

A practical dismissal letter should be built from records, then written in factual, non-emotional language. Guidance summarized by Oyster recommends verifying the termination basis with records such as appraisals, incident chronology, prior warnings, PIPs, witnesses, and policies, then drafting a concise notice that states the employee's identity, effective termination date, and the specific reason for dismissal in factual terms, as described in Oyster's guide to a letter of termination.

That means the reason section should sound like this:

“This decision is based on your failure to meet the performance expectations of your role despite prior coaching and written warning dated [date].”

Or this:

“This decision follows the investigation into the policy violation reviewed with you on [date], including the findings communicated in our meeting.”

Not this:

“You haven't been a good fit for the team.”

And not this:

“We've lost confidence in your judgment.”

The first two examples tie the decision to facts and process. The second two sound subjective, emotional, and hard to defend.

Include the operational details people forget

A dismissal letter is not complete when the reason is written. It is complete when the employee can read it and know exactly what happens next.

Include these items in plain language:

• Final compensation: when final pay will be issued, and whether unused PTO, holiday pay, or severance applies
• Benefits information: what ends, what continues, and where questions should go
• Return of company property: laptop, badge, keys, phone, files, card, or equipment
• Continuing obligations: NDA, confidentiality duties, non-compete, or other signed obligations if applicable
• Contact point: a named HR or company contact for follow-up questions

A common mistake is softening or omitting the reason for termination. That may feel kinder in the moment, but it creates ambiguity later, and the letter can become evidence in a dispute.

End with a formal close

Use a clean sign-off. Don't add unnecessary sentiments that muddy the message.

A strong close might say:

“Please direct any questions regarding final pay, benefits, or return of company property to [name/title/contact].”

That's enough. The purpose of the letter is notice and documentation. The purpose of the meeting is respectful communication. Don't turn either one into a debate.

Tailoring the Letter for Different Dismissal Scenarios

The structure stays stable. The wording changes based on the reason for dismissal.

That's where many managers get into trouble. They use one generic template for every situation, then wonder why the letter feels either too harsh for a layoff or too vague for misconduct. The safest approach is to adjust the emphasis, not invent a new format every time.

Published guidance commonly places termination at the end of a progressive discipline process. KJK's manager guidance says lesser corrective measures should be considered before termination and notes that a progressive discipline policy may include 3 steps: verbal warning, written warning, and final written warning or suspension, with each stage documented in writing, as discussed in KJK's guidance on manager best practices for termination.

Dismissal letter focus by scenario

Scenario Key Focus Recommended Tone Information to Emphasize Poor performance Prior coaching and unmet expectations Direct, measured Warnings, goals, review dates, final pay Gross misconduct Factual findings and policy breach Firm, controlled Incident dates, investigation outcome, immediate logistics Redundancy or layoff Business reason unrelated to conduct Respectful, empathetic Role elimination, transition support, pay and benefits Failed probation Fit against role standards during probation period Clear, brief Review discussions, probation terms, effective date

Poor performance

Performance dismissals usually need the most documentation because they're often built on a pattern, not a single event.

Good phrasing

“Your employment is terminated effective [date] due to continued failure to meet the performance requirements of your role. This decision follows prior coaching discussions and written warning dated [date], during which the required improvements were communicated.”

Bad phrasing

“You just haven't improved enough and the team needs someone stronger.”

Why the first works: it points to documented expectations and prior steps. Why the second fails: it sounds personal and subjective.

If the employee was on a PIP or formal improvement plan, reference the process without rewriting the entire file. The letter should summarize, not litigate.

Gross misconduct

Misconduct letters should be more precise and less expansive. Managers often make one of two mistakes here. They either write almost nothing because they're nervous, or they include every rumor, quote, and witness reaction they can remember.

Good phrasing

“Your employment is terminated effective immediately following the investigation into the incident on [date]. The company concluded that your conduct violated [policy name], as discussed with you in the meeting on [date].”

Bad phrasing

“Everyone agreed your behavior was threatening and unprofessional, and several people said they no longer felt comfortable around you.”

The safe version states the finding and ties it to policy. The risky version overstates, speculates, and drags witness sentiment into the letter. That may create more issues than it solves.

Redundancy or layoff

This scenario calls for a different tone because the dismissal isn't tied to wrongdoing or poor performance.

Good phrasing

“We regret to inform you that your position is being eliminated effective [date] due to business restructuring. This decision is not based on your conduct or performance.”

Bad phrasing

“We're letting you go because business has been slow and we have to make cuts somewhere.”

The first version is respectful and clear. The second sounds casual and careless. Even when the underlying reason is straightforward, wording still matters.

Use this type of letter to emphasize practical next steps, transition timing, property return, and any severance or benefits information that applies.

Failed probationary period

Probation dismissals should still be handled carefully. “Probation” doesn't mean “no process” or “say whatever you want.”

Good phrasing

“During your probationary period, we reviewed your performance against the requirements of the role. Based on those reviews, we've decided to end your employment effective [date].”

Bad phrasing

“It's obvious this role isn't for you.”

The better version keeps the focus on assessed role requirements. The weaker version sounds dismissive and personal.

Concise doesn't mean vague. The letter should identify the basis for dismissal clearly enough that the employee understands the reason, but not so expansively that you create new inconsistencies.

Best Practices for Delivering the Letter

A well-drafted letter can still create risk if the meeting is sloppy. Delivery matters. Timing matters. Proof of service matters.

That's especially true for remote teams, field staff, and small companies where a manager might be tempted to send a PDF by email and call it done. Existing guidance often focuses on what the letter says. The bigger operational issue is whether you can prove who received it, when they received it, and what accompanying rights or instructions were communicated.

UC Berkeley's sample dismissal letter includes a proof-of-service form and recommends appeal-rights language. Related UCOP guidance notes that a dismissal letter follows an Intent to Dismiss only after the appeal period passes and that, if the employee is union-represented, the intent notice must also be sent to the union, as reflected in UC Berkeley's sample letter of dismissal process.

Use a meeting checklist, not improvisation

Go into the meeting with a script and roles assigned.

• Choose a controlled setting: Use a private, neutral room for in-person meetings. For remote terminations, use a secure video meeting rather than delivering the news only by email.
• Have the right people present: Usually the manager and HR. If your organization uses a witness, confirm who that is in advance.
• State the decision early: Don't spend ten minutes building up to it. Tell the employee the decision, the effective date, and that you have a letter explaining the details.
• Keep the conversation brief: Answer practical questions. Don't argue the merits of the decision in the meeting.
• Coordinate access and logistics: Know when accounts are disabled, who collects equipment, and how final pay details will be handled.

If your company has a broader offboarding checklist, the dismissal meeting should line up with it exactly.

Here's a useful visual summary to keep handy before the meeting.

Handle remote delivery carefully

Remote dismissals create notice problems fast. An employee may say they never received the attachment, didn't see the email until later, or didn't understand whether the termination was effective immediately.

Use a tighter process:

• Deliver the letter during the video meeting: Tell the employee you are sending it while you are speaking.
• Send it to the correct personal or confirmed email address: Don't rely on a shared mailbox or an address the employee may lose access to immediately.
• Request acknowledgment of receipt: Keep the request simple and factual.
• Document the delivery method and time: Note who attended, when the letter was sent, and how receipt was confirmed.
• Mail a hard copy when appropriate: For higher-risk situations, a physical copy can strengthen your proof of delivery record.

The question isn't only “what should the letter say?” It's also “how will we prove the employee received the exact notice we intended to deliver?”

Keep your spoken message consistent with the letter

Managers create avoidable risk when they freelance in the room. They apologize by contradicting the written reason. They hint that the decision might change. They offer side promises that aren't documented.

Use plain, stable language:

• “The decision has been made.”
• “Your employment ends effective [date].”
• “The letter explains the reason and next steps.”
• “Questions about final pay and benefits should go to [name].”

Avoid lines like “personally, I disagreed with this” or “if it were up to me, this wouldn't be happening.” Those comments may feel compassionate, but they undermine the company's position immediately.

Common Pitfalls and How to Avoid Them

Most bad dismissal letters aren't malicious. They're written by managers trying to sound kind, informal, or thorough. That impulse causes trouble.

Weightmans notes a recurring problem in sensitive or contested dismissals: many letters fail because they don't clearly state the factual basis and findings tied to misconduct, while also raising the question of how much detail is enough versus too much, as discussed in Weightmans' article on writing a dismissal letter.

Mistake and correction

Mistake: using soft, vague language “We don't think this is working out.”

Correction: State the actual reason in factual terms tied to the process or policy.

Vagueness feels gentler in the moment, but it creates ambiguity in the file. A dismissal letter should be respectful, not blurry.

Mistake: over-explaining the evidence Managers sometimes pour witness statements, speculation, or emotional detail into the letter.

Correction: Summarize the factual basis and reference prior meetings, findings, or policy provisions instead of restating the entire case.

The risky instinct to personalize

Mistake: turning a business document into personal commentary “You've disappointed the team,” or “we had hoped you'd mature into the role.”

Correction: Remove judgments, assumptions, and character assessments.

The letter should describe conduct, performance, findings, and next steps. It should not diagnose motive or personality.

Inconsistency is often worse than bluntness

A manager may write “position eliminated” in the letter, then tell the employee verbally that the actual issue was poor performance. Or the letter says “effective today,” while the benefits notice uses a different date.

That inconsistency can do more damage than a direct but well-supported letter.

Use this quick red-flag screen before issuing any draft:

• Check labels: Is this performance, misconduct, redundancy, or probation failure?
• Check dates: Do the letter, payroll timing, access changes, and meeting plan match?
• Check promises: Did anyone offer severance, references, or extra time that isn't reflected in writing?
• Check tone: Is every sentence factual, necessary, and supportable?

If a sentence makes the manager feel better but doesn't improve clarity or compliance, cut it.

Your Dismissal Letter Final Checklist

Use this before the meeting and again before sending the letter.

• Verify legal compliance for the employee's location, status, and any protected or recent complaint issues.
• Confirm policy adherence so the termination process matches your handbook, discipline policy, and approval path.
• Match the reason to the file and make sure the stated basis is supported by documented facts.
• Specify the effective date clearly, including whether termination is immediate or after notice.
• Remove subjective language such as “bad fit,” “poor attitude,” or personal judgments.
• Outline final pay and benefits in plain language, including timing and who handles questions.
• List return-of-property instructions with items, deadlines, and the responsible contact person.
• Reference ongoing obligations such as confidentiality or other signed post-employment duties, if applicable.
• Plan delivery carefully by confirming attendees, meeting format, witness coverage, and proof of receipt.
• Proofread every detail including names, dates, policy references, sign-off, and attachments.

A dismissal letter works when it reflects a disciplined process. It fails when it tries to compensate for the lack of one.

If your team is growing and you need cleaner HR records before difficult moments arise, Redstone HR helps small and midsize teams centralize leave, approvals, and policy tracking in one audit-ready system. That kind of operational discipline makes every HR process easier, including the ones managers hope they won't have to handle.