The 15% PAGA cap doesn't apply itself.

Most California employers first heard about the 2024 PAGA reform from a one-line summary in a trade-press article. The summary said something like "penalties capped at 15%." It was true. It was also misleading. The cap is conditional, not automatic, and the condition is documentary evidence the employer either has on the day a notice arrives or doesn't.

This post is about the gap between we took reasonable steps and we can prove we took reasonable steps — what the amended statute actually conditions the cap on, section by section, in the order the sections show up in a real defense.

What the statute actually says

Labor Code §2699(g) caps PAGA civil penalties at 15 percent where the employer took all reasonable steps before receiving a notice. Section 2699(h) caps them at 30 percent where the employer takes all reasonable steps to be in compliance within 60 days after the notice. That is the whole of the mechanism, and four things about it get dropped in almost every retelling.

It reaches civil penalties only. Not the underlying wages. Not the meal-and-rest premiums, the §226 statutory penalties, the waiting-time penalties, or the fees. The portion of a wage-and-hour matter most likely to actually be paid out is not the portion the cap touches.

It is a ceiling, not a floor. The statute says penalties "shall not be more than" the stated percentage. An employer who establishes reasonable steps has won an upper bound, not an amount.

A court may go past it regardless. Section 2699(e)(2) permits a court, "notwithstanding the limitations set forth in subdivisions (g) and (h)," to exceed the limitations set forth in those subdivisions. The cap is a discretionary instrument with an escape hatch written into the same section.

The burden sits with the employer. The employer asserts reasonable steps and the employer proves them. Reasonableness is judged, in the statute's own words, "on the totality of the circumstances, taking into account the size and resources available to the employer" — one of the few genuinely employer-friendly phrases in §2699, because it means a sixty-person contractor is not measured against a public company's compliance department.

That is also why there is no cap-delta arithmetic on this page. Producing a number that way requires assuming a settlement value, assuming the court honors the cap, assuming it declines to exceed it under (e)(2), and assuming the employer carries a burden no California appellate court has yet construed. Four assumptions stacked into one confident dollar figure is not analysis.

What survives is the direction, which is the part that was doing the work anyway. An employer holding a contemporaneous record has an argument available. An employer without one does not have the argument at all, and the difference is categorical rather than fractional.

And the timing is tighter than most operators assume. The window closes when a records request under section 226, 432, or 1198.5 arrives — not when the lawsuit does. The records request usually comes first.

What "reasonable steps" actually means

Section 2699(g)(2) enumerates four examples. They are not aspirational. They are evidentiary.

1. Periodic payroll audits with action taken in response to the results. Not the audit alone. The audit plus the response.
2. Dissemination of lawful written policies. Not "we have a handbook." Distributed, acknowledged, with a chain of custody.
3. Training of supervisors on applicable Labor Code and wage order compliance requirements. Not annual blanket compliance training. Specific. Documented. Repeated.
4. Taking appropriate corrective action with regard to supervisors. Corrected is the operative word — not reminded, not spoken to.

Read the list again and notice what is in every item: a response. Not a finding, a response to a finding. The audit is not the reasonable step; the action taken in response is. The complaint is not the reasonable step; the corrective action is. Every one of the four is a closed loop, and the loop is the part employers skip — most of them have the finding somewhere and nothing recorded after it.

Each item has to be shown, not asserted. A handbook on a shelf is not evidence. A training video that ten supervisors clicked through in November 2023 is not, on its own, evidence that supervisors were trained on the specific wage order in effect when the violation allegedly occurred.

One more sentence from the same subdivision deserves more attention than it gets, because it is the honest reassurance in a section otherwise short on them: "The existence of a violation, despite the steps taken, is insufficient to establish that an employer failed to take all reasonable steps." Being imperfect does not forfeit the argument. Having no record does.

Two disclosures belong here rather than in a footnote. No California appellate court has yet said what satisfies "all reasonable steps," so every description of the standard on this page — ours included — is a reading of statutory text and not a report of holdings. The LWDA's February 2026 proposed PAGA regulations do not change that: they cover notice content, cure procedure, filer conduct, and settlement review, and do not interpret the phrase.

The Donohue layer

In Donohue v. AMN Services (Cal. 2021), the California Supreme Court held that time records showing missed, short, or delayed meal periods create a rebuttable presumption of violation. The presumption is rebuttable — but the rebuttal vehicle has to be specific.

The employer in Donohue ran a per-period electronic system that asked employees to confirm their meal periods. The Court described it, and did not condemn it as a category. It failed there because the timekeeping underneath it rounded punches, so the prompt fired against numbers that had already erased the short break it was supposed to surface. The defensible version of the claim is therefore narrow: the California Supreme Court described an employer system of the same per-period design and said that, without the rounding, it "would have ensured accurate tracking of meal period violations." We don't round, and deployment enforces that: attestation prompts fire on unrounded punch times — where the timekeeping underneath rounds punches, the rounding is turned off, and where unrounded punches cannot be supplied, we say so rather than prompt off rounded data.

What we will not say is that attestation is the evidence the Court endorsed. Donohue left the sufficiency question for remand, and no court has ever held that an employee attestation rebuts the Donohue presumption. Anyone telling you otherwise is selling you something. Attestation is an argument with a good pedigree and no holding behind it, which is a real thing to have and not the same thing as a defense.

It is also worth being precise about what attestation is not doing. It is not one of the four enumerated examples in §2699(g)(2) — the audit, the policies, the training, and the corrective action are. The attestation earns a Donohue evidentiary argument. The enumerated modules are what speak to reasonable steps. Two different jobs, two different instruments, and conflating them is the most common error in this category.

A waiver signed at hire is neither. A hire-day waiver establishes that the employee was informed of the rule. It does not establish that any particular break on any particular day was offered, taken, or knowingly skipped. Plaintiffs' counsel know the difference. So does the bench.

The 2026 rulemaking

In February 2026, LWDA published its first proposed PAGA regulations. They do not raise the documentary bar on the reasonable-steps showing — the proposed text is procedural: notice form and content, cure mechanics for smaller employers and wage-statement claims, filer-conduct rules, and agency review of settlements. Nothing in it interprets "all reasonable steps," sets an audit cadence, or prescribes training or acknowledgment formats. The full walkthrough is here.

What the rulemaking does do is make every post-notice pathway a deadline-driven documentary exchange — cure proposals, conference statements, settlement submissions — each of which is run from records that either existed on the day the notice arrived or did not. The standard for the caps is where the 2024 statute left it: statutory text, unconstrued by any appellate court, judged on the totality of the circumstances.

When the notice has already arrived

A PAGA notice in the inbox changes the analysis, though not in the way the trade-press summaries have it. Section 2699(g) reaches steps taken before the notice, so what is still available depends on what was already documented on the day it arrived — a legal question on your facts, and one for your counsel. What is newly on the clock is §2699(h)'s 60-day window for taking all reasonable steps to be in compliance after the notice.

For employers below a statutory headcount threshold, §2699's cure provision allows a confidential cure proposal to be submitted to LWDA within a short window after the notice, with a further period to implement if the agency accepts. The cure scope was expanded in the 2024 reforms to cover minimum wage, overtime, meal and rest, expense reimbursement, and wage-statement defects — the predominant predicates in most PAGA filings. We give the shape rather than the dates and the thresholds, so that nobody counts a deadline off a blog post.

For employers above that threshold, the parallel mechanism runs later and through the court rather than the agency: on being served with a summons and complaint, the employer may request a court-supervised early evaluation conference and a stay of court proceedings. The conference gives the employer time and structure to demonstrate reasonable steps without immediately litigating. The stay matters — it prevents plaintiffs' counsel from forcing the case forward while the employer is building the record.

Which of these is available to a given employer, and whether either is worth invoking, is a legal conclusion applied to specific facts. It is your counsel's call and we will not make it for you. What we can say about both paths is operational: each requires a system of record capable of generating the evidence quickly, which means the integrations to the existing timekeeping and payroll stack already working, the policy and training records already retrievable, and bilingual content reaching employees within days rather than weeks. A 60-day window does not forgive a slow vendor.

What this looks like productized

The work in this post is what Floburn ships as MicroForensics — an orchestration layer built on top of an employer's existing timekeeping (BusyBusy, ExakTime, ADP, Paylocity, Samsara) and payroll (Gusto, QuickBooks, ADP) systems, with the connector built per stack, running the four enumerated modules on a schedule: the recurring payroll audit, the policy dissemination and acknowledgment record, the supervisor training record, and the corrective-action log. Every finding opens an item. Every item carries a mandatory correction field, and nothing closes until someone enters what was done.

The stack stays. The record is the byproduct; the product is that nothing stays open. A timekeeping app can capture a signature. It will not chase the exception, pay the premium, retrain the foreman, or close the item — and the closing is the half of every §2699(g)(2) example that employers are missing.

If a notice has already arrived, the operational priority is implementation speed. If none has, the priority is getting the record running before one does — or before the records request that usually arrives first. We are not a law firm. We build the record; your counsel makes the argument.

A worked walkthrough of the diagnostic and what it covers lives on the California payroll page. If you want the conversation, the discovery call is the right starting point. If you want the next post in your feed, the journal RSS feed is the right tool.