Every wage and hour case that comes into our office starts the same way. Before we talk strategy and long before mediation, we ask the client for one thing: the raw time and payroll data. Not a summary. The punch-level time records, the payroll register with every pay code, and the wage statements. That data is going to testify in the case whether the employer likes it or not, and I would rather hear what it has to say before the plaintiff’s lawyer does.
I have written before about what executives should demand from their defense counsel once a lawsuit lands. This week I want to go behind the desk and show what we actually do with an employer’s records in the first days of a case using the Scaled Comp software, because that process reveals — better than any policy memo — which records matter, why speed matters, and what “reasonable steps” looks like when it is being tested rather than described. Full disclosure: I co-founded Scaled Comp, and Zaller Law Group uses it as a tool under counsel’s direction in our litigation and audit work. More on that at the end.
1. The clock may already be running before the PAGA notice arrives — and your records are the first thing it measures.
Under the 2024 PAGA reform, an employer that took “all reasonable steps” to comply before receiving a PAGA notice can have its penalties capped at 15% of the maximum, and an employer that takes those steps within 60 days after the notice can cap them at 30%. What many employers miss is that the statute ties the 15% cap not only to the PAGA notice but also to the employer’s receipt of a request for personnel or payroll records under Labor Code §§226, 432, or 1198.5 — whichever comes first. The innocuous letter from an employee’s attorney asking for a “copy of my client’s personnel file and pay records” is very often the starting gun, and by the time the PAGA notice follows, the window for the 15% cap may have already closed.
That is why one of the very first things we do is pull the records, and the first thing we learn is whether they exist in usable form. California requires employers to keep payroll records for at least three years (Labor Code § 1174(d)), to keep copies of wage statements for three years (§ 226(a)), and — under the Wage Orders — to record meal periods. When a client cannot produce a clean, punch-level export going back three years, that is the first finding of the case, and it is a bad one: under Hernandez v. Mendoza (1988) 199 Cal.App.3d 721, once an employee shows the employer’s records are inadequate, the burden shifts and the employee’s own recollection of hours worked can carry the day. An employer with no records is not defending a case; it is negotiating a surrender.
2. Within days — not months — we know the actual compliance rate, and that changes every decision that follows.
Here is what the software does once the data is loaded. It measures every shift against the rules: was a meal period started by the end of the fifth hour, was it at least 30 minutes, was a second meal provided by the end of the tenth hour, and — if rest breaks are recorded — were they provided based on hours worked. It flags each late, short, or missed break. It then does the step that most employers never do on their own: it matches each flagged shift against the payroll register to see whether a meal or rest premium was actually paid for that day. The output is a compliance rate — by location, by manager, by pay period — along with the count of pay periods and workweeks in the limitations period and an exposure model built on the employer’s actual numbers rather than the plaintiff’s assumptions. It also keeps two numbers that are easy to confuse: for PAGA penalty purposes, a shift with three flags is still one violation, while premium pay liability is calculated per missed break. Both numbers matter, and they are not the same.
The traditional way to get this analysis was to retain a damages expert months into the case, wait several more months for a report, and pay a fee that could rival a small settlement. The reason we built the software was to compress that to days. And the speed is not a convenience — it is the whole point. The 60-day window for the 30% cap is meaningless if you do not know where the violations are until day 90. The decision whether to push for early mediation — which, as I discussed in the mid-year 2026 PAGA data, cuts off the accrual of pay periods that otherwise add to the exposure every month — depends on knowing the number. A case where 3% of shifts show a late meal period with no premium paid is defended, budgeted, and settled completely differently than one where the figure is 35%. In the first week, we know which case we have.
3. Premium payments are the evidence — record them as though they will be Exhibit A, because they will be.
Under Donohue v. AMN Services, LLC (2021) 11 Cal.5th 58, time records showing a late, short, or missed meal period raise a rebuttable presumption that a violation occurred. That presumption is rebutted with evidence — that the employee was provided the break and chose to skip it, or that the employer recognized the issue and paid the premium. This is where the payroll register becomes the employer’s best witness or its worst. When the analysis shows a late meal punch on a given day and a § 226.7 premium paid on that same day, the story is that the employer’s system caught the problem and paid for it. That does not erase the underlying issue for every purpose, but it eliminates the unpaid-premium claim, it cuts off the derivative wage statement and waiting time claims that Naranjo v. Spectrum Security Services, Inc. (2022) 13 Cal.5th 93 makes available when premiums go unpaid, and it is the single strongest piece of evidence that the employer’s compliance program is real rather than aspirational.
But the software can only give the employer credit for what it can match. Three recordkeeping practices determine whether that credit is available:
- Code premiums separately. Meal premiums and rest premiums should be their own pay codes and their own line items on the wage statement. Naranjo held that premium pay is wages that must be reported on wage statements; premiums buried in “other pay” or “adjustments” are invisible to the analysis and to the court.
- Pay premiums at the regular rate, not the base rate. Ferra v. Loews Hollywood Hotel, LLC (2021) 11 Cal.5th 858. A premium paid at the wrong rate is a documented underpayment on every day it appears.
- Tie the premium to the day. A lump-sum “true up” at the end of the month cannot be matched to the shift it was meant to cover. Pay it in the pay period of the missed break.
4. The analysis becomes the defense at every stage of the case — not just a number for mediation.
Employers sometimes assume the exposure analysis is a one-time exercise to set a settlement authority. It is not. The same data set is reused at nearly every stage:
- The 60-day window. Location- and manager-level results tell the employer exactly where to direct corrective action within the 60 days after the notice, and the documentation of that action is the 30%-cap file.
- Arguing the penalties down. The reform gives courts discretion to reduce penalties that would be unjust or oppressive, and provides a reduced penalty where a violation resulted from an isolated, nonrecurring event of short duration. Neither argument can be made in the abstract; both require showing the court what the records actually reflect.
- The mediation brief. Compliance rates and the pay-period and workweek counts, benchmarked against comparable settlements on a per-pay-period and per-workweek basis, are the difference between negotiating from data and negotiating from fear.
- Opposing certification. When compliance varies widely by location and manager, that variation is evidence that liability cannot be determined on a class-wide basis without individualized inquiries.
- Rebutting the plaintiff’s expert. The plaintiff’s damages model will typically treat every 5:01 punch as a violation and ignore premiums paid, waivers, and shifts short enough that no meal period was required. Our analysis identifies each of those categories shift by shift.
Two structural notes. First, the analysis is run through counsel and at counsel’s direction so that it is protected as attorney work product; an employer that runs the same analysis on its own, outside of counsel, may be creating a discoverable document. Second, the report does not decide the legal questions — whether the employer’s conduct amounts to reasonable steps, and which cap applies, are judgments for counsel and ultimately the court. The data gives counsel something to argue with.
5. Run the same analysis when nobody is suing you. That is what “reasonable steps” looks like on paper.
The statute’s list of reasonable steps starts with “conducting periodic payroll audits and taking action in response to the results of the audit,” followed by disseminating lawful written policies, training supervisors, and taking corrective action with regard to supervisors — evaluated under the totality of the circumstances, including the employer’s size and resources and the nature, severity, and duration of the violations. I have covered the action items under the reform before. The point I want to make here is narrower: the audit the statute describes and the litigation analysis described above are the same analysis. The only difference is when it is run and who is asking.
An employer that runs it on a recurring basis — monthly or quarterly, depending on size — gets a report by location and manager, acts on it (retraining a manager, fixing a scheduling practice, paying the premiums the audit identifies), documents the action, and then runs it again. The trend line is the reasonable-steps story: 12% of shifts at one location showed late meal periods with no premium paid in the first quarter, the manager was retrained and the scheduling template changed, and the figure was 3% the next quarter. That is a narrative a court can evaluate, and it is far more persuasive than a declaration that the company “takes compliance seriously.”
The audit also does something the penalty caps do not: it reduces the exposure itself. Every violation caught and corrected is a premium paid now rather than a premium, a wage statement penalty, and a PAGA penalty litigated later. And because PAGA penalties accrue per aggrieved employee per pay period, shrinking the number of employees who experienced any violation directly shrinks the case a plaintiff’s firm can bring. Two cautions: the audit will identify premiums that are owed, and the employer needs to be prepared to pay them — that is the point of the exercise, not a reason to avoid it. And reasonable steps are proven with documents. The audit report, the memo directing corrective action, the training sign-in sheet, and the follow-up audit are the file. A sincere belief that the company was compliant is not.
The bottom line: in every PAGA case, the employer’s payroll records testify first, and they testify about the period before the employer knew it had a problem. The employers who fare best are the ones whose records already tell the right story — punch-level data that exists and can be exported, premiums that are paid, coded, and matched to the day they cover, a rest break reporting mechanism that leaves a trail, and a recurring audit with documented corrective action behind it. Get those in place now, and the first week of the case looks very different.









