Disabled Employees & Accommodation

Fired after disclosing a disability: the “sudden performance problem” pattern

By Bruce Weisenberg · Published July 31, 2026 · Last reviewed July 31, 2026 · 8 min read

It is one of the most familiar stories in California employment law. Years of solid reviews, raises, maybe a promotion. Then something changes — a diagnosis gets disclosed, a doctor's note arrives with restrictions, a leave request goes in — and within weeks, the same employee has become a "performance problem." A first-ever write-up. A performance improvement plan. Standards no one mentioned before, applied with sudden precision. There is a name for this: papering the file. Nobody ever writes down "we're firing her because of the disability." They write down "missed deadlines" and "communication issues," dated after the disclosure. California courts know how to read the dates.

The pattern has a shape

It rarely announces itself. A review cycle turns critical after years of "meets" and "exceeds." A manager suddenly documents every interaction. Old work gets re-examined and re-scored. A performance improvement plan arrives with goals that keep moving, or that no one else in the role is held to. Duties get quietly reassigned "to lighten your load." Meetings you used to be in happen without you. Each item defensible alone; together, a file being built. The questions that expose it are the ones these cases always turn on: who knew about the condition, how did they know, and when did they know? Those are the big things. Line those answers up against the dates on the paper, and the file often tells on itself — the building started when the employer learned.

The sequence is evidence

California courts have said so directly. In Lin v. Kaiser Foundation Hospitals (2023), the employer's story was clean: it had decided to cut Lin's position before it knew of her disability — a layoff already planned, nothing to see. That is the defense in nearly every one of these cases: "the decision predated the disclosure." The Court of Appeal looked at the paper and reinstated her case. The layoff list had been provisional, and it kept changing. The negative assessments of her work appeared after her disability became apparent. A jury could infer from that sequence that the disability was a substantial motivating reason for the decision. Two points inside that holding matter to anyone living this pattern. First, "the decision was already made" is no shield when the decision was still soft at the time of disclosure. Second, the disability does not have to be the only reason. Under FEHA it need only be a substantial motivating reason — so a real performance concern and unlawful discrimination can coexist, and the case still stands.

"We're just worried about you"

Sometimes the pattern wears kindness. Duties pulled, hours cut, a forced leave of absence — framed as concern for your wellbeing or safety. California law is blunt about this: good intentions do not make it lawful. In Wallace v. County of Stanislaus (2016), a sheriff's department removed a deputy from his position based on a sincere but mistaken belief that his condition made the work unsafe. No hostility anywhere in the record — pure concern. Still unlawful, because acting on the condition is the violation, whatever the motive behind it. And in Zamora v. Security Industry Specialists (2021), an employee with a knee injury was let go rather than considered for work he could do within his restrictions. The Court of Appeal reinstated his claims, finding real evidence of pretext — signs the stated reason was not the real one. Concern that ends your paycheck is not a defense. It is often the case itself.

When the problems really did come first

Now the honest pricing, because none of these cases is a slam dunk, and one question decides many of them: which came first. If the performance problems were genuinely raised and documented before the disclosure, timing will not rescue the claim. Arteaga v. Brink's (2008) is the cautionary tale. An armored-car employee was under investigation for cash shortages. Only after the investigation was underway did he disclose symptoms and file a workers' compensation claim. He was terminated days later — and the court affirmed judgment for the employer. Close timing can get a case started, but it does not create a triable issue of pretext where the employer's concerns came before the protected activity and the discharge rested on them. The court added a warning worth hearing: the law does not let an employee who senses the end coming raise an old condition as a shield against discipline already in motion.

That does not make such cases hopeless. It means the order of events is everything, and it must be faced squarely. Which came first — the documented concerns, or the disclosure? The personnel file will answer that, one way or the other.

What makes these cases — and what breaks them

Beyond raw timing, a familiar set of facts separates the strong cases from the weak ones. Shifting explanations — a reason that changes between the firing meeting, the unemployment filing, and the lawsuit. Breaks from the employer's own playbook — the progressive-discipline steps everyone else gets, skipped for you. Comparators — colleagues with the same shortcomings and no PIP. The reviewer swap — the manager who rated you highly replaced by one who did not, right around the disclosure. And the Lin fact: a decision described as final that the documents show was still moving when the employer learned of the condition. Notice what is not on the list: a confession. There isn't going to be one — remember, they never write it down. Together, these facts let a jury read between the lines, which is exactly what juries are allowed to do.

Save the reviews while your login still works

• Save your old performance reviews now. Access to the HR system typically ends the day employment does. The before-and-after contrast — years of good reviews, then the turn — is often the spine of the case, and you want your own copies.
• Write the timeline while it's fresh. The date you disclosed, to whom, in what words — and the date of the first write-up, the PIP, the pulled duties. Precision here is worth more than outrage anywhere else.
• Signing a PIP is ordinarily treated as acknowledging receipt, not agreement. If you disagree with its contents, say so in writing, briefly and factually — and the work done during the PIP period becomes part of the record.
• Don't quit to escape it. Resigning mid-PIP usually trades real claims for relief that lasts a week. An outside read at that point costs nothing and forecloses nothing.
• Mixed timelines are common. Criticism that came before a disclosure does not automatically end the analysis — under Lin, what happens after the employer learns can carry weight of its own. What matters is the full sequence, laid out accurately.

The worst part of this pattern is the gaslighting built into it: you go to HR with years of good reviews behind you, and they tell you what reality is — when you're the one living it. The answer is the record. Years of reviews do not lie about who you were before the employer learned — and in California, the courts know how to read the difference.

Common questions

Bruce Weisenberg represents employees — only employees — across California (State Bar No. 260521). More than seventeen years in employment law, on his own since 2014, working on contingency. Read about Bruce →  ·  Tell me what happened →