Employee Termination Checklist Template
Four documents and three sheets that compute two gaps in days before a termination decision is executed, not after.
Free download · No account needed
Documentation Completeness Check
A 338-day-old warning, and a 9-day gap to a protected activity
Marloe Logistics, fictional 240-person warehouse software company. Two cases run the same week in August 2026.
| Employee | Stated reason | Staleness gap | Proximity gap | Verdict |
|---|---|---|---|---|
| Grant Feola | Safety violations | 338 days | Not applicable | Flagged, then cleared |
| Ines Castellanos | Role eliminated | Not applicable | 9 days | Flagged, paused |
Grant's flag closed the same week once a fresh, dated incident replaced the stale warning, and discharge proceeded. Ines's flag routed straight to legal review, because no document behind her stated reason predates the accommodation request.
A termination checklist usually asks yes-or-no questions about documentation and stops there: is there a written warning on file. That question misses what actually decides a case. A warning that is real but 338 days old, with two positive check-ins logged since, is a materially weaker file than a 338-day-old warning with nothing contradicting it, even though both answer the yes-or-no question the same way. And a decision that lands nine days after an employee's accommodation request is a different case than one landing nine months after, regardless of how solid the paperwork otherwise looks.
The Documentation Completeness Check computes two gaps in days before a decision is treated as final: staleness in the documents behind the stated reason, and proximity to the most recent protected activity on file. Clark County School District v. Breeden held that a temporal-proximity argument needs a gap "very close" in time, naming three- and four-month gaps too long alone, and a 20-month gap no evidence of causality at all. A nine-day gap sits well inside the range that counts, before either decision was communicated.
At Marloe Logistics, a fictional 240-person warehouse software company, Grant Feola's file held a 338-day-old warning with two positive check-ins logged since. Flagged, then cleared the same week once a fresh, dated incident replaced it, with discharge following three days later. Ines Castellanos requested a medical accommodation on 3 August 2026; the memo naming her role for elimination is dated five days after that request, and her termination was scheduled nine days after it. Flagged, paused, and routed to legal review, since no document supporting the stated reason predates the request.
What is in the pack
Decision Memo
States the stated reason and both Documentation Completeness Check results, even the one marked not applicable, plus what closed a flag or why it is paused. An employee relations case keeps the same standing record for a pattern instead of one incident.
Separation Script
What to actually say in the room: the decision, the effective date, and pay and benefits logistics, kept to one short exchange so nothing said in the moment reopens a question the review process already closed.
Separation Agreement Notes
What a release can and cannot waive, including that wages already earned stay owed whether or not it is signed, the same fact a signed handbook policy states up front rather than leaving it to be inferred at exit.
Communication Plan
What the departing employee's immediate team is told, when, and by whom, kept to the operational facts: the role is open, who covers what, and where questions go, nothing about the reason itself.
Documentation Completeness Check
One row per case with both gaps stated in days, staleness and proximity, plus a verdict: clear, or flagged with the specific gap named, computed before the decision is treated as final rather than defended after.
Final Pay Calculation
The exact deadline and wage components for the employee's actual work state, not a company-wide assumption: California requires payment immediately, Texas allows six calendar days, each checked against its own rule rather than a policy written for one state.
Task Checklist
One task per row with an owner and a trigger, from confirming the check has cleared through the final handoff to the employee's team, the same owner-by-task discipline a substantiated investigation's outcome memo hands off once a finding is closed.
How it works
- 1
Send the case and everything dated behind it
The stated reason, the most recent document supporting it and its date, anything logged about the employee since, and any protected activity on file in roughly the past year.
- 2
Get both gaps computed, not assumed
Staleness in days from the last supporting document to the review date, proximity in days from the most recent protected activity to the decision, and whether either document predates the other.
- 3
A flagged gap gets fixed or routed, never skipped
A stale file gets a fresh, dated entry before the decision proceeds; a short proximity gap with no predating document routes to legal review before the meeting is scheduled.
- 4
Final pay lands on the deadline that actually applies
The specific date and wage components for the employee's real work state, plus what a missed deadline would have cost, computed once the case is clear to proceed.
Frequently asked questions
Is this template free?
Yes. The whole pack, the Decision Memo, Separation Script, Separation Agreement Notes and Communication Plan, plus all three sheets, downloads as real files with no signup. Edit with AI is a separate, optional path that creates a free account and installs the same pack as a private workspace.
How is this different from a normal termination checklist?
A normal checklist asks whether a written warning exists and stops. This one computes how old that warning is and what has happened since, plus how close the decision falls to the employee's most recent protected activity, flagging either gap before the decision is communicated rather than after.
What counts as a protected activity for the proximity check?
A leave or accommodation request, a discrimination or harassment complaint, and participation in someone else's complaint or investigation, each dated. The check counts days from the most recent one on file to the date the decision is communicated or scheduled, then checks whether any supporting document predates it.
Does a stale warning always block a termination?
No. Staleness is a flag to fix, not an automatic denial. Grant Feola's 338-day-old warning was flagged, then cleared the same week once a fresh, dated incident replaced it as the basis for the decision. A role-elimination reason skips staleness entirely, since it carries no conduct document to go stale.
How does the Final Pay Calculation pick the right deadline?
From the employee's actual work state, not the company's home state. California requires payment immediately at discharge, Texas allows six calendar days, and Ohio folds final pay into the ordinary semimonthly payday with no acceleration. The sheet computes the specific date and the wage components for whichever rule applies.
What format are the downloaded files?
Word documents for the Decision Memo, Separation Script, Separation Agreement Notes and Communication Plan, and CSV spreadsheets for the Documentation Completeness Check, Final Pay Calculation and Task Checklist. All open natively in Word, Google Docs, Excel or Sheets, and recompute cleanly against an updated case export.
Find out whether this case is clear to proceed
Send the stated reason, the documents behind it, and any protected activity on file. What comes back is both gaps computed in days, a clear verdict, and the final pay deadline for the employee's actual work state.
Run my completeness check