SB 291 directs the Contractors State License Board (CSLB) to deliver an annual report, due October 1 each year, containing detailed statistics on complaints, investigations, citations, referrals, disciplinary actions, interim orders, cost recovery, and case‑aging metrics for the prior fiscal year. The statute specifies the categories, breakouts, and performance measures the board must include.
The requirement gives the Legislature a standardized, recurring data set to evaluate CSLB performance, identify enforcement bottlenecks, and monitor the incidence of particular violations. For CSLB and regulated parties, the statute converts enforcement activity into quantifiable public performance metrics — with implications for resource allocation, oversight, and public transparency.
At a Glance
What It Does
The bill requires CSLB to submit a single annual report (due October 1) covering the prior fiscal year that enumerates complaints by source and type, closures and reasons, citations and disciplinary actions (including specific statutory violations), referrals to prosecutors and the Attorney General, interim and restraining orders, cost recovery, and detailed case‑aging averages for key enforcement steps.
Who It Affects
CSLB must compile and publish the data; licensed contractors, registered home improvement salespersons, and unlicensed persons acting as licensees will appear in the report; the Attorney General and local prosecutors are named as recipients of referral counts; Legislature and oversight committees gain the primary users of the report.
Why It Matters
The statute turns previously fragmented enforcement activity into a uniform dataset the Legislature can use to evaluate backlogs, staff productivity, and enforcement outcomes. That transparency can shape budget decisions, prompt policy changes, and create reputational effects for regulated parties.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
SB 291 imposes a reporting obligation on the Contractors State License Board to produce a comprehensive annual enforcement report summarizing the prior fiscal year. The report must break complaints down by source (for example, consumers, trade groups, government) and by type (licensee versus nonlicensee), and must enumerate how complaints were resolved before and after field investigation with stated reasons for closure such as settlement or arbitration referral.
The bill requires CSLB to publish per‑staff productivity figures: the total number of complaints closed by consumer services representatives in the Intake/Mediation Center and the number closed by investigators and special investigators in the Investigation Center, as well as a separate count of complaints closed by other staff. It also mandates a snapshot of pending caseloads grouped into 90‑day age buckets with percentages, which makes backlog dynamics visible rather than opaque.Enforcement outputs must be reported in detail: counts of citations (by type and whether vacated/withdrawn), the number and type of disciplinary actions (including a specified call‑out for violations of Section 7125.4), citations involving particular statutory provisions, referrals to local prosecutors and the Attorney General, the number of interim suspension orders and temporary restraining orders sought and granted, and monetary cost recovery amounts ordered and collected.Finally, the statute standardizes case‑aging metrics by demanding average days for six discrete intervals in the enforcement lifecycle — from intake closure pre‑investigation through registrar final decisions after proposed administrative rulings — which creates a common way to monitor timeliness across stages and over time.
The Five Things You Need to Know
CSLB must file the annual report by October 1 for the prior fiscal year; the report is structured and prescriptive rather than discretionary.
The report must list complaints by source and type and specify closures both before and after field investigations with categorized reasons (e.g.
settled, referred to arbitration).
CSLB must report productivity metrics per staff: complaints closed per consumer services representative in Intake/Mediation and per investigator and special investigator in Investigation, plus counts closed by other staff.
The bill requires detailed case‑aging averages for six enforcement stages (intake closure pre‑investigation; investigation closure; referral to Attorney General; AG filing of accusation; time from accusation to hearing/settlement; time from proposed decision to registrar final decision).
The report must enumerate citations and disciplinary actions (including counts tied to specified code sections), referrals to prosecutors and the Attorney General, interim suspension and TROs sought/granted, and amounts of cost recovery ordered and collected.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Mandatory annual reporting requirement and scope
This opening paragraph makes the report an annual statutory duty and ties the reporting period to the prior fiscal year with a fixed submission deadline of October 1. Practically, that obligates CSLB to maintain fiscal‑year aligned records and to schedule internal workflows so data can be validated and aggregated in time for the legislative date.
Complaint classification and closure reasons
These subsections require CSLB to quantify complaints by source (public, trade, government, board‑initiated) and by type (licensee or nonlicensee), and to report counts for complaints closed both before and after field investigations with explicit closure categories such as settled or referred to arbitration. For administrators, this means standardizing intake and investigation categorizations and capturing closure reasons reliably at the point of case disposition.
Per‑staff productivity and pending case age buckets
CSLB must produce per‑staff closure totals for the Intake/Mediation Center (per consumer services representative) and Investigation Center (per investigator/special investigator), plus a tally of closures by other staff. The board must also report pending complaints segmented into 90‑day increments and show each segment as a percentage of total pending cases. Those metrics enable comparisons of individual unit throughput but create a need to decide how to attribute mixed‑action cases or shared responsibilities.
Citations, disciplinary counts, and referrals (with statutory call‑outs)
This cluster requires counts of citations issued to licensees and nonlicensees (including vacated/withdrawn counts), detailed numbers of disciplinary actions (with differentiation by initiating instrument such as accusation or failure to comply with citation or arbitration), and explicit counts for violations of named code sections (7121, 7121.5, 7159.5(a)(5), and a separate call‑out for 7125.4). It also asks for counts of referrals to local prosecutors and the Attorney General. Operationally, that forces caseworkers to tag matters to specific statutory provisions at closure.
Interim actions and cost recovery
The bill demands counts of interim suspension orders and temporary restraining orders sought and granted, plus dollar amounts for cost recovery ordered and collected. These measures capture emergency enforcement and financial remedies, which can be politically salient to consumers and legislators monitoring deterrence and restitution.
Case‑aging averages for six enforcement stages
The statute prescribes six average‑day metrics covering intake closure pre‑investigation through registrar final decision after an ALJ proposed decision. Because each average corresponds to a distinct handoff or decision point, CSLB must implement or refine time‑stamp practices and ensure coordinated data flows with the Attorney General when cases cross agencies.
This bill is one of many.
Codify tracks hundreds of bills on Government across all five countries.
Explore Government in Codify Search →Who Benefits and Who Bears the Cost
Every bill creates winners and losers. Here's who stands to gain and who bears the cost.
Who Benefits
- Legislative oversight committees — gain a standardized, annual dataset to evaluate CSLB performance, identify bottlenecks, and make funding or statutory recommendations.
- Consumers and consumer advocates — receive better visibility into complaint volumes, outcomes, and timelines, which strengthens public accountability and comparative assessments of board responsiveness.
- CSLB management — receives structured performance metrics that can be used to justify resource requests, redesign processes, or target training to units with high backlog or low throughput.
- Policy analysts and researchers — get consistent, year‑to‑year data enabling trend analysis on enforcement outcomes, prevalence of particular statutory violations, and the efficacy of remedies like interim suspensions and cost recovery.
Who Bears the Cost
- Contractors State License Board — must absorb the administrative, IT, and staffing costs of data extraction, validation, categorization by statutory provision, and report production on an annual schedule.
- Local prosecutors and the Attorney General — may face increased or more visible referral counts that require review and potential prosecutorial resources, especially if reporting spurs enforcement pushback.
- Licensed contractors and registrants — face greater public exposure of enforcement activity and statistical trends that could influence contractor reputations and market‑level scrutiny.
- State budget/administration — if CSLB requires system upgrades or additional staffing to meet reporting detail, the Legislature may need to fund those changes, creating fiscal implications.
Key Issues
The Core Tension
SB 291 pits transparency and oversight against administrative cost and potential metric‑driven behavior: the Legislature gains granular data to hold CSLB accountable, but producing that data reliably will require investment, careful methodological choices, and safeguards to prevent perverse incentives that prioritize favorable numbers over thorough, merit‑based enforcement.
The statute promises transparency but leaves significant implementation choices to CSLB. The board must decide how to tag complaints to the many required categories (by source, type, statutory violation, closure reason) and how to attribute closures to individual staff members in cases that involve multiple touchpoints.
Those operational decisions will materially change what the report shows and how comparable year‑to‑year numbers are. The requirement to calculate averages across discrete stages forces better time‑stamping of events but also creates incentives to optimize for metrics rather than substantively resolving cases.
There are unanswered questions about data handling and public access. The bill requires counts and averages but does not prescribe format, minimum cell sizes to protect privacy, or whether the report will be published in machine‑readable form.
Statistical releases that fail to anonymize identifying details can expose complainants or small businesses; conversely, over‑aggregation reduces the report’s usefulness. Finally, the statute calls for counts tied to specific code sections without defining processes for multi‑violation cases, which could inflate counts if one case is tallied under several sections or mislead readers about distinct enforcement actions.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.