Incident reporting and investigations

Incident reporting only works if the follow-up is visible

Reporting an accident, near miss or unsafe condition is only the first step. The value comes from investigation, action ownership, evidence and clear follow-up.

Practical guide

What this page covers

Capture the right detailOperational teams need a simple route to report incidents, near misses and unsafe conditions while the information is still fresh.
Support the investigationInvestigation records should make it clear what happened, what evidence exists and what needs to change.
Track actions to completionActions need owners, dates and visibility so they do not disappear once the initial report has been submitted.
Connect H&S with training and documentsIncidents often lead back to training, policies, checks or equipment, so the record should link to the wider control framework.

Relevant Portal areas

See it in context

The live demo lets you explore Luminar Portal from employee, manager, admin and director views.

FAQs

Common questions

What should incident reporting software capture?

It should capture what happened, who was involved, immediate actions, investigation notes, evidence, corrective actions and closure status.

Why link incidents to investigations?

An incident report is only the start. Linking it to investigation actions helps ensure follow-up is visible and accountable.

Can Luminar Portal support H&S follow-up?

Yes. Incidents can sit alongside observations, safety checks, evidence, tasks and management reporting.

Does it help with audit evidence?

Yes. A structured record helps show what was reported, what was investigated and what action was taken.

Who should have access to incident records?

Access should normally be role-based, with relevant managers, H&S leads, HR or senior users seeing the records they are authorised to review.