Every experienced director has a safety protocol, usually several: the heat illness plan, the hydration policy, the Emergency Action Plan that lives in a binder behind the front desk and got updated last spring.
The gap between having those protocols and actually running summer camp through them is wider than most programs realize, and the directors who close it are running a different kind of operation than the ones whose protocols only exist on paper.
This is a checklist for closing that gap. Each item assumes the protocol already exists. The work is making it function on the day, under heat, under parent pressure, and under the operational chaos of a Tuesday afternoon in July.
Failure Point One: The Binder Behavior Gap
The most common safety failure in well-run summer programs is the gap between what's written and what staff actually knows. Site leads can describe the protocol in a meeting and then blank on the trigger threshold when a kid is wilting on the field. The work is moving it out of the binder and into staff muscle memory.
Run the protocol verbally at every Monday morning staff huddle. Make it a live walkthrough of "what we do if X happens this week," with rotating scenarios, not a recap of the binder. Two minutes, every week. The staff member who can verbalize the protocol on the spot is the one who can execute it in the moment.
Print the decision rules in card form. Most field staff don't need the eight-page heat illness policy. They need a laminated card with the trigger thresholds, the immediate actions, and the escalation number, in every coach's bag, every site lead's clipboard, and the front desk. If a staff member has to walk anywhere to find the answer, the system has already failed.
Test recall in week two. Reading the safety document at orientation is only a baseline. The real test is whether three random staff members can verbalize the heat protocol when no one prepped them for the question.
Failure Point Two: Unclear Decision Rights
When does camp pause, who calls a mandatory hydration break, and when does a parent question get escalated? Most programs have answered these on paper without naming the decision rights for the person on the ground in the moment.
Designate one decision-maker per site, per shift. The site lead may or may not be the head coach. What matters is that the site lead's name is on the call, and every staff member knows who that is before the day starts.
Pre-decide the close calls. The rule for "what happens at 92 degrees with 60% humidity" should be made in May and written on the card, so the site lead at 2pm on a Saturday isn't weighing it under parent pressure. The director decides once, and the site lead executes the same way every time after.
Build in a no-second-guess policy. When a site lead calls a hold based on the protocol, the director publicly backs the call, every time, even when a parent complains afterward. A site lead who gets overruled on a safety call in front of parents stops making safety calls, so director backing is what keeps the system functioning over a long summer.
Failure Point Three: Reactive Parent Communication
Programs that communicate with parents about safety after an incident are working after the moment that mattered. The shift is moving the communication to the front of the summer.
Send the heat plan to parents before camp starts, as a standalone document rather than a paragraph buried in the parent handbook. Include the trigger thresholds, what happens at each level, what the program will do, and what families can do to prepare their kid. Parents who know the protocol in advance don't push back on it when it's invoked.
Pre-empt the second-guessing. The communication should explicitly name that the program will not run camp through dangerous conditions and that the director makes that call. Families who understand this in May don't argue about it in July.
Communicate the close calls, even when nothing happened. When the protocol triggers a longer water break or an early end, send a short note to the affected families that day. It frames the action as the system working, builds parent confidence, and keeps the rumor mill from turning a routine adjustment into a crisis story.
Failure Point Four: Broken Information Flow Back to the Director
Site leads handle things on the ground, and many never reach the director, who then can't see the pattern that would inform next summer's planning. Near-miss events are the most informative safety data a program collects and the most likely to disappear into the gap between site and office.
Build a near-miss log. A simple form, fillable in two minutes from a phone, that captures what happened and what didn't: the kid who looked off but was caught early, the cooler that ran dry before a refill arrived, the storm warning that came fifteen minutes before the planned end. The log is data the program uses to improve, and treating it as anything else will kill the reporting flow within a week.
Read the log weekly. During camp season, the director's Friday review is the near-miss log from Monday through Thursday. Patterns surface fast when they're read systematically, and a program that catches one in week two prevents the incident in week six.
Run an end-of-summer debrief while the memory is fresh. Before staff scatters, walk through the log with site leads, covering what surprised them, what the protocol got right, and what was missing. That conversation, captured and filed, is the foundation of next summer's plan. Most programs skip it and rebuild the same gaps the following year.
Failure Point Five: Hydration as a Kid-Behavior Problem
Most programs treat hydration as a kid-responsibility variable. Remind them to drink, tell them to bring a bottle, check in if they look thirsty. That makes hydration outcomes depend on the compliance of eight-year-olds, which is fragile. The shift is treating hydration as an environment-design variable the program controls.
Build the drinking into the schedule. Mandatory water stops at fixed intervals, run as a default block of the day rather than something the coach has to remember. Twenty seconds every twenty minutes, every day, no exceptions. When hydration is a scheduled activity, individual compliance becomes structural rather than behavioral.
Cold water beats room-temperature water for hot-day compliance. A kid who hates the bottle on the sideline will drink from a cold cooler, and the cooler is a logistics decision the program controls while the bottle is a behavior it can only nudge. Pick the lever you actually have.
Track the empty bottles. A coach who walks the sidelines at the end of a session and notices three kids with full bottles is collecting data the director needs, and those names go on tomorrow's watch list. This catches the kids who would otherwise under-drink for days before anyone noticed, and it never needs to be parent-facing to do its job.
What the Director Specifically Owns
Two moves signal safety as a leadership priority rather than a delegated task. Be visible on the hard days: the director who shows up at a camp site during a heat advisory, talks to staff, and is seen by parents demonstrates that the protocol comes from the top, and delegation can handle execution but not that cultural signal. And treat near-miss data as confidential, because staff who flag a near-miss have to know the log won't be used against them. Programs that run the log as performance management get one summer of clean logs and learn nothing.
The Bigger Picture
The gap between programs that see an incident every few summers and programs that see one in any given July almost always traces back to execution under pressure rather than to anything missing from the written protocol. That execution work is what this checklist describes.
