Workplace Safety Incidents: A Quarter of Dispositions That Change Only for a Reason

Every incident classified once, and reclassified only for a reason

A quarter of safety incidents has to end with one disposition per incident. A first aid case stays off the recordable count, a medical treatment or lost time case goes on it, an injury to a subcontractor's worker is routed to that contractor's own report, and a second report of the same event is marked as a duplicate of the first. Lost days follow the class. The order of the rules matters, because one incident can match more than one.

Incidents live in a SharePoint list, corrective actions are ClickUp items, incident forms and photos are filed in Box, and the policy and every notice for the quarter sit in a Drive folder. Site leads ask questions by email and the field posts in Slack. The first pass is not the hard part. The hard part is the stream of notices that each change one field and should leave every other field exactly where it was.

Who works in the room

Anything about an incident's class, disposition or lost days goes to Ada, the safety room's default agent. Myco owns the draft report, the corrective actions and the site lead threads. When Ada finishes re-running a batch, it hands any incident a site lead has asked about to Myco in the same thread, and Myco drafts the reply on that lead's existing email thread rather than starting a new one.

From first disposition to quarter close

The precedence list and recording rules are in the run folder and in the room guidelines, so Ada and Myco apply the same order. Every write to SharePoint or ClickUp waits for the safety manager.

Notices that change one field and leave the rest alone

Each notice in the quarter has a narrow scope, and most of the care goes into keeping it narrow. A site boundary correction moves eleven incidents from one site to its neighbor, and that is all it does: no disposition changes because of it. A corrective action closure changes the status of each named ClickUp item and the matching status on the incident, and nothing about the incident's disposition, lost days or site. Ada states the scope in the thread before proposing any change, and the safety manager approves against it.

The medical update and the hotline cross-reference work the other way. They change what an incident is, so each named incident is re-run against the full precedence list rather than patched in place. A site lead who asks why an incident dropped off the recordable count gets one reply on the thread they opened, with the incident number and the hotline reference now on file. Every agent turn that wrote to SharePoint keeps its run history, which is what the safety manager opens when a count is questioned.

What the checks catch

• A disposition changed during a site boundary correction, when the notice only moves the site field
• A corrective action closure that also edited lost days or the disposition of the linked incident
• A spot-check report line for an incident outside the nine named, which comes off whatever it says
• A class upgrade patched on the class field alone, without re-running the incident against the full precedence list
• A reply to a site lead started as a new email instead of on the thread the lead opened

What stays with people

• Approving every disposition and field change before SharePoint or ClickUp is updated
• Deciding classification questions the precedence list does not settle
• The reply to each site lead, which Myco drafts on the lead's thread and the safety manager sends
• Signing the quarter and its per-site reports

Integrations in this workflow

Kylon is not an EHS management system, and it does not take the place of one. It sits across the safety desk's tools and holds the coordination between them.

• Box
• ClickUp
• Gmail
• Google Drive
• SharePoint
• Slack

• SharePoint holds the incident list with class, disposition, lost days, site and duplicate reference
• ClickUp tracks corrective actions and the per-site report items created at close-out
• Box holds incident forms, photos and witness statements
• Gmail carries replies on site lead threads, each one sent by the safety manager
• Google Drive keeps the precedence list, the quarter's notices and the draft incident report
• Slack is where superintendents and foremen outside the room post updates from site

Where to start

One quarter is the natural first cycle. Connect the SharePoint list that holds your incidents, and write one rule into the room guidelines: every notice states which fields it may change, and the safety manager approves each change against that scope.

“Each notice changes what it says it changes, and the thread shows that nothing else moved.”

Set it up with your agent

Open a new Room, add your agent and paste this prompt. It connects the tools, builds the App with you and asks for your rules one step at a time, and nothing goes out until a person approves it.