The paper trail that starts early

What a performance plan usually signals

There are three honest possibilities, and they are not equally likely.

Genuine remediation. Real, specific, achievable targets, a manager investing time, and a path back. These exist. You can usually tell because the targets are things you could actually hit and someone is helping you hit them.

Documentation for a decision already made. The targets are vague, or measurable but not achievable in the window, or dependent on people who are not cooperating. The plan’s function is to produce a file.

Budget wearing a performance mask. A reduction in force is coming and performance-based exits avoid the notice obligations and optics of a layoff.

You usually cannot tell which one you are in from the inside, and spending energy diagnosing it is less useful than preparing for all three. The preparation is identical.

The calm written response

This is the single most useful thing to do, and most people skip it because it feels confrontational. It is a record.

Thank you for the plan. I want to confirm I have understood it correctly. My understanding is that success means [restate each target in measurable terms]. Two points of clarification: [the factual correction], and [the dependency or resource question]. I have attached a short summary of my current projects and recent outcomes for the file. I’m committed to working through this and would like to meet weekly to track progress.

That paragraph is cooperative, professional and useful if things go well. It is also a dated, contemporaneous, non-hostile record if they do not.

The part people regret skipping

Request your personnel file while you still work there. Under Labor Code 1198.5 you can inspect and receive a copy, and the employer has 30 calendar days to comply. Reading your own file tells you what is actually in it, which is frequently different from what you assume.

Write down the sequence. This is dates, not a grievance. When did you raise a concern, report a problem, request a leave, disclose a condition, or file a complaint. When did the documentation begin. If those two things are close together, that is a fact worth having written down contemporaneously, and it may matter later. If they are far apart, you have lost nothing.

And the thing not to do

Do not start forwarding company documents to your personal email as insurance. It feels protective and it is the most common unforced error in this entire process. Taking confidential or proprietary material can create a separate legal problem that can outweigh everything else, and it can hand the employer a clean reason that has nothing to do with the original dispute. See What you may keep for the line between your records and their records.

The ideal

In the ideal process, documentation is contemporaneous and shared as it is created. Feedback arrives when the work happens, concerns are specific enough to answer, a performance plan states what good looks like and what support exists, and nothing in the file is a surprise at the exit meeting. A genuine record protects a fair employer as much as a worker, which is why employer guides recommend it. The ideal is not less documentation. It is documentation the worker saw at the time.

Why it works

A record built over months defeats a memory assembled in a week. Galanter (1974) identified the repeat player’s advantages as including superior access to institutional facilities and expertise in building a file that fits the rules of the forum. The employer writes the reviews, sets the plan metrics, and keeps the system the records live in. The worker’s evidence is recollection, plus whatever they happened to save. That is why contemporaneous notes of your own, dated and factual, matter out of proportion to the five minutes they take.

What employer-side guides say

The employer side states the purpose in plain words. Thomson Reuters’ Practical Law guidance for employers, “Employee termination: how to reduce potential legal risks,” instructs businesses to document performance inadequacies in reviews, put discipline in writing, and use performance improvement plans, and says: “Nothing beats a paper trail.” It explains that documenting concerns dramatically improves the odds of showing legal reasons for a dismissal, and that inadequate documentation creates suspicion an illegal practice was the real basis. Documentation is recommended as litigation preparation. Read your own file with that sentence in mind.

The plan built to survive a lawsuit

There is a further refinement worth naming, because you can learn to spot it. The ideal is a plan that changes or measures something real: specific gaps, support that actually arrives, targets a person could reach. The deviation is a plan written to survive a lawsuit rather than to improve performance. Its tell is stability. Pay, title, core duties and advancement prospects all stay exactly as they were, so the plan itself cannot be characterised as a punishment, while the file it generates becomes the employer’s answer later.

The First Circuit confronted a version of this in Walsh v. HNTB Corp., 169 F.4th 330 (1st Cir. 2026). Read it with its limit, because the limit is the point: the court rejected any automatic rule in either direction and treated whether a performance plan is an adverse action as a fact-specific question. On the facts before it, where the plan changed no duties, title, compensation or advancement prospects, it was not adverse. The case does not hold that a plan can never be an adverse action, and it should not be quoted to you, or by you, as if it did. What it tells a reader is narrower and more useful: a plan engineered to change nothing except the record is the hardest kind to challenge as an act in itself, which is precisely why the record you build alongside it matters. (The Supreme Court’s decision in Muldrow v. City of St. Louis, 601 U.S. 346 (2024), which lowered the harm threshold for Title VII transfer claims, has a similar limit. It did not displace the stricter standard that governs retaliation claims.)

When the reason starts to move

The counterpart to a paper trail is your own note of what you were told, and it matters most when the telling changes. Write down the reason given for any major decision about you: the exact words, the date, and who said them. If the reason offered at the exit meeting is a restructure, the reason offered to an agency is performance, and the reason offered later still is conduct, the movement itself is evidence. California law recognises the general principle that inconsistent or shifting explanations can support an inference that the stated reason is not the real one. The framework case is Guz v. Bechtel National, Inc., 24 Cal.4th 317 (2000), which sets out the employer’s burden to produce a legitimate, nondiscriminatory reason once a worker has made an initial showing. Guz is that burden case, not a one-line holding about shifting stories, and this site cites it for the framework rather than as a slogan. The practical point needs no citation at all: reasons that are written down when they are given cannot quietly become different reasons later.