Labor Code §6401.9 + draft Title 8 §3343

Eight Changes in the New Section 3343 Draft — Two Change Your Plan

Cal/OSHA's September 2026 Section 3343 draft revises eight provisions. Two change what your prevention plan actually has to do. Here they are.

The September 2026 draft revises eight provisions of the proposed Section 3343; the most consequential change deletes the subjective “adequately addressed” standard.

Both of the changes that matter are credited to stakeholder comment, and both touch what your prevention plan actually has to do: how a hazard report escalates, and how you investigate what happened. The other six are cross-references, a typo fix, and alignment wording. Useful signals about where the draft is maturing, not rebuild triggers.

Draft standard, enforceable statute
§3343 is a draft standard. Labor Code §6401.9 is the law, and has been enforceable since July 1, 2024. Build to the statute now; treat §3343 as a forward-looking overlay that will change your plan's specificity, not its existence.

Before: what the July 22 draft said

The July 22, 2026 draft was open for written comment through August 17, 2026 to rs@dir.ca.gov. That window has closed. On escalation, it told supervisors to escalate a hazard report when the responsible person “has not adequately addressed the hazard.” On post-incident response, it framed the investigation around what caused the incident. Both are the kind of language that gets argued about during an inspection instead of settled by a record.

The two changes that reshape your plan

§3343(c)(6)(A): from subjective to checkable. The July text read “has not adequately addressed the hazard.” The September text reads “has not responded to the report as required by subsection (c)(4).” The Division’s stated rationale, verbatim from the revision notes: “based on stakeholder comments that ‘adequately addressed’ is not defined and subjective.” That converts a soft, litigable obligation into a dateable one. Someone did or did not respond to the report by the required step. Your escalation procedure should name the response step, not the judgment.

§3343(c)(11): multi-factor causation. The September draft adds “the cause of the incident conditions and factors that contributed to the incident” and “if any measure would have prevented the incident.” Stated rationale: “based on a stakeholder comment to treat incidents as the product of multiple contributing factors rather than a single proximate cause.” This reshapes the post-incident investigation template directly: you are no longer writing one root cause, you are recording contributing conditions and answering a prevention counterfactual.

Two edits that survive any final text
1. Escalation procedure: replace "adequately addressed" thinking with a named response step and a clock. 2. Investigation template: add a contributing-factors section and the question "would any measure have prevented this?" Both patterns are good practice under §6401.9 today and required under the draft as written.

All eight revisions, side by side

The Division’s own redline key: regular text is the July 22 draft, underline is additions, strikeout is deletions. One row per revision note, verbatim rationale in column four.

ProvisionBefore — July 22 draftAfter — September draftStated rationaleWhat it means for you
(b) designated representativeNo cross-referenceAdds "as defined in section 3203"Stakeholder comment: clarify 'written authorization' and align with section 3203Point your authorization form at the §3203 definition if you have union-represented staff
(b)(9) work practice controls (A)"based on the identification and evaluation of workplace violence hazards" (plus a duplicated phrase)"employer's workplace violence hazard assessment required by subsection (c)(9)"Stakeholder comment: align with the language in subsection (c)(9)One hazard-assessment reference now drives the controls definition — keep them cross-linked
(c)(6)(A)"has not adequately addressed the hazard""has not responded to the report as required by subsection (c)(4)"Stakeholder comments: 'adequately addressed' is not defined and subjectiveRewrite your escalation procedure: the trigger becomes a missing response, not a judgment call
(c)(11)Post-incident procedures framed around a single proximate causeAdds the conditions and factors that contributed to the incident, and "if any measure would have prevented the incident"Stakeholder comment: treat incidents as the product of multiple contributing factors rather than a single proximate causeRewrite your investigation template: a factor list plus a prevention counterfactual question
(c)(12)Plan review cadence wordingWording adjusted for consistencyStakeholder comment: maintain consistencyNo operational change once your review cadence matches subsection (c)
(d)(3)(B)Cross-reference to "(b)(68)(C)"Cross-reference correctedMade to correct a typoNone — a proofread draft, nothing more
(e)(1)(E)Training content not tied to records accessTraining aligned to records access in subsection (f)(7)Stakeholder comment: align the training requirement with access to records in subsection (f)(7)Add "how employees obtain copies of records" to your training outline
(f)(4)(B)References "designated representatives as defined in section 3204"Section 3204 reference deletedStakeholder comments: a reference to section 3204 is not necessaryNone — one fewer cross-reference to maintain

After: what the September draft is

A redline against the July 22 draft. Its header reads, verbatim: “Workplace Violence Prevention in General Industry – Draft September 2026 / Draft revisions compared to July 22, 2026 draft.” Seven of the eight notes are credited to stakeholder comment; one, (d)(3)(B), is a typo fix.

Two of the eight are cleanups: the (d)(3)(B) typo and the (c)(12) consistency wording. They are worth noticing precisely because they are boring: a draft that is fixing duplicated phrases and cross-references is being proofread, which is what a maturing document looks like.

There is no comment deadline. The September draft has no milestone block of its own on the advisory index page; it appears only as an attachment inside the October 27 meeting block. The only stated deadline on the page is the July 22 draft’s August 17, 2026, which has passed. The live channel is the monthly OSHSB public comment period.

Bridge: what to change in your plan

Nothing is enforceable, so don’t rebuild around draft language. Do this instead:

  1. Make the two template edits above: escalation response step, multi-factor investigation. Both are defensible under §6401.9 today and unavoidable under the draft.
  2. If you have union-represented staff, align your designated-representative authorization language with the §3203 definition the draft now points at.
  3. Make sure training covers how employees obtain copies of records. (e)(1)(E) aligns training to (f)(7), and record access is already a statutory right within 15 calendar days.
  4. Keep running the current law clean: plan, log, training records, hazard identification and correction records.

Earlier draft? Read this next

Coming from the July round?
This post supersedes our July analysis in substance, not in status. The July 22 draft post stays up for reference and URL equity: [SB 553 Permanent Standard: July 2026 Draft Changes](/blog/sb553-july-2026-draft-changes). Its comment window closed August 17, 2026. For the full rulemaking picture, start at the [Section 3343 rulemaking timeline](/blog/sb553-section-3343-rulemaking-timeline).

September draft questions, answered

What changed in the September 2026 draft? Eight provisions. Seven credited to stakeholder comment, one typo fix. Two change operations: (c)(6)(A) and (c)(11).

Is there a comment deadline? No. Monthly Standards Board public comment is the live channel; the July round’s August 17 deadline has passed.

What is a designated representative? Someone authorized in writing to act for your employees. The draft adds a §3203 cross-reference to pin down “written authorization.”

Does the draft change my training requirements? Not yet. (e)(1)(E) would tie training to records access in (f)(7). Today’s duty is §6401.9(f): initial, annual, and on changes.

How many drafts has Cal/OSHA issued? Eight versions: 2018, 2018, 2022, July 2024, May 2025, April 2026, July 2026, and the September 2026 redline.

Make the two edits →

Not legal advice. Revision notes and draft status per DIR's advisory page and the September 2026 discussion draft attached to the October 27 agenda. Quote the draft text itself before relying on any provision. Next: the full rulemaking timeline.

See your WVPP built in 10 minutes

One demo. Your site-specific plan, scrubbed log, and training proof — ready to hand over.

jamie@yourshop.com Get a demo →