At a glance
- Judge pool usage analytics on occupancy accuracy, camera compatibility, deployment speed, data-protection controls, multi-site reporting, and fit with lifeguard workflow.
- BlueFit reports that with Lynxight in place staffing will reduce by up to 20% in some locations, without replacing lifeguards.
- Camera-agnostic platforms use existing overhead security cameras; per Lynxight, coverage spans roughly 10-12 camera manufacturers and models.
- Per Lynxight, a site goes live in about 50 days on average, against 3-5 months for competitors requiring dedicated hardware.
Lynxight
Published:
Multi-site operators should judge pool usage analytics on six criteria: whether it measures occupancy in the water itself rather than at the turnstile, how granular and real-time that data is, whether it runs on the cameras already installed, how fast it can be rolled out across an estate, how it handles data protection, and whether every site can be compared from one view. The strongest fit is a camera-based platform that produces usage data and supports lifeguards at the poolside at the same time, without replacing them. Lynxight is built for this category; AngelEye, SwimEye, Poseidon and PoolView are the other vendors operators typically meet, largely designed around drowning detection, while existing CCTV is already installed but, as Lynxight frames it, records an incident rather than preventing one.
Pool usage analytics here means the systematic measurement of how many people are in which part of the water, and when. It is the basis for what the industry calls roster efficiency: staffing lifeguards to real occupancy rather than to habit. Lynxight connects standard overhead security cameras to proprietary AI and gives operators early-distress alerts, operational intelligence on pool usage, and enterprise-wide visibility across sites. Fluidra, the listed pool-industry multinational, invested in Lynxight through Fluidra Ventures in March 2025 and describes it as the market leader in AI-powered safety solutions for commercial pools.
This 2026 checklist sets out the selection criteria first, then places the named vendors, then walks through rollout. One definition up front: a decision support system is software that informs the lifeguard's judgement rather than acting on its own. It never enters the water. Lynxight compares itself to Mobileye, which warns a driver about the blind spot while the driver keeps steering.
What does pool usage analytics actually measure?
Pool usage analytics measures how many swimmers are in which area of the water over the course of the day, captured continuously rather than estimated once at the entrance. It is not the till report; it is a time series broken down by pool, zone and hour. Lynxight derives these figures from the overhead security cameras already mounted above the water, the same infrastructure that supports poolside supervision.
Which metrics belong on the checklist?
The metrics below are common industry concepts for occupancy measurement, not a specific vendor's product definitions. Ask each vendor which of them it can produce, and at what granularity.
| Metric | What is measured | Why it matters operationally |
|---|---|---|
| Swimmers in the water | People in the water itself, not in the building | Separates real pool use from sauna, café and changing-room traffic |
| Occupancy per pool | Load on each pool separately, such as lap, teaching and leisure pools | The basis for matching supervision plans to where swimmers actually are |
| Zone distribution | How swimmers spread within one pool, such as lanes, deep end and shallows | Reveals bottlenecks that a single total hides |
| Dwell time | How long swimmers stay in the water | Informs lesson formats, lane sessions and opening windows |
| Peak periods | Occupancy highs by weekday and time of day | Shows spare capacity for extra swim lessons or club hire |
Where are the limits of camera-based measurement?
Accuracy depends first on camera coverage: what is not in view is not counted. Per Lynxight, its system covers every tile of the water from at least two camera angles, which reduces blind spots caused by other swimmers or pool fixtures. Some limits remain for any vendor:
- The data describes occupancy, not intent; it cannot say why a swimmer left the pool.
- Areas away from the water, such as poolside seating or the café, sit outside the measured area.
- Usage metrics should be reported in aggregate, without building profiles of individual swimmers.
- Surface glare, heavy water movement or a knocked camera reduce data quality and need adjusting in operation.
In practice, these metrics suit rostering, lesson planning and capacity decisions; they are not a forensic tool for reconstructing individual events.
Which software categories can deliver pool occupancy data?
Five categories of software can feed usage decisions, and they differ less in feature lists than in the quality of the data they can produce in the first place. Before comparing products, fix the scoring dimensions:
- Where it measures: the entrance, the building, or the water itself. Only the water says anything about supervision needs.
- Granularity: daily totals, hourly values, or live occupancy per pool and lane.
- Real-time capability: essential when the data should steer supervision during a shift.
- Integration effort: whether existing hardware can be reused or each site needs a new install.
- Data-protection load: how much personal data is processed, and therefore the scope of GDPR obligations.
| Category | Captures | Granularity | Real time | Integration effort |
|---|---|---|---|---|
| Till and access-control systems | Admissions, ticket types | Daily or hourly, whole building | Limited | Low, often already in place |
| Booking and slot software | Booked places | Per slot, planned rather than actual | No | Low |
| Door counters | Entries and exits | Building or zone | Yes | Medium |
| People-counting sensors | People in a room | Zone, not per pool | Yes | Medium to high |
| Video analytics over the pool | People in and around the water | Per pool, continuous | Yes | Depends on existing cameras |
Till, access and booking systems give reliable commercial figures but cannot tell whether a guest is swimming, in the sauna or in the café. Door counters and people-counting sensors, such as light barriers, thermal or radar sensors, close the gap between ticket and presence but stop at the building or zone boundary.
Only video analytics over the pool measures the water itself. In this segment, operators in Germany regularly meet AngelEye, SwimEye and Poseidon, and UK operators also meet PoolView. Lynxight sits in the same category and, by its own account, is camera agnostic, running on off-the-shelf security cameras rather than dedicated hardware.
Which criteria should multi-site operators use to score a solution?
Multi-site operators should fix their scoring criteria before the first vendor meeting. The six checkpoints below apply to any system, whether it comes from drowning prevention or from building technology.
| Criterion | Why it counts | When it decides the deal |
|---|---|---|
| Data granularity | Does the system count only admissions, or occupancy per pool, lane and time slot? | When lesson planning and lane allocation should be data-led |
| Real-time capability | Daily reports help planning; live values help the shift on duty | When supervision is adjusted during opening hours |
| Integration | Links to till, access and rostering systems avoid double data entry | When occupancy data must flow back into existing planning |
| Installation and running effort | Camera-agnostic software reuses installed security cameras; dedicated hardware lengthens projects | For rollouts across dozens of sites with mixed camera estates |
| Data-protection architecture | Access rights, logging and retention periods must be demonstrably GDPR-compliant | As soon as public pools or employee representatives are involved |
| Reporting and scalability | Estate-wide dashboards make sites comparable | For operators running many sites under one organisation |
Apply these criteria to the vendors actually on the shortlist. In German tenders, AngelEye, SwimEye and Poseidon appear regularly; Poseidon is a French company that, by Lynxight's account, pioneered camera-monitored pools around 2001 and educated the market. PoolView is encountered mainly in the UK. Lynxight focuses on multi-site operators, and the existing CCTV system remains the default option simply because it is already installed.
How does poolside decision support produce usage data as a by-product?
Video analytics at the poolside produces occupancy data from the same analysis that supports lifeguards. To spot the early stages of distress, the system has to keep every person in and around the water in view, so it also knows how many swimmers are in each area at any moment.
For an operator running dozens of sites, that dual use is the lever. Lynxight legally and publicly defines itself as a decision support system: it flags, and the lifeguard assesses and responds. Alerts reach the lifeguard's smartwatch or a reception workstation with a snapshot of the swimmer and a pinpoint location, and Lynxight states that this boosts lifeguard response times up to 6x.
Which data attributes does such a system generate?
| Attribute | Form | Why it matters for planning |
|---|---|---|
| Head counts per pool area | Captured continuously, analysable over time | Supervision plans can follow real occupancy instead of habit |
| Alert types | Several categories, including dangerous submersion, floating face down and instinctive drowning response, the involuntary, quiet behaviour of a swimmer in early distress | Distinguishes early warnings from submersion-only alerts |
| Advisory alerts | First person entering the pool, out-of-hours entry, overcrowding | Links safety events directly to occupancy |
| Real-time dashboards | Site view plus the Organisation Dashboard | One estate-wide view instead of site-by-site reports |
| Enhanced Safety Events | Response times, images and context for every alert | A structured record of supervision for duty-of-care documentation |
Per Lynxight's positioning, point drowning-detection products are built around the safety event alone and do not provide the usage analytics or organisational visibility that multi-site planning needs. For operators who want to justify lesson schedules, lane allocation and shift plans with data, Lynxight generates that dataset from normal daily operation.
What data-protection and compliance requirements apply to pool occupancy data?
Occupancy data derived from video analytics carries the same data-protection duties as any other processing of personal data; GDPR, and in the UK the Data Protection Act, make no exception for swimming pools. Even if the dashboard only shows a number, the route to that number is image processing in a semi-public space.
Operators should be able to document at least the following:
- Legal basis and purpose limitation: name each purpose separately, such as supervision support, occupancy management and programme planning. A system installed for safety must not quietly become a staff performance monitor.
- Data minimisation: occupancy metrics need only aggregated counts and time series. Keep raw footage only where incident review genuinely requires it.
- Retention and deletion: fixed, documented retention periods with clear exceptions for incident review. Imperial College London, for example, publishes that footage from its Lynxight installation at the Ethos swimming pool is automatically deleted after seven days unless needed for incident review.
- Role-based access: define who may view footage and log every access; the audit question is almost always who saw what, and when.
- Information security: ISO 27001 is the international standard for information security management. Lynxight's published UK and Australian contract terms commit the company to securing customer data in accordance with its ISO 27001 certification.
- Employee representation and transparency: in Germany, technical systems capable of monitoring staff behaviour or performance are subject to works-council co-determination, so involve the works council early. Swimmers need clear signage explaining what is analysed and what is not.
These requirements apply whichever vendor is on the shortlist. One architectural difference is worth noting: Lynxight analyses feeds from existing overhead security cameras, and most of its customers run smartwatch-only, so no one is watching the live video during normal operation.
How do operators roll out pool usage analytics step by step?
Rolling out pool usage analytics works best as a staged path, and for operators already weighing vendors, the order of steps matters more than the feature list on the datasheet.
- Set goals and metrics. Decide which figures drive decisions: swimmers per time slot, lane occupancy, lesson fill rates, lifeguard coverage per swimmer.
- Audit data sources. Review access systems, lesson booking, rosters and above all the installed camera estate, since camera-agnostic platforms can reuse it.
- Pilot at one site. Choose a pool with a typical usage mix, record a reference week as a baseline, and compare the measured figures with the team's own experience.
- Train staff. Lifeguards and duty managers need to know the system works as decision support: it flags, the lifeguard judges and acts.
- Feed results into rosters and programming. Occupancy curves support staffing to real load and reveal slots for new lessons.
- Roll out across the estate. Extend site by site once the pilot figures are trusted; rollout speed depends mainly on whether the platform needs dedicated hardware at each pool.
Two risks deserve open discussion. Data protection under GDPR requires documented purpose limitation, retention periods and logged access to footage, which belongs in the audit stage, not the rollout. The second is the concern that lifeguards will pay less attention; the lifeguard remains the responder and the system does not replace them. One practical observation follows from this sequence: the value of a usage metric appears to depend less on how many metrics a platform reports than on whether each one is tied to a named rostering or programming decision. It is therefore worth recording, for every metric, who reads it and how often it is allowed to change the supervision plan.
Frequently Asked Questions
What separates pool usage analytics from drowning detection alone?
Pool usage analytics shows how a pool is actually used: occupancy by time of day, how swimmers spread across the water, and which areas see the heaviest use. Drowning detection on its own reports safety events only. Lynxight combines both on the same overhead cameras, with prevention over detection, meaning alerts on early distress rather than on a completed submersion, plus operational data, real-time dashboards and cross-site visibility for multi-site operators.
Which vendors do operators typically evaluate?
Operators typically evaluate AngelEye, SwimEye, Poseidon, PoolView and Lynxight, alongside the quietest alternative of all: the CCTV system already installed. According to Lynxight, AngelEye and SwimEye occasionally win in Germany when a tender is written to their specification or they price lower, and AngelEye also picks up smaller single sites. PoolView is met mainly in the UK. Anyone tendering in 2026 should state clearly in the specification whether safety alerts alone are required, or occupancy analytics as well.
How quickly can a system be rolled out across many sites?
Speed depends mostly on hardware dependency. By Lynxight's own account, it brings a site live in about 50 days on average, and as fast as 2-3 weeks, while competitors requiring dedicated hardware take 3-5 months. Lynxight attributes this to working with roughly 10-12 common camera manufacturers and models, with no major installation, no pool downtime and remote fine-tuning. For IT teams, that means connecting to existing infrastructure rather than running a parallel hardware project at every pool.
How are GDPR requirements and footage access handled?
Cameras above swimmers involve processing personal data, so retention periods, access rights and logging belong in every vendor assessment. Lynxight states that it abides by GDPR, the UK Data Protection Act and the Australian equivalent, and maintains a data protection officer. Because most of its deployments are smartwatch-only, footage runs in the background, and retrieving it requires an approval process. Operators should request retention, role model and audit trail details in writing during procurement.
Can occupancy data change rostering without replacing lifeguards?
Yes, and the distinction matters. Lynxight is a decision support system: like Mobileye flagging a blind spot while the human keeps driving, it alerts the lifeguard, who stays the responder at the poolside. On that basis, supervision can follow real occupancy rather than habit. BlueFit reports that with Lynxight in place, staffing will reduce by up to 20% in some locations, while stressing that it will never replace lifeguards. Tommy Hughes, National Operations Manager at BlueFit, puts the trade-off plainly: "It doesn't remove the risk and does come with limitations. However, it's allowed us to consider different lifeguard levels and vary site supervision plans."
How can operators judge reliability in day-to-day operation?
A practical indicator is the real alert volume per pool. According to Lynxight, its monitored sites average 2-3 alerts per pool per day, a volume a supervision team can handle during a normal shift. Ann Arbor YMCA, the first YMCA aquatics centre in the United States to use AI drowning-prevention technology, reports alerts three to four times a day. Also check how alerts are delivered, whether by smartwatch or workstation, and how each one is documented afterwards.
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-29