How to Staff Lifeguard Posts by Risk Zones, Not Just Area

Why 'so many feet per guard' hides the real risk

Statutes and codes often fix simple numbers: Nevada requires at least one lifeguard for each 400 feet (about 122 m) of beach front and a tower for each 600 feet (about 183 m). Such rules give inspectors an easy test and operators a defensible floor, but they colour the whole coastline with one brush while incidents are distributed very unevenly.

Drowning and near-drowning cluster at depth transitions, at the edge of swimming zones, in currents and surf, and wherever children and weak swimmers gather. Spreading guards evenly by measured shoreline can leave those hot spots thinly covered while capable staff stand watch over calm, empty water.

So treat the fixed ratio as the compliance floor and a starting grid, not as the answer. The answer is a risk map that tells you which of your beaches, and which parts of each beach, deserve more posts, higher towers and mobile backup.

Score the zone, not the shoreline

Divide the site into surveillance cells that match how a guard can actually see and reach the water — typically 100–300 m of frontage on open water, or the functional span of a pool stand. Score each cell before the season, then re-score after any change: altered bottom profile, new structures, shifted swim boundaries or a different visitor mix.

Scoring produces a comparative map rather than an average, so leadership can see at a glance which cells need higher density and which can be held by a single well-placed stand. Involve the lifeguards themselves; they know which positions are blind and where help is most often called.

The factors below drive the score. Assign weights locally — there is no single correct weighting, and an experienced duty supervisor should sanity-check the output.

• Depth changes, drop-offs, diving areas, and shallow zones where children and non-swimmers stay.
• Currents, surf, tides, rip risk, cold-water upwellings and shifting wave zones.
• Peak bather load: how many people are actually in the water in the cell at maximum attendance.
• Visitor profile: share of children, older adults, unaccompanied groups and alcohol-influenced crowds.
• Visibility from the post: glare, structures, foliage, water clarity and blind spots behind piers and buoys.
• Reach: distance to the farthest point of the zone, bank and seabed conditions, and emergency access for responders.
• Daily variability: sun angle, wind, tide, event schedules and programmed children's sessions.

Turn scores into a roster, not just a map

Group cells into low, moderate, high and very high bands, and set a baseline staffing density for each. High-risk cells get a post closer to the water and higher off the ground for a better view, a shorter zone of responsibility, and often a roving guard or a boat on the outer edge of the swim area in addition to the fixed stand.

Neighbouring cells should overlap slightly so no gap opens at the seam between two posts. Where a seam crosses a risk boundary, move the post toward the more dangerous cell rather than placing it exactly halfway.

The roster should follow predicted load, not a single flat summer number. A weekday before 4 pm, a weekend, a school camp and a public holiday each warrant a different shift size, so build a base schedule and a surge schedule that can be switched on from attendance counts and weather warnings.

Verify visibility and reach on site, every season

The risk map is only a hypothesis until it passes on-site checks. Run zone verification drills: place a silhouette or manikin in each cell — including on the bottom and at the surface near the stand — and record whether the guard can see it and reach the farthest point within the target time. Common pool benchmarks are reaching any point of the zone within about 20 seconds and recognising a simulated victim within about 30 seconds.

Repeat the checks at different times of day and in different conditions, because morning glare, evening light and light haze change visibility; a position that works at noon can be blind at six in the evening. Re-test after any session-type change, such as lane swimming versus open recreation, and whenever a new team member starts.

In pools this formal check is often called a Lifeguard Zone Visibility Test, and its goal is full coverage of the whole water volume with no blind spots. The same logic transfers to a beach: a 'working' zone means visible and reachable, not merely an equal share of the coastline.

Protect attention: rotate and cap uninterrupted duty

Continuous scanning fatigues quickly, and even a perfect risk map fails if the guard's focus lapses. Widely used guidance for pool lifeguards is to rotate positions every 15, 20 or 30 minutes, spend no more than about 30 minutes in one static position, and stay on poolside duty no longer than about 60 minutes before a break. Open-water crews should apply the same principle to the busiest towers.

Aim rotation from less demanding to more demanding positions and back, so attention does not erode on a monotonous stand. Build relief capacity into the headcount: a shift needs enough people for breaks, handover, training and sickness, or a zone is left unobserved during rotation.

Log time-on-post and breaks. If an inspection or an incident review asks why a zone was unguarded at a given moment, the answer must rest on an approved rotation schedule, not on an informal arrangement.

Where the model stops: compliance and honest limits

A risk-based model redistributes effort but does not override binding minimums. If your jurisdiction fixes a tower every 600 feet and a guard every 400 feet of beach front, or a specific staffing plan for a venue type, those requirements stand regardless of what a scoring exercise suggests. The model answers 'how do we arrange staff within the floor', not 'may we place fewer'.

Rules differ by jurisdiction and change over time, so verify the current code or health-authority requirement for your location before applying a zone map. Where a lifeguard staffing plan must be submitted to a health authority or regulator, the scored map becomes supporting documentation, not a substitute for approval.

Be honest about the method's limits: your data on load and incidents is thinner in low-season periods, weather shifts faster than a map gets revised, and scoring cannot replace the judgement of an experienced senior guard on scene. Revisit the map at least annually and after any serious incident, and treat it as a living document.