Fired right after you spoke up: how the real reason gets proven
Key takeaways
- No case requires a confession. Retaliation is proven by showing the stated reason doesn't hold — through inconsistencies, contradictions, and the employer's own records (Guz, 2000).
- Reasons that move are evidence. An explanation that shifts between the firing meeting, the unemployment response, and litigation is itself proof of pretext — proof the stated reason isn't the real one.
- Your personnel file is a statutory right: California employers must let you inspect and copy it within 30 days of a written request — including after termination (Lab. Code § 1198.5).
- Missing paper cuts against the employer too: a serious performance problem that left no records supports the inference that the reason was built afterward.
- You don't need the smoking gun to start. You need the sequence and the snag; litigation's discovery tools are built to extract the rest.
The stated reason will be tidy. "Performance." "Restructuring." "Not the right fit." It arrives in a short meeting with HR present, phrased to be repeatable — while the real sequence started weeks earlier, with a report about the billing practice, or the harassment, or the missing overtime. Nobody ever writes down "we're firing you in retaliation for your complaint." Retaliation cases get won anyway, because the gap between the tidy reason and the actual timeline is where these cases are decided, and the tools for prying it open are more concrete than most people think.
Who knew, how did they know, and when did they know
No case requires a confession. Retaliation is proven by circumstances, and the law is explicit that circumstances are enough: the protected act, the adverse action — the firing, the demotion, the cut hours — and evidence connecting them. Three questions organize almost everything: who knew about your complaint, how did they know, and when did they know? Those are the big things, because in most of these cases there's a point where things went from fine to totally off the rails — and the case is about showing that point coincides with the complaint. Which statute governs, and who has to prove how much, is its own subject, covered by the retaliation guides on this site (what counts as protected, what timing does, which law applies). This guide is about the narrower, more practical question: how the stated reason gets taken apart.
Reasons that move are evidence
The California Supreme Court said it in Guz v. Bechtel (2000): a stated reason fails when it is unworthy of credence — false, inconsistent with itself, or contradicted by the employer's own conduct. The most reliable tell is movement. "Performance," in the room. "Position eliminated," in the response to your unemployment claim. "Restructuring," to the Civil Rights Department. A fourth version at deposition. Each version is recorded somewhere, and courts treat the drift itself as evidence that none of the versions is the real one. The classic test looks for weaknesses, implausibilities, inconsistencies, and contradictions in the stated reasons — an employer that cannot keep its story still supplies all four. This is why the early documents matter so much. The reason stated first, before anyone was thinking about litigation, becomes the fixed point every later version is measured against.
The file you can demand by statute
California hands you a tool most people never use. Under Labor Code section 1198.5, once you make a written request, your employer must let you inspect and copy your personnel file within 30 days — and the right belongs to former employees, not just current ones. Payroll records carry their own, faster deadline. What arrives is a time capsule: the reviews as they actually read, the write-ups that exist and the ones that don't, and — often the most telling part — what entered the file after you spoke up. There's a name for that: papering the file. A "longstanding performance problem" that generated no paper until the week after your complaint is not a longstanding performance problem. It is a story under construction, and the file's own dates say so. The request costs a stamp, it works after you've been fired, and it routinely turns the first conversation with a lawyer from guessing into reading.
Their own playbook, applied to everyone but you
Two comparisons do steady work in these cases. The first is to other people: colleagues with the same shortcomings — the missed target, the late reports, the blunt email — who got coaching or nothing, while you got fired. The second is to the employer's own rules: the progressive-discipline policy in the handbook, with its warnings and improvement periods, applied to everyone in the building except the person who complained. In Guz itself, part of the fight was over a company that allegedly used a "restructuring" to remove people without ever running the discipline process its own policies promised. When an employer skips its own steps, the skipped steps become the question it has to answer.
What nobody wrote down cuts the same way
Remember: they never write down the real reason. Some employers take that logic a step further and assume the safest stated reason is an undocumented one — nothing on paper, nothing to contradict. The law runs the other way. Claim a problem bad enough to fire over, produce no paper from the time it supposedly happened, and the absence itself supports the inference that the reason was built afterward. Real performance problems leave traces — emails, review comments, meeting notes — as a byproduct of being managed. A grave problem that left no trace, in a company that documents everything else, asks a jury to believe the one silent exception happened to involve the person who spoke up.
What discovery does to a tidy story
The employee's half of the evidence is thin by design: the timeline, the complaint, the firing. That is the half a case starts with, not the half it ends with. Once a claim is filed, discovery — the formal process for forcing the other side to turn over evidence — reaches the employer's paper: the messages among decisionmakers in the days around your complaint, the draft versions of the "restructuring" list, the calibration notes, the dates on which the file grew. All of it discoverable. All of it fair game. That machinery exists precisely because proof of motive usually lives in the employer's systems, not the employee's memory. So the question at the start is never "can I prove everything today?" It is whether the sequence and the paper you can reach — your timeline, your complaint with its date, the personnel file, the unemployment response — make the stated reason worth testing.
Assembling your half
The materials worth gathering are few and specific. A written timeline, with dates: the protected act, who received it, each change afterward — who knew, how, and when, in your own document. The complaint itself, or the email that put it in writing. The personnel file, requested under section 1198.5. The employer's response to your unemployment claim, kept intact — it is often the first version of the story, locked in early. Your past reviews, copied before access closed or recovered through the file request. And any separation paperwork, unsigned, with its deadline noted — the release it contains is the employer's attempt to buy the very claims this page describes, a subject with its own guide.
Common questions
My reviews were strong for years and now they say I was fired for performance. How is that disproven?
Through the record: your actual reviews (a personnel-file request recovers them), the lack of paper from when the problem supposedly happened, colleagues treated differently for the same conduct, handbook discipline steps that were skipped, and any drift in the stated reason over time (Guz, 2000). Long good records don't disprove a sudden real problem — but they force the employer to explain why the problem surfaced only after you spoke up.
How do I get my personnel file?
Send a written request — email works — asking to inspect and receive a copy of your personnel records under Labor Code section 1198.5. The employer has 30 days, the right survives termination, and you can request payroll records alongside. Keep the request and the response — how fast and how complete the answer is tells you something too.
The company told the unemployment office something different from what they told me. Does that matter?
A great deal. Shifting explanations are among the most reliable signs of pretext. Each version is recorded, and the differences between the firing meeting, the EDD response, and later statements become evidence that the stated reason isn't the real one. Keep every document from the unemployment process.
I don't have proof of why they really did it. Is it too early to talk to a lawyer?
No. You're not expected to hold the proof — motive evidence lives in the employer's records, and discovery exists to reach it. What matters at the start is the sequence: a protected act, an adverse action like a firing or demotion, and facts that make the stated reason worth testing. That's a conversation, not a burden of proof.
I already signed the severance agreement. Is everything gone?
Not automatically. Releases are generally binding. But agreements have to follow the laws that govern them, some rights can't be waived, and age-related releases carry a revocation window — a period to take back your signature. What was signed, when, and on what terms deserves a careful read before you conclude anything.
Article history
July 31, 2026 — Published and reviewed by Bruce Weisenberg.