5 Incident Documentation Mistakes Churches Make

5 Incident Documentation Mistakes Churches Make

Steward

Steward

Good intentions don't protect your church from liability. Even organizations committed to safety often make documentation mistakes that create problems down the road. Here are the five most common ones - and how to avoid them.

1. Waiting Too Long to Document

The longer you wait to write an incident report, the less accurate it becomes. Details fade. Memories shift. What seemed clear in the moment becomes fuzzy a week later.

The fix: Document incidents as soon as safely possible - ideally within 24 hours. If you're using digital tools, capture the basics on your phone right away, then complete the full report later.

2. Leaving Out Key Details

A report that says "Child fell on playground" doesn't give you much to work with. What equipment was involved? Were there witnesses? What was the weather like? Was the child supervised?

The fix: Use structured forms that prompt reporters to include essential information. At minimum, every incident report should capture:

  • Who was involved (names, ages, roles)
  • What happened (specific description)
  • When it occurred (date and time)
  • Where it happened (specific location)
  • Who witnessed it
  • What actions were taken
  • Who was notified

3. Editing Original Reports

It's tempting to "fix" a report when you learn new information. But altering original documentation destroys its credibility. If a report is ever scrutinized in legal proceedings, edits create the impression that something is being hidden.

The fix: Treat original reports as permanent. Add new information as follow-up notes or amendments that are clearly dated and attributed. Never delete or overwrite the original.

4. Inconsistent Reporting Thresholds

When every staff member decides independently what's "worth" reporting, you get inconsistent documentation. One person reports every scraped knee; another only reports trips to the emergency room.

The fix: Create clear guidelines about what should be documented. Err on the side of over-reporting - it's easier to have a record you don't need than to need a record you don't have.

Common categories that should always be documented:

  • Physical injuries (any severity)
  • Property damage
  • Security concerns
  • Behavioral incidents
  • Medical emergencies
  • Safety hazards identified
  • Complaints or concerns raised

5. No Follow-Up Documentation

The initial incident report is just the beginning. What happened next? Was the issue resolved? Were policies changed? Did similar incidents occur later?

The fix: Track incidents through resolution. Document:

  • Investigation steps taken
  • Decisions made
  • Communications with involved parties
  • Policy or procedure changes
  • Final resolution

This creates a complete record that demonstrates your organization took the incident seriously and responded appropriately.

The Bottom Line

Incident documentation isn't about creating paperwork - it's about protecting your ministry and the people you serve. When documentation is thorough, timely, and well-organized, it demonstrates professionalism and care. When it's incomplete or inconsistent, it creates risk.

The good news is that these mistakes are entirely preventable. With the right systems and habits, your church can document incidents in a way that serves everyone's interests.

Know you're covered when it matters

Try it free for 60 days. Founder pricing when you subscribe.

No credit card required. Set up in 15 minutes. Cancel anytime — export your data whenever you need it.