SB 328 directs the Department of Toxic Substances Control (DTSC) to provide written notice to sponsors of housing development projects when they submit requests that trigger DTSC oversight of investigation, characterization, or remediation work. The bill frames that notice as the department’s formal communication of subsequent review actions and any additional information required to begin or continue review.
For developers, local agencies, and environmental consultants, the measure aims to reduce procedural uncertainty that can delay housing projects by forcing DTSC into a predictable notice cycle tied to project submissions. It does not convert those notices into binding final approvals; instead, it structures the review dialogue between DTSC and project proponents so both sides know what the next steps are and when the department will respond.
At a Glance
What It Does
The bill requires DTSC to issue written notices that identify the next review actions and information needs after a housing‑related oversight request. The statute ties the department’s responsiveness to a schedule that varies with project scale and mandates continuing, cyclical review of subsequent submissions.
Who It Affects
Housing developers seeking DTSC oversight for cleanup and remediation activities, local planning agencies processing post‑entitlement permits, environmental consultants preparing cleanup applications, and DTSC staff responsible for intake and review are directly affected.
Why It Matters
By formalizing initial and follow‑up communications, the bill aims to make remediation review timelines more predictable around housing projects—a common choke point for entitlements—while preserving DTSC’s technical review discretion.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
SB 328 creates a structured intake-and-notice process when a housing development project seeks DTSC oversight for any phase of site investigation or cleanup, or when a post‑entitlement permit deemed complete by a local agency requires DTSC input. At intake the department must issue a written notice that tells the requestor what next steps DTSC will take and flags any additional information the department needs before review can proceed.
After DTSC issues that notice, the requestor provides the additional materials to DTSC within whatever timeframe DTSC specifies. Each time the requestor submits new materials, DTSC must continue the review cycle: examine the submission, identify any further relevant information, and send another written notice that describes subsequent actions or needed items.
That creates a predictable loop of submission, written response, and further submission until DTSC reaches a technical conclusion or the parties otherwise resolve outstanding matters.The bill’s scope covers oversight activities connected to housing development projects and any interim steps needed to reach a DTSC determination—so it captures workplans, assessments, cleanup programs, and requests for closure letters in the course of entitlement work. It leaves DTSC’s substantive technical judgment intact; the statute structures communications and response expectations rather than dictating remediation outcomes.
The department must follow applicable statutory authorities when implementing the process.SB 328 also defines the covered terms and ties the procedure into existing local‑agency permit workflows. The result is a statutory overlay that forces a transparent paper trail at each intake stage, which will matter operationally for how developers sequence entitlement, remediation contracting, and financing during project delivery.
The Five Things You Need to Know
For intake notices, the bill sets two size‑based response windows: DTSC must provide the required written notice within 60 business days for housing projects of 25 units or fewer, and within 120 business days for projects of 26 units or more.
The statute explicitly lists covered request types: voluntary cleanup agreements, prospective purchaser agreements, agreements under the California Land Reuse and Revitalization Act of 2004, requests for approval of completion of site mitigation, requests for Affirmation of No Further Action or No Further Remedial Action letters, and any interim steps necessary for those determinations.
When seeking information under this section, a requestor must provide any site history they have, including known prior ownership of the property.
The bill requires DTSC to continue reviewing each submission and to provide written notice of subsequent actions or additional information required for each new submission (i.e.
it formalizes iterative review cycles rather than a single intake pass).
SB 328 permits DTSC to implement the process using its statutory authority under Division 45 of the Health and Safety Code or the California Land Reuse and Revitalization Act of 2004.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Scope — which requests trigger the procedure
Subsection (a) casts a broad net: it applies whenever a housing development project submits a request that initiates DTSC oversight of investigation, characterization, or remediation activities, and it also applies to post‑entitlement phase permits deemed complete by a local agency that require DTSC response. Practically, that means the procedural obligations follow both formal cleanup‑agreement filings and the administrative permit steps that happen late in entitlement.
Notice content — what DTSC must tell the requester
Subsection (b) requires DTSC to provide written notice identifying subsequent actions in the review process and any additional information needed to begin substantive review. The phrase ‘subsequent actions’ is functional: the notice must let a developer know whether DTSC will screen the site, request a work plan, require an assessment, or take other steps that materially affect the schedule and scope of work.
Response windows tied to project size
Subdivision (c) creates time‑bound windows for DTSC to issue the written notice after intake and differentiates those windows by project scale. The statutory approach recognizes that resource needs scale with project size and attempts to operationalize that difference into predictable administrative timing.
Iterative review and requester obligations
Subdivision (d) governs the back‑and‑forth: DTSC identifies additional information, the requestor submits the materials within a department‑set timeframe, and DTSC must then respond again in the same staged manner. Importantly, the bill leaves the requestor’s response deadlines to DTSC, so compliance hinges on the department’s internal practices for setting those timeframes and tracking submission cycles.
Information duties, limits on process, and definitions
These subsections require requestors to provide any information they possess about site history and set out basic boundaries for the process—clarifying that the statute does not cap DTSC’s ability to comment or require a final determination within the notice windows. The provision also supplies working definitions for ‘department,’ ‘housing development project,’ ‘local agency,’ and ‘postentitlement phase permit,’ anchoring the procedure to existing statutory terms so agencies and practitioners can map responsibilities to familiar concepts.
Authority to implement and operability
The statute directs DTSC to use available statutory authority when implementing the process and sets the section’s operability date several years after enactment. That delayed operability gives DTSC time to adjust intake workflows and develop procedures, but it also places a deadline on implementation planning at the agency level.
This bill is one of many.
Codify tracks hundreds of bills on Environment across all five countries.
Explore Environment 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
- Housing developers and project sponsors — Gain clearer procedural expectations at intake, which helps sequence remediation work, entitlement milestones, and lending conditions.
- Local planning agencies — Obtain predictable DTSC responses for post‑entitlement permits, smoothing coordination during permit issuance and reducing hold‑ups tied to environmental technical reviews.
- Environmental consultants and remediation contractors — Benefit from a formalized communication cadence that clarifies what deliverables DTSC expects and when, aiding project scoping and staffing.
Who Bears the Cost
- Department of Toxic Substances Control — Must adapt intake workflows, track business‑day response windows, and sustain iterative review cycles; implementation will consume staff time and may require new case‑management systems.
- Developers and consultants — Face administrative overhead to meet repeated submission cycles and to respond to department‑set deadlines for follow‑up information, potentially increasing consultant fees and project management costs.
- Local agencies and permitting staffs — May need to coordinate more closely with DTSC and manage permit schedules around the department’s written notices, complicating local permit timelines and staffing.
Key Issues
The Core Tension
The central dilemma is between predictability and completeness: the bill forces DTSC to be predictable about what it will ask for, which helps developers plan, but it preserves agency discretion over the technical review and the cadence of follow‑ups—so faster initial responses can still lead into open‑ended, iterative cycles that delay final decisions.
SB 328 solves a common procedural problem—unclear agency responses at intake—by creating a formal notice cycle, but that fix creates trade‑offs. The statute prescribes response windows for DTSC but leaves other critical timelines (notably the requestor’s response deadline) to be set by the department, which means predictability depends on DTSC’s implementation choices.
If the department sets short turnaround windows for requestors, developers may struggle to assemble high‑quality technical submissions quickly; if the department sets long ones, the statute’s goal of speeding projects will be undermined.
Another tension arises from codifying iterative review without converting notices into final agency action. The written‑notice framework increases transparency but also institutionalizes a repeated exchange that can lengthen the overall calendar if not managed to closure.
Finally, the bill requires DTSC to rely on existing statutory authority for implementation and delays operability, which gives the agency flexibility but also transfers implementation risk: the success of the policy will hinge on DTSC’s staffing, intake procedures, and resource allocation rather than on the statute alone.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.