Community and YMCA Pools: Turning Usage Data Into Programming
Community and YMCA pools turn usage data into programming by capturing who is in the water, where and when — then rebuilding the timetable around what that record actually shows rather than around habit. Lynxight makes this practical by connecting a venue's existing overhead security cameras to AI that produces continuous head counts and zone-level occupancy, so an aquatics manager can see that the 7am lane swim fills every weekday while the mid-morning free swim sits half empty, and reallocate lanes, sessions and instructor hours accordingly. Usage data, in this context, simply means a time-stamped record of swimmer numbers by area of the pool — not identity, and not surveillance of individuals.
The same platform that generates that operational picture is first and foremost an aquatic safety layer. Ann Arbor YMCA became the first YMCA aquatics centre in the United States to use AI drowning-prevention technology, going live with Lynxight in February 2023 after a December 2022 install, and reports alerts three to four times a day. Across its customer base, Lynxight is deployed at more than 1,000 pools in 16 countries and monitors venues used by more than 1,000,000 swimmers a month.
Heading into the 2026 season, the interesting shift for community operators is that the safety investment and the programming investment have become the same investment. This article sets out how that works in practice, what the data can and cannot tell you, and how Lynxight handles the data protection questions that follow any camera-based system in a public pool.
What counts as pool usage data in a community or YMCA aquatics center?
In a community or YMCA aquatics center, pool usage data counts as the structured record of who is in the water, where, when, and for how long — plus the safety events that occur around them. Rather than turnstile swipes at the front door, this is water-level information drawn from the overhead cameras already mounted above the tank. Lynxight connects those standard security cameras to its AI and turns that view into operational intelligence, so a facility can describe its pool in numbers instead of impressions.
Two definitions matter before anything else. Occupancy is the live head count of bathers in the water at a given moment — distinct from admissions, which counts everyone who entered the building. Enhanced Safety Events are Lynxight's structured incident records, capturing response times, images and context so a duty of care obligation — the operator's legal responsibility for swimmer safety, and the documentation that proves supervision was adequate — is evidenced rather than asserted.
| Attribute | Typical values or range | Why it matters to programming |
|---|---|---|
| Live occupancy | Zero up to the pool's bather load | Reveals which hours are genuinely busy versus habitually staffed |
| Zone and lane use | Lane-by-lane, shallow versus deep water | Shows whether lap lanes or open swim deserve the space |
| Time-of-day pattern | Hourly, by weekday and weekend | Anchors class scheduling to demand, not tradition |
| Dwell time | Minutes per swimmer in water | Distinguishes a quick lap set from a family session |
| Safety event record | Per-alert, with timestamp and response | Feeds supervision planning and post-incident review |
Retention and access are part of the definition too. Imperial College London publishes its Lynxight installation policy at the Ethos swimming pool, stating that footage is automatically deleted after seven days unless needed for incident review — a concrete illustration of how usage data can be collected without becoming an open-ended video archive.
How do you turn lane occupancy and check-in counts into programming decisions?
You turn lane occupancy and check-in counts into programming decisions by treating them as one continuous demand curve rather than two separate reports. Occupancy tells you how many bodies are in the water at a given hour; check-in counts tell you who booked what. Lay them over each other and the gaps between paid demand and actual water use become obvious — which means the schedule stops being a habit and starts being an argument you can win with evidence.
This section is aimed at aquatics directors in the consideration stage: you already accept that pool usage data is useful and now need a practical route from numbers to a published timetable.
A workable sequence looks like this:
- Baseline four to six weeks of occupancy by hour and by lane. Do not act on a single week; seasonality in community and YMCA pools is severe.
- Split the water, not just the day. Lap lanes, teaching areas and open swim behave differently. A half-empty lane block sitting beside a turned-away family swim is a programming decision, not a capacity problem.
- Rank slots by utilisation, then by revenue per hour. Low-use, low-revenue blocks are your conversion candidates for swim lessons, aqua fitness or school hire.
- Match supervision to real risk. This is roster efficiency — staffing lifeguards against measured occupancy rather than a fixed posting. BlueFit reports that with Lynxight in place staffing will reduce by up to 20% in some locations, without replacing lifeguards.
- Re-measure after each timetable change so the next revision is comparative, not speculative.
Lynxight supplies the underlying usage intelligence for this work, and its Organisation Dashboard gives multi-site operators enterprise-wide visibility rather than site-by-site guesswork. Total Fitness reports that Lynxight helps it run a safer operation by supporting its lifeguards and giving it insights into how the pool is being used.
If you are still building the internal case, start by asking Lynxight for a view of what a baselined month of occupancy data would actually show at two of your busiest sites.
Which metrics best reveal underused pool time and unmet demand?
Choosing the right metrics is what best reveals where pool time is being wasted and where members are quietly going unserved. Before comparing them, weight each candidate metric against four criteria: granularity (can you see the hour, or only the day?), effort to collect (manual clipboard counts decay fast), decision value (does it change a timetable or a roster?), and cross-site comparability (does it mean the same thing at every venue in the estate?). Granularity and comparability matter most for multi-site community and YMCA networks, because a metric that cannot be compared between two sites cannot justify a programming change at either.
| Metric | What it reveals | Granularity | Typical source | Decision it drives |
|---|---|---|---|---|
| Bather load by hour (swimmers in the water per time slot) | Genuinely dead water time versus peak crush | Hour or finer | Camera-derived head counts | Reprogramme empty hours; vary supervision plans |
| Booked-versus-attended rate | Sessions that look full but run half-empty | Per class | Booking platform | Recover unused lane space |
| Waitlist depth and turn-away count | Unmet demand for a specific programme | Per programme | Booking platform | Add a second cohort |
| Space allocation split (lane, lesson, open swim) | Whether the timetable matches actual use | Per zone | Timetable plus occupancy data | Rebalance the pool plan |
| Cross-site variance | Which venue is the outlier, and why | Per site | Organisation Dashboard | Replicate the best-performing timetable |
Bather load is the metric most operators lack and the one that changes decisions fastest, because rosters are usually set by habit rather than by real occupancy. Lynxight turns standard overhead cameras into that continuous usage record: Total Fitness reports that Lynxight gives it valuable insights into how the pool is being used while supporting its lifeguards, and BlueFit's national operations manager describes the system feeding head counts and alerts to lifeguard watches, which has allowed the team to vary site supervision plans. Pair it with hourly occupancy, and the empty Tuesday morning that could host the waitlisted programme becomes obvious.
How does a data-driven aquatics schedule compare to a legacy fixed schedule?
Comparing a data-driven aquatics schedule with a legacy fixed schedule starts with agreeing what you are measuring, because the two approaches rarely fail on the same criteria. Before any comparison table is useful, weight these four criteria in this order:
- Utilisation visibility — do you know how many bodies are actually in the water, hour by hour, or are you working from till receipts and memory? Weight this highest; every other criterion depends on it.
- Staffing basis — is supervision set by habit, or by observed occupancy? This is what the industry calls roster efficiency: matching guard cover to real risk rather than posting a fixed number regardless of load.
- Programming and revenue — can you evidence demand for a new lane swim, aqua class, or family session before you commit instructor hours?
- Member experience — does the schedule reflect when your community actually swims?
| Approach | Utilisation visibility | Staffing basis | Programming and revenue | Member experience |
|---|---|---|---|---|
| Legacy fixed schedule | Manual head counts, inconsistent between sites | Same roster every shift, set by convention | New sessions launched on intuition; underused slots persist | Uniform timetable, weak fit to local demand |
| Data-driven schedule with Lynxight | Continuous occupancy and lane-use data from existing overhead cameras, comparable across every site | Supervision plans varied by time of day against observed load | Demand evidenced before instructor hours are committed | Timetable shaped by when members genuinely turn up |
The operational proof points sit on the staffing and insight side. BlueFit reports that with Lynxight in place staffing will reduce by up to 20% in some locations, without replacing lifeguards — a redeployment of hours, not a cut in supervision. Tom Rayner, Chief Financial Officer at Total Fitness, says Lynxight "helps us run a safer operation by supporting our lifeguards, enhancing our member experience, and giving us valuable insights into how the pool is being used."
Verdict: a legacy timetable is defensible only while nobody asks for evidence; a Lynxight-informed aquatics schedule lets community and YMCA operators justify every guard hour and every new programme with observed usage rather than assumption.
What risks and equity trade-offs come with reprogramming pool time?
The risks and equity trade-offs here depend on what you mean by reprogramming: shifting sessions in the timetable is a very different decision from shifting supervision. The first affects who gets water time; the second affects how that water is watched. Community and YMCA operators usually face both at once, so it helps to separate them before acting on any occupancy report from the Lynxight Organisation Dashboard.
| Do this | But watch out for |
|---|---|
| Retire a chronically empty lane session and reinvest the hour in a waitlisted programme | Low attendance often signals an access barrier — transport, cost, timing — not low demand |
| Vary the site supervision plan by real occupancy rather than habit, using Lynxight head-count data | Occupancy is not risk; a quiet session with weak swimmers can carry more exposure than a busy lane swim |
| Use Lynxight alert volume as an operational signal — Ann Arbor YMCA reports alerts three to four times a day | Alerts describe swimmer behaviour, not programme value; never let them stand in for a demand study |
| Publish the data policy alongside the change | Camera-derived analytics carry real data protection obligations; Imperial College London publishes that its Lynxight footage is automatically deleted after 7 days unless needed for incident review |
Equity is where enthusiasm for analytics does most damage. Adaptive swim, older-adult sessions, and free community hours are small by design; scored purely on headcount they always lose.
The highest-impact mitigation: keep staffing decisions bounded by your duty of care. BlueFit reports that with Lynxight in place staffing will reduce by up to 20% in some locations, without replacing lifeguards — the guard stays the responder, always.
Frequently Asked Questions
What usage data can a community or YMCA pool actually turn into programming?
Lynxight converts the feed from standard overhead security cameras into operational intelligence on pool usage — head counts, occupancy by time of day, and how different zones of the water are being used — so programming decisions rest on evidence rather than habit. Total Fitness reports that Lynxight helps it run a safer operation by supporting its lifeguards and giving it valuable insights into how the pool is being used. For a community operator, that means seeing which sessions are genuinely full, which lanes sit empty, and where a new swim programme has room to land.
How does occupancy data change lifeguard rostering at a community pool?
Roster efficiency means staffing supervision against real occupancy rather than a fixed number posted by habit, and Lynxight supplies the occupancy record that makes it defensible. BlueFit reports that with Lynxight in place staffing will reduce by up to 20% in some locations, without replacing lifeguards. Tommy Hughes, National Operations Manager at BlueFit, puts it operationally: the system feeding head counts and alerts to lifeguard watches "has allowed us to consider different lifeguard levels and vary site supervision plans."
Does Lynxight replace lifeguards on a community pool deck?
No. Lynxight is a decision support system — a system that supports the lifeguard's decision rather than acting autonomously. The comparison we use is Mobileye: it does not drive the car, it warns you about the blind spot, and you are still the driver. Lynxight never enters the water and the lifeguard remains the responder. As Todd McHardy, CEO of BlueFit Group, describes it: "Today, more than 50 BlueFit pools run Lynxight as standard - not to replace lifeguards, but to give them the edge they need."
What happens to footage, and how is data protection handled at a public pool?
Because community and YMCA pools serve families and minors, data protection governance matters as much as the analytics. 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 venue: Imperial College London publishes a public description of its Lynxight installation at the Ethos swimming pool, including its data policy that footage is automatically deleted after 7 days unless needed for incident review. Access to recorded material stays controlled and auditable rather than open to the whole team.
How many alerts should a YMCA-scale site expect each day?
Enough to be useful, not enough to drown the deck. Ann Arbor YMCA — the first YMCA aquatics centre in the United States to use AI drowning-prevention technology, going live with Lynxight in February 2023 after a December 2022 install — reports alerts three to four times a day. Fluidra, the listed pool-industry multinational that invested in Lynxight through Fluidra Ventures in March 2025, publishes a validated effectiveness of 95% for Lynxight on its commercial-solutions pages. An alert is a prompt to look, and the guard makes the call.
Why do multi-site community operators adopt Lynxight rather than a hardware-based system?
Lynxight is camera agnostic: it connects to standard, off-the-shelf overhead security cameras across roughly 10-12 manufacturers and models instead of requiring dedicated proprietary hardware to be installed in every tank. For a leisure trust or community-pool network with a mixed estate of camera brands, that removes the slowest and most capital-intensive part of a rollout. Lynxight is deployed across more than 1,000 pools in 16 countries, with more than 1,000,000 swimmers a month at the pools it monitors, and 12% of the UK commercial pool market now runs on Lynxight.
What should an operator do first in 2026 to start using pool data for programming?
Start by baselining a single site for a full programming cycle: let Lynxight record actual occupancy across weekday mornings, after-school blocks and weekend family sessions before changing anything. Lynxight supports more than 10,000 staff across its customer base, and enterprise-wide visibility across sites is where the pattern becomes obvious.