blog
California Senate Bill 35 (SB 35) reshaped the approval process for multifamily housing developments by introducing a streamlined, ministerial approval pathway for qualifying projects. While the bill is primarily viewed through a housing development lens, it carries significant compliance implications for contractors, especially those operating in the prevailing wage space.
Below is a practical guide to SB 35 focused on what contractors, subcontractors, and compliance teams need to know to stay compliant and audit ready.
Before diving into compliance details, it’s worth flagging a development that changes how this law should be understood today: SB 35 is no longer a standalone statute operating on its original 2017 terms.
In October 2023, Governor Newsom signed SB 423 (Wiener), which took effect January 1, 2024, and substantially amended the streamlined ministerial approval process originally created by SB 35 (codified at Government Code § 65913.4). Some jurisdictions and planning departments now refer to the process as “SB 423 (formerly known as SB-35).”
Key changes contractors should know about:
For contractors and compliance teams, the practical takeaway is this: prevailing wage still applies broadly, but which additional labor standards apply (skilled and trained workforce, apprenticeship utilization, healthcare expenditures) now depends on specific project size and building height thresholds rather than a blanket rule. The sections below reflect the current SB 423-amended framework.
SB 35 allows qualifying multifamily housing projects to bypass discretionary approvals and move through a streamlined, by-right approval process if they meet objective zoning and affordability requirements.
Key features include:
SB 35 explicitly ties streamlined approval eligibility to prevailing wage compliance.
Under SB 35, developers must certify one of the following:
This applies even when the project is privately funded.
For contractors and subcontractors, this means:
Failure to comply can lead to:
SB 35 reinforces standard California Labor Code §1776 recordkeeping requirements.
Contractors must maintain and verify certified payroll records, make records available for inspection upon request, and retain documentation sufficient to support reported wages and classifications.
As seen in similar compliance frameworks, certified payroll alone is not sufficient for audit protection. Contractors should also maintain:
Without these, contractors risk exposure during Labor Commissioner investigations, worker complaints, and potential audits.
Under the pre-2024 version of SB 35, a single objective standard applied broadly across covered projects. SB 423 replaced that with a tiered labor standard based on project size and building height:
Rather than assuming a flat STW threshold applies, contractors need to check a given project against its unit count and building height to determine which labor standards apply. A 12-unit, 3-story project and a 200-unit high-rise can trigger very different obligations under the same law. All subcontractors on a covered project are still required to comply with whichever standards apply.
Developers (and often contractors supporting them) must submit monthly compliance reports to the local jurisdiction and demonstrate adherence to STW requirements.
Failure to comply may result in:
As with other public works frameworks, SB 35 places responsibility on prime contractors to enforce compliance across all tiers. This includes collecting certified payroll from subcontractors, verifying wage rates and classifications, and ensuring proper contract language is in place.
If a subcontractor fails to comply, liability may flow upstream, particularly where oversight procedures are lacking.
SB 35 aligns with broader California apprenticeship requirements:
Noncompliance in this area is a frequent audit trigger and often overlaps with STW requirements.
SB 35 projects may also intersect with:
Core requirement for all covered work. Includes:
If federal funding is involved:
If HUD funding is used:
If a PLA is in place, some enforcement mechanisms (e.g., payroll record provisions) shift to arbitration frameworks instead of statutory enforcement.
Scrutiny under SB 35 enforcement can come through the following forms:
Common audit triggers include:
Penalties can include:
Contractors should approach these projects with a compliance-first strategy:
Compliance under SB 35 requirements layers prevailing wage, workforce requirements, and reporting obligations. Contractors who succeed under SB 35 will be those who build compliance into project workflows early, maintain a well-documented paper trail of proof of compliance, and actively manage subcontractor risk.
As enforcement continues to evolve, partnering with experienced prevailing wage consultants can help ensure your projects stay compliant from bid to closeout. Connect with us to learn how you can get assistance in the compliance process.
blog
blog
blog
blog
blog
blog