Documenting Performance So a Termination Holds Up

Why this matters

When a firing gets challenged - an unemployment appeal, a wrongful-termination claim, a lawyer's letter - nobody in the room was there. The only witness that speaks is the file. If the file shows the person knew the standard, knew they were failing it, got a fair chance, and was treated like everyone else, the firing holds. If the file is thin, dated the morning you decided, or full of opinions instead of facts, a fair firing can still lose. This card is about the record, not the conversation: what it has to prove, and how to build it so it survives a stranger reading it cold.

The stranger test

Build every performance record to pass one test: a neutral outsider (an unemployment examiner, an arbitrator, a juror) reads only your file, months after the fact, knowing none of the backstory. Would that person conclude the firing was fair and lawful? Your memory of how bad this employee was does not travel into that room. The file does. Everything below serves that one test.

What a defensible file has to prove

A file that holds up establishes four things, in facts:

• Notice. The person knew the standard. Not "should have known," but was told, and you can point to when. See related: Setting Expectations a Tech Can Actually Be Held To.
• Awareness. The person knew they were falling short. The warnings, coaching, and reviews that put them on notice, each dated.
• Opportunity. They got a real, timed chance to correct, not a window too short to actually change in.
• Consistency. They were held to the same bar as everyone else in the same role.

If any of the four is missing from the paper, that is the hole a challenge drives through. Read your file and ask which of the four it fails to show.

Write it when it happens, not when you need it

Contemporaneous means recorded at the time, and it is the single habit that separates a file that holds from one that looks manufactured. A note dated the day of the incident is evidence. The same note reconstructed the week you decided to fire is worse than nothing, because once one entry looks backfilled, the outsider distrusts all of them.

• Log the fact the day it happens, even two lines: date, what occurred, the effect.
• Do not wait for a "big enough" incident. The pattern is the case, and a pattern only exists if the small entries were captured as they came.
• If a record genuinely has to be written after the fact, date it honestly as written-after and say why. An honest late note beats a disguised one.

Facts an outsider can check, not conclusions they will discount

The outsider cannot verify your opinion and will discount it. They can verify a dated, observable event. So the file records events, not verdicts. "Careless and unreliable" is your conclusion and it proves nothing. "On the 9th, left before the checklist was signed; callback logged the 11th" is a fact the outsider can weigh. The rule: if you could not show the entry to the person and have them agree the event happened, it is not ready for the file. The mechanics of writing one entry live in a sibling card; see related: The Write-Up That Actually Corrects the Problem.

The gaps that sink an otherwise good case

Most files do not fail on the incidents. They fail on the connective tissue.

• A consequence you named but never enforced. If a warning said "next time is a final warning" and the next time came and went with nothing, the file now proves your standards are optional. See related: A Verbal Warning Didn't Stick: Decision Tree.
• Praise that contradicts the discipline. A glowing review, a raise, or a "meets expectations" box checked weeks before the firing hands the challenge its whole argument. Your reviews and your warnings have to tell the same story.
• Selective records. Documenting only the person you want gone, while others do the same thing unpapered, reads as targeting, not performance management. Consistency is proof; inconsistency is a pretext.
• A standard that lives only in your head. A rule enforced but never communicated is a rule the person can honestly say they never knew.

Keep the record, and keep it clean

• Store it where it survives turnover and a lost laptop, separate from daily job files, with access limited to who needs it.
• Keep it after they leave. A claim or an unemployment appeal can arrive well after the last day, so retain performance and termination records for a defined period set with your attorney or HR resource rather than tossing the file when the person goes.
• Facts only, on the page. Frustration, sarcasm, and speculation in a note become exhibits later. Anything you would not want read aloud does not belong in the file.
• Because how a for-cause record must be handled varies by state and situation, confirm your retention and termination process with an employment attorney or your state labor office before you rely on it.

The through-line

You are not writing to remember what happened; you are writing so a stranger who was not there rules it fair. Notice, awareness, opportunity, consistency, captured in dated facts as they happen and kept clean. Build the file that way from the first small entry, and the hardest day stays a business event instead of a legal one.

References

• Society for Human Resource Management (SHRM), documenting performance and progressive discipline
• U.S. Equal Employment Opportunity Commission (EEOC), consistent-treatment and recordkeeping principles
• U.S. Department of Labor and your state labor office, records-retention guidance
• See related: The Write-Up That Actually Corrects the Problem, Progressive Discipline That Is Fair and Defensible, How to Fire an Employee the Right Way