Investigations that finish sooner and hold up better.

Logged → Under Investigation → Closed. Reference number, severity, type, date and time occurred, date reported, location with coordinates, and the description — one record everything else hangs from.

Event and immediate-action narratives are scored on capture. A two-line description doesn't proceed to analysis, because an investigation built on one is not worth running.

Injury type, body part, nature and classification; days away, restricted and transferred; return-to-work date; treatment type, facility and physician — the detail statutory forms demand and spreadsheets lose.

Job title, department, supervisor, employment start, and total, company and job-specific experience in months. The factors that turn “an operator made a mistake” into a question worth asking.

OSHA-recordable, OSHA-reportable and MSHA-reportable are properties of the event, decided when it is logged — not remembered later.

Multi-site organisations with a site register and an employee register behind the event.

Each evidence item carries a PEEPO category and subcategory, a title and description, its source and a source reference — so the report shows not just what was concluded but where it came from.

Items receive a quality score and written feedback, and are marked as contributing or not. Completeness across the five PEEPO categories is tracked at investigation level.

Photographs, documents and records attach to the investigation and are carried into the report as a numbered register — the appendix a regulator or a lawyer looks for first.

Witness records with contact detail and statements, held against the event.

A timestamped chronology — each entry categorised, sourced and orderable, with key events flagged. Reconstructing this from memory weeks later is where most investigations quietly fail.

Step by step: what the procedure specified, what actually happened, and the variance named — matched, minor deviation, major deviation or skipped — with an explanation and a contributing-factor flag. Work-as-imagined against work-as-done, in a table.

Absent or failed defences · individual and team actions · task and environmental conditions · organisational factors. Each factor carries a category, subcategory and description.

Every contributing factor is rated for how specific it is and how strongly the evidence supports it, and links back to the PEEPO items behind it. A vague factor cannot hide among precise ones.

Problem statement, the chain, and the resulting cause with its category — plus a depth score, a quality score and a validation pass. A chain that terminates at a person does not score well.

Grounded in Human and Organisational Performance and occupational-health practice, and given the whole investigation record rather than the single field in front of it. AI suggestions are marked as AI-suggested and carry a confidence value. The investigator accepts, edits or rejects, and signs off.

PEEPO completeness, ICAM quality and an overall quality score, alongside progress — visible in the app while there is still time to act on them, and kept off the client-facing report by design.

Recommendations link to the ICAM factors and the 5-Whys chains they address. An action with nothing behind it is visible, and so is a factor nobody did anything about.

Elimination through to PPE, recorded per action — so a finding closed with a toolbox talk is not quietly equivalent to one closed by a design change.

Specific, measurable, achievable, relevant and time-bound are each assessed and rolled into a score. “Improve awareness of the procedure” does not survive the test.

Verification method, the evidence relied on, who verified it and when — recorded against the action.

A dated effectiveness check with a result and notes, distinct from completion. Whether the control actually worked is a different question from whether somebody did the task.

Owner, department, due date, priority and status, in tile, list or kanban views with drag-to-status.

Cover page, document control, contents, people involved, sequence of events, evidence register, ICAM findings with evidence strength, risk assessment, witness accounts, recommendations and a sign-off block — with page numbering and a running confidentiality mark on every page.

Executive summary written for a board rather than a file, lessons-learned, and an action tracker. PDF and PowerPoint.

OSHA 301 · MSHA 7000-1 · RIDDOR F2508 · MHSA section 23 · COIDA WCL-2 · Australian state notification, with the correct state regulator derived from your organisation. Deadlines are stated on the output.

Patterns across investigations rather than one incident at a time — which is where repeat contributing factors become visible.

Identity-provider metadata and certificate, domain verification, just-in-time provisioning, a default role for new users, and enforced-SSO as an option.

MFA with backup codes, per user.

Role-based access with a per-user permission set.

An append-only record of who did what and when, across the investigation.

Row-level security across the application tables — an organisation's investigations are reachable only by that organisation.

Soft deletion throughout. An investigation record is not destroyed by a misclick.

Legal entity and registration, NAICS and SIC, employee and contractor counts, average hours worked, regulatory identifiers, insurer and policy, and a named regulatory contact.

There is no self-serve public API today. Exchange with an existing EHS platform is a scoped export and import contract, built per integration. Not SOC 2 or ISO 27001 certified.

Companion apps for field capture are in build and not in service today. The web application is responsive and works on a phone browser; anything beyond that is roadmap, not product.