A worker files a quick notice (PIN) in their own words. An admin reviews it, sends a Flash to the people who need to know, then runs the investigation with root causes, corrective actions and a sign-off chain, with every step dated and on the record.
A quick notice: what happened, where, who, and photos. It is your own account in your own words; nothing suggests causes. Vehicle incidents ask for collision information; Security incidents can list stolen items.
Where: FieldView → Report an Incident
Who can: Everyone (Report an Incident is on by default)
Every incident you've been picked to work on: where you're lead investigator, sign-offs where it's your turn, and claims you own. The lead investigator can save the investigation without Incidents access.
Where: Report an Incident → Investigations
Who can: Lead investigators, reviewers
What you filed, with its progress: Received → Reviewed → Action → Closed. Once fixed, tap Looks fixed or Still a problem.
Where: Report an Incident → My incidents
Who can: Everyone
Every incident with multi-select filters, a Deadlines column and filter, D&A and cost-range filters, sorting on any column and export.
Where: Dashboard → Incidents → Submitted incidents
Who can: Incidents: View
An incident starts as the PIN. Review it before anything goes out; the reviewed PIN is what the Flash attaches.
Where: Incident → Review
Who can: Incidents: Edit
Some companies only want a notification when a PIN is filed. Switch the Flash approval process off and the Flash, its review step and its deadline are hidden; the PIN notification still goes out. On by default.
Where: Incidents → Settings → Deadlines
Who can: Incidents: Edit
The default Flash list pre-fills the recipients; you pick the final list and which photos go in. It attaches the reviewed PIN as a PDF marked preliminary, and keeps exactly what was sent in the Flash history. Send another when there's news.
Where: Incident → Flash panel
Who can: Incidents: Edit
Three clocks from the PIN: Flash (4 h), preliminary investigation (48 h, Mark preliminary complete) and final investigation (7 days, sent for review). Yellow, orange, red, green when met.
Where: Incidents → Setup → Deadlines
Who can: Change: Incidents Edit
Classification, status, lead investigator, vehicle cost range then estimated and final cost, and Drug & alcohol (D&A) form completed: Yes, No or N/A.
Where: Incident → Details
Who can: Incidents: Edit
Add each person and their involvement. For an injury, pick the body part and how it happened from one standard list. A Contributor gets a Competency step: tickets, training, SWPs and orientation as they stood on the day.
Where: Incident → People
Who can: Incidents: Edit; injury detail needs View Injury & Claim Detail
Attach company assets. Collision information from the PIN shows as a third-party vehicle. Stolen items on a Security incident, tied to a real asset when there is one, are also listed under Stolen assets.
Where: Incident → Assets
Who can: Incidents: Edit
Tick the causes you found, then Done — check against the record: up to five questions about what the record shows. Root cause cards read What happened → Why → Root cause, each with its fix.
Where: Incident → Root Cause
Who can: Incidents: Edit
The cause lists investigators pick from, managed for the company.
Where: Incidents → Setup → Incident Causation Models
Who can: Manage Incident Causation Models right
Every fix is an ordinary action item linked to the incident (and its root cause), shown on the Actions tab and in the Action Items register.
Where: Incident → Actions
Who can: Incidents: Edit
Reviewers added and ordered per incident. Each signs in turn; nobody can sign before the stage ahead of them, and that order is enforced by the server.
Where: Incident → Review → Sign-off flow
Who can: Add reviewers: Incidents Edit
Drag in several files at once. Download all photos gives one zip; Select → Remove selected takes photos off.
Where: Incident → Supporting docs
Who can: Incidents: Edit
Link the incident to a workers' comp claim from its Claim tab. The Case timeline tab lays out what happened, in order (Enterprise).
Where: Incident → Claim / Case timeline
Who can: View Injury & Claim Detail
Who is told when a PIN is filed (people, positions), and who hears when someone goes on light or modified duty or is cleared.
Where: Incidents → Setup → PIN Notifications / Modified Duty Notifications
Who can: Incidents: Edit
The investigation record as PDF or Word, built from the same data as the screen.
Where: Incident → Download
Who can: Incidents: View
Delete this record permanently removes an incident. There is no undo; recovery is from a backup through support.
Where: Incident → Delete this record
Who can: Company Admin