Labor Code §2699(g) ends 15% cap eligibility when a records request under §226, §432, or §1198.5 arrives — not when a PAGA notice does. The records request almost always comes first, and it does not look like the beginning of anything.
A single-page letter arrives asking for a former employee's personnel file. It is polite. It cites a statute. It is signed by a firm nobody at the company has heard of, and it asks for the file to be produced within thirty days.
Almost every employer treats this as an administrative errand. Someone in HR pulls what they can find, copies it, mails it, and marks it done. Nobody calls counsel, because nothing has been filed and nobody is being sued.
Two things happened that afternoon that nobody wrote down. The first is that a clock started on a statutory production deadline whose breach is itself a violation. The second is more consequential and almost never noticed: for purposes of the 15 percent PAGA cap, a door closed.
Labor Code §2699(g)(1) makes the 15 percent cap on PAGA civil penalties available where the employer took all reasonable steps to comply before receiving a notice — or before receiving a request for records under §226, §432, or §1198.5.
That is the whole mechanism, and its consequence is that the trigger is not litigation. It is correspondence. An employer whose reasonable-steps record is assembled in the weeks after a records request arrives has assembled it on the wrong side of the line the statute draws.
Section 2699(h) still supplies the post-notice track — the 30 percent cap for taking all reasonable steps to be in compliance within 60 days after a PAGA notice. But that is a different subdivision with a different standard and a different number, and reaching it requires that a notice actually arrive.
The hedges belong right here rather than at the bottom. Both figures cap civil penalties only — not the unpaid wages, not the premiums, not the §226 statutory penalties, not the fees. Both are ceilings and not floors; the statute says penalties "shall not be more than" the stated percentage, and §2699(e)(2) permits a court to exceed the limitations of subdivisions (g) and (h) notwithstanding those subdivisions. And no California appellate court has yet said what satisfies "all reasonable steps," so everything anyone tells you about the standard, us included, is a reading of statutory text rather than a report of holdings.
What survives the hedges is a question of sequence, and sequence is not a matter of degree. The record either predates the letter or it does not.
There are two of them, they run on different clocks, and they are usually sent together.
Personnel file, §1198.5. A current or former employee — or a representative, which in practice means the plaintiff's firm — may inspect or receive a copy of the personnel records relating to performance or to any grievance concerning the employee. The employer has 30 days. A failure to comply carries a $750 penalty recoverable by the employee, along with injunctive relief and attorney's fees.
Payroll records, §226(b)–(c). The employee may inspect or copy the records the employer is required to keep, and the employer has 21 days. Same $750 penalty structure at §226(f).
Employment application and signed documents, §432. An employee who signed an instrument relating to obtaining or holding employment is entitled to a copy on request.
Both of the deadline provisions are also PAGA predicates in their own right where the failure is systematic, which produces the somewhat absurd but entirely real outcome that a badly handled records request can become a count in the notice that follows it.
From the requesting side, this is reconnaissance, and it is cheap.
The response tells opposing counsel most of what they need to know before deciding whether to invest in a case. Did the production arrive on time. Was it complete. Do the wage statements contain the nine items §226(a) requires, or are two of them missing across every period. Are there signed policy acknowledgments, and do they line up with the dates of employment. Is there any documented response to anything — a corrected statement, a premium paid with a reason code, a training record for the supervisor named in the story the client told.
An employer who produces a complete, organized, on-time package has said something specific about the difficulty of the case. An employer who produces a partial package in week six has said something else, and the something else is an invitation.
This is the part operators find hardest to accept, because it inverts the usual intuition about record-keeping. The production is not merely a compliance obligation to be discharged. It is the first and cheapest opportunity to change someone's mind about whether to proceed — and it happens before there is a matter, before there is a demand, and while the employer still has every option.
For employers who hire at the jobsite, the request often lands on a file that was never assembled in one place to begin with.
The I-9 is in the trailer, the signed handbook acknowledgment may exist in a binder at a site that closed in 2023, the safety orientation was signed on a clipboard, and the certified payroll for the public job is with the bookkeeper who does that one thing. Producing a "complete personnel file" within thirty days is not a retrieval problem. It is an assembly problem, and the assembly has never been done.
Which means the honest answer to "how long would it take you to produce a complete file on any named employee" is, for many employers in this profile, "we do not know." That answer is worth discovering on a Tuesday when nobody is asking, rather than on day nineteen of a thirty-day clock.
Four things, none of which require counsel to set up, all of which require counsel the moment a letter actually arrives.
Route it on arrival. Certified mail and any correspondence from a law firm goes to a named person the day it lands, not into the general mail pile. We have written before about what four days of a cure window cost when nobody opened the envelope.
Log it. Date received, requester, statute cited, deadline computed, date produced, what was produced, and how it was delivered. The log is the artifact that later shows the request was handled, and it takes about ninety seconds per letter.
Call your counsel before producing. What must be produced, what is outside the request, and what the production says strategically are legal questions on your facts. This post is not a production checklist and no post should be.
Understand what the clock did to the cap. Not so you can act on it — that is your counsel's analysis — but so that the timing question gets asked at all. The failure worth guarding against is not a bad answer to that question. It is that nobody knows the question exists.
Everything above is procedural. The substance is that the reasonable-steps record §2699(g)(2) describes — periodic payroll audits with action taken in response, lawful written policies, supervisor training on Labor Code and wage order compliance, and corrective action as to supervisors — is either running before the letter arrives or it is not.
It cannot be created in the thirty days. Not because anyone forbids it, but because what the subdivision describes is a history: audits conducted periodically, policies disseminated, training delivered, corrective action taken. A file assembled in June cannot describe what was done in the preceding two years unless it was being kept during them.
The law already requires most of these records. The only question is whether yours are complete — and the day you find out should not be the day someone else asks.
Pick a name before you call us. Then the discovery call runs the exercise against your real systems instead of a hypothetical: how long it actually takes to produce a complete file on that person, and what is missing from it. If a request has already arrived, call your counsel first — we work behind them, not around them.