Setting Up Swim Video Analytics at Your Club

TLDR

A successful swim analytics installation depends as much on operational readiness as on the hardware itself.
The four non-negotiable prerequisites before camera day: consent policy in place, network connection confirmed, staff assigned, and session scope defined.
Camera placement for swim analytics is different from meet coverage — height, angle, and overlap all affect tracking accuracy.
A 3-lane pool typically requires a 1–2 day installation window; the first week should be treated as a calibration period, not a full rollout.

1) What you need before you start

Before a single camera goes up, three things need to be in place. If your club has not aligned on filming consent and retention yet, start with the pool filming privacy guide before ordering hardware.

Operationally:

A named data handler (who is responsible for data requests, retention, and deletion)
Written consent from parents/guardians of all participating athletes
A drafted privacy notice (signage for the deck and parent-facing document)
Defined session scope (which practices, which areas, which sessions are in/out of scope)

Technically:

Network assessment completed (see section 2)
Power source availability at or near the mounting point
Facility access confirmed for installation day (pool staff, building management, maintenance)

Administratively:

Coaching staff briefed on what the system does and what their daily role is
Pilot success metrics defined before launch (not retroactively)

If any of these aren't in place, delay installation. The technology is the easy part; the operational and consent foundation determines whether the program succeeds.

2) Site assessment

Pool geometry

Swim analytics systems that use overhead cameras need a clear sightline down the length of each lane. Assess:

Pool length: 25-yard, 25-meter, or 50-meter pools all have different field-of-view requirements. Camera count and placement differ significantly between pool lengths.
Lane count: Each lane should have clean overhead coverage. Obstructions (lighting fixtures, overhead equipment, scoreboards) may require mounting adjustments.
Ceiling or mounting height: Most camera systems perform best at heights between 12 and 18 feet above the water surface. Higher mounting captures more lanes per camera but reduces per-swimmer detail.

Lighting

Pool lighting affects tracking accuracy. Assess:

Even illumination across lanes: Uneven lighting (bright on one side, dim on the other) can affect computer vision accuracy. Many facilities have this issue with older fluorescent fixture layouts.
Glare from skylights: Pools with skylights can have severe glare at certain times of day that reduces video quality. Check at the time of day when you'll be running practices.
Underwater lighting: For underwater cameras, confirm that underwater lighting is operational and consistent. Murky water or dim underwater conditions significantly affect analysis quality.

Network

This is frequently underestimated and is the most common cause of delayed installations.

Bandwidth: Video analytics systems typically require 10–50 Mbps upload bandwidth per lane for cloud-based processing, or reliable local network connectivity for on-premises edge systems.
Wi-Fi vs ethernet: For reliable performance, ethernet at the mounting point is strongly preferred over Wi-Fi. Pool environments (high humidity, concrete, metal superstructures) are hostile to Wi-Fi signal quality.
Existing infrastructure: Check whether the facility has any network drops near the pool ceiling. Running new ethernet drops adds time and cost to the installation.

3) Camera placement principles

Camera placement for swim analytics is not the same as placing cameras for meet broadcasting. The goals are different:

Meet broadcasting: wide, high shots that capture the full pool aesthetic.
Swim analytics: consistent coverage of individual lanes with enough resolution to track per-swimmer metrics accurately.

Overhead cameras

Position: Centered above each lane, perpendicular to the water surface. Off-center or angled placement introduces parallax errors that reduce timing and position accuracy.
Height: Lower placement (12–14 ft) gives better resolution per swimmer; higher placement (16–18 ft) allows a single camera to cover more lanes. Your system vendor will specify the optimal range for their lens and processing setup.
Overlap: Adjacent camera zones should overlap by at least one body length at each end of the pool. This ensures that swimmers don't "disappear" from tracking when they transition between camera zones.

Underwater cameras

Not all systems include underwater cameras. When they do:

Mount at the lane rope level, 3–5 feet below the surface, pointed slightly upward.
Cover the first 5–8 meters from each wall (turns, underwaters, and breakouts are the primary targets).
Confirm waterproofing rating before installation. Pool chemistry is more aggressive than typical outdoor environments.

Avoid these common mistakes

Mounting behind structural beams that interrupt sightlines at the turns
Placing cameras on moveable equipment (lane rope reels, starting block carts) that gets repositioned between practices
Sharing mounting points with meet timing cameras that have different angle requirements

4) Privacy and consent prerequisites

Don't skip this section. Privacy is the #1 reason club programs fail to scale after installation.

Before the first session goes live:

Consent is collected from all athletes/guardians who will be filmed. For athletes under 13, this is a COPPA requirement in the US.
Signage is posted at the pool entrance and on deck. At minimum, the sign should state: when filming occurs, who can access footage, and how to ask questions or request deletion.
Access controls are configured: coach view, parent view, and admin view are separated. No shared credentials.
Retention policy is active: raw video has a default short retention, and someone is responsible for deletion requests.

For a more detailed compliance checklist and state-specific guidance, see the privacy playbook: /blog/pool-filming-privacy

5) Staff onboarding and first session

Before the first session

Run a no-athletes walkthrough with coaching staff. Show what the dashboard looks like, how to start a session, and how to end one.
Confirm that the system is tracking correctly with a short test swim (use staff or volunteer athletes before the first live practice).
Designate one "system owner" per session who is responsible for starting and stopping tracking. Don't leave this to whoever happens to be near the tablet.

First session guidance

Treat the first week as calibration, not production. Tracking accuracy improves as the system learns your pool's specific conditions.
Don't try to do too much in the first session. Coach the practice as normal; let the system run in the background. Review data after.
After the session: share one data point with families (a summary report, a pace chart, one key metric). This seeds adoption. Families who see data in week one stay engaged.

Common first-week problems

Problem	Likely cause	Fix
Swimmer IDs are swapped	Lane assignments not entered before session	Confirm lane/swimmer assignments before starting
Timing accuracy low	Camera angle or height outside spec	Contact vendor; physical adjustment may be needed
Data not appearing on coach dashboard	Network connectivity issue	Check ethernet connection; reboot edge device
Families can't access their data	Account setup not completed	Send setup instructions before first session, not after

6) First-week launch checklist

Complete all items before considering the installation live.

Hardware:

Cameras mounted at correct height and angle
All camera zones tested with a test swim
Power supply to all cameras verified (no extension cords across wet areas)
Network connection stable (ethernet preferred; test upload speed)
Underwater cameras (if applicable) positioned and watertight

Privacy and compliance:

Parent/guardian consent collected for all athletes
Deck signage posted
Privacy policy shared with families
Data handler named and reachable
Retention and deletion policy configured in system

Operational:

Coaching staff trained on starting/stopping sessions
Session scope documented (which practices, which lanes)
System owner assigned per session
First post-session summary sent to families
Feedback channel open for staff and families

FAQ

How long does it take to install a swim analytics system?

A typical 3-lane installation takes 1–2 days, including hardware mounting, cable runs, network setup, and system calibration. More complex setups (50-meter pools, multiple camera systems, underground cable routing) can take 3–5 days. Allow at least one week between installation and first live session for testing and staff training.

How many cameras are needed for a 3-lane pool?

Camera count depends on the system, pool length, and ceiling height. A 25-yard pool at standard ceiling height typically uses 2–4 overhead cameras for 3-lane coverage, plus optional underwater cameras at each end. Your vendor should provide a specific camera layout plan for your facility.

What internet speed is needed for swim analytics?

Requirements vary by system. Cloud-based video analytics typically need 10–50 Mbps upload per lane. Edge computing systems (that process locally and only sync summaries) have much lower bandwidth requirements — often under 5 Mbps. Confirm with your vendor.

Can swim analytics cameras be installed in a shared facility?

Yes, but it requires coordination with facility management. Most shared facilities require written approval for hardware mounting. Some facilities limit what can be permanently mounted; portable or semi-permanent installation options may be available for shared pool situations.

What if our pool has poor lighting?

Poor or uneven lighting is one of the most common challenges for video analytics in older pools. Options include: supplemental LED lighting above affected lanes, scheduling practices during times of day when natural light is favorable, or selecting a vendor whose system handles low-light conditions better. Confirm lighting conditions with your vendor before committing.

How do we handle athletes who opt out?

Opt-out athletes should not be assigned to tracked lanes during covered sessions. Most systems allow you to designate specific lanes as "untracked" for a session, or to exclude a specific swimmer's data from storage. Confirm your vendor's opt-out workflow before going live.