How to Write an Incident Report at Work

An incident report should let a reader reconstruct what happened without inheriting the writer’s assumptions. Record observations, actions, and sources separately from interpretation.

Build A Time-Ordered Record

Start with the basics: date, time, location, people present, and how the incident was discovered. Then write the sequence:

14:12: Employee observed water beneath the east ice machine.

14:14: Area was closed to customers and a wet-floor sign was placed at each entrance.

14:19: Shift lead called facilities and opened ticket 2087.

Use exact times where available. If a time is estimated, label it.

Describe, Do Not Diagnose

Write “water was visible below the inlet hose,” not “the hose failed,” unless a qualified inspection confirmed the cause. Quote witnesses accurately and identify the source.

Connect Routine Evidence

If the incident relates to recurring checks, preserve the relevant completion record, reading, or photo. MyTeamTask includes searchable checklist history and photo proof, which can help a manager locate operational evidence. Follow your organization’s retention and incident procedures.

For a rough report, use:

Rewrite as a factual workplace incident report. Organize events chronologically. Separate observations, witness statements, immediate actions, and follow-up. Preserve times, measurements, names, and uncertainty. Do not infer causes or liability.

Wrivio’s Local mode can keep rewrite text on the PC when selected, but the final report must still be stored and shared according to workplace policy. Have the responsible manager verify it before submission.

For less formal operational continuity, see how to write a shift handover report.