Every experienced director has a safety protocol. Most have 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 that gap are running a different kind of operation than the ones whose protocols only exist on paper.
This is a checklist for closing the gap. Each item assumes the underlying protocol already exists. The work here is making sure the protocol functions 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 when asked in a meeting and can't recall the relevant trigger threshold when a kid is wilting on the field. The work is moving the protocol out of the binder and into staff muscle memory.
Run the protocol verbally at every Monday morning summer staff huddle. The format is a live walkthrough of "what we do if X happens this week," with rotating scenarios, rather than a recap of the binder. Two minutes, every week. The staff member who can verbalize the protocol on the spot is the staff member 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 phone number, kept in every coach's bag, every site lead's clipboard, and the front desk. If the 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 only counts as baseline, and the actual test of whether orientation worked 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 the camp pause? Who calls a hydration mandatory break? When does a parent question get escalated to the director? Most programs have answered these questions on paper without having actually named 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 is the person whose name is on the call, and every staff member at the site knows who that is before the day starts.
Pre-decide the close calls. The decision 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 running cost-benefit analysis under parent pressure. The director makes the call once, and the site lead executes it the same way every time after that.
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 calls afterward complaining. Site leads who get second-guessed on safety calls in front of parents stop making safety calls. Director backing is the only thing that 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 doing the work 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. The communication needs to be a standalone document rather than a paragraph buried in the parent handbook, with 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 standalone 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 triggered a longer water break or an early end to a session, send a short note to the affected families that day. The note frames the action as the system working, builds parent confidence in the protocol, and prevents 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. Many of those things never reach the director, who then can't see the pattern that would inform next summer's planning. Near-miss events, in particular, 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 happen. The kid who started looking off but was caught early. The water cooler that ran dry before a refill arrived. The thunderstorm warning that came in fifteen minutes before the planned end. The log functions as 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 being read systematically, and programs that catch a near-miss pattern in week two prevent the incident in week six.
Run an end-of-summer debrief while the memory is fresh. Before camp staff scatters, sit down with site leads and walk through the near-miss log. What surprised them. What the protocol got right. What was missing. That conversation, captured and filed, is the foundation of next summer's better plan. Most programs skip this step 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 water bottle. Check in if they look thirsty. This framing makes hydration outcomes dependent on the compliance of eight-year-olds, which is a fragile system. 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 reminds the kids to do. Twenty seconds every twenty minutes, on the schedule, every day, with no exceptions. When hydration is a scheduled activity, individual kid compliance becomes structural rather than behavioral.
Cold water beats room temperature water for hot-day compliance. A kid who hates the water bottle on the sideline will drink from a cold cooler. The cooler is a logistics decision the program controls, while the water bottle is a kid behavior the program 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 water bottles is collecting data the director needs. Those names go on the watch list for tomorrow. Hydration tracking is an internal coaching responsibility that catches the kids who would otherwise under-drink for three days running before anyone noticed, and it never needs to be a parent-facing program to do its job.
What the Director Specifically Owns
A few moves that signal safety as a leadership priority rather than a delegated responsibility.
Be visible on the safety calls. 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. Delegation works fine for executing the protocol, but the cultural signal that safety isn't optional has to come from the director's physical presence on the hard days.
Hold the staff line publicly. When a parent complains about a hold, a hydration break, or an early end, the director's response is always some version of "our site lead made the right call," and it stays that way even when the director privately wants to talk to the staff member about something else.
Treat near-miss data as confidential and important. Staff who flag a near-miss have to know the log doesn't get used against them. The director's job is to create the conditions under which staff report freely. Programs that treat the near-miss log as performance management get one summer of clean logs and learn nothing.
The Bigger Picture
The gap between programs that experience an incident every few summers and programs that experience 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.
Run through the list before the first hot week. The summer that doesn't end with a 911 call is built in May.
