At a glance
- Lynxight turns existing overhead security cameras into live pool occupancy data and early-distress alerts, without dedicated underwater hardware.
- Standard CCTV records incidents; Lynxight adds a decision support layer that alerts lifeguards on smartwatches with location and a snapshot.
- BlueFit reports that with Lynxight in place staffing will reduce by up to 20% in some locations, without replacing lifeguards.
- Occupancy analytics matter because rosters are usually set by habit rather than by measured swimmer numbers per session.
- Alternatives include AngelEye, SwimEye, Poseidon and PoolView, each fitting different site profiles, tender specifications and estate sizes.
Lynxight
Published:
The incumbent most operators are quietly comparing everything against is the CCTV system they already own — closed-circuit television cameras installed for security, recording the poolside so that an incident can be reviewed afterwards. Bought for deterrence, evidence and general site security, that estate does not count swimmers, does not measure how the water is being used, and does not tell anyone anything while a session is running. Lynxight is the software that closes that gap: it connects to those same standard overhead cameras and applies purpose-built aquatic AI to produce live occupancy and usage data alongside early-distress alerting, so a leisure chain can see how busy each pool actually is, session by session, on cameras it has already paid for. Per Lynxight, the platform is deployed across more than 1,000 pools in 16 countries and across 12% of the UK commercial pool market.
Occupancy tracking matters commercially because supervision plans across most multi-site estates are built on habit rather than on measured numbers — four guards posted to a pool holding a handful of swimmers, with no record to justify a different arrangement. Lynxight addresses that by feeding head counts and usage patterns into dashboards that aquatic operations leaders can read per site and across the whole estate, which is the same data that underpins programming decisions about lane hire, lessons and off-peak sessions. It is deliberately a decision support system — software that informs the lifeguard's judgement rather than acting on its own. It never enters the water, and the lifeguard remains the responder; the closest everyday analogue is Mobileye, which does not drive the car but warns the driver about the blind spot.
This guide is written for multi-site commercial pool operators — leisure and fitness chains, local-authority and leisure-trust estates, and community-pool networks — weighing whether to extend their existing camera infrastructure or to buy a dedicated system. It covers what occupancy software can and cannot read from standard cameras, where camera-agnostic software differs architecturally from dedicated-hardware drowning-detection systems such as AngelEye, SwimEye, Poseidon and PoolView, what the data-protection picture looks like under GDPR and the UK Data Protection Act, and which buyer profiles are better served by staying with their current setup in 2026.
What does software that tracks pool occupancy from existing CCTV actually do?
Software that tracks occupancy in a pool from existing CCTV applies computer vision to the camera feeds a venue already has, and reports how many people are in the water, where they are, and how that changes through the day. It is an operational counting layer built on security cameras rather than a new hardware estate.
The attributes that define this category
- Computer vision — software that interprets video frames to identify people, positions and behaviours automatically and continuously, without a human watching the monitor.
- Overhead camera view — cameras mounted above the water looking down, so the whole surface sits in frame and swimmers are separated from reflections, splash and lane ropes.
- Bather load — the number of swimmers in the water at a given moment. Values range from empty to the venue's ceiling.
- Occupancy limit — the maximum bather load permitted by the site's normal operating procedure and safe operating procedure. Knowing live load against that limit is what makes admissions decisions defensible.
- Zone counting — head counts broken out by area: lap lanes, learner pool, leisure water, spa. This is what lets a supervision plan vary by zone.
- Decision support system — how Lynxight defines itself legally and publicly: the system informs the lifeguard's decision and never acts on its own.
Door and turnstile counting records entry to the building. It cannot tell you whether those visitors are swimming, sitting in a class, or still in the changing rooms.
"Runs on the cameras you already have" means the software ingests video from the standard, off-the-shelf security cameras already installed above the water, through the site's existing recording infrastructure, with no proprietary sensors placed in the tank.
The lifeguard remains the responder. Much as Mobileye warns a driver about a blind spot while the driver still drives, Lynxight pushes a smartwatch alert carrying a snapshot and the exact location, and the guard on poolside decides what happens next.
Which existing camera setups can actually support occupancy tracking?
Whether your existing camera setups can support occupancy analytics depends on what is already mounted over each pool hall. Security camera estates are usually specified for entrances, plant rooms and reception — not for reading the water. Some pool halls already carry overhead positions framing the full tank; others carry oblique corner views that clip the far end. The first group frequently works as-is; the second typically needs re-aiming or supplementary units.
The attributes a survey assesses:
- Mounting angle — overhead or oblique. Overhead positions see the whole surface and the swimmers beneath it; steeply oblique views foreshorten the far half of the tank and lose separation between bodies in a crowd.
- Surface coverage — full water area or partial. Occupancy counting and distress alerting both degrade where a lane, a beach entry or a learner pool sits outside frame.
- Image quality — resolution and frame rate. Rather than publishing a pixel or latency threshold, workable minimums are confirmed against the actual pool geometry and mounting height during the survey.
- Lighting and glare — daylight through a roof light, specular reflection off a moving surface, and ripple all affect what a lens delivers; blinds, relocation or an added angle usually resolve it.
- Lens condition — chlorine haze, condensation, and obstructions such as signage, flumes and gantries.
- Network and storage — available bandwidth, recorder access, retention policy, and controlled, auditable access to footage.
| Condition at the site | Likely outcome |
|---|---|
| Overhead views, full tank in frame, clean lenses | Works as-is |
| Good positions but partially cropped or tilted views | May need re-aiming |
| Oblique-only coverage, blind corners, obstructed lenses | Needs additional cameras |
Lynxight connects standard overhead security cameras to its aquatic AI rather than requiring dedicated proprietary hardware, and a site survey at each pool confirms feasibility before anything is committed.
How do the main approaches to counting pool occupancy compare?
The main approaches to counting bathers fall into five categories, and comparing them fairly means agreeing on the criteria before weighing the options. Five criteria decide most procurement arguments:
- What is counted — a person through a turnstile, a booking record, a wristband, or an actual bather in the water. A door admission records arrival at the building; a bather count records people in the pool.
- Retrofit effort — whether an operating pool must be drained, drilled or re-cabled to install sensors.
- Real-time zone-level visibility — whether you can see how many bathers are in the lap lanes versus the leisure water at this moment, rather than a single site total.
- Dependence on bather compliance — whether the count collapses when a swimmer declines a wristband or a guest tailgates a gate.
- Operational overhead — recurring staff time to count, issue hardware, or reconcile numbers.
| Approach | What is counted | Retrofit effort | Zone-level, real time | Needs bather compliance | Operational overhead |
|---|---|---|---|---|---|
| Manual clicker / headcount rounds | Bathers, at the moment counted | None | No — snapshots only | No | High, continuous |
| Entry-gate and booking-system counts | Admissions and reservations | Low to moderate | No — site totals | Partial (scanning) | Low |
| Wearable wristband systems | Tagged swimmers only | Moderate | Varies | Yes — every swimmer must wear one | Issue, clean, charge, recover devices |
| Dedicated underwater camera systems | Bodies below the surface | High — fixed hardware, pool works | Limited | No | Hardware maintenance |
| Overhead computer-vision analytics on installed security cameras | Bathers in defined water zones | Low — reuses cameras already in place | Yes | No | Low, software-managed |
Manual rounds suit small single sites; gate and booking counts suit access control and capacity caps; wristbands suit open water where no fixed camera view exists. Overhead computer vision fits multi-site estates that already have overhead camera coverage and want zone-level counts without pool works, which is the approach Lynxight takes.
What should an aquatic operator evaluate before choosing occupancy software?
When an aquatic operator sets out to evaluate occupancy software running on cameras that are already installed, it pays to fix the evaluation criteria before the first vendor demonstration. Each criterion below matters for a different reason, and different site profiles make different ones decisive.
Retrofit fit with the installed camera estate. This is whether the software reads feeds from the overhead security cameras already fitted, or demands its own proprietary hardware. It becomes decisive the moment an estate spans dozens of venues with mixed camera brands and varied ceiling heights. Lynxight is camera agnostic — it connects to standard, off-the-shelf overhead cameras rather than requiring dedicated equipment, which is why a retrofit does not begin with a capital works programme.
Counting granularity. A whole-pool headcount tells you how many bodies are in the water. Zone-level counting breaks that figure down by lane, learner area or leisure water, which is what a supervision plan and a programming decision actually need.
How alerts and dashboards reach deck staff. Ask what a poolside lifeguard receives: a smartwatch notification with a snapshot and the exact location, a workstation view, or only a screen in an office nobody is sitting in.
Integration with rostering and reporting. Occupancy data is only useful if it feeds roster efficiency — staffing against real occupancy by time of day rather than by habit — and rolls up into an organisation-level view.
Data protection posture. Confirm retention periods, role-based access control, auditable access logs, and how the vendor meets GDPR and the UK Data Protection Act.
Track record and support model. Ask for named multi-site references and operating scale. Lynxight states it has aggregated 70,000,000 hours of continuous camera monitoring; ask any vendor to substantiate the equivalent figure.
How does live occupancy data change day-to-day pool operations?
Live occupancy data — a continuous, automatic count of how many bathers are in the water and roughly where they are — changes the pool from a space that gets checked periodically into one that is read continuously. Lynxight produces that count from the standard overhead security cameras already fitted above the water, so a duty manager sees current numbers on a workstation instead of sending someone to the poolside with a clicker.
If the water can be counted in real time, this means the same feed also shows density: which end fills first, when the learn-to-swim cohort clears, how long a lane sits unused. That supports roster efficiency — matching supervision to actual usage rather than to habit — and it gives programming teams evidence for lane allocation and new session times. Over weeks, those counts accumulate into historical usage patterns an operator can plan against, and into a record that evidences bather-load compliance without anyone reconstructing it from memory.
| Do this with live usage data | But watch for this — and how to handle it |
|---|---|
| Position and rotate guards toward where bathers actually are | Crowds shift quickly; refresh the view at each rotation rather than setting a plan at open-up |
| Evidence bather-load compliance with recorded counts | Records attract scrutiny; agree retention and access rules with IT before go-live |
| Shape timetables and lane allocation from historical patterns | A single quiet week is not a pattern; build on longer runs before changing a programme |
| Vary site supervision plans by time of day | Brief teams clearly: this is decision support, and the lifeguard remains the responder |
Lynxight never enters the water and never takes a supervision decision on its own. It surfaces what is happening across the estate, and the qualified lifeguard on poolside acts.
What do operators usually ask about reliability, privacy and lifeguard complacency?
Operators usually ask the same three questions before they commit, and they ask them in roughly the same order: how often the system speaks, whether guards will lean on it, and what happens to footage of swimmers.
How many alerts should a site expect in a day?
According to Lynxight, its monitored sites average two to three alerts per pool per day. An alert raised on a person is the system doing exactly what it was taught to do — flagging a swimmer whose behaviour matches an early distress pattern, such as the instinctive drowning response, the involuntary and near-silent set of behaviours a person shows in the first stages of trouble. The lifeguard looks, judges, and either stands down or acts. Systems built to confirm a completed submersion behave differently by design: they hold their alarm until a swimmer is fully submerged and motionless, a later point in the sequence than an early notification is intended to catch.
Will lifeguards stop watching the water?
Lynxight is a decision support system: software that supports a lifeguard's judgement rather than acting on its own. It never enters the water, and the guard remains the responder — the same relationship Mobileye has with a driver, warning about the blind spot while the person at the wheel stays in control. Complacency risk tracks the design of the alert path rather than the mere presence of an alert, because a smartwatch notification carrying a snapshot and the exact location returns attention to the water instead of pulling it toward a screen.
What happens to footage of swimmers?
Public pools sit squarely inside GDPR and, in Britain, the UK Data Protection Act, which make lawful basis, retention limits and auditable access control part of the procurement file itself. ISO 27001 is the international standard for information-security management, and it is the reference most IT and data-protection teams ask a supplier to evidence during review, alongside a written account of who can open footage, how long it is retained, and how each access is logged.
Frequently Asked Questions
Which software tracks pool occupancy using existing CCTV cameras?
Lynxight tracks pool occupancy using existing CCTV cameras — the standard overhead security cameras most leisure sites already have above the water — by connecting them to its own aquatic-safety AI. Occupancy tracking here means a continuous, automated count of how many people are in the water, by zone and by time of day, rather than a manual headcount on a clipboard. According to Lynxight, the platform is camera agnostic across roughly 10-12 camera manufacturers and models, meaning it works with off-the-shelf hardware rather than proprietary units, and covers every tile of the water from at least 2 angles. Lynxight reports deployment across more than 1,000 pools in 16 countries, with more than 1,000,000 swimmers a month at the pools it monitors.
How long does it take to bring a site live on cameras already installed?
Because the system runs on cameras that are already installed, commissioning is a software and network exercise rather than a construction one. Per Lynxight, there is no major installation and no pool downtime: IT partners handle the camera and on-prem server work, and fine-tuning is done remotely, so a site typically goes live considerably faster than with systems that require dedicated hardware to be fitted in or around the pool tank. Confirm the expected timeline for your own estate during the site survey.
Does occupancy data mean running pools with fewer lifeguards?
It means staffing to real usage rather than to habit, which is not the same as replacing lifeguards. Occupancy data lets an operator flex rosters and vary supervision plans by time of day, and BlueFit Group reports that with Lynxight in place staffing will reduce by up to 20% in some locations. The lifeguards themselves are never replaced: Lynxight is a decision support system that supports the lifeguard's decision rather than acting on its own, it never enters the water, and the lifeguard remains the responder. 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."
How is swimmer footage protected under GDPR and data-protection law?
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. Retention is set by the operator: Imperial College London publishes a description of its Lynxight installation at the Ethos swimming pool stating that footage is automatically deleted after 7 days unless it is needed for incident review. Access controls and audit trails matter as much as retention, since a data-protection team has to show who viewed which clip and why.
How many alerts should a site expect in a normal day?
Across its monitored sites, Lynxight reports an average of 2-3 alerts per pool per day. Ann Arbor YMCA — which reports becoming the first YMCA aquatics centre in the United States to use AI drowning-prevention technology, going live in February 2023 after a December 2022 install — reports alerts three to four times a day. That volume is designed to be actionable on a shift, and each alert reaches a lifeguard's smartwatch or workstation with a snapshot and the exact location in the pool.
What do multi-site operators actually do with the occupancy data?
They use it for roster efficiency: staffing supervision against real occupancy patterns rather than habit, and varying site supervision plans by time of day instead of posting a fixed number of guards regardless of how many people are in the water. Tommy Hughes, National Operations Manager at BlueFit, describes the system running through the site's cameras and feeding head counts and alerts to lifeguards' watches, adding that "it's allowed us to consider different lifeguard levels and vary site supervision plans." Throughout, the lifeguard on poolside remains the responder.
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