An incident report is the document you hope you never need and can’t afford to get wrong. A camper gets hurt, a behavior crosses a line, a near-miss happens on the waterfront — and weeks or months later, a parent, a board, or an insurer asks what happened, what you did, and when. The answer has to be a record, not a memory. The trouble is that the moment of the incident is the worst moment to be filling out a careful form, and the staffer holding the clipboard isn’t the one who’ll have to defend it later.
This is a guide to logging camp incidents and injuries so the safety paper trail holds up — consistent in the field, clear to the parent, and complete by the time anyone asks. It rests on one idea: every incident is the same record, captured the same way, no matter who writes it.
Consistency is what makes a report defensible
The failure mode of paper incident forms isn’t that they’re lost, though they are. It’s that they’re inconsistent. One counselor writes a paragraph, another writes three words, a third forgets the time. When you read across them later, you can’t — every report is shaped differently because every reporter is different.
A defensible record captures the same fields every time: which campers were involved, who reported it, the incident type, the severity, the time and location, a description of what happened, and any first aid given. The fields do the work the reporter shouldn’t have to. A stressed staffer filling in a structured incident report captures what matters because the form asks for it, not because they remembered to. And a reviewer reading a hundred such reports can actually read across them, because they share a shape.
Severity belongs in that shape. Minor, moderate, serious, critical — a ranked field tells you which incidents are notes and which demand action now, without reading every line. The type matters too: an injury, a safety issue, and a behavioral incident are different records, and a behavioral one needs its own fields — the antecedent and the consequence — to be worth anything later.
Notify parents from the record, not from memory
The parent call is the highest-stakes part of incident handling, and the easiest to get subtly wrong. Notify too late and you’ve lost their trust. Notify from memory and you paraphrase — the details soften, the severity drifts, and the version the parent hears isn’t the version on the form.
Notifying from the same record that holds the incident fixes both. The facts are settled — what happened, the severity, the first aid given — and the notification carries those actual facts to the family’s contacts, on the channel they prefer. Just as important, the notification is recorded against the incident. “When were the parents told” stops being a question you answer from memory and becomes a timestamp on the record. For a serious incident, that one fact — that you notified, and when — is often what the conversation later turns on.
This is the same point the camper medical records make about a medication log: an event you can’t account for is the one you’ll be asked about.
Follow-up that survives the week
Most incidents aren’t closed in the moment they’re logged. A camper is monitored, a behavior gets a plan, a hazard gets reported to maintenance — and that follow-up is exactly the part a paper form can’t hold. The form captures the moment; it has nowhere to record what happened next.
An incident that lives on the camper record can carry its own follow-up. It moves through states — open when logged, follow-up while there’s work to do, resolved when it’s done. Each follow-up note attaches to the incident with its author and date, so the thread of what was done, and by whom, stays with the original event. The open and follow-up incidents become a list you work, not a stack of forms you hope someone is watching. A resolution note closes the loop: an incident is either resolved with a record of how, or it’s still visibly open and waiting. Nothing falls into the gap between “reported” and “handled,” because the record won’t let it.
Serious incidents can escalate to the right person with a note, so the moderate scrape and the situation that needs the director’s eyes don’t sit in the same undifferentiated pile.
Log the small stuff, because patterns live there
The instinct is to log only the serious incidents and let the small ones go. That instinct quietly throws away the most valuable thing the record produces: patterns.
One scraped knee is nothing. The same stretch of trail reported five times in two weeks is a hazard you can fix before the sixth report is a broken wrist. One homesick night is normal. A cabin generating a run of behavioral incidents is a staffing or grouping problem you can act on while there’s still season left. None of these patterns are visible in any single report. They’re only visible when you log consistently — the minor with the serious, the behavioral with the injuries, and the positive moments too — and let the entries accumulate into a trend you can actually read.
A record built only from emergencies tells you about emergencies. A record built from everything tells you where the next emergency is likely to come from. That cumulative value is the whole argument for logging the small stuff: the report you skip is the data point that would have shown you the pattern.
One record, from the field to the file
Incident logging fails when it’s a stack of paper. Paper forms are inconsistent, so they don’t read across. They hold the moment but not the follow-up, so things get lost. They sit apart from the parent notification and the camper’s medical record, so the safety picture is scattered across three places when someone asks for it whole.
Putting incidents on the camper record closes that gap. Every report shares a shape, so it’s defensible. Parent notifications fire from the record and are logged against it. Follow-ups attach and resolve, so nothing is dropped. And because every incident — minor, serious, behavioral, positive — lands in the same place, the patterns surface. Camp Runner is one system for that record — medical, incidents, and the rest on a single camper, priced at $1.50 per active camper per month for the whole thing.
You run the safety of the camp. Camp Runner carries the record, so the report holds up, the parent hears the facts, and the follow-up doesn’t get lost. Incident logging is one piece of summer camp operations kept on the camper record. If your incident log is still a binder you’d rather not test against a hard question, join the waitlist.
Common questions
- What should a camp incident report capture?
- Every incident report should capture the same fields: which campers were involved, who reported it, the type and severity, the time and location, what happened, and any first aid given. Behavioral incidents add the antecedent and the consequence. Consistent fields are what make the record defensible — when every report captures the same things, a reviewer can read across them, and nothing depends on which staffer happened to write it up.
- How quickly should parents be notified of a camp incident?
- As soon as the incident is logged and the facts are settled. Notifying from the same record that holds the incident means the parent hears the actual details — what happened, the severity, any first aid — not a paraphrase reconstructed later. The notification is also recorded against the incident, so 'when were the parents told' is a fact on the record, not a question you answer from memory.
- How do you make sure incident follow-ups don't get lost?
- Attach the follow-up to the incident itself. An incident moves through states — open, follow-up, resolved — and each follow-up note lives on the incident with its author and date. The open and follow-up items are a list you can work, not a stack of paper forms. A resolution note closes the loop, so an incident is either resolved with a record of how, or it's still visibly open.
- Why log minor incidents and not just serious ones?
- Because patterns live in the minor ones. A single scraped knee is nothing; the same playground reported five times in a week is a hazard you can fix. Logging consistently — including the small stuff and positive behavior — is what turns individual reports into a trend you can read. The record's value is cumulative, and you can't read a pattern from incidents you never wrote down.
