Retaliation & Whistleblowing

How soon is too soon? Timing and California's 90-day retaliation presumption

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

You reported something — wage theft, harassment, an illegal practice — and within weeks the write-ups started, or the schedule shrank, or the job ended. The first question in every one of these conversations is the same: is the timing enough? California sharpened its answer in 2024. For several kinds of claims, an adverse action within 90 days of speaking up is now presumed to be retaliation, and the employer has to start explaining. Outside the window, timing still does real work. And when the punishment arrives slowly — assignments drying up over months instead of a firing on Friday — the law knows how to read that too.

The 90-day rule: the law assumes it first

Senate Bill 497 — the Equal Pay and Anti-Retaliation Protection Act, effective January 1, 2024 — changed the arithmetic of these cases. When an employer disciplines, demotes, fires, cuts pay or hours, or threatens any of that within 90 days of an employee's protected activity under the covered statutes, the law presumes the action was retaliatory. The employer then must state a legitimate, non-retaliatory reason. If it cannot, that element of the claim is established. The same law added teeth: a civil penalty of up to $10,000 per employee, per violation — paid to the employee who was retaliated against, on top of other remedies.

What the presumption does, practically, is flip who has to start explaining. Before, an employee had to build the causal link from scratch. Now, inside the window, the link is assumed and the employer talks first. Punished within three months of raising a concern? That shift alone changes how a demand letter reads — the letter stops asking the employer to concede a connection and starts asking it to disprove one.

Which claims carry it — and which don't

The presumption lives in three Labor Code sections, each guarding its own ground. Section 1102.5, the whistleblower statute, protects reports of legal violations — to the government, to law enforcement, or internally to someone with authority over the problem. Section 98.6 protects wage claims and complaints to the Labor Commissioner. Section 1197.5 protects Equal Pay Act rights. Complaints about discrimination or harassment travel under a different law — FEHA — and the 90-day presumption does not attach there. That is a distinction, not a weakness. FEHA retaliation has its own well-built framework, and whistleblower claims carry an extra advantage worth knowing. Under the California Supreme Court's decision in Lawson v. PPG (2022), a section 1102.5 plaintiff need only show the protected activity was a contributing factor — one ingredient — in the adverse action. The employer must then prove, by clear and convincing evidence — a demanding standard — that it would have done the same thing anyway. Many situations fit more than one of these statutes at once, which is one reason the same facts can support several claims.

Who knew, how, and when

Strip any retaliation case to the frame and those three questions hold it up. A decisionmaker who never knew about the complaint can't have retaliated for it — so causation starts by tracing knowledge to the person who swung the axe. The how matters because knowledge travels sideways: you told your supervisor, your supervisor briefed the director, the director made the "restructuring" call. And the when is the hinge the case turns on: the complaint has to come before the turn, and the closer the turn follows it, the louder the sequence speaks. This is the classic proof recipe California courts have used for decades — the employer's knowledge of the protected activity, the proximity in time between that activity and the adverse action, and conduct in between consistent with retaliatory intent (Morgan v. Regents (2000)). The inference gains force where your record was clean until the complaint. An employer with genuine performance concerns usually acts on them before the protected activity — not the week after.

When the punishment comes slowly

Not all retaliation is swift. Some employers wait — for a review cycle, a reorganization, a plausible occasion. Some prefer attrition to firing: assignments drying up, exclusion from meetings, staffing pulled, criticism arriving where praise used to. A gap in time does not end the inquiry. James Wysinger, a district manager at the Automobile Club of Southern California, filed a discrimination complaint — and no axe fell. What followed instead, stretched over a long gap: undeserved negative reviews, staff cut from his office, indifference to his health concerns, and finally a denied promotion. The court held that a long gap between the protected activity and the adverse action does not defeat causation where the employer fills that gap with a pattern of conduct consistent with retaliatory intent (Wysinger v. Automobile Club of Southern California (2007)). The pattern itself can also be the adverse action: California measures the harm by the totality of the conduct — the whole course of it — not each slight in isolation. If your punishment was a campaign rather than an event, the months it took do not erase it. They describe it.

What they'll say back

The defense in a timing case is always the same, so hear it now: "the problems started before the complaint." Sometimes the paper backs that up — and when it does, timing alone won't carry the case. Arturo Arteaga is the honest example. He worked for Brink's, the armored-car company, and cash shortages had turned up on his routes; the investigation was already underway when he first raised his medical condition and filed his claims. When Brink's fired him based on that investigation, the court held the close timing could not, by itself, establish that the stated reason was a cover (Arteaga v. Brink's (2008)). None of these are slam dunks, and discipline already in motion before you spoke up is the employer's strongest card.

But the same test cuts the other way, and that's where most real cases live. A complaint followed by the first write-up in years tells one story. Concerns that supposedly existed all along but never reached paper until two weeks after you spoke — that tells another. The order of events decides which case exists, and the paper will show the order.

The dates that decide it

These cases are ultimately built from a calendar, so the calendar deserves care:

• The date you spoke up — and to whom. Causation requires that a decisionmaker knew. An email or text fixing the date and the recipient does more work than almost anything else.
• When the first adverse act came — and every one after it. Write-ups, schedule cuts, pulled assignments, exclusion: each with a date, in order.
• What your record showed before. Reviews, commendations, raises — copies kept somewhere your employer doesn't control.
• Whether the 90-day window applies. If your complaint involved wages, whistleblowing, or equal pay and the response came within three months, the presumption may already be carrying part of your case.
• What was said when. An employer's story that changes — from the firing conversation, to the unemployment paperwork, to whatever comes later — is itself a fact worth capturing as it happens.

No one is going to confess, and the case doesn't need one. The law's substitute is quieter and sturdier: a presumption where the statutes grant one, an inference where the closeness speaks, a pattern where the calendar does. The dates already exist — in your sent folder, your reviews, your schedule. The work is laying them out in order, because laid out in order, the timeline is the argument.

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 →