Washington's HB 1162 Is In Effect. Healthcare Facilities Without Updated Plans Are Out of Compliance Now.

HB 1162 took effect January 1, 2026, updating Washington's workplace violence prevention requirements for healthcare facilities. Unlike laws with distant deadlines, this one is live — the question for every covered facility is no longer preparation but proof.

The common architecture, Washington's version

Washington's healthcare WPV framework follows the structure shared across state laws: a written prevention plan grounded in facility risk assessment, employee training, incident reporting and recordkeeping, and protection from retaliation for workers who report. HB 1162 is the 2026 update to requirements Washington has imposed on healthcare employers for years.

A state template is not a compliance program

Washington, like California, publishes free model materials — documents to fill in. A template produces a plan; it does nothing to deliver training across shifts, track who attended, or generate the incident and training records that L&I or a union representative can request. The document is the floor. The records are the program.

The proof layer across facilities

Arkvos verifies each training and briefing with photo, GPS, and a record-integrity-timestamped attendance record, gives administrators a live completion dashboard across facilities, and exports the audit record in one click. It is the difference between asserting the training happened and demonstrating it.

Frequently asked questions

When did Washington's HB 1162 take effect?

January 1, 2026. Covered healthcare facilities were required to be in compliance as of that date.

Which states require healthcare workplace violence prevention programs?

As of 2026, active healthcare-specific laws exist in California, Connecticut, Illinois, Louisiana, Maine, Maryland, Minnesota, New Jersey, New York, Ohio, Oregon, Texas, Vermont, Virginia, and Washington. A multi-state health system is almost certainly operating under several mandates simultaneously, each with its own plan, training, and recordkeeping specifics.

Doesn't Washington provide a free workplace safety template?

Yes — Washington publishes model plans and materials, as California does for SB 553. These are fill-in documents. They satisfy the written-plan element but provide nothing for the operational elements: delivering training across shifts, verifying attendance, and maintaining the incident and training records the law requires.

What should a facility be able to produce on request?

The written plan, the risk assessment behind it, incident records, and training records showing which employees completed which training and when. The training records are where paper systems fail — verified attendance with photo, location, and timestamp is the version that withstands review.

Already holding an OSHA citation?

Arkvos offers a free OSHA citation response generator. Upload the citation and get a formal response letter, a corrective action plan with dates, and a checklist of evidence to attach. Employers have 15 working days from receipt of a citation to contest it. Open the free citation responder.

Factual anchors and primary sources

Arkvos separates product capabilities from regulatory requirements. For federal OSHA requirements, the primary authority is OSHA's current regulations and guidance. California construction employers should also review the applicable Cal/OSHA Title 8 requirements.

OSHA 29 CFR 1904.33 requires the OSHA 300 Log, annual summary, OSHA 301 Incident Report forms, and privacy case list if one exists to be retained for five years after the end of the calendar year they cover. Cal/OSHA Title 8 §1509(e) requires construction supervisors to conduct toolbox or tailgate safety meetings, or equivalent, with crews at least every 10 working days. Requirements vary by jurisdiction and work activity, so employers should verify the rule that applies to their facts.

Continue through the Arkvos safety library

Use the topical libraries below to move between product workflows, industries, standards, sourced guidance, and compliance documentation instead of treating this as an isolated page.