Community Pool Occupancy: Setting Up a Group of Counters for Main Pool, Kids Pool, Spa, and Deck

Most counting articles start with a single number — how many people are in the room. A community pool does not work that way. The main pool, the wading pool, the spa, and the deck each have their own legal limit, and those limits are set by different rules.

The main pool and wading pool are governed by bather load: a health-department formula based on water-surface area, typically one swimmer per 20 square feet at depths over 5 feet and one per 15 square feet at shallower depths. A 1,200-square-foot main pool with a 5-foot maximum depth comes out to a capacity of 80 swimmers. The wading pool next to it, at 200 square feet and a tighter ratio for small children, comes out to 20.

The spa is governed by a much smaller surface and a tighter ratio still — often one bather per 10 square feet. A 50-square-foot hot tub seats five people legally. It will look full at four.

The deck is governed by the fire code, not the health code. It is a gross-area assembly-occupancy calculation that the local AHJ adopts off the IBC or NFPA 101. A 3,000-square-foot pool deck at 15 square feet per person caps at 200, but during a hot weekend a deck that holds 200 stops feeling pleasant at 120 — and the parents holding babies on the side are part of that count even though they are not in the water.

These four numbers tell four different operational stories, and the moment you collapse them into one people in the pool area tally, you have hidden the zone that is actually over its limit. A Saturday afternoon where the spa is at six (over) and the main pool is at 42 (well under) reads as 48/110 on a single counter and looks fine. The spa is the problem and you cannot see it.

On the dashboard, create one cloud counter per zone. Name them so the names will read well on a public board: Main Pool, Kids Pool, Spa, Deck. If you also want a cumulative day-pass tally at the front gate, add a fifth named Entries Today.

For each one, open the counter's settings and fill in Maximum capacity with the number from your zone table — the placeholder on the create form even reads "e.g. 100, for pool/venue limits", so you are using the field exactly as designed.

What capacity does today: once a zone reaches its number, the +button stops adding. The tap registers, nothing happens, and the card sits at-cap on the grid. That is the cue for the lifeguard to start a waitlist, close the gate, or pull one bather out before the next one goes in. It is not a substitute for the chair's judgment — it is a quiet floor that the chair does not have to think about until it triggers.

On the dashboard, each counter row has a thumbtack icon to the right of the action buttons. Click it on Main Pool, Kids Pool, Spa, and Deck — each card joins the Multi Counter row at the top of the dashboard as you pin it.

Open the Multi Counter page and you will see the four cards laid out side by side. Click the page title and rename the grid after the facility — "Riverside Aquatic Center — Live Capacity" or "Building C Pool" — anything more specific than the default. That title travels with the public share link, so the spectator does not see a generic "Multi Counter" header.

The parent guide on Multi Counter — pinning, sharing, and visibility walks through the mechanics in more detail; everything in that article applies here. The rest of this piece focuses on the pool-specific operational pattern.

On the Multi Counter page, click Share Grid. A modal opens with one public URL — view-only, no login, the whole grid on a single screen with all four zones updating live.

The right place for that URL is a tablet on the lifeguard stand. Bookmark the link to the tablet's home screen, leave the screen on, and the head guard has a constant glanceable read of every zone. When the Spa card flashes yellow on its way to five, the head guard sees it without leaving the chair.

This is also the right URL for any board the facility wants the public to see. Many community pools have started posting a wall-mounted display in the entry vestibule that reads "Main Pool 42/80 — Spa 4/5 — Kids Pool 12/20" in real time. Patrons walk in already knowing what they are getting. Complaints drop. The display is the same spectator URL on a TV-mode browser source.

Some operational notes specific to this view:

• The spectator page polls every few seconds and flashes only the cell that changed, so the rest of the board does not blink. Friendly to wall TVs.
• Spectators cannot increment, decrement, or change settings. The link is read-only by design.
• One active grid link per account — generating a new one rotates the old. Use the Revoke button at end-of-day or end-of-season to take the URL offline.

This is the section that matters most. The grid spectator link is what the head guard watches, but the head guard is not the one tapping the count up and down. The guards in the chairs are. Each guard needs a write-enabled link that touches only their zone and nobody else's.

For every counter on the dashboard, open the per-counter share modal and mint a named edit link. Use names that identify the chair and the shift — "Main Pool — Chair 1 — Sat AM", "Kids Pool — Maria", "Spa — Front Desk", "Deck — Manager." Each link is a write-enabled URL that the guard opens on their own phone, bookmarks to the home screen, and uses for the whole shift.

The operational pattern looks like this:

Head guard tablet  →  grid spectator link  (view-only, all zones, public)
Main pool guard    →  edit link → Main Pool counter only
Kids pool guard    →  edit link → Kids Pool counter only
Spa guard          →  edit link → Spa counter only
Front desk         →  edit link → Entries Today counter only

Four zones, four phones, four narrowly-scoped links. Nobody can accidentally bump the wrong counter. The spa guard sees only the spa card; the main-pool guard sees only the main pool. The aggregate appears on the head guard's tablet and the public wall display, both via the spectator link, and both update within seconds of any tap.

Three benefits fall out of this setup that are hard to get any other way:

Per-actor history. Because each edit link has a name, every increment is attributed to the link's name in the counter's history. End-of-shift, the audit reads "Maria added 22 to Kids Pool between 1pm and 2pm; Chair 1 added 47 to Main Pool over the same hour." That is useful for shift-end reporting and indispensable when a parent disputes whether their kid was counted.

Surgical revoke. Mid-shift, if a tablet goes missing or a volunteer walks off, you revoke that one named link from the counter's share modal. Every other guard's link keeps working. The grid spectator link is untouched. The full-system-wide "reset access" lever is the Revoke button on the grid share modal, and you do not have to pull it just because one phone walked away.

No login, no app install. The guard does not need an account. They open the URL on whatever phone they have, bookmark it to the home screen, and they are done. End-of-summer, the link is revoked and the guard's phone holds nothing of value. Onboarding a new guard mid-season is a 30-second job.

The deeper walk-through of the per-counter share modal and the named-link system is in the cross-device guide; read that piece if you want the full mechanics. For pool operations specifically, the four-phone fan-out above is the pattern.

Each cloud counter has its own Public/Private visibility toggle on the share modal. The grid spectator URL shows every counter you have pinned AND marked Public, and silently omits the ones marked Private.

A common community-pool choice: mark Main Pool, Kids Pool, and Spa as Public — those are the safety-relevant numbers a patron should know before walking in — and mark Deck as Private. The deck count is useful internally for staffing and shade-structure decisions, but a deck number on the front wall confuses patrons ("is the pool full or the chairs full?") and is rarely the number a parent is making a decision on.

Flip the flag back to Public any time the deck reading is something you do want to publish — for instance, during a busy holiday weekend when "deck almost full" is the message you want patrons reading on the way in.

The fifth counter — Entries Today at the front desk — is doing a different job from the four zone counters. It is a cumulative day-pass tally, incremented once per arrival and never decremented. The deck and zone counters are net-occupancy counts, going up on entry and down on exit, and never accumulating past the moment.

Keep them separate. Conflating "how many people entered today" with "how many people are on the deck right now" is the single most common mistake at community pools that try to count anything. The day-pass tally is what reconciles against the cash drawer at close; the deck tally is what tells the lifeguard whether to start a waitlist. Both are useful. Neither substitutes for the other.

A practical sanity check: the day-pass tally at end-of-day should equal or exceed the highest deck reading from the afternoon. If your day-pass total is 180 but the deck peaked at 220, somebody slipped in without scanning. If it is the reverse — 180 day-passes and the deck never broke 90 — the staff is undercounting on exit. Either reading on its own would not have surfaced either gap.

A community pool that counts every zone for a week starts to see patterns that anecdote could never produce. A few you can expect:

• Spa fills last and clears first. The spa is rarely the constraint at noon; it is the constraint at 6:30pm when families have left and adults take it over. If your spa is hitting cap in the evening, that is not a Saturday-afternoon problem.
• Kids pool peaks during swim lessons. The kids pool capacity is most stressed during scheduled programming, not free swim. If your wading pool keeps hitting cap mid-morning, your lesson schedule is the lever — not the wall posting.
• Main pool peaks 1pm to 3pm in summer. This is the textbook curve. If yours doesn't match, something specific to your facility is shifting it — a popular local lunch spot opening at 12:30, a shaded amenity that delays entry, a lifeguard rotation.
• Deck fills faster than water. People stake out a chair before getting in. Deck-at-cap with water-at-half is the most common pool complaint and is usually a furniture problem, not a capacity problem. More lounge chairs would help; reducing pool capacity would not.
• After-school 3pm to 5pm at apartment and HOA pools. Different pattern from rec centers. Plan staffing accordingly.

None of these are surprising in retrospect. None of them are visible without zone-by-zone counts.

Two minutes at close:

Revoke the grid spectator link if you do not want overnight access — for many facilities it is fine to leave running, but some boards prefer it offline after hours. The Revoke button is in the Share Grid modal.

Revoke each guard's named edit link. This is the per-counter share modal, one click per named link. Tomorrow's shift gets fresh links. If you keep the same staff day to day and you trust the phones, you can leave the links live for the season; choose by your facility's risk posture.

Leave the counters intact. Do not delete them at close — the next morning's grid is the same grid, the history accumulates day over day, and the patterns above only emerge when you let the counts run for weeks. Reset (set to zero) the zone counters at open if you want a fresh-day reading; do not delete them.

One touch the operations team usually appreciates: rename the named edit links at the start of each week to include the date or week number — "Kids Pool — Maria — Week 6". The audit log then reads cleanly when you go back through the season.

The pool-specific shape of the Multi Counter pattern is four zones, four phones, one tablet, one public board. The capacity field on each counter is the safety floor; the per-zone edit link is what the guards actually tap on; the grid spectator link is what the head guard and the patrons watch. Wire those three pieces up once at the start of the season and the daily operating cost is roughly zero.

If you have not yet created the four zone counters, the dashboard is where to start. If you want the parent piece on the grid itself — pinning, naming, the public visibility toggle — read the Multi Counter Pro guide. If you want the deeper walk-through of named edit links, the cross-device guide is the companion. And if a capacity-alerts notification add-on would fit your operation, drop us a note — that is where the roadmap is heading.