Every operator knows the shape of a school holiday week. Wednesday of week two, the venue at capacity by 10:30, a queue at the till, two staff off sick, and a party at noon that booked for eighteen and arrived as twenty-six. This is when your venue makes its year. It's also when safety systems quietly bend, because every corner cut in August is cut under pressure by good people trying to keep the queue moving.
The uncomfortable pattern is simple: footfall and incidents rise together, but attention doesn't scale with them. The checks that feel effortless on a wet Tuesday in February compete with forty other demands at peak. So the honest question for peak season isn't “do we have safety procedures?” It's “which of our procedures survive contact with a full building?”
The checks that slip first
Ask around the industry and the same items come up every time. The mid-day walkround gets skipped because nobody can be spared from the floor. The ball pit headcount gets approximate. Wet-weather days bring buggy jams that drift in front of exits, the exact failure we covered in our fire safety guide. Cleaning happens fast and undocumented. And the close-down inspection, the one that catches the damage today's four hundred children did to the netting, gets compressed into lights-off-and-home because everyone's been on their feet for ten hours.
None of these are laziness. They're what happens when a system designed for normal load meets double load with the same headcount. Which means the fix isn't “try harder”. It's designing the peak version of the system in advance.
Write the peak-day version of your checks
Your daily checks shouldn't be identical in February and August, and pretending otherwise is how they get abandoned. A peak-day variant makes three changes.
First, it moves the deep checks to the edges of the day. The full equipment walkthrough happens before doors open, unrushed, when the frame is empty. What remains during trading are short, frequent spot checks: high-wear points (slide exits, rope bridges, the toddler gate latch) on a rota, fifteen minutes each, owned by a named person per shift block.
Second, it accepts that some things need more frequency at peak, not less. Toilets, wet pockets on the frame after spillages, the ball pit surface scan. Double the footfall roughly doubles the rate at which things degrade, and the checklist should say so out loud.
Third, it names deputies. On a February Tuesday, “the manager does the walkround” works. In August the manager is doing a refund, a birthday no-show and a first aid case at the same time. Every check on the peak-day list needs a first owner and a fallback, decided at the morning briefing rather than negotiated mid-crisis.
Temporary staff, permanent standards
Summer casuals and agency cover keep the season possible, and they're also your highest-risk cohort: least trained, least invested, and most likely to be alone with a zone at the exact moment something needs judgement. The controls are unglamorous. Every temp gets the same induction as a permanent starter, recorded with a date and signature, before their first solo shift and not during it. DBS status checked before they're anywhere near unsupervised contact, the ground we covered in our DBS guide. And pair every new face with an experienced one for their first week; the buddy is also your quality control on whether the induction stuck.
Watch your under-18s especially. The temptation to stretch a capable sixteen-year-old into close-down duties or lone supervision grows exactly when the law and your risk assessment say it shouldn't.
Capacity is a safety number, not a sales number
Your maximum occupancy exists for evacuation and supervision reasons, and peak season is when it gets tested by a queue of families who drove forty minutes in the rain. Decide the policy before August: what the cap is, who has authority to close the door, and what the till staff say when they do. A session-based booking system does this automatically and politely; a free-for-all door does it through one overwhelmed supervisor. If you're regularly bumping the ceiling, that's a scheduling problem to solve with sessions and staggered party slots, not a limit to quietly ignore.
And when you do run at the cap, supervision ratios need to have been decided at the same time. More children per zone means the zone rota tightens or the zone closes. A venue that opens every zone at maximum occupancy with holiday staffing has made a decision; better to make it on paper in July than discover it in an incident report in August.
Log everything, especially in the chaos
Peak season is when incident logging feels most optional and matters most. More footfall means more bumps, more near-misses, and more of the patterns that only show up in records: the same corner, the same time of day, the same piece of kit. It's also when a skipped log costs the most, because the claim that arrives in November lands on whatever evidence August left behind. The discipline we argued for in the RIDDOR guide (record everything, report selectively) earns its keep here. If the paper version dies in a busy week, that's an argument for logging that takes forty seconds on a phone, not an argument for not logging.
Tired staff make the season's worst mistakes
By week four of the summer holidays, everyone is running on fumes, and fatigue is a safety variable like any other. The supervisor who has done eleven straight opening shifts stops seeing the frame; it's become wallpaper. The host on a double stops enforcing the sock rule because enforcement takes energy. This is precisely when the near-miss log goes quiet, not because near-misses stopped but because noticing did.
The mechanical controls are rotas that spread the load: nobody owns every open, breaks actually taken rather than theoretically scheduled, and the checks rotated between people specifically so fresh eyes hit each zone. For your under-18s the law draws hard lines regardless of how willing they are: no more than 8 hours a day or 40 a week, a 30-minute break once a shift passes four and a half hours, and daily rest requirements that a party-season rota can't quietly eat. The HSE's guidance on young workers covers the detail, and your rota software should be enforcing it before anyone asks.
One more thing worth saying plainly: the operator is the most fatigued person in the building, and the checks the owner skips set the ceiling for how seriously anyone else takes theirs. If you're going to protect one habit through August, protect the morning walkround. The venue notices whose signature is on it.
The September debrief
The most valuable hour of peak season happens after it ends. First week of September, checklist completion rates in front of you, incident log open: which checks actually got done, which zones generated the incidents, which temp worked out well enough to invite back at Christmas, and what broke that limped through August on tape and hope. That last list becomes your autumn maintenance plan, and the whole exercise becomes next July's briefing. Venues that do this get better every season. Venues that don't have the same August every year, with the same surprises.
Where SafePlay fits
SafePlay is built for exactly the weeks when attention is scarce: peak-day checklists with named owners and timestamps in Daily Checks, temp inductions and DBS status visible per person in Staff Compliance, and the dashboard showing at a glance which checks got done across the venue while you were dealing with the party of twenty-six. Come September, the debrief data is already sitting there, because it collected itself during the chaos.