A PAGA notice arrives with a 33-day clock already running. When the time edit log, payroll register, wage statement samples, and policy acknowledgments aren’t pre-staged, pulling them across HRIS and payroll takes 10 to 15 business days. Half the cure window is gone before anyone makes a real decision. That’s what this piece is about: a proof-packet workflow that gets the records ready before the notice ever lands.

The workflow shift behind LWDA’s proposal

On February 6, 2026, the California Labor and Workforce Development Agency (LWDA) published its first formal proposed regulations governing PAGA notices, cure procedures, and settlement reporting. In 20 years of PAGA, LWDA had never formally defined what a compliant notice had to look like. Now it has. The written comment period closed March 23, 2026. LWDA held a public hearing on April 9, 2026, and is reviewing comments before finalizing.

Nothing is final yet, but the direction is clear. Notices will carry named Labor Code sections, claimant employment dates, exact work locations, and case-specific facts — not boilerplate allegations. Pay-period detail comes back into play during cure documentation. If your records can’t match that level of specificity, you’ll burn the cure window assembling evidence instead of evaluating whether to cure, contest, or settle.

California PAGA notice requirements under the proposed regulations

What changed. Per LWDA’s February 2026 rulemaking, PAGA notices will use an Agency-prescribed form with claimant-specific facts, including the claimant’s employment dates, workplace address or location, position, job duties, specific Labor Code sections allegedly violated, and facts and theories supporting each alleged violation. Boilerplate or conclusory allegations would not be enough. The Labor Code sections most commonly cited:

The proposal also adds two new filer controls. Firms that filed 200+ PAGA notices in the preceding 12 months are classified as “high-frequency filers” and face heightened LWDA scrutiny. “Vexatious filers” who repeatedly submit noncompliant notices may be required to clear LWDA prefiling review — a screening step against the new form and content rules — before new notices can be served.

What didn’t change. Filings still go to LWDA. The 33-day cure window under Labor Code section 2699.3 stays the same. The private right of action structure is unchanged, and so is the employee’s ability to file a civil action if the notice period lapses without resolution.

Two separate procedural tracks. Labor Code 2699.3 now splits PAGA response into a small-employer and a large-employer path:

• Fewer than 100 employees: you may submit a written cure proposal directly to LWDA, and LWDA determines whether the proposed cure is adequate.
• 100 or more employees: before a responsive pleading is filed, you may ask the court for an Early Evaluation Conference (EEC) with a neutral evaluator and a stay of court proceedings.

The procedural track is set by headcount, not by choice. Know which one you’re on before a notice arrives; the artifacts you need are similar, but who signs them and where they go is not.

The practical upside for employers. Claimant-specific notices make it possible to map each allegation to a specific record — one Labor Code section, one claimant, one work location. That only works if the matching records are already staged. If they aren’t, the fact-specific notice hands plaintiff’s counsel the checklist and starts your clock at zero.

Decide fast: cure, contest, or settle

Wrong pick burns the cure window. The decision has to happen in the first 72 hours, not the second week, and it has to be made by someone who can see the records, not just the allegation. Counsel drives the final call. HR and payroll own the record assembly that makes any of these paths workable.

Build a PAGA-ready proof packet

What belongs in the packet (with the HRIS reports that actually produce it):

• Time edit logs with modifier identity, supervisor approval timestamp, and reason code for each edit — not just the corrected clock entry. Most HRIS platforms expose this under a timecard audit trail or time-detail-with-modifications report.
• Payroll registers broken out by employee and earning code for every alleged pay period, including overtime, meal-period premiums, and reimbursements. Pull the pay-period-detail or payroll-results export, not a year-to-date summary.
• Wage statement samples validated against Labor Code Section 226’s nine-item requirement (employee name, last four of SSN or ID, hours, rates, gross/net, deductions, pay period, employer name/address, piece-rate units if applicable) — plus the accrued paid sick leave balance required under Labor Code 246(i), which may appear on the wage statement OR in a separate writing provided on the designated pay date.
• Signed policy acknowledgments for meal and rest period policies, overtime authorization, and any on-duty meal or wage-statement waivers — stored with the signature date, not just the policy text.

The test that predicts whether your packet works: try to export a point-in-time snapshot of wage statements from a pay period that closed three months ago. Not a re-run of current data against historical dates. If the export generates live data instead of an archived snapshot, your packet has the gap. That gap is the single most common reason we see contestable cases settle. The records existed; the dated export didn’t. The fix is a recurring export; counsel still drives cure/contest strategy once the notice is in the door.

The 72-hour PAGA intake workflow

A repeatable PAGA response runs on three things you set up once and run every pay cycle — not a scramble you stand up from scratch 33 days before a decision has to be made.

Why PAGA filings held steady after 2024 reform

The 2024 amendments in AB 2288 and SB 92 reset some of PAGA’s mechanics: standing is tighter, penalties can be capped at 15% of the applicable amount if the employer can prove documented “reasonable steps” toward compliance before the notice arrives (the statute points to periodic payroll audits, lawful written policies, supervisor training on Labor Code and wage-order compliance, and corrective action on supervisor violations — and the list is not exhaustive), and cure eligibility expanded for small employers. Civil penalties still run $100 per aggrieved employee per pay period under the default rate (reduced to $50 for isolated, non-recurring violations, and to $25 for wage-statement errors the plaintiff could easily spot), which creates settlement pressure even on low-incident claims. LWDA’s own record still shows a concentrated channel of repeat-filer firms.

The operational failure isn’t any single notice. It’s treating the response as a one-off scramble instead of a standing workflow that runs every pay period. The recordkeeping breakdown traces back to the same root: payroll, timekeeping, and policy documents live in separate systems with no shared export. Closing that gap is both an operational and a legal project. The export discipline is what you own; counsel still drives cure/contest/settle strategy once a notice lands. Schedule the export the day after each pay period closes. That’s the only calendar change most teams need.

For the recordkeeping side of this issue, outsourced HR compliance support from VertiSource HR, HRIS document storage and recurring tasking in VSHR HR Cloud, and time-and-attendance audit trails are the VertiSource pages that connect most directly.