We catch missed breaks, unpaid break premiums, and open safety items — then chase each one to a documented fix.

Labor Code §2699(g) caps PAGA civil penalties at 15% where the employer took all reasonable steps before notice — or before an employee’s personnel or payroll records request, which often comes first; §2699(h) caps them at 30% for remediation within 60 days after. Two qualifications matter. Whether the steps were enough is the court’s call, on the totality of the circumstances. And the percentages are ceilings, not floors: §2699(e)(2) lets a court award more, “notwithstanding the limitations set forth in subdivisions (g) and (h).” The cap reaches Labor Code civil penalties only, it is conditional on evidence rather than policies, and no record means no cap.

§2699(g)(2) names four examples: periodic payroll audits with action taken in response, lawful written policies disseminated to employees, supervisor training on Labor Code and wage order compliance, and corrective action as to supervisors. Reasonableness is judged “on the totality of the circumstances, taking into account the size and resources available to the employer.” Each item must be shown — with timestamps, signatures, and a chain of custody that survives discovery — and we produce a dated, exportable record of all four. The same subdivision adds the part employers rarely hear: “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. Policies that exist only in a handbook, with nothing showing they were distributed or followed, are what forfeits it. No California appellate court has yet said what satisfies “all reasonable steps.”

Together, the 2024 reforms require employers claiming the §2699 cap to demonstrate four things contemporaneously: that policies were written and distributed, that supervisors were trained, that the employer audited compliance periodically, and that surfaced violations were corrected. LWDA proposed its first PAGA regulations in February 2026; they are procedural — notice content, cure mechanics, settlement review — and do not interpret the reasonable-steps standard. They are proposed, not final, and nothing on this page assumes they take effect. Demonstration is by evidence, not assertion — meaning a per-pay-period record tied to specific employees, dates, and times.

It is the time data — clock-in, clock-out, GPS, geofencing — which is the input, not the record. Several timekeeping products can capture a signature at clock-out, and the box is sometimes configured long before anyone asks who acts on what it surfaces. Capability is not adoption, and a signature is not the loop: an app can capture a signature, but it will not chase the exception, pay the premium, retrain the foreman, or close the item. What a §2699 argument leans on is the employee’s contemporaneous affirmation or dispute that breaks were taken, hours are accurate, and pay matches expectation — and then the correction entered alongside anything that came back wrong. MicroForensics is built on top of BusyBusy or ExakTime — it ingests the time data, routes per-pay-period attestations, and runs the correction to close.

No. MicroForensics sits above your existing HRIS, timekeeping, and payroll systems. We build the connector for your stack — ADP Workforce Now, Paylocity, Gusto, BusyBusy, ExakTime, Samsara, Motive, Geotab, or your combination — by API where one exists, by export, SFTP, or structured manual entry where one doesn’t. The connector is scoped and priced in the records diagnostic. You keep your stack. We orchestrate. We don’t replace.

We can’t tell you what your policy covers, and we won’t guess. What we can tell you is where to look: wage-and-hour is usually the narrow part of an EPLI policy — excluded outright, or sublimited to defense costs — so ask your broker to show you the wage-and-hour endorsement language rather than the summary. We are also not aware of any published California EPLI or workers’ comp credit for running a documented compliance program, so don’t buy this expecting a premium reduction. Insurance is, at best, money after the fact; the §2699 caps turn on the record you built before.

Two different answers, and the difference is worth being plain about. On harassment: California employers are strictly liable for harassment by a supervisor — no record and no service changes that — and Gov. Code §12950.1(c) says training compliance “does not insulate the employer from liability for sexual harassment.” What the law does compel is a record: the FEHA policy acknowledgment and the harassment-prevention training records (2 CCR §§ 11023, 11024(b)(2)). The crew-facing surface carries both, dated and tracked to completion, because the employer owes them anyway. One textual point your counsel may find useful: Gov. Code §12940(k) requires “all reasonable steps” to prevent harassment — the same words amended §2699(g) uses on the wage-and-hour side — so one record architecture answers both statutes’ phrasing. That is evidence and posture, not a statutory penalty mechanism. On discrimination: no. No California statute rewards documentation there the way §2699 does for wage-and-hour civil penalties — liability turns on the adverse decision itself, not on notice — so we make no claim on discrimination, and we would be skeptical of a vendor who does.

A waiver signed at hire establishes that the employee was informed of the meal-break rule. It does not establish that any particular break on any particular day was taken or knowingly waived. Donohue v. AMN Services (Cal. 2021) held that noncompliant time records create a rebuttable presumption of violation. 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” — so we don’t round. Be clear about what that is and isn’t: no court has ever held that an employee attestation rebuts the Donohue presumption, and Donohue itself left sufficiency for remand. The hire-day signature is policy. The contemporaneous attestation is dated evidence your counsel can argue from. Neither is a ruling.

In hours, not weeks. A lawyer’s letter demanding records — a request under section 226, 432, or 1198.5 — usually arrives before any lawsuit does, and a §2699 PAGA notice after it; what answers either is one production package. The standing record is already in the evidentiary format defense counsel uses — production is retrieval, not construction. Payroll, timekeeping, HR, and safety are reconciled into one record as the shifts happen, so the package is an export from one place rather than a search across payroll, the time clock, the HR file, and the safety binder. The records that can go into the package are inventoried with you in the records diagnostic. The export is gated to your authorized custodian of records: someone on the defendant’s team, not Floburn, controls it, and that gate is what preserves the chain-of-custody foundation opposing counsel would otherwise attack. Weeks of counsel-supervised assembly, billed at counsel rates, collapse to the custodian’s export session. We don’t publish a dollar figure for that difference — it runs on your counsel’s rate card, not ours. The timeline is a property of how the record is kept, not a promise about your matter. No outcome is guaranteed; every matter turns on its facts.

You keep it — that is a design decision, not a courtesy. The record is built in evidentiary format from the first shift, your authorized custodian of records holds the standing export, and the exports are structured, queryable files your counsel or a successor vendor can use without us. Floburn operates the loop; your company owns the record. If the engagement ends, the closing export is part of offboarding, and nothing about the record’s usability depends on Floburn continuing to exist.

If all reasonable steps were taken and documented before the notice, §2699(g) caps civil penalties at 15% — applied by the court on a totality-of-the-circumstances showing, and subject to §2699(e)(2), which lets a court exceed the limits. If documentation is incomplete, §2699(h) caps penalties at 30% for remediation within 60 days after. MicroForensics can be implemented inside that window — that is the cure-provision use case. Separate pathways exist by headcount: employers with 100 or more employees can request a court-supervised early evaluation conference; employers under 100 have a confidential LWDA cure path with its own short clock. Which pathway applies to you, whether you qualify, what to cure, and what your exposure is are legal conclusions on your facts. Your counsel makes those calls; we build the material they argue from, and the earlier we start the more of it there is.