Hazards numbered, incidents owned.
Versioned, signed-off risk assessments and a full incident pipeline on one thread: every hazard rated and controlled, every event investigated to root cause, every corrective action a real task. Nothing closes until the work that prevents the next one is done.
What is Bulk Safety & Incidents?
Bulk Safety & Incidents is the safety layer of Bulk's manufacturing operations software. Versioned, signed-off risk assessments and a full incident pipeline sit on one thread: every hazard rated and controlled, every event investigated to root cause, and every corrective action a real task. Nothing closes until the work that prevents the next one is done.
Every assessment, placed by its worst residual.
Live risk assessments roll up into a likelihood × severity heat map, each sitting in the cell of its single worst controlled risk. Hover any cell to see exactly what's there. The corner you don't want anything in is the corner you can actually watch.
Rate it, control it, watch the risk drop.
Each control measure carries the risk before controls and the residual after, so the document shows its own work. Numbered and versioned, run through approval, sent for forced sign-off, and re-reviewed on a schedule. An AI assistant drafts the measures; a human confirms every one.
A welding repair six metres from stored solvent: exactly the job risk assessments exist for. Three hazards, each rated before and after controls.
Report it, investigate it, and prove you fixed it.
A four-stage report mints a numbered incident; the investigation runs the same root-cause toolkit as Quality. The corrective actions don't just get written down: each becomes a linked task, and the incident physically cannot close until they're resolved. INC-042 below is live: two tags are still holding the gate. Resolve them, then try the close.
Guard interlock bypassed in Cell 3
Is this machine cleared to run?
Each asset's pre-use checks decide one thing: can production start. Ready means cleared, blocked means a check is outstanding, override means a manager took responsibility on the record. One read tells the floor what's good to go, backed by the audits engine.
Safety that leaves a trail.
residual
sign-off
til fixed
blocked
Safety doesn't sit in a binder.
Risk and incidents reach into the modules that resolve them: corrective actions become real work, investigations share Quality's toolkit, and readiness rides on the audits engine.
Tasks & Projects
Corrective actions and risk-measure controls become linked tasks that gate incident closure.
Quality
Incident investigations run the same fishbone, 5-Why and root-cause suite as quality.
Audits
Pre-use checks and asset readiness are a live read over the audits engine and its executions.
People
Reporters, witnesses, reviewers and signers all resolve to real employees and departments.
Teamboards
The risk matrix, incidents, pending approvals and review calendar feed the SQDCP boards.
AI Assistant
Drafts a task description and risk measures for an assessment. Every write is human-confirmed.
Questions, answered.
What is Bulk Safety & Incidents?
It keeps risk assessments and incidents on one thread: hazards are rated on a likelihood × severity matrix and controlled, events are investigated to root cause, and every corrective action becomes a real task.
Do I have to replace my ERP to use it?
No. Safety & Incidents is one module of Bulk's manufacturing operations software and connects to the rest of the floor, so your system of record stays where it is.
How is risk rated?
Every hazard is scored on a likelihood × severity matrix, and each control measure shows the risk both before and after — the initial rating next to the residual — so the document proves its own value.
How does an incident get closed?
Corrective actions become tasks, and the incident can't close until every one of them resolves — so an event only closes once the work that prevents the next one is done.
Are risk assessments controlled and signed off?
Yes. Assessments run through an approval workflow with revisions and scheduled reviews, and a blocking sign-off on the active revision means the current version is always the one in force.
How do you know an asset is safe to run?
Pre-use checks decide whether an asset can start, so its readiness — cleared to run or blocked — is visible at a glance.
Run one real incident end to end.
We'll take one event from your floor and walk it the whole way, report to root cause to corrective tasks to a clean close, so you can see the trail it leaves behind.