If It Wasn't Documented, It Didn't Happen.
Incident documentation is the systematic recording of workplace events including injuries, near misses, hazards, and security incidents. It forms the foundation of your safety management system and is required by law.
Learning Objectives:
Capture every event that matters
Effective safety programs document more than just injuries. Every event in this list creates a paper trail that protects your workforce.
The gold standard for thorough documentation
Every incident report should answer six fundamental questions. Miss one, and your documentation has a gap that investigators, lawyers, or OSHA will find.
Full names and job titles of all injured parties. Names of witnesses. Supervisor on duty. First responders who provided aid. Anyone else present in the area. Include contact information for follow-up.
Specific actions and sequence of events in chronological order. What the person was doing, what equipment was being used, what went wrong. Describe the injury or damage in detail. Include the body part affected and nature of injury (laceration, fracture, burn, etc.).
Exact date and time (use 24-hour clock for precision). Day of the week. Shift (day, swing, night). How long the employee had been on shift. When the incident was reported. When medical treatment was provided.
Building, floor, room, or area. Specific workstation or equipment. Include landmarks or reference points ("3 feet from the south exit door"). Outdoor locations should include weather conditions. Take photos of the exact location.
Contributing factors: equipment failure, environmental conditions, procedural gaps, training deficiencies. Be careful here—state observable facts, not speculation. Write "Floor was wet with no signage posted" NOT "Employee was careless." Root cause analysis should follow; the initial report captures conditions, not conclusions.
The mechanism of injury or damage. What physical action or condition led to the event? "Employee's foot slipped on oil residue, causing a fall from a 4-foot platform." Include environmental conditions: lighting, noise, temperature, weather, congestion.
Facts, not feelings
The single most important rule of incident documentation: stick to observable, verifiable facts. Your report may be read by OSHA inspectors, attorneys, insurance adjusters, and judges. Every word matters.
Protect what proves the truth
Physical and digital evidence tells the story that words alone cannot. Properly preserved evidence can make or break an investigation.
Capturing what people saw, heard, and experienced
Witness accounts add critical perspectives to your documentation. How you collect them matters as much as what they say.
Know the law, meet the deadlines
OSHA requires specific documentation for workplace injuries and illnesses. Failure to comply results in citations and significant fines.
Secure, searchable, and reliable
Modern incident documentation relies heavily on digital tools. These practices ensure your digital records are defensible, secure, and easy to retrieve.
Digital records should include automatic timestamps showing when they were created, modified, and by whom. Never backdate records. If a report is completed later, note the actual completion date and explain the delay. Metadata provides an audit trail that proves when documentation occurred.
Store records on secure servers with automatic backups. Use cloud-based systems with redundancy. Paper records should be scanned and stored digitally as well. Never store incident records on personal devices, USB drives, or unsecured locations. A lost record is as bad as no record at all.
Limit who can view, edit, and delete records. Use role-based permissions (supervisors can create, safety managers can review, admins can manage). Maintain an access log showing who viewed or modified each record. Incident records often contain sensitive personal and medical information.
OSHA requires records to be kept for 5 years. Workers' compensation records: check your state requirements (often 30+ years). Exposure records (chemical, noise, radiation): 30 years per OSHA. When in doubt, keep records longer rather than destroying them too early.
Use consistent templates that prompt reporters to capture all required information. Pre-built forms reduce the chance of missing critical details. Include required fields so forms cannot be submitted incomplete. Templates also make records easier to search and analyze for trends.
Mobile apps let workers report incidents from the field in real time. Photos, GPS location, and timestamps are captured automatically. Voice-to-text reduces barriers for workers who struggle with written reports. Immediate reporting means fresher, more accurate information.
Avoid these pitfalls that undermine your reports
Even well-intentioned reporters make these mistakes. Knowing them in advance helps you produce bulletproof documentation.
From documentation to prevention
Documentation doesn't end with the initial report. The real value comes from what you do with the information to prevent recurrence.
Document specific actions to prevent recurrence. Assign responsible parties with deadlines. Prioritize actions by risk level (eliminate hazard > engineering controls > admin controls > PPE). Include both immediate fixes and long-term systemic changes.
Track completion of every corrective action. Verify that fixes actually work (don't assume implementation equals effectiveness). Set follow-up review dates at 30, 60, and 90 days. Document verification activities and results.
Summarize what happened, why it happened, and what was done to prevent it. Share findings with relevant teams and departments. Add lessons learned to training materials. Update Standard Operating Procedures where needed.
Communicate findings focused on system improvements, not individual fault. Use "safety alerts" or "lessons learned bulletins" to share across the organization. When workers see that reporting leads to improvements (not punishment), reporting increases.
Your incident documentation checklist
Keep these essentials in mind every time you document a workplace event:
Calculating your results...