<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>The PAGA Review</title>
    <link>https://pagareview.com</link>
    <description>Defense-side statutory analysis, litigation strategy, and regulatory developments under California PAGA.</description>
    <language>en-us</language>
    <lastBuildDate>Sun, 18 Oct 2026 22:21:09 GMT</lastBuildDate>
    <atom:link href="https://pagareview.com/feed.xml" rel="self" type="application/rss+xml"/>
    <managingEditor>arthur@arthurkaradzhyan.com (Arthur Karadzhyan)</managingEditor>
    <webMaster>arthur@arthurkaradzhyan.com (Arthur Karadzhyan)</webMaster>
    <copyright>© 2026 Arthur Karadzhyan. All rights reserved.</copyright>
    <docs>https://www.rssboard.org/rss-specification</docs>
    <item>
      <title>The Standing Overhaul: How AB 2288 Ended the Omnibus PAGA Complaint</title>
      <link>https://pagareview.com/standing-overhaul-ab-2288</link>
      <guid isPermaLink="true">https://pagareview.com/standing-overhaul-ab-2288</guid>
      <pubDate>Tue, 10 Mar 2026 00:00:00 GMT</pubDate>
      <dc:creator>Arthur Karadzhyan</dc:creator>
      <category>Statutory Deep Dive</category>
      <description>AB 2288 rewrites PAGA standing from the ground up. The reformed § 2699(c) requires named plaintiffs to have &apos;personally suffered each of the violations alleged&apos; — language drafted to supersede Huff and eliminate representative claims for violations the plaintiff never experienced. This analysis traces the statutory text, the legislative history confirming the override, and the defense opportunities the new framework creates.</description>
      <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<p><strong>Updated October 18, 2026.</strong> Corrected reform applicability, nonprofit eligibility, and limitations/tolling descriptions; linked the legislative record.</p><h2>The Statutory Shift</h2>
<p>Under the pre-reform law, PAGA standing was governed by a single phrase: "aggrieved employee" meant "any person who was employed by the alleged violator and against whom one or more of the alleged violations was committed." One violation — any violation — opened the door to representative penalties for every Labor Code provision the plaintiff's counsel chose to allege, regardless of whether the named plaintiff had personal experience with each category of violation.</p>
<p>The amendments generally apply to civil actions brought on or after June 19, 2024, but not actions for which the required notice was filed before June 19. October 1 is the operative date of the revised § 2699.3 procedures, not the general standing cutoff. (§ 2699(v).)</p>
<p>AB 2288 replaced that definition. Section 2699(c)(1) now reads:</p>
<blockquote><em>
<p>For purposes of this part, “aggrieved employee” means any person who was employed by the alleged violator and personally suffered each of the violations alleged during the period prescribed under Section 340 of the Code of Civil Procedure, except that for purposes of actions brought pursuant to paragraph (2), “aggrieved employee” means any person who was employed by the alleged violator against whom one or more of the alleged violations was committed within the period prescribed under Section 340 of the Code of Civil Procedure.</p>
<p></em></blockquote></p>
<p>Two changes do the work. First, "personally suffered" replaces "against whom one or more of the alleged violations was committed." The former definition already required a violation against the employee; the reform narrows which additional violations that employee may pursue. Second, "each of the violations alleged" replaces "one or more of the alleged violations." The threshold moves from any-one-violation to every-violation.</p>
<h2>The Huff Override</h2>
<p>The legislative record identifies the target. The Senate Judiciary Committee’s June 23, 2024 analysis reports the Chamber of Commerce’s position that the reform supersedes the broader standing recognized in <em>Huff</em> and <em>Johnson</em> by requiring the named employee to have suffered the alleged violations within the one-year limitations period. (Analysis, p. 15.)</p>
<p>Under <em>Huff v. Securitas Security Services USA, Inc.</em> (2018) 23 Cal.App.5th 745, an employee who suffered a Labor Code violation could pursue PAGA penalties for other violations committed against coworkers without personally suffering every violation. The committee analysis describes that rule and the proposed narrowing of standing. (Analysis, p. 15.) The reform’s operative distinction is each violation rather than one or more violations.</p>
<p>The Senate Judiciary analysis describes the change as limiting standing to employees who suffered the same types of violations alleged, while preserving the nonprofit exception. The Labor Federation’s position reproduced in that analysis likewise supports requiring personal experience of the same code sections alleged. (Analysis, pp. 2, 14.)</p>
<p>This is not implicit repeal. It is deliberate statutory override, documented in the legislative record by the organizations that negotiated the text.</p>
<h2>Provision-Level Standing Analysis</h2>
<p>The reformed statute creates a provision-by-provision standing requirement. A named plaintiff with standing for § 226.7 claims (meal and rest break premiums) has no standing for § 510 claims (overtime) unless she also personally suffered overtime violations within the applicable one-year limitations period, accounting for statutory tolling.</p>
<p>For defense practice, this transforms how PAGA complaints are evaluated at intake. The first question is no longer "Does this plaintiff have standing to bring any PAGA claim?" It is: "For which specific Labor Code provisions does this plaintiff have standing, and which provisions are alleged without individual support?"</p>
<p>The mismatch between individual allegations and representative claims — which was irrelevant under <em>Huff</em> — is now the primary vector for a motion to dismiss or motion to strike. Every post-reform PAGA complaint should be audited, provision by provision, against the named plaintiff's actual work experience.</p>
<h2>The Nonprofit Carve-Out</h2>
<p>AB 2288 preserves broader standing for one category of representative: nonprofit legal aid organizations. Section 2699(c)(2) provides that a qualifying nonprofit — one with 501(c)(3) status, meeting the definition of a qualified legal services project or qualified support center under Business & Professions Code § 6213, and that served as counsel of record in PAGA civil actions for at least five years before January 1, 2025 — may file as counsel of record for an aggrieved employee against whom one or more of the alleged violations was committed within the applicable limitations period. The organization acts as counsel, not as a party.</p>
<p>The operative distinction: for cases brought by nonprofit legal aid, the standing threshold remains "one or more" rather than "each." This preserves the pre-reform <em>Huff</em> framework exclusively for nonprofit-represented plaintiffs.</p>
<p>The California Rural Legal Assistance Foundation’s support statement, reproduced in the Senate Judiciary analysis, explains that broader standing protects farmworkers who fear immigration consequences, blacklisting, and retaliation against themselves and people close to them. (Analysis, pp. 15–16.) The exception preserves that representative enforcement role for employees represented by qualifying nonprofit counsel.</p>
<p>For defense counsel, this means evaluating whether opposing counsel is a qualifying nonprofit before investing in a standing challenge. If so, the broader "one or more" threshold governs, and the provision-level standing analysis does not apply.</p>
<h2>The Statute of Limitations Interaction</h2>
<p>Section 2699(c)(1) ties standing to the one-year period "prescribed under Section 340 of the Code of Civil Procedure." The named plaintiff must have personally suffered each alleged violation within the applicable period; § 2699.3(e) excludes the statutory administrative periods from the time for commencing suit, and any other applicable tolling must be assessed. This temporal constraint compounds the substantive standing requirement: even a plaintiff who experienced overtime violations three years ago lacks standing for overtime claims if no overtime violation occurred within the most recent year.</p>
<p>This creates a defense opportunity in cases involving historical violations. An employer who corrected its overtime practices 14 months before the PAGA notice was filed has a standing argument: the named plaintiff cannot have "personally suffered" an overtime violation "during the period prescribed under Section 340" if the practice was corrected before the one-year window opened.</p>
<blockquote><strong>Strategic Implications</strong><br/>
<p><strong>The standing overhaul creates three categories of defense motion practice.</strong></p>
<p>First, provision-level standing challenges at the pleading stage. Every PAGA complaint should be audited against the named plaintiff's individual allegations. Where representative claims are alleged without corresponding individual experience — the pattern that was routine under <em>Huff</em> — a motion to dismiss or motion to strike is warranted.</p>
<p>Second, targeted discovery on the named plaintiff's individual work experience. Under the reformed statute, the named plaintiff's specific history — which facility, which shift, which policies applied, which violations she actually experienced — determines the outer boundary of the claims she can pursue. Interrogatories and deposition testimony focused on individual experience now have dispositive significance.</p>
<p>Third, temporal standing arguments where employer compliance changed during the relevant period. If the employer corrected a practice before the applicable limitations window, after accounting for tolling, the named plaintiff may lack standing for that violation category even if she experienced the violation historically.</p>
<p>Judicial interpretation determines how the “personally suffered each” requirement applies to particular claims. Defense counsel who present well-developed standing challenges now — grounded in the statutory text and the legislative record confirming the <em>Huff</em> override — will shape the interpretive framework for years.</p>
<p></blockquote></p>
<h2>Sources</h2>
<p><a href="https://leginfo.legislature.ca.gov/faces/codes_displaySection.xhtml?lawCode=LAB&sectionNum=2699.">Labor Code § 2699</a> · <a href="https://leginfo.legislature.ca.gov/faces/codes_displaySection.xhtml?lawCode=LAB&sectionNum=2699.3.">Labor Code § 2699.3</a> · <a href="/sources/ab2288-chaptered.pdf">AB 2288, chaptered bill</a> · <a href="/sources/sb92-chaptered.pdf">SB 92, chaptered bill</a>.</p>
<p><a href="/sources/ab2288-senate-judiciary.pdf">Senate Judiciary analysis of AB 2288, June 23, 2024</a>.</p>]]></content:encoded>
    </item>
    <item>
      <title>The Cure Mechanism Under § 2699.3(c)(2): A Defense Reference</title>
      <link>https://pagareview.com/cure-mechanism-deep-dive</link>
      <guid isPermaLink="true">https://pagareview.com/cure-mechanism-deep-dive</guid>
      <pubDate>Mon, 09 Mar 2026 00:00:00 GMT</pubDate>
      <dc:creator>Arthur Karadzhyan</dc:creator>
      <category>Statutory Deep Dive</category>
      <description>A comprehensive analysis of the cure mechanism enacted by the 2024 PAGA reforms — statutory text, legislative context, procedural requirements, defense strategy framework, and unresolved questions that will shape the next generation of cure litigation.</description>
      <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<p><strong>Updated October 18, 2026.</strong> Corrected the receipt/postmark distinction, cure quotations, prior-uncured-notice limitation, partial cure, headcount, and review procedures.</p><h2>Overview</h2>
<p>The 2024 PAGA reforms transformed the cure mechanism from an underutilized procedural footnote into a primary defense tool. Before AB 2288 and SB 92, administrative cure applied to a narrower set of violations. The reformed cure framework — spanning § 2699.3(c)(2) for small employers, § 2699.3(c)(3) for wage statement violations, and the parallel penalty-cap provisions under § 2699(g) and (h) — now occupies a central position in PAGA defense strategy.</p>
<p>This reference document maps the statutory architecture, identifies the procedural requirements that defense counsel must satisfy, and catalogues the open interpretive questions that early litigation will resolve.</p>
<h2>Statutory Text</h2>
<blockquote><em>
<p>For purposes of subdivisions (c) and (f) of Section 2699.3, and except for violations of subdivision (a) of Section 226, "cure" means that the employer corrects the violation alleged by the aggrieved employee, is in compliance with the underlying statutes specified in the notice required by this part, and each aggrieved employee is made whole. An employee who is owed wages is made whole when the employee has received an amount sufficient to recover any owed unpaid wages due under the underlying statutes specified in the notice dating back three years from the date of the notice, plus 7 percent interest, any liquidated damages as required by statute, and reasonable lodestar attorney's fees and costs to be determined by the agency or the court.</p>
<p></em></blockquote></p>
<blockquote><em>
<p>Within 33 days of receipt of the notice sent by the aggrieved employee or representative, an employer that employed fewer than 100 employees in total during the period covered by the notice may submit to the agency a confidential proposal to cure one or more of the alleged violations. The employer shall specify which of the alleged violations it proposes to cure.</p>
<p></em></blockquote></p>
<blockquote><em>
<p>The employer may cure the alleged violation within 33 calendar days of the postmark date of the notice sent by the aggrieved employee or representative. The employer shall give written notice within that period of time by certified mail to the aggrieved employee or representative and by online filing with the agency if the alleged violation is cured, including a description of actions taken, and no civil action pursuant to Section 2699 may commence. If the alleged violation is not cured within the 33-day period, the employee may commence a civil action pursuant to Section 2699.</p>
<p></em></blockquote></p>
<h2>Two Cure Tracks</h2>
<p>The reformed statute creates two distinct cure pathways, each with different procedural requirements, employer size thresholds, and LWDA involvement.</p>
<h3>Track 1: Small Employer Cure — § 2699.3(c)(2)</h3>
<p>Available only to employers with fewer than 100 employees during the period covered by the PAGA notice. The threshold counts all employees — exempt and nonexempt, permanent and temporary — at any location. This is a confidential, LWDA-administered process.</p>
<p><strong>Procedural sequence.</strong></p>
<p>The employer submits a confidential cure proposal to the LWDA within 33 days after receiving the PAGA notice. The LWDA may set a conference to assess cure sufficiency; the employer must complete the cure by the agreed deadline, no later than 45 days after the conference. Sworn notice of completion must include the required supporting records, including a payroll audit and check register for payment obligations. After a preliminary finding of cure, the employee may request an agency hearing. The agency then issues its determination; a finding of adequate cure bars the civil action as to that violation, subject to the employee’s superior-court challenge and the statutory abuse-of-discretion standard. (§ 2699.3(c)(2)(A)–(D).)</p>
<p><strong>Curable violations under § 2699.3(c)(2).</strong></p>
<p>SB 92 expanded administrative cure eligibility by removing several frequently invoked provisions from § 2699.5. The cure mechanism now reaches some of the most frequently alleged PAGA violations: § 226 (wage statements), § 226.7 (meal and rest period premiums), § 510 (overtime), § 2802 (expense reimbursement), § 1194 (unpaid wages), and § 1197 (minimum wage), among others.</p>
<blockquote><strong>Key Point</strong><br/>
<p>The "cure" definition under § 2699(d)(1) requires three components operating simultaneously: (1) the employer corrects the violation, (2) the employer achieves compliance with the underlying statute, and (3) each aggrieved employee is made whole. For wage violations, "made whole" means payment of owed wages dating back three years from the PAGA notice, plus 7% interest, statutory liquidated damages, and reasonable lodestar attorney's fees and costs. This is a demanding standard that requires individualized calculation and remediation.</p>
<p></blockquote></p>
<h3>Track 2: Wage Statement Cure — § 2699.3(c)(3)</h3>
<p>Available to employers of any size but limited to violations of Labor Code § 226 (itemized wage statement requirements). This track operates through direct notice rather than LWDA intermediation — the employer gives written notice by certified mail to the aggrieved employee and by online filing with the LWDA that the violation has been cured, including a description of actions taken.</p>
<p>The wage statement cure track is procedurally simpler but substantively narrower. It does not extend to overtime, meal and rest break, or other wage violations even when those underlying violations manifest on the wage statement.</p>
<h2>Legislative Context</h2>
<p>The cure mechanism cannot be understood apart from the political negotiation that produced it. AB 2288 and SB 92 emerged from a compromise between Governor Newsom, the legislature, and business and labor stakeholders, driven by the threat of a November 2024 ballot measure that would have repealed PAGA entirely. The cure provisions represent the business community's core demand: a meaningful off-ramp that allows compliant employers to resolve claims without protracted litigation.</p>
<p>The legislative design reflects several deliberate choices. The small employer threshold at 100 employees channels the most resource-constrained businesses into a streamlined LWDA-administered process, while directing larger employers toward the Early Evaluation Conference under § 2699.3(f). The confidentiality protections — cure communications are shielded under Evidence Code § 1152 — encourage candid engagement by ensuring that cure proposals cannot be weaponized in subsequent litigation. And the expanded list of curable violations ensures the mechanism reaches the high-volume, high-exposure claims (meal and rest breaks, overtime, expense reimbursement) that drive most PAGA settlements.</p>
<p>The reformed framework supplies express agency review, a cure-completion record, a hearing on the employee’s request, and judicial review. Those steps make documented compliance with the statutory cure requirements central to the defense.</p>
<h2>Defense Framework</h2>
<h3>Pre-Notice Infrastructure</h3>
<p>The cure mechanism rewards preparation. The 33-day window from receipt of the notice to cure proposal submission is short — and the cure itself must be completed within 45 days after any LWDA conference. Employers who receive a PAGA notice without existing compliance infrastructure will struggle to meet these deadlines.</p>
<p>Defense counsel advising employers proactively should establish three elements before any PAGA notice arrives: (1) a compliance audit protocol that can identify and quantify violations within days of a notice, (2) pre-drafted cure proposal templates for the most common violation categories (meal breaks, overtime, wage statements, expense reimbursement), and (3) an escrow or payment mechanism capable of disbursing individualized remediation amounts on short timelines.</p>
<h3>Evaluating Whether to Cure</h3>
<p>Not every PAGA notice warrants a cure attempt. The decision framework turns on several variables:</p>
<p><strong>Employee count.</strong> The § 2699.3(c)(2) cure track is available only to employers with fewer than 100 employees. Employers above that threshold cannot access this process (though they may pursue the EEC under § 2699.3(f) or seek penalty caps under § 2699(g) and (h)).</p>
<p><strong>Violation type.</strong> The violation must be curable — it cannot appear on the § 2699.5 non-curable list. Some of the most aggressively litigated violations (discrimination-related penalties, occupational safety violations) remain outside the cure mechanism's reach.</p>
<p><strong>Cure cost vs. litigation cost.</strong> A complete cure requires making every aggrieved employee whole, including three years of back wages, 7% interest, liquidated damages, and attorney's fees. For widespread violations affecting a large employee population, the cure cost may approach or exceed projected settlement value — at which point litigation (with its attendant penalty caps under § 2699(g) and (h)) may offer a more favorable economics.</p>
<p><strong>Repeat cure limitation.</strong> Employers may not invoke the cure provision more than once every 12 months for the same Labor Code section violation. An employer that cures a meal break violation in March cannot use the cure mechanism for another meal break PAGA notice received in September.</p>
<p><strong>Prior uncured notice limitation.</strong> Section 2699.3(d) also bars use of these notice-and-cure provisions if the employer has been served with a prior notice alleging the same violation that it did not cure. A prior notice alone does not establish this bar; examine what was alleged and whether it was cured.</p>
<blockquote>
<p>The 12-month and prior-uncured-notice limitations create a genuine strategic tension. Curing a violation now may foreclose the cure option for a subsequent, potentially larger exposure. Defense counsel should assess the employer's ongoing compliance posture before committing to a cure — an employer likely to generate future violations of the same type may be better served by pursuing penalty caps under § 2699(g) or (h) rather than exhausting the one-time cure option.</p>
<p></blockquote></p>
<h3>Documenting the Cure</h3>
<p>The statute requires sworn notice of cure completion accompanied by supporting documentation. For wage-related violations, this includes a payroll audit and check register. The documentation burden is not merely procedural — it provides the evidentiary basis for the LWDA's sufficiency determination and, if disputed, for the superior court's abuse-of-discretion review.</p>
<p>Defense counsel should treat the cure documentation as if preparing for summary judgment. Every element of the cure should be documented contemporaneously: identification of the affected employee population, calculation of individual owed amounts, evidence of payment disbursement, revised policies, training records, and any operational changes made to prevent recurrence.</p>
<h2>The Penalty-Cap Parallel Track</h2>
<p>The cure mechanism operates alongside — but distinct from — the penalty-cap provisions under § 2699(g) and (h). These provisions do not eliminate penalties entirely but reduce them to 15% or 30% of the otherwise applicable amount based on the employer's compliance efforts.</p>
<p><strong>15% cap (§ 2699(g)).</strong> Available when, prior to receiving the PAGA notice or a records request, the employer took "all reasonable steps" to comply with the identified provisions. Reasonable steps may include periodic payroll audits, dissemination of lawful written policies, supervisor training, and corrective action. The totality of circumstances is considered, including the employer's size, resources, and the nature, severity, and duration of the violations.</p>
<p><strong>30% cap (§ 2699(h)).</strong> Available when, within 60 days of receiving the PAGA notice, the employer takes all reasonable steps toward prospective compliance with the identified provisions.</p>
<p><strong>Neither cap applies</strong> where the employer's conduct was malicious, fraudulent, or oppressive, or where the LWDA or a court found within the preceding five years that the employer's challenged practice was unlawful.</p>
<blockquote><strong>Strategic Implications</strong><br/>
<p><strong>Cure and reasonable compliance steps should be evaluated together.</strong> An adequate administrative cure can bar the civil action for the cured violation. In litigation, § 2699(j) eliminates penalties for a cure combined with reasonable-steps compliance, and for a qualifying wage-statement cure; other cured violations carry a penalty of no more than $15 per employee per pay period. Large employers can pursue judicial early evaluation. Where cure is impractical, assess the 15% or 30% limits and judicial discretion under § 2699(e)(2).</p>
<p>Defense counsel should evaluate all three tiers at the outset of every new PAGA matter and present the client with a clear decision tree: Can we cure? If not, can we cap at 15%? If not, can we cap at 30%? If not, what is the residual exposure and what does the litigation path look like?</p>
<p></blockquote></p>
<h2>Open Questions</h2>
<p>The statutory framework answers several threshold questions directly. Remaining disputes turn on the facts, the sufficiency of remediation, and the application of the statutory standards.</p>
<h3>What constitutes "all reasonable steps"?</h3>
<p>The 15% and 30% penalty caps turn on all reasonable steps toward compliance. The statute supplies illustrative measures and a totality-of-the-circumstances assessment. The relevant proof is the employer’s actual compliance work in light of its resources and the nature, severity, and duration of the violations; the mere existence of a violation is insufficient to defeat the limit. (§ 2699(g)–(h).)</p>
<h3>How does the LWDA evaluate cure sufficiency?</h3>
<p>The statute directs the LWDA to assess the proposal, obtain information as needed, supervise the cure timetable, and verify completion. The February 2026 proposed regulations add procedural detail, but proposed text is not itself an operative rule. The statutory correction, compliance, and make-whole requirements remain the foundation of the cure analysis.</p>
<h3>Can an employer partially cure?</h3>
<p>The statute expressly allows an employer to propose curing one or more alleged violations and requires it to identify which ones. (§ 2699.3(c)(2)(A).) The EEC provisions likewise contemplate curing some violations while others remain disputed. (§ 2699.3(f)(2), (7).) The practical question is whether the employer completely cures each selected violation for the affected employees, not whether it must concede every claim in the notice.</p>
<h3>What is the scope of "made whole"?</h3>
<p>The statute requires owed wages dating back three years, 7% interest, statutory liquidated damages, and reasonable lodestar attorney’s fees and costs determined by the agency or court. It expressly permits cure of disputed wage amounts by paying sums the agency or court determines could reasonably be owed. (§ 2699(d)(1).) The practical disputes concern calculation, proof, and the amount of reasonable fees; fees are an express part of the cure definition.</p>
<h3>Does the 100-employee threshold apply at the time of the notice or the violation period?</h3>
<p>The statute refers to fewer than 100 employees in total during the period covered by the notice. The LWDA’s published guidance counts all individuals employed during the one-year period before notice, including exempt, nonexempt, temporary, seasonal, former, and out-of-state employees. This is not merely a snapshot of current California headcount. Near-threshold employers should reconcile the complete employment roster with the notice period and the agency’s guidance.</p>
<h3>How do courts review LWDA cure determinations?</h3>
<p>The administrative hearing and superior-court review provisions in § 2699.3(c)(2)(D) make the cure record consequential. The statute addresses an abuse-of-discretion challenge and offsets amounts already paid, exclusive of penalties, against a later judgment if the court finds the cure determination inadequate. Counsel should preserve the audit, calculations, proof of payment, and the agency’s reasons.</p>
<h2>LWDA Proposed Rulemaking (February 2026)</h2>
<p>On February 6, 2026, the LWDA published a Notice of Proposed Rulemaking to adopt the first formal regulations governing PAGA's administrative procedures. The proposed regulations add 33 new sections to Title 8 of the California Code of Regulations and directly address the cure mechanism's implementation.</p>
<p>Key regulatory proposals for the cure process include: standardized requirements for cure proposal content, procedures for LWDA conferences and notifications, clarification that the 100-employee count includes all employee types, confidentiality protections under Evidence Code § 1152 for cure-related communications, and a framework for disputing and appealing LWDA cure determinations.</p>
<p>The original comment period closed March 23, 2026. The agency held a hearing April 9 and issued modified proposed text August 3, with comments closing August 18. The agency’s rulemaking page reviewed October 18 still describes proposed rulemaking activity. Consult the linked rulemaking record for the latest procedural status.</p>
<p>---</p>
<p><em>Originally developed March 9, 2026; statutory references and procedural descriptions corrected October 18, 2026. The rulemaking discussion distinguishes proposed text from enacted law.</em></p>
<h2>Sources</h2>
<p><a href="https://leginfo.legislature.ca.gov/faces/codes_displaySection.xhtml?lawCode=LAB&sectionNum=2699.">Labor Code § 2699</a> · <a href="https://leginfo.legislature.ca.gov/faces/codes_displaySection.xhtml?lawCode=LAB&sectionNum=2699.3.">Labor Code § 2699.3</a> · <a href="/sources/ab2288-chaptered.pdf">AB 2288, chaptered bill</a> · <a href="/sources/sb92-chaptered.pdf">SB 92, chaptered bill</a>.</p>
<p><a href="/sources/ab2288-senate-judiciary.pdf">Senate Judiciary analysis of AB 2288, June 23, 2024</a>.</p>
<p><a href="https://www.labor.ca.gov/resources/paga/paga-faqs/">LWDA PAGA FAQs</a> · <a href="https://www.labor.ca.gov/resources/paga/rulemaking-labor-code-private-attorneys-general-act-of-2004/">Official rulemaking record</a> · <a href="https://www.labor.ca.gov/wp-content/uploads/sites/338/2026/02/2026-2-6-Express-Terms-of-Prop-Rulemaking_LWDA_PAGA-Z2026-0121-03.pdf">February proposed text</a>.</p>]]></content:encoded>
    </item>
    <item>
      <title>LWDA’s First PAGA Regulations Proposal: The March 2026 Analysis</title>
      <link>https://pagareview.com/lwda-proposed-paga-regulations-2026</link>
      <guid isPermaLink="true">https://pagareview.com/lwda-proposed-paga-regulations-2026</guid>
      <pubDate>Mon, 09 Mar 2026 00:00:00 GMT</pubDate>
      <dc:creator>Arthur Karadzhyan</dc:creator>
      <category>Practice Alert</category>
      <description>The LWDA published the first-ever formal PAGA regulations on February 6, 2026. The proposed rules add 33 new sections to the California Code of Regulations covering cure procedures, notice requirements, settlement oversight, and vexatious filer designations. The original comment period closed March 23, 2026; this article includes an October 18 status note.</description>
      <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<p><strong>Updated October 18, 2026.</strong> Preserved the March analysis as a historical article and added the agency’s August rulemaking developments and current status.</p><blockquote>
<p><strong>October 18, 2026 update.</strong> The original comment period closed March 23. The LWDA held a hearing April 9, issued modified proposed text August 3, and closed the additional comment period August 18. Its current rulemaking page continues to identify proposed rulemaking activity. The discussion below addresses the February proposal and the original March deadline; it does not state that either proposed version is an adopted regulation. <a href="https://www.labor.ca.gov/resources/paga/rulemaking-labor-code-private-attorneys-general-act-of-2004/">Rulemaking record</a> · <a href="https://www.labor.ca.gov/wp-content/uploads/sites/338/2026/08/2026-8-3-Modified-Proposed-Regulatory-Text-Z2026-0121-03.pdf">August modified text</a>.</p>
<p></blockquote></p>
<h2>The Development</h2>
<p>On February 6, 2026, the California Labor and Workforce Development Agency published a Notice of Proposed Rulemaking to adopt 33 new sections to Title 8 of the California Code of Regulations implementing the 2024 PAGA reforms. Since PAGA's enactment in 2004 — and through the AB 2288 / SB 92 reform package — no formal regulations have governed the statute's administrative procedures. The proposed rules change that.</p>
<p>The written comment period closes March 23, 2026. The LWDA has not scheduled a public hearing but will hold one if it receives a written request at least 15 days before the comment deadline. Comments may be submitted to Danielle West, PAGA Rulemaking and Policy Analyst, at Danielle.West@labor.ca.gov.</p>
<h2>What the Proposed Regulations Do</h2>
<p><strong>Standardize PAGA notice content.</strong> The regulations require PAGA notices to use an LWDA form and provide "short and plain" factual statements and theories for each alleged violation. Bare legal conclusions and boilerplate allegations — the filing pattern that has driven the volume of frivolous PAGA claims — are explicitly identified as insufficient. Critically, the proposed rules limit subsequent litigation and settlements to the Labor Code violations and theories of liability included in the PAGA notice. Violations not adequately alleged in the notice cannot be litigated or settled later.</p>
<p><strong>Structure the small employer cure process.</strong> The regulations provide the procedural framework for § 2699.3(c)(2) cure proposals, including what the employer's cure proposal must contain, how LWDA conferences are scheduled and conducted, timelines for cure completion, and procedures for disputing and appealing cure determinations. The regulations confirm that cure-related communications are protected under Evidence Code § 1152.</p>
<p><strong>Clarify the 100-employee threshold.</strong> The proposed rules specify that the small employer designation includes all employees — exempt and nonexempt, permanent and temporary — at any location within the preceding year. Employers near the threshold should assess their headcount under this standard.</p>
<p><strong>Create a vexatious filer designation.</strong> The LWDA proposes a process for designating high-frequency and vexatious PAGA filers, with prefiling screening orders and a public list maintained on the LWDA portal. This directly targets the mass-filing practice that has driven PAGA claim volumes despite the 2024 reforms.</p>
<p><strong>Expand settlement oversight.</strong> Proposed rules require more robust settlement submission packages, give the LWDA at least 45 days to review proposed settlements, and require notice to other employees who have pending PAGA claims against the same employer. The last point could complicate the current practice of resolving overlapping and competing PAGA claims through a single settling plaintiff.</p>
<p><strong>Specify the employer response process.</strong> The proposed rules give procedural detail to the existing statutory ability to respond to a PAGA notice, including the filing channel and supporting content. They do not create that statutory response right for the first time.</p>
<h2>The March 2026 Practice Implications</h2>
<p><strong>Submit comments by March 23.</strong> The cure sufficiency standard, the scope of the employer response mechanism, and the vexatious filer criteria are all areas where defense-side input can shape the final regulations. Employers with experience receiving boilerplate PAGA notices should consider providing concrete examples of the filing practices the LWDA is targeting.</p>
<p><strong>Audit cure readiness.</strong> The proposed regulations operationalize the cure process with specific submission requirements and timelines. Employers with fewer than 100 employees should pre-draft cure proposal templates that satisfy the proposed content requirements. For a small-employer cure proposal, the 33-day clock runs from receipt of the PAGA notice; the separate wage-statement cure deadline runs from the notice’s postmark — preparation before a notice arrives is the only way to meet the deadline without compromising cure quality.</p>
<p><strong>Re-evaluate the 100-employee headcount.</strong> The inclusion of all employee types — exempt, nonexempt, permanent, temporary — in the count may push employers above the threshold who assumed otherwise. Employers near the line should calculate their headcount under the proposed standard and determine whether they fall within the small employer cure track or must pursue the Early Evaluation Conference under § 2699.3(f).</p>
<p><strong>Prepare for longer settlement timelines.</strong> The proposed 45-day LWDA review period for settlements, combined with the notice requirement to other pending PAGA claimants, will extend the time from settlement agreement to court approval. Defense counsel negotiating PAGA settlements should build this lead time into the resolution timeline.</p>
<blockquote>
<p>The proposed regulations remain subject to modification based on public comments. Final rules could differ from the published proposal. But the structural framework — standardized notices, cure process details, settlement oversight, vexatious filer designations — is likely to survive in some form. Defense counsel who engage with the rulemaking now, rather than waiting for final adoption, will be better positioned when the regulations take effect.</p>
<p></blockquote></p>
<h2>Sources</h2>
<p><a href="https://leginfo.legislature.ca.gov/faces/codes_displaySection.xhtml?lawCode=LAB&sectionNum=2699.">Labor Code § 2699</a> · <a href="https://leginfo.legislature.ca.gov/faces/codes_displaySection.xhtml?lawCode=LAB&sectionNum=2699.3.">Labor Code § 2699.3</a> · <a href="/sources/ab2288-chaptered.pdf">AB 2288, chaptered bill</a> · <a href="/sources/sb92-chaptered.pdf">SB 92, chaptered bill</a>.</p>
<p><a href="https://www.labor.ca.gov/resources/paga/paga-faqs/">LWDA PAGA FAQs</a> · <a href="https://www.labor.ca.gov/resources/paga/rulemaking-labor-code-private-attorneys-general-act-of-2004/">Official rulemaking record</a> · <a href="https://www.labor.ca.gov/wp-content/uploads/sites/338/2026/02/2026-2-6-Express-Terms-of-Prop-Rulemaking_LWDA_PAGA-Z2026-0121-03.pdf">February proposed text</a>.</p>]]></content:encoded>
    </item>
    <item>
      <title>The Penalty Architecture: A Defense Map to the Reformed § 2699</title>
      <link>https://pagareview.com/penalty-architecture-reformed-2699</link>
      <guid isPermaLink="true">https://pagareview.com/penalty-architecture-reformed-2699</guid>
      <pubDate>Sat, 28 Feb 2026 00:00:00 GMT</pubDate>
      <dc:creator>Arthur Karadzhyan</dc:creator>
      <category>Statutory Deep Dive</category>
      <description>AB 2288 replaced PAGA&apos;s binary penalty structure with a graduated framework of six tiers — from zero (full cure) to $200 (malicious conduct) — calibrated to employer behavior. This analysis maps each tier, the &apos;all reasonable steps&apos; standard that controls the 15% and 30% caps, and the judicial override discretion that makes every penalty determination negotiable.</description>
      <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<p><strong>Updated October 18, 2026.</strong> Clarified default-penalty scope, the isolated-event duration test, wage-statement exceptions, and the 15% cap calculation.</p><h2>The Pre-Reform Baseline</h2>
<p>Before AB 2288, PAGA penalties operated on a two-step ladder: $100 per aggrieved employee per pay period for initial violations, $200 for subsequent violations. Courts had limited discretion to reduce penalties, exercised inconsistently. The result was a penalty calculus that plaintiffs' counsel could model with precision and defendants could predict with dread — aggregate exposure scaled linearly with headcount and violation duration, often reaching seven or eight figures before any factual inquiry into the employer's conduct or intent.</p>
<p>The reformed § 2699 combines a revised default-penalty schedule with caps and cure rules in a graduated architecture that ties penalty magnitude to employer behavior. Six tiers, from zero to $200, each triggered by different factual predicates.</p>
<h2>Tier 1: Zero Penalty — Full Cure</h2>
<p>An employer who satisfies the 15% or 30% reasonable-steps cap (subdivisions (g) or (h)) and cures the violation pays no civil penalty for that violation. Section 2699(j) provides: "An employer who satisfies subdivision (g) or (h) and cures a violation shall not be required to pay a civil penalty for that violation."</p>
<p>This is the strongest position in the reformed framework. It requires both reasonable-steps compliance <em>and</em> a completed cure — correction of the violation, current compliance, and individualized remediation for each aggrieved employee. The combined requirement means the zero-penalty tier is available only to employers who were already trying to comply (or moved quickly after notice) and who also fully cured.</p>
<p>An employer who cures a § 226 wage statement violation also pays zero, regardless of the reasonable-steps analysis.</p>
<h2>Tier 2: $15 Per Employee Per Pay Period — Cure Without Reasonable Steps</h2>
<p>An employer who cures but does not satisfy the reasonable-steps caps pays no more than $15 per employee per pay period for cured violations. Section 2699(j): "Any other employer shall pay a civil penalty of no more than fifteen dollars ($15) per employee per pay period for the statute of limitations set forth in Section 340 of the Code of Civil Procedure for any violations that the employer cures."</p>
<p>This tier exists for employers who failed to take reasonable pre-notice or post-notice compliance steps but who nevertheless completed a full cure. The penalty is not zero, but it represents an 85% reduction from the standard $100 rate — a powerful incentive for cure even where the reasonable-steps caps are unavailable.</p>
<h2>Tier 3: $25 — Wage Statement Violations (Determinable)</h2>
<p>Where the violation involves wage statement itemization under § 226(a), paragraphs (1) through (7) and (9), the penalty drops to $25 per aggrieved employee per pay period "if the employee could promptly and easily determine from the wage statement alone the accurate information." For paragraph (8) violations (employer identification), the $25 rule addresses confusion about the employer’s identity or, for a farm labor contractor, the entity securing its services. The reduced wage-statement penalty does not apply when no itemized statement was provided for a pay period at issue. (§ 2699(f)(2)(A)(i).)</p>
<p>The Labor Federation’s support statement reproduced in the Senate Judiciary analysis describes lower penalties for technically deficient paystubs from which employees can verify their pay and employer. (Analysis, p. 14.) The legislative design distinguishes between wage statements that are technically noncompliant but functionally informative and those that actually prevent the employee from understanding their pay.</p>
<h2>Tier 4: $50 — Isolated, Nonrecurring Violations</h2>
<p>The penalty is $50 per aggrieved employee per pay period "if the alleged violation resulted from an isolated, nonrecurring event that did not extend beyond the lesser of 30 consecutive days or four consecutive pay periods." Section 2699(f)(2)(A)(ii).</p>
<p>This tier rewards employers whose violations are genuinely aberrational. A software update that temporarily miscalculates overtime may fall within this category if the event is isolated and nonrecurring and satisfies both the 30-day and four-pay-period limits. Three biweekly pay periods alone would exceed 30 days. A systemic practice that persists for a year does not.</p>
<p>The legislative history describes a reduced penalty for isolated violations; the enacted text controls the precise duration limits. The defense burden is establishing that the violation was truly isolated — which requires evidence of the employer's pre-violation compliance and post-violation correction.</p>
<h2>Tier 5: $100 — Standard Penalty</h2>
<p>For Labor Code provisions without a specifically provided civil penalty, the default penalty remains $100 per aggrieved employee per pay period. This is the residual rate for violations that are neither isolated ($50), wage-statement-specific ($25), cured ($0 or $15), nor aggravated ($200).</p>
<h2>Tier 6: $200 — Aggravated Violations</h2>
<p>The $200 rate applies in two circumstances: (i) within five years preceding the alleged violation, the LWDA or any court issued a finding or determination that the employer's challenged practice was unlawful, or (ii) the court determines the employer's conduct was malicious, fraudulent, or oppressive. Section 2699(f)(2)(B).</p>
<p>The first trigger is objective — a prior finding or determination creates a per se basis for the $200 rate. The second is subjective — malice, fraud, or oppression requires a factual determination of employer intent.</p>
<p>The legislative history describes the higher tier as tied to prior adverse findings or malicious, fraudulent, or oppressive conduct. Those predicates, rather than the mere repetition of a violation, control the enhanced default penalty. (Senate Judiciary analysis of AB 2288, pp. 12–15.)</p>
<blockquote><strong>Key Point</strong><br/>
<p>The reformed penalty structure eliminates the initial/subsequent distinction ($100/$200) and replaces it with a conduct-based framework. The $200 rate is no longer automatic for "subsequent" violations — it requires either a prior agency/court finding or a judicial determination of malicious, fraudulent, or oppressive conduct. For employers without a prior adverse finding who are not acting in bad faith, the effective ceiling drops from $200 to $100.</p>
<p></blockquote></p>
<h2>The Reasonable-Steps Caps</h2>
<p>The 15% and 30% penalty caps are the most consequential defense provisions in the reform package. They apply regardless of violation type, are available to employers of any size, and reduce exposure by 70% or 85%.</p>
<p><strong>The 15% Cap — § 2699(g).</strong> Available where the employer, <em>prior to receiving the PAGA notice or a records request</em>, "has taken all reasonable steps to be in compliance." The statute provides examples: periodic payroll audits, dissemination of lawful written policies, supervisor training, appropriate corrective action. Reasonableness is evaluated under the "totality of the circumstances" considering "the size and resources available to the employer, and the nature, severity and duration of the alleged violations."</p>
<p>Critically: "The existence of a violation, despite the steps taken, is insufficient to establish that an employer failed to take all reasonable steps." This statutory sentence is the conceptual foundation of the caps. It separates the question of violation from the question of penalty — an employer can violate the Labor Code and still qualify for the 15% cap if its compliance efforts were reasonable.</p>
<p><strong>The 30% Cap — § 2699(h).</strong> Available where the employer, <em>within 60 days after receiving the PAGA notice</em>, "has taken all reasonable steps to prospectively be in compliance." The same reasonableness factors apply, but the temporal trigger is different: the 30% cap rewards post-notice compliance rather than pre-notice compliance. An employer that responds to a PAGA notice by immediately auditing, correcting, and training can cap its exposure at 30% even if it had no compliance infrastructure before the notice.</p>
<p><strong>Neither cap applies</strong> where the $200 aggravated rate applies — prior findings of unlawful practice, or malicious/fraudulent/oppressive conduct.</p>
<blockquote><strong>Strategic Implications</strong><br/>
<p><strong>The penalty caps reshape the economics of every PAGA negotiation.</strong></p>
<p>Before the reforms, a plaintiff's damages model was: violation count × employee count × pay periods × $100 (or $200). The defendant's only lever was disputing the violation count or seeking judicial discretion to reduce.</p>
<p>After the reforms, the defense model introduces multipliers: Is the cap 15% or 30%? Is the violation isolated ($50) or wage-statement-specific ($25)? Did the employer cure ($0 or $15)? The same underlying violation can generate per-employee-per-pay-period exposure ranging from $0 to $200 depending entirely on the employer's conduct before, during, and after the PAGA notice.</p>
<p>Defense counsel should build compliance evidence into the engagement from day one. The 15% cap requires proof of pre-notice compliance efforts. That means identifying and preserving evidence of payroll audits, policy dissemination records, training logs, and corrective action documentation — before litigation discovery narrows the universe of available evidence. Documented reasonable compliance steps can support the 15% limit, an 85% reduction from the otherwise applicable penalty, subject to the statutory exceptions and judicial discretion.</p>
<p>For the 30% cap, the 60-day clock from notice receipt is the critical timeline. Defense counsel retained after a PAGA notice should immediately assess whether the employer can take "all reasonable steps to prospectively be in compliance" within 60 days. If so, the penalty ceiling drops to 30% — and if the employer also cures, the penalty drops to zero.</p>
<p></blockquote></p>
<h2>Judicial Override</h2>
<p>Section 2699(e)(2) provides that a court "may award a lesser amount than the maximum civil penalty amount specified by this part, including the penalty amounts in subdivisions (g) and (h), or may, notwithstanding the limitations set forth in subdivisions (g) and (h) exceed the limitations set forth in those subdivisions, if, based on the facts and circumstances of the particular case, to do otherwise would result in an award that is unjust, arbitrary and oppressive, or confiscatory."</p>
<p>This is a bidirectional override. Courts can go below the caps or exceed them when the facts satisfy the statute’s unjust, arbitrary and oppressive, or confiscatory standard. The Senate Judiciary analysis describes the additional discretion to avoid unjust outcomes. (Analysis, pp. 2, 13–14.)</p>
<p>The override ensures that no penalty determination is mechanical. Every case is subject to equitable adjustment based on its specific facts. For defense counsel, this means the penalty caps are not self-executing floors — they are starting points for a judicial determination that accounts for the totality of the employer's conduct, the severity of the violations, and the proportionality of the aggregate penalty.</p>
<h2>Derivative Claim Limits</h2>
<p>Section 2699(i) addresses a longstanding defense concern: stacking penalties for derivative violations that arise from the same underlying conduct. An employer who fails to pay overtime (§ 510) also generates a wage statement violation (§ 226 — failure to accurately report hours worked) and a waiting time violation (§ 203 — failure to pay all wages at separation). Under the pre-reform framework, each derivative violation generated its own penalty stream, multiplying exposure for what was functionally a single compliance failure.</p>
<p>The reformed statute bars additional derivative penalties under §§ 201, 202, and 203 and restricts additional penalties for specified § 204 and § 226 violations when the employee also collects a penalty for the underlying unpaid wage violation. It preserves the relevant willful-or-intentional, knowing-or-intentional, and missing-statement exceptions. (§ 2699(i).) The court retains discretion to reduce penalties for "any alleged violation if the same conduct or omission resulted in multiple violations."</p>
<h2>The Weekly-Pay Adjustment</h2>
<p>Section 2699(o): "the penalty recovered pursuant to this part shall be reduced by one-half if the employees' regular pay period is weekly rather than biweekly or semimonthly."</p>
<p>This addresses a structural inequity in the pre-reform framework. An employer paying weekly accumulated twice as many PAGA pay periods as an employer paying biweekly — penalized for paying employees more frequently. The 50% reduction for weekly pay periods neutralizes this artifact.</p>
<p>---</p>
<p><em>This analysis covers the penalty provisions as enacted. Judicial interpretation will refine the boundaries of each tier, the "all reasonable steps" standard, and the scope of judicial override discretion. Updated as courts apply these provisions.</em></p>
<h2>Sources</h2>
<p><a href="https://leginfo.legislature.ca.gov/faces/codes_displaySection.xhtml?lawCode=LAB&sectionNum=2699.">Labor Code § 2699</a> · <a href="https://leginfo.legislature.ca.gov/faces/codes_displaySection.xhtml?lawCode=LAB&sectionNum=2699.3.">Labor Code § 2699.3</a> · <a href="/sources/ab2288-chaptered.pdf">AB 2288, chaptered bill</a> · <a href="/sources/sb92-chaptered.pdf">SB 92, chaptered bill</a>.</p>
<p><a href="/sources/ab2288-senate-judiciary.pdf">Senate Judiciary analysis of AB 2288, June 23, 2024</a>.</p>]]></content:encoded>
    </item>
    <item>
      <title>Manageability as the New Contested Terrain: A Defense Framework for § 2699(p)</title>
      <link>https://pagareview.com/manageability-defense-framework</link>
      <guid isPermaLink="true">https://pagareview.com/manageability-defense-framework</guid>
      <pubDate>Sun, 15 Feb 2026 00:00:00 GMT</pubDate>
      <dc:creator>Arthur Karadzhyan</dc:creator>
      <category>Strategy Note</category>
      <description>The manageability provision gives defense counsel an express basis for targeted trial-evidence and claim-scope limitations. This framework maps the provision onto existing defense strategies and identifies the arguments most likely to gain traction.</description>
      <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<p><strong>Updated October 18, 2026.</strong> Corrected the statutory citation to § 2699(p), removed an inaccurate class-certification quotation, and distinguished statutory scope limits from Estrada’s inherent-authority holding.</p><h2>Thesis</h2>
<p>Section 2699(l) is the most consequential procedural reform in the 2024 PAGA package. Unlike the cure mechanism — which requires affirmative employer action within a narrow window — manageability operates as a structural limitation on the scope of claims that can proceed to trial. It authorizes evidence and claim-scope limitations so a claim can be effectively tried. It does not impose Rule 23 prerequisites.</p>
<p>The defense bar has not yet developed a unified approach to manageability motions. This strategy note proposes a framework.</p>
<h2>The Statutory Standard and the Class Certification Analogy</h2>
<p>Section 2699(p) provides: “The superior court may limit the evidence to be presented at trial or otherwise limit the scope of any claim filed pursuant to this part to ensure that the claim can be effectively tried.” Section 2699(q) separately preserves consolidation and coordination of overlapping claims. Neither provision contains the phrase “criteria similar to” class certification.</p>
<p>For defense practice, the analogy creates both opportunity and risk.</p>
<p><strong>The opportunity.</strong> Class-action trial-planning experience can help counsel demonstrate individualized factual disputes and propose manageable methods of proof. The request should be grounded in the express statutory authority and the evidence needed to try the actual PAGA claims.</p>
<p><strong>The doctrinal boundary.</strong> <em>Estrada v. Royalty Carpet Mills, Inc.</em> (2024) 15 Cal.5th 582 held that courts lack inherent authority to strike PAGA claims for unmanageability and rejected importing class-action manageability prerequisites. The later statute expressly authorizes evidence and scope limits. A defense motion should seek a supported statutory limit rather than assume that a failed class-certification showing automatically defeats a PAGA claim.</p>
<h2>Framework: Three Categories of Manageability Arguments</h2>
<h3>Category 1 — Individualized Inquiry Claims</h3>
<p>The strongest manageability arguments arise where the alleged violations require employee-by-employee proof. Meal and rest break claims are the paradigmatic example: whether a particular employee was denied a compliant break often depends on individual circumstances — the employee's specific schedule, their supervisor's practices, whether the employee voluntarily waived the break.</p>
<p>When a claim covers many employees, locations, shifts, or supervisors, counsel should identify the actual variations that affect proof and explain why the proposed trial plan fails to address them. Declarations, payroll records, and policy evidence should support a specific limitation rather than an assertion that size alone makes the claim untriable.</p>
<h3>Category 2 — Multi-Location, Multi-Policy Claims</h3>
<p>Claims spanning business locations with materially different practices can create proof problems. Fifty locations do not necessarily mean fifty distinct policies; counsel must establish which relevant practices differ and why those differences matter. A targeted scope or evidence proposal is stronger when it addresses proven variation rather than headcount alone.</p>
<p>Defense counsel should identify and document operational differences across locations. Organizational charts, site-specific policy manuals, and declarations from regional managers all support the argument that a unified trial is unmanageable.</p>
<h3>Category 3 — Temporal Complexity</h3>
<p>Different governing regimes can complicate overlapping actions, but the reform’s applicability generally turns on the action and notice dates specified in § 2699(v), not automatically on each violation’s date. Counsel should identify the applicable law and any overlapping pre-reform action before seeking coordination or separate trial treatment.</p>
<p>Defense counsel should highlight the temporal line and argue for separate treatment of pre- and post-reform claims.</p>
<h2>Procedural Timing</h2>
<p>Manageability should be raised early — ideally at the Early Evaluation Conference under § 2699.3(f). Waiting for a dispositive motion stage allows the case to develop complexity that itself becomes an argument against manageability limitations. The EEC is the statutory mechanism for putting scope limitations on the table before either side has invested heavily in discovery.</p>
<p>At early evaluation, counsel should present an evidence-supported account of the disputed claims and proposed resolution. If judicial scope limitations are needed, seek them from the court through an appropriate case-management request; a confidential EEC submission is not itself a dispositive ruling.</p>
<blockquote><strong>Strategic Implications</strong><br/>
<p><strong>The value of the provision depends on a concrete trial proposal.</strong> Show which proof cannot be tried effectively as proposed, what narrower evidence or claim scope will solve the problem, and how that approach permits adjudication of the remaining claims.</p>
<p>The framework proposed here — individualized inquiries, multi-location complexity, and temporal issues — covers the majority of wage-and-hour PAGA claims. Defense counsel should begin incorporating manageability analysis into their initial case assessments and raising the issue at the earliest procedural opportunity.</p>
<p>The practical objective is an order that permits an effective trial on a defined record. A carefully supported request under § 2699(p), together with coordination under § 2699(q) where appropriate, gives the court a workable alternative to an unsupported dismissal request.</p>
<p></blockquote></p>
<h2>Sources</h2>
<p><a href="https://leginfo.legislature.ca.gov/faces/codes_displaySection.xhtml?lawCode=LAB&sectionNum=2699.">Labor Code § 2699</a> · <a href="https://leginfo.legislature.ca.gov/faces/codes_displaySection.xhtml?lawCode=LAB&sectionNum=2699.3.">Labor Code § 2699.3</a> · <a href="/sources/ab2288-chaptered.pdf">AB 2288, chaptered bill</a> · <a href="/sources/sb92-chaptered.pdf">SB 92, chaptered bill</a>.</p>
<p><a href="/sources/estrada.pdf"><em>Estrada v. Royalty Carpet Mills</em>, Supreme Court opinion</a>, especially pages 2–3 and 32–33.</p>]]></content:encoded>
    </item>
  </channel>
</rss>