What is an incident report — and why does it matter?
An incident report is a formal written account of any event that caused harm, nearly caused harm, or disrupted normal operations. This includes workplace injuries, equipment failures, safety near-misses, customer complaints, security breaches, and property damage.
The purpose is threefold: to create an accurate record of what happened, to support any investigation or corrective action, and to provide a defensible document if the incident leads to a claim, dispute, or regulatory inquiry. A good incident report is factual, specific, timestamped, and written by someone who witnessed or managed the event.
What to include in an incident report
Every incident report — regardless of industry or incident type — should contain these core fields:
Incident report example — good vs bad
The same incident, written two different ways:
The difference is accountability, specificity, and tone. The good report is factual — it describes what happened without assigning blame. It includes timestamps, names, and references to prior records. It would hold up in an insurance claim. The poor report would not.
The most common incident report mistakes
Writing it too late
Every hour between an incident and its report increases the chance of error. Memory fades, witnesses move on, and the sequence of events gets compressed into a single statement. The standard is to report within the same shift. If the incident is serious, report immediately and supplement with a fuller account as soon as conditions allow.
Using opinion instead of fact
"The employee was careless" is an opinion that will be challenged. "The employee did not use the marked walkway" is a fact. Stick to what was observed, what was measured, and what was recorded. Save analysis for the separate root cause review.
Leaving out witnesses
Witnesses are the corroborating evidence for your account. A report with no witness names is harder to defend. Even if a witness did not see the incident itself, they may have observed the conditions immediately before or after it.
No named author
An unsigned incident report is not a legal document. The name of the person completing the report — and their role and relationship to the incident — must be clearly recorded.
Allowing edits after submission
If an incident report can be edited after it is filed, it is not a record — it's a draft. If a correction is needed, add a supplementary note with a new timestamp and author, referencing the original report.
A good incident report answers six questions: who was involved, what happened, when it happened, where it happened, what was done in response, and why it happened (if known). If your report can't answer all six, it isn't complete.
How to log incidents digitally in Loginboard
Loginboard includes a built-in incident log as part of every board. Each incident record is timestamped at submission, named to the reporting team member, and immutable — it cannot be edited after it is filed. If a correction is needed, a new entry references the original.
Incidents are tracked through to resolution: when a manager logs a resolution note, the incident is marked closed. The full incident history is searchable by keyword or date — invaluable when a client dispute or insurance claim requires you to locate a specific record quickly.
Start logging incidents digitally — free, no card required.