How to Write an Incident Report (Step-by-Step)

How to Write an Incident Report — Step-by-Step Guide | IncidentVault
✍️ How to Write an Incident Report

How to Write an Incident Report — Step-by-Step Guide

A poorly written incident report is not just incomplete — it is a liability. Vague descriptions, missing witness information, and undocumented scene conditions create the gaps that plaintiffs’ attorneys exploit and that insurance carriers use to question claims. A well-written incident report tells the complete, factual story of what happened — and leaves no gaps for someone else to fill in later.

⚡ Key Takeaway

An effective incident report captures five categories of information: the basic facts (who, what, when, where), the environmental context (conditions, equipment, contributing factors), witness information (names, contacts, statements), the immediate response (first aid, notifications, corrective action), and evidence (photographs, documents, physical evidence). IncidentVault’s guided incident forms prompt for every required element by incident type — ensuring complete documentation regardless of which staff member is completing the report and regardless of the circumstances under which it is submitted.

Immediate
Write the report immediately — every hour of delay degrades the accuracy of witness memory
Facts Only
Report facts, not opinions or conclusions — “the floor was wet” not “the floor was dangerously wet”
Complete
Better to have too much information than too little — gaps invite adverse inference

The Five Essential Elements of Every Incident Report

Element 1: Basic Incident Facts

  • Date and time: Exact date and time the incident occurred (not when it was reported)
  • Location: Precise location — not “the parking lot” but “the northwest corner of the main parking lot, near the exit ramp, approximately 20 feet from the street”
  • Person(s) involved: Full names, contact information, and relationship to the organization (employee, customer, contractor, visitor)
  • Description of what happened: A clear, factual narrative of the sequence of events — what occurred, in what order, without conclusions about fault or cause
  • Type of incident: Classification (slip-and-fall, vehicle accident, workplace injury, security incident, etc.)

Element 2: Environmental Context

  • Physical conditions: Floor/surface condition, lighting, weather (for outdoor incidents), temperature, visibility
  • Equipment or substances involved: Any machinery, vehicle, chemical, or product involved in the incident — make, model, serial number where applicable
  • Contributing factors observed: Any conditions observed at the time that may have contributed to the incident (wet floor, missing signage, equipment malfunction, inadequate lighting)
  • Staffing context: Who was working in the area, what activities were occurring, what the involved person was doing immediately before the incident

Element 3: Witness Information

  • Witness names and contact information: Full names, phone numbers, and email addresses of everyone who witnessed the incident — collected before witnesses leave the scene
  • Witness statements: A brief summary of what each witness observed — in their own words, not paraphrased into conclusions
  • Non-witness contacts: Names of people who responded to the incident even if they did not witness it (supervisor who arrived after, first aid responder, security officer)

Element 4: Immediate Response

  • First aid provided: Exactly what first aid was given, by whom, and when — specifically whether the injured person declined medical attention or was offered it
  • Medical treatment: Whether emergency services were called, whether the person sought or was transported to medical care, and any medical facility name
  • Notifications made: Which management personnel were notified, at what time
  • Corrective action at the scene: What was done immediately to address the hazardous condition — floor dried, area roped off, equipment locked out, signage placed

Element 5: Evidence

  • Photographs: Photos of the exact scene, the hazardous condition, any visible injuries (with consent), and anything relevant to understanding what happened — taken before anything is moved, cleaned, or repaired
  • Security footage: Note the location and timestamp of any security camera footage that may have captured the incident — initiate a hold request immediately to prevent overwriting
  • Documents: Police report numbers, medical transport records, equipment inspection records, maintenance records for the area where the incident occurred

The Six Most Common Incident Report Mistakes

⏰

Delayed Reporting

Every hour between the incident and the report degrades the accuracy of witness memory, allows scene conditions to change, and potentially allows security footage to be overwritten. Report immediately — imperfect details can be supplemented later, but lost evidence cannot be recovered.

💬

Including Opinions and Conclusions

“The floor was obviously not maintained properly” is an opinion. “The floor had a wet surface with no wet floor sign present at the time of the incident” is a fact. Reports should contain only facts — what was observed, what was said, what was done. Conclusions and fault assessments belong in investigation reports, not incident reports.

🚶

Missing Witness Information

Witnesses who leave the scene before their information is collected are effectively lost for the purposes of the incident report. Collecting witness names and contact information before anyone leaves the scene is one of the most important immediate actions after any incident — and one of the most commonly skipped.

📸

No Photographs

A photograph taken before the scene changes is evidence that no subsequent description can replicate. The floor condition, the lighting, the placement of objects, and the state of equipment at the moment of the incident are facts that photographs capture definitively. Every staff member has a camera phone — using it immediately is one of the highest-value incident response actions available.

❓

Vague Location Descriptions

“The parking lot” is not a location. “The northeast corner of the main parking lot, approximately 15 feet from the handicapped parking spaces, near the cart return” is a location. Vague location descriptions make scene reconstruction difficult or impossible when the incident is reviewed months later by someone who was not there.

📝

Admissions of Liability

Incident reports should never contain admissions of liability — phrases like “our floor cleaning procedures were not followed” or “the area had not been inspected as required.” These are conclusions about fault that should be reserved for investigation analysis, not placed in the incident report that may be subpoenaed in litigation.

Guided forms that produce complete, defensible incident reports — every time.

IncidentVault’s incident forms guide reporters through every required element by incident type — so complete documentation happens automatically, regardless of who completes the report or under what circumstances.

Frequently Asked Questions

Both perspectives are valuable, and best practice is to collect both. The supervisor’s report captures the organizational context — what activities were occurring, what conditions were present, what immediate response was taken. The employee’s or injured person’s own account captures their perspective of the sequence of events and the conditions they experienced. In IncidentVault, the supervisor completes the primary incident report, and the involved employee’s statement is captured as a separate field or attached document within the same incident record. For customer or visitor incidents, the customer’s own account is collected (with their consent) as part of the incident record. Never have the injured person complete the primary incident report — their role is to provide their account, not to document the organizational response to their injury.
Yes — incident reports can and should be supplemented with additional information as it becomes available after initial submission. A witness who was initially unavailable may provide a statement later. The injured person’s medical treatment may clarify the nature of the injury. Security footage review may add details to the scene description. In IncidentVault, supplemental information is added as an update to the incident record — with the update timestamped and attributed to the user who added it. The complete history of all additions and changes is preserved in the audit trail, showing both what was known at the time of initial submission and what was learned subsequently. What cannot be changed is the original report’s content — IncidentVault’s audit trail preserves the original submission so that any subsequent changes are visible as additions rather than replacements of the original record.
Incident report retention requirements vary by incident type and applicable regulatory or legal requirements. OSHA requires retention of the 300 Log and 301 Incident Reports for 5 years. Workers’ compensation records have state-specific retention requirements that commonly range from 3 to 10 years from the date of injury or claim closure. General liability incident reports should be retained for at least the applicable statute of limitations plus a reasonable buffer — which may range from 3 to 7 years for adult claimants, and longer for incidents involving minors (where the statute of limitations may not begin until the minor reaches majority). Incidents that escalated to litigation should be retained indefinitely or for the duration of the legal hold, whichever is longer. IncidentVault retains records for the configured retention period — always verify applicable retention requirements with your legal counsel and insurance carrier for each incident type.
What to say: Express genuine concern for the person’s wellbeing. Offer first aid and ask if emergency services should be called. Inform them that an incident report will be completed. Collect their contact information and offer them a copy of the incident report number. What not to say: Do not admit fault on behalf of the organization (‘I’m so sorry, we should have fixed that’). Do not make statements about insurance coverage (‘Our insurance will cover this’). Do not speculate about the cause of the incident or assign blame to anyone. Do not promise specific outcomes regarding compensation or medical coverage. Do not discourage the person from seeking medical attention or legal advice if they choose to. The standard guidance — be compassionate about the person’s wellbeing, professional about the documentation process, and neutral about liability — serves both the human interaction and the organization’s legal interests simultaneously.
⚠️
Legal & Regulatory Disclaimer The information on this page is provided for general informational purposes only and does not constitute legal, insurance, compliance, or risk management advice. Incident management, claims, and legal requirements vary by jurisdiction, industry, and organization type. Always consult qualified legal counsel, your insurance carrier, and applicable regulatory authorities before making decisions about incident reporting procedures, claims management, or compliance programs. IncidentVault is a software platform — not a law firm or insurance company. All figures and estimates referenced are illustrative only.