A checklist does not satisfy §6401.9(c)(2)(G) and (H). The law requires a hazard assessment for each worksite and prompt correction with proof that the fix worked.
Subilu records every hazard from trigger through correction to verified close. Each hazard has a category, a source, a task with a due date, and a verification note that proves someone checked the work. That chain is what inspectors ask to see.
Before: a clipboard and a hope
You walk the site, check a few boxes, file the sheet. The register still faces the window. The back door still sticks. The night crew still works alone. Nothing ties observation to fix. No owner, no date, no verification. When Cal/OSHA asks how you corrected it, you point to the checklist and the conversation stops.
After, the hazard is a record with a site, a category, a source, and a status that moves from identified to closed. The correction is a task with an owner and a due date tied to severity. High gets 7 days, medium 30, low 90.
The bridge is Subilu hazard tasks. One flow connects assessment, assignment, and verified close.
Triggers that create a hazard record
§6401.9 expects more than one way to find hazards. Subilu uses four sources plus employee identified reports.
| Trigger | When | Example |
|---|---|---|
| Scheduled | Cadence, default 365 days per site | Quarterly walk of doors, lighting, sight lines |
| Incident | A violent incident is logged | Type 2 threat at register creates hazard for that layout |
| Employee report | Anonymous tip or direct report | Closer reports no escort to parking lot |
| Deficiency | Review finds a gap | Investigation notes camera blind spot |
Employee identified is not optional. §6401.9(c)(2)(B) requires active involvement. Subilu captures it through the anonymous tip portal. Staff submit without a login, the tip becomes a hazard with source employee_report, and that hazard links to a correction task.
Correction anatomy: task to verified_closed
A hazard without a correction is an open finding. In Subilu, correction is a task tied to the hazard.
- Task created from evaluation, with assignee, due date, and description.
- Work completed, with a completion note.
- Verification by a second person, status becomes verified_closed only after a verification note.
High and critical require verification by default. The note is timestamped and attributed, so you can show who confirmed the fix and when.
How participation feeds corrections: survey to hazard to task
Inspectors ask employees if they helped identify hazards. A signature page does not satisfy §6401.9(c)(2)(B).
The loop is survey to hazard to task. Staff submit through the tip form, that report becomes a hazard with source employee_report, the hazard is evaluated, then a correction task is created and assigned. Employees see only that the report was received and addressed, no exposed names. At annual review, each correction row traces back to a report, not a manager invention.
Cadence vs annual
Annual is the minimum. §6401.9(c)(2)(J) requires an annual WVPP review, but hazard assessment runs on events and on schedule. Subilu sets inspection cadence per site, default 365 days, and you can shorten it for high risk sites.
Review outside the calendar when:
- A violent incident occurs
- An employee report suggests a new hazard
- A deficiency appears during inspection
- Operations change, like new hours or layout
If you only assess once a year you will miss the hazards the statute says to catch promptly. Subilu flags overdue inspections and corrections, so nothing sits past due unnoticed.
Check one site this week. List its last three hazards, their sources, and status. Any row stuck on identified or in progress without an owner and date is your next task.
Not legal advice. Source: Labor Code §6401.9(c)(2)(G), (H) and (J) and DIR WVPP guidance. Pair with Your WVPP in 21 Sections.