Incident Reporting at Camp: What to Log and Why It Protects You
Log more than you think you need to
The incidents that create problems months later are rarely the dramatic ones, those get documented. It's the near-miss, the minor scrape, the homesick camper who seemed fine by dinner. If a reasonable parent would want to know, it's reportable. A low threshold costs minutes; a missing record can cost far more.
What a usable incident record contains
Who, what, where, when, witnesses, action taken, and follow-up owner, written the same day, by the person closest to the event, in their own words. Avoid diagnosis and blame; record observations. The test of a good record: could someone who wasn't there reconstruct the event and the response a year later?
Consistency beats eloquence. A simple structured form that every staffer fills the same way is worth more than occasional detailed narratives, because patterns only emerge from comparable records.
Reports are only useful if they're findable
Paper forms in a binder can't answer 'has this camper had other incidents this week?' or 'is this activity area producing more injuries than last season?' Keeping incident logs in the same system as the roster ties every report to a person, a place, and a time, and turns documentation from a liability chore into an early-warning system.
See how Encampment.io handles this for summer camps.
Encampment.io for Summer Camps