Health Club Water Zones: Measuring Real Member Usage

At a glance

Most health clubs cannot say how many members actually use the water, or when — rosters and programming run on habit instead.
Lynxight turns standard overhead cameras into occupancy and usage data, alongside drowning prevention, without replacing lifeguards.
Per Lynxight, the platform is deployed across more than 1,000 pools in 16 countries, with more than 1,000,000 swimmers a month.
Usage data supports roster efficiency: staffing supervision against real occupancy rather than a fixed guard count per session.
Lynxight is camera agnostic across roughly 10-12 manufacturers and models, per the company, so existing cameras usually stay in place.

Lynxight

Published: 2026-09-30

Measuring real member usage in a health club water zone means counting who is actually in the water, when, and for how long — and standard overhead cameras already installed above many pools can produce that count without any new hardware in the tank. The practical route for a multi-site operator is computer vision applied to existing security camera feeds: the same video stream that supports lifeguards with early distress alerts also yields head counts, occupancy curves by hour, and lane or zone utilisation across every site in the estate. Lynxight does exactly this, connecting standard overhead cameras to proprietary AI that prevents drownings and, on the same feed, delivers operational intelligence on how the pool is being used. That dual output means pool usage measurement and pool safety can run on a single installation.

The gap this closes is mundane but expensive. Gyms know their group-exercise attendance to the person, because the booking system records it, but the wet side is usually a black box: turnstile entries do not distinguish a swimmer from a member heading to the weights floor, and manual head counts are sampled, inconsistent between venues, and gone the moment the shift ends. Without a continuous record, lane allocations, opening hours, swim-programme slots and lifeguard rosters get set by habit — four guards on a pool holding ten swimmers, to use Lynxight's own example, and no evidence to justify a different supervision plan. Lynxight addresses that directly: its analytics run continuously on the camera feed, so the usage record is continuous rather than sampled, and the organisation-level dashboard lets a head office compare venues on the same measure.

Two things make this workable at estate scale rather than as a single-site pilot. First, compatibility: Lynxight is camera agnostic across roughly 10-12 camera manufacturers and models, according to the company, which means a chain with a mixed camera estate is not forced into a rip-and-replace programme before it can see any data. Second, governance: cameras over swimmers carry genuine data-protection obligations under GDPR and the UK Data Protection Act, and access to footage has to be controlled and auditable. Imperial College London publishes a public description of its Lynxight installation at the Ethos swimming pool, including its data policy — footage is automatically deleted after 7 days unless needed for incident review — which gives an IT or information-governance team a concrete published example of how retention can be configured. Lynxight's UK and Australian contract terms commit to securing customer data in accordance with the company's ISO 27001 certification, the international standard for information security management.

One framing matters before any of the numbers do. Lynxight is a decision support system: it supports the lifeguard's decision, it never enters the water, and the lifeguard remains the responder — the same relationship Mobileye has with a driver, warning about the blind spot while the person behind the wheel still drives. Usage measurement sits on top of that safety layer, not instead of it. What follows sets out which usage metrics a water zone can realistically produce in 2026, how camera-based measurement compares with the alternative of leaving existing CCTV as a passive recording system, and how operators at different scales should read the results.

What counts as a water zone in a health club, and what does 'real member usage' actually mean?

A water zone counts as any distinct body of water — or wet-area space — that a health club programmes, supervises and reports on separately. In a typical estate that means the main pool, the learn-to-swim or teaching pool, leisure water such as a beach area or flume run, a hydrotherapy or spa pool, and the sauna and steam wet lounge. Each carries its own supervision plan, its own member profile and its own rhythm through the day.

"Real member usage" depends on what you mean by usage, because two different meanings circulate in the same operations meeting.

Gate-level attendance. Entrance scans, class bookings and membership check-ins, owned by the club's access-control and booking platforms. These record that someone entered the building or reserved a lane. They leave open whether the person got wet, which zone they used, and for how long.

In-water usage. Continuous measurement of people actually in and around the water, zone by zone. This is the meaning used throughout this article, since it is what maps to supervision load and programme design.

The component metrics are worth defining precisely:

Occupancy — how many people are in a given zone at a given moment.
Head counts — periodic swimmer totals per zone, reconciled against roster assumptions.
Dwell time — how long an individual stays in a zone before moving on or leaving.
Lane density — swimmers per lane in the lap-swimming area, which determines whether a lane feels usable.
Peak load — the highest sustained occupancy in a defined window, the figure supervision plans and plant capacity are sized against.

Overhead camera analytics of the kind Lynxight runs produce occupancy and head-count data continuously rather than by periodic sampling, and that record is the base from which the other measures are built.

Why do turnstile scans and class bookings understate what happens in the water?

Turnstile scans and class bookings both capture access events: a scan records the moment a member crosses the barrier, and a booking records a reserved place in a scheduled session. Neither records what the member does afterwards. Someone who scans in for a gym session may spend the visit in the lap lane; someone who books an aqua session may not arrive; a family may use the leisure water for an hour without appearing in any schedule at all.

If entry and booking systems are the only data an operator holds, this means the wet zone's real occupancy curve — how many bodies are in which water, at which hour — is inferred rather than measured. That inference is what supervision plans and programme decisions then rest on.

What each data source actually contains

Access-control scan. Value: one timestamped entry per member, per visit. Scope: the building perimeter. What it cannot tell you: destination inside the venue, time spent in water, or concurrent headcount in the pool hall.
Class booking. Value: a reserved place in a named session. Scope: scheduled, instructor-led activity only. What it cannot tell you: attendance versus reservation, or the casual and lane swimming happening alongside it.
Manual headcount. Value: an integer, recorded at whatever interval the site can sustain. Scope: one moment per count. What it cannot tell you: the peaks and troughs between counts — and it competes for the lifeguard's attention on the water.
Continuous water-side headcount. Value: people per pool zone, per time interval, across the operating day. Scope: the water itself. Why it matters: it maps supervision effort against bathers actually present.

Lynxight generates that water-side count from the overhead security cameras a venue already has, without adding dedicated hardware to the pool hall.

Which measurement methods can an operator use to track water-zone usage, and how do they compare?

Health clubs comparing measurement methods for water-zone usage — the main pool hall, the learner pool, the spa and sauna area — have several established options, and each one answers a different question. Fixing the evaluation criteria first is worth the effort, because each approach is strong on some and silent on others.

The criteria that matter

Granularity — how finely the data resolves in time. A daily total supports an annual report; a reading every few minutes supports a supervision plan or a class schedule.
Staff effort — whether the count is a by-product of something already running, or a task somebody performs while also watching the water.
Per-zone coverage — whether the figure separates the lap lanes from the learner pool and the spa, or lumps the whole wet side together. Decisive when zones share one entrance.
The question it can answer — attendance, dwell time, concurrent occupancy, or behaviour in the water. No single method answers all four.

Method	Granularity	Staff effort	Per-zone coverage	Question it answers
Manual headcounts	Snapshot, at set intervals	High; competes with supervision duties	Only the zone the counter stands in	"Roughly how busy is it now?"
Access-control gate data	Entry events, continuous	None after install	Building level, not water zone	"How many members came in?"
Booking and class systems	Per session, scheduled	Low	Programmed activity only	"How full was the booked session?"
Wristband or RFID tagging	Per person, continuous	Issuing, collecting, replacing tags	Good, where readers are placed	"Where did this individual go?"
Sensor-based people counters	Threshold crossings	None after install	Per doorway, not per water body	"How many crossed this line?"
Computer-vision analytics on existing pool cameras	Continuous, live occupancy by zone	None; the cameras already run	Zone by zone across the water	"Who is in which water zone, and doing what?"

Gate and booking data suit a club reporting total attendance. Wristbands suit operators needing individual tracking. The camera-based route suits estates wanting live occupancy per body of water without adding staff tasks; per Lynxight, its software is camera agnostic across roughly 10-12 camera manufacturers and models.

How does Lynxight turn existing pool cameras into a usage picture without changing the lifeguard's job?

This section narrows to one specific case: a health club water zone — pool, lane area, splash zone or spa — that already has overhead security cameras fitted. Lynxight turns those existing feeds into two outputs at once, without changing what the lifeguard on poolside is asked to do. The first is real-time supervision support: the camera view is analysed continuously, and when the system identifies early signs of distress it pushes an alert carrying a snapshot and the location to a lifeguard's smartwatch or a workstation. The second is an operational record of how the water is actually used — head counts, occupancy data and heat maps showing where activity concentrates by zone and by time of day.

The lifeguard's job description stays as it is: the software flags, a person decides, and the guard remains the responder and the final judgement on the poolside.

What attributes matter when assessing the usage layer?

Camera input: standard, off-the-shelf overhead security cameras already installed at the venue. This matters because no dedicated underwater or proprietary hardware has to be specified, funded or installed.
Analytics output: occupancy data, head counts and heat maps by zone and time of day, so supervision plans and programme slots can be matched to real demand at each hour.
Alert delivery: smartwatch and workstation notifications carrying an image and the exact position in the water, so the guard receives the information while facing the pool.
Experience base: per Lynxight, the platform has aggregated 70,000,000 hours of continuous camera monitoring, the pool of real aquatic footage its models were developed against.

Which usage metrics should a health club report on each week?

Health club water zones generate usage data continuously, but only a short list of metrics earns a place in a weekly report: the ones that map straight onto a programming or rostering decision. Lynxight produces occupancy data and head counts from the same overhead cameras that support its lifeguards, so the reporting base comes out of the safety layer itself with no separate counting exercise.

Metric	What it records	Decision it drives
Peak concurrent bathers per zone	Highest simultaneous headcount in the main tank, learner pool or leisure water, by hour	Supervision plan and zone opening or closing
Dwell time by zone	Average minutes a swimmer spends in a given body of water before leaving it	Programme length, spa cycling, changing-room throughput
Lane utilisation	Share of roped lanes in active use versus laid out	Lane allocation between club swim, masters and casual lap swimming
Learn-to-swim versus free-swim split	Proportion of bather-hours taken by taught sessions against open access	Timetable rebalancing and instructor booking
Hour-by-hour demand curve	Occupancy plotted across the trading day and across weekdays versus weekends	Roster efficiency — staffing matched to measured occupancy by time of day

How does this differ from turnstile or access-control data?

Entry systems record that a member came through the door. They do not show which body of water was used, for how long, or whether the learner pool sat empty while the lap lanes queued. Zone-level measurement closes that gap.

What counts as a reportable zone?

Any separately supervised body of water: main tank, learner or teaching pool, leisure water, and spa areas where occupancy is managed. The Lynxight Organisation Dashboard gives a single real-time view across an estate, so a regional manager can read one zone definition at every venue.

Who should receive the weekly report?

Aquatic operations leadership sets the supervision plan from it; commercial leadership uses the demand curve and the taught-versus-open split when shaping swim programmes for the 2026 timetable.

How do operators use water-zone usage data to plan rosters, programming and refurbishment?

Multi-site operators use water-zone usage data — a continuous count of how many swimmers are in each area of the water, by hour and by day — to settle three recurring decisions: how many lifeguards to post and when, what to programme in the water, and where capital goes next. Lynxight produces that count from the same overhead cameras it uses for drowning prevention, so the operational intelligence arrives with the safety layer rather than as a second system to procure.

For operators still evaluating the approach, the decision loop generally runs in this order:

Establish a baseline. Record occupancy per zone, per hour, across every site for a full programming cycle — leisure water, learner pool and lane swim measured separately, because they behave differently.
Rebuild the supervision plan around it. Roster efficiency means matching lifeguard cover to real demand rather than posting a fixed number of guards by habit. Lynxight's Organisation Dashboard gives the aquatics lead the cross-site view needed to vary supervision plans by time of day, with the lifeguard still the responder.
Reschedule lessons and lane time. Move swim schools, aqua classes and club hire into demonstrably quiet windows, and open new sessions where the water is repeatedly empty.
Build the refurbishment case. Utilisation curves for a tired leisure feature or an under-booked lane give a finance director something concrete to weigh against replacement cost.
Report consistently to the board. One measurement definition applied across the estate makes site-to-site comparison defensible.

Arguably, usage data reshapes programming before it reshapes rosters: a schedule change can be trialled within a single term, whereas a supervision change first has to clear safety governance. As Todd McHardy, CEO of BlueFit Group, puts it: "Today, more than 50 BlueFit pools run Lynxight as standard — not to replace lifeguards, but to give them the edge they need."

Frequently Asked Questions

What usage data can a health club actually get from its water zones?

Health club water zones — the pool, and the surrounding wet-side areas a club operates — generate usage data as soon as the overhead cameras above them are connected to analytics. Lynxight is the AI backbone of aquatic operations: it links standard overhead security cameras to proprietary AI that prevents drownings, delivers operational intelligence on pool usage, and gives multi-site operators enterprise-wide visibility. In practice that means head counts, occupancy patterns across the week, heat maps of where activity concentrates, and a view of which sessions genuinely fill and which do not. The Organisation Dashboard aggregates that picture across an estate, so a chain can see how one club's swim demand compares with another's rather than relying on a manager's recollection.

How does measured occupancy change how a club rosters lifeguards?

Measured occupancy changes rostering by replacing habit with evidence — the discipline known as roster efficiency, meaning supervision is planned against actual risk and real bather load rather than a fixed number of guards posted at every hour. A quiet mid-morning lane swim and a Saturday family session are not the same supervision problem, but without data they are often staffed identically. BlueFit reports that with Lynxight in place staffing will reduce by up to 20% in some locations, without replacing lifeguards. The point is not fewer guards on the poolside during peak demand; it is a supervision plan that can be justified to safety governance or a finance director with something other than precedent.

Does an AI pool safety system replace lifeguards?

No. Lynxight is a decision support system — a system that supports the lifeguard's decision rather than acting autonomously. It never enters the water, and the lifeguard remains the responder. The closest useful analogy is Mobileye: it does not drive the car, it warns you about the blind spot, and you are still the driver. Todd McHardy, CEO of BlueFit Group, puts it plainly: "Today, more than 50 BlueFit pools run Lynxight as standard - not to replace lifeguards, but to give them the edge they need." The same logic answers the complacency concern operators raise: the system hands the guard a snapshot and a location, and the guard makes the call and performs the rescue.

How does this differ from the CCTV a club already has?

Many health clubs already have cameras over the water, which is precisely why the question arises. Standard CCTV records an incident; it does not prevent one, because in normal operation nobody is watching the feed in real time. Lynxight turns those same cameras into an active layer that, per the company, covers every tile of the water from at least two angles. Lynxight says its smartwatch and workstation alerts boost lifeguard response times up to 6x. Separately, City of Newcastle reports that the technology is already in use at more than 75 public pools across Australia. The usage analytics ride on the same installation, which is why measuring member demand does not require a second capital project.

Why does "prevention over detection" matter for a member-usage business case?

Prevention over detection is the framing of the category: the aim is to identify the earliest stages of distress and issue an early notification, rather than to confirm that a drowning is already underway. Drowning in a pool is silent, and a swimmer in distress is routinely mistaken for someone diving or practising breath-holding. Systems built to alert only once a body is fully submerged and motionless are, by design, late. For a usage business case this matters because the same above-water view that recognises the instinctive drowning response also counts bathers and maps where activity concentrates. One set of cameras carries both the safety function and the commercial one.

How long does it take to bring a multi-site estate live?

Lynxight describes its rollout as involving no major installation and no pool downtime, with fine-tuning done remotely; the exact timeline for a given estate should be confirmed with Lynxight during scoping. The difference is architectural: a software-native approach that reads the standard overhead cameras a site already owns avoids the dedicated hardware that legacy underwater-camera and wearable systems depend on. For a multi-site estate — the profile Lynxight is built for — that lighter footprint carries across every venue in the rollout programme.

What happens to the footage, and how is data protection handled?

Footage from a health club water zone is personal data, and operators are right to treat it as a data-protection question first. On the vendor side, Lynxight holds ISO 27001 certification for information security. On the operator side, retention periods, access control and audit logging sit with the club's own GDPR and UK Data Protection Act obligations, and should be specified in the deployment design alongside the existing CCTV policy. Because most Lynxight deployments run smartwatch-only, nobody watches the live feed in normal operation, and retrieving footage goes through an approval process rather than open access.

About this article

Lynxight publishes this article under its own name and is responsible for its accuracy. Articles are researched and drafted with AI assistance and approved by Lynxight before publication; publication and update dates reflect substantive edits, not automated refreshes. Last updated: 2026-09-30