You get:
- angry language that burns bridges and invites lawsuits
- vague reasons that confuse the recipient
- no transition plan (so work stops abruptly)
- unintentional admissions of liability
- no documentation of what was returned or paid
But a termination letter is not a breakup text.
It is a professional offboarding document.
- Reason must be factual, not emotional
- Effective date must be clear to avoid confusion
- Transition responsibilities protect both parties
- Neutral closing preserves optional future relationships
- A “never say this” warning prevents costly mistakes
Without professional drafting, termination creates unnecessary risk.
This framework forces AI to think like an HR professional who ends relationships cleanly.
Assume the role of a professional writing specialist for offboarding, termination, and transition communications. Your task is to draft a termination letter that ends a professional relationship cleanly and neutrally. Generate TWO VERSIONS: STANDARD VERSION (professional, neutral, detailed) SHORT VERSION (1-2 sentences for low-stakes, good-faith separations) EACH VERSION MUST INCLUDE: 1. REASON FOR TERMINATION (factual, non-accusatory) Options: contract period ends, budget reduction, performance concerns (with documentation note), mutual agreement, breach (specify) 2. EFFECTIVE DATE OF TERMINATION 3. TRANSITION RESPONSIBILITIES (what they need to do) - Return property - Complete handoff - Submit final invoice 4. YOUR RESPONSIBILITIES (what you will do) - Final payment - Access removal - Reference policy 5. NEUTRAL CLOSING - Professional, preserves relationship if possible PLUS: 6. "NEVER SAY THIS" ADVISORY - One phrase to delete if it appears in your draft INPUTS: Relationship Ending With: [VENDOR / EMPLOYEE / CONTRACTOR / CLIENT / OTHER] Reason for Termination: [CONTRACT ENDED / BUDGET REDUCTION / PERFORMANCE CONCERNS / MUTUAL AGREEMENT / BREACH / OTHER] Effective Date: [INSERT DATE] Outstanding Obligations (what they owe you, or you owe them): [DESCRIBE] Do You Want a Future Relationship Possible?: [YES / NO / INDIFFERENT] RULES: - Reason must be factual, not emotional (no "we're frustrated") - If performance is the reason, state "documentation available upon request" (don't detail in the letter) - Effective date must be unambiguous (e.g., "Your last day of work is X") - Transition responsibilities must be specific and time-bound - The "never say this" advisory must be a direct quote of a common harmful phrase
- For employee termination, always involve HR and legal counsel before sending anything.
- The short version is only for good-faith, low-stakes endings (e.g., contract naturally expired).
- Keep a copy of the letter and proof of delivery in your records.
- The “never say this” advisory is your most important takeaway — believe it.
- For performance-based terminations, have documentation ready before sending the letter.
Relationship Ending With: Vendor (IT support contractor)
Reason for Termination: Contract period ends (30-day rolling contract, we are choosing not to renew)
Effective Date: June 30, 2026
Outstanding Obligations: Vendor owes final invoice; we owe payment for May services (~$3,500)
Do You Want a Future Relationship Possible?: Yes (they’re fine, we just need a different skill set)
This framework improves outcomes by forcing:
- factual, non-accusatory reasons
- clear effective dates
- specific transition responsibilities
- factual, non-accusatory reasons
- clear effective dates
- specific transition responsibilities
- neutral closings that preserve relationships
- “never say this” warnings for common mistakes
This framework improves outcomes by forcing:
Great termination letters don’t burn bridges — they build off-ramps.
Build Better AI Systems
Subscribe for advanced prompt engineering, AI legal tools, termination letter frameworks, and practical strategies for professionals and business owners.