When a team evaluates a new system, an aquatic facility safety technology rental guide should do more than list equipment. It should explain the facility’s risks, operating conditions, response workflow, deployment constraints, and measures for judging fit. A clear brief helps directors compare options and gives vendors the context needed to discuss an appropriate approach.
A useful brief connects technology to the real operating environment: who swims, what conditions staff face, how alerts reach personnel, and what happens next. Define measurable evaluation criteria and clear boundaries so reviewers assess technology as an additional layer of protection, not a replacement for lifeguard supervision.
Begin with the decision the organization needs to make. Is the team evaluating swimmer wearables, lifeguard entry alerts, or a combination? State whether this is a new deployment, replacement, or expansion. Identify who approves the purchase and who will manage daily operation.
Describe the facility in practical terms. Include venue type, aquatic areas, hours, seasonal changes, programs, and how swimmers move between zones. Avoid broad labels such as “large pool.” Give enough detail to clarify sightlines, deck access, and staff positions.
Keep the brief factual. Label uncertain counts as estimates and assign someone to verify them. The GUARDian Hub overview can help frame product questions, but the brief should describe your own site rather than borrow assumptions. Consult the CDC’s drowning prevention guidance for the general principle that layered prevention measures matter; use it as background, not as a substitute for local rules or your own emergency plan.
Conditions affect deployment and what staff need to interpret. Record water clarity, lighting, bubbles, reflections, currents, and other features that vary by area or time. Include routine conditions as well as less common changes, such as weather or unusually heavy activity.
Describe the facility’s rhythm, too. A lesson area with frequent instructor movement may call for a different alert workflow from a lap-swim area. Note busy periods, program transitions, staff handoffs, and zones where deck communication is difficult. Such detail helps assess whether a proposed approach fits actual use.
Separate observations from conclusions. Write “the teaching area is crowded during afternoon lessons,” not “the sensor will fail there.” Ask vendors to explain compatibility and limitations for each condition. WAVE describes its wearable, wireless approach as working in clear and dark or murky water; request an explanation or demonstration relevant to the facility’s own setting.
For natural-water sites, specify the areas included, water changes, weather exposure, and how staff communicate across the site. Do not assume one test represents every season. Ask what site information the vendor needs, and document any conditions that cannot be replicated in a demonstration.
An alert is useful only when staff know where it appears and what action follows. Identify relevant events, intended recipients, and how personnel distinguish urgent notifications from routine system information. Clarify whether the team is considering swimmer wearables, lifeguard water-entry detection, or both.
Request an end-to-end explanation rather than a device list. WAVE’s system uses wearable sensors to detect prolonged submersion or lifeguard water entry and can alert staff through vibrating bracelets and facility alerts. Treat these as alerting functions within supervised operations. Staff still need to see, assess, and respond under facility procedures.
A technology layer should complement barriers, active supervision, and the facility’s emergency action plan, not replace them. Review the aquatic emergency action plan review guide when documenting how written response procedures fit the alert workflow.
| Brief topic | What to document | What to ask |
|---|---|---|
| Event types | Which swimmer or staff events warrant notification | What conditions trigger an alert, and what is outside scope? |
| Recipients | Roles that need notification by time and zone | How are alerts routed to those roles? |
| Delivery | Wearable, hub, audible, or other channels considered | What does each recipient perceive, and how is it acknowledged? |
| Response | Who verifies the event and initiates facility procedures | Can the workflow be demonstrated with our team? |
| Follow-up | How events and system issues will be documented | What records and system-health information are available? |
Use realistic scenarios. Ask what happens if one guard enters the water while another supervises a separate zone. Ask how a notification reaches a designated responder during a busy lesson, and what the supervisor does if it is not acknowledged. These questions expose workflow gaps that a feature checklist may miss.
Technology must fit existing authority and the emergency action plan. Name who wears devices, monitors the hub, oversees shifts, trains staff, and handles maintenance or support requests. Avoid assigning responsibility to “the team” without identifying who owns each task on a particular shift.
Map the alert path from detection to action. Identify the first recipient, backup recipient, supervisor, and person who records an event. Explain changes during breaks, rotations, lessons, and low-staff periods. State plainly that technology supports trained personnel and established supervision; it does not take over those responsibilities.
Consider existing tools. Vibrating bracelets, hub alerts, and facility notifications should be considered alongside radios, whistles, phones, and face-to-face communication. The emergency action plan review guide can help teams think through written response procedures.
Make responsibilities actionable with a simple role matrix. For each shift, record the primary responder, backup, supervisor, and equipment checker. If one person holds multiple roles, document what happens when those duties conflict. Review the matrix with staff who will use it, not only with procurement or leadership.
Consider a facility with a morning lap-swim shift followed by youth lessons. The brief should identify when the outgoing guard transfers the alert wearable, who checks the new wearer’s device, and which supervisor confirms that the recipient list reflects the lesson staffing plan. If a device is temporarily unavailable, write down the interim procedure and the person authorized to decide whether operations can proceed under facility policy. The point is not to prescribe a universal staffing rule; it is to surface decisions before a busy transition.
Then test a second case: a guard is assisting a swimmer while another staff member monitors the remaining zone. Who leads the response, who covers the other swimmers, and how does the supervisor know the alert was acknowledged? Record the answers as a workflow, not an assumption. Any unresolved conflict belongs in the brief as an issue requiring management review.
State the physical and operational limits a system must respect. Note whether construction, drilling, permits, contractors, or closure periods would create barriers. Document available power and network access where relevant, storage arrangements, and whether equipment must move between areas.
Compare deployment approaches using the same criteria. WAVE positions its system as wearable and wireless, with deployment that does not require permanent construction. AquaSense wristbands are non-tethered and have a multi-year battery, so they do not require daily recharging. These features may simplify some routines, but the brief should still ask how equipment is assigned, checked, stored, and supported on site.
| Evaluation area | Facility question | Evidence to request |
|---|---|---|
| Installation | Can the site accommodate permanent work or downtime? | Deployment steps, site requirements, and schedule |
| Daily handling | Who issues, collects, and stores wearables? | Handoff process and orientation plan |
| Power and connectivity | What infrastructure exists in each area? | Requirements and operating limits in writing |
| Water conditions | What changes by zone, season, or time? | Compatibility discussion and relevant demonstration |
| Ongoing ownership | Who checks equipment and follows up on issues? | Support, maintenance, and system-status procedures |
Ask for a practical walkthrough that includes setup, a staff handoff, a test alert, and documentation afterward. Include users and supervisors. A demonstration should show what the system does and what remains staff responsibility. The how-it-works information can help prepare questions about components and operation.
Separate one-time tasks from recurring work. A deployment plan should identify who receives equipment, where it is stored, who checks it, and how issues are reported. If the system is moved between facilities or aquatic zones, ask what must be repeated and how staff confirm the correct configuration is active.
Not every desirable feature is a must-have. Mark each line item as required, preferred, or informational. A requirement might be that alerts reach an assigned staff role through a channel the facility can use during its normal operating hours. A preference might be a particular storage arrangement. A third category can capture requests for clarification, such as how a vendor supports a seasonal layout change. This separation prevents a polished demonstration from overshadowing a genuinely incompatible constraint.
Ask vendors to identify their assumptions. If a proposal assumes a fixed number of wearables, a particular hub location, or a specific network arrangement, write that assumption beside the relevant requirement. The team can then decide whether it reflects the actual site or needs correction before cost and implementation are compared.
Define evaluation before purchase so the team does not rely on a general impression afterward. A pilot or demonstration can test whether staff can use the system as intended, alerts reach assigned people, and the workflow fits operating routines. Measures should be observable and tied to facility goals.
Possible operational measures include completion of staff orientation, percentage of planned shifts with assigned devices, successful alert receipt during practice scenarios, time to acknowledge test notifications, and completeness of equipment checks. These are process checks, not proof that any system can prevent every incident. Choose measures appropriate to the site and review them with staff and leadership.
Use a short test record: scenario, date, participants, expected alert path, observed result, unresolved issue, owner, and follow-up date. For example, during a lesson-transition drill, note which staff member receives the test notification, whether it is acknowledged, and whether the rest of the pool remains covered. Do not use a test as a substitute for the facility’s emergency drills or procedures.
Include procurement without letting price replace operational fit. WAVE offers subscription bundles with term options; request current details and confirm what equipment and services are included for the configuration under consideration. The WAVE pricing page is a starting point for comparing scope with the facility’s needs.
A scorecard can make the decision easier to explain to leadership. Give each reviewer the same criteria and the same response choices, such as meets, needs clarification, or does not meet. Add a short evidence note for every critical item. For example, “alert reached the assigned supervisor in the tabletop exercise” is more useful than “communication seemed good.” Avoid combining unrelated criteria into one score: staff usability, site compatibility, response clarity, and recurring workload should remain visible as separate findings.
At the end of a trial, hold a short debrief with the people who participated. Ask what was clear, what required a workaround, and what they would need before using the workflow during normal operations. Assign an owner and date to each follow-up. If the team cannot resolve a major gap, retain it as an explicit decision risk rather than burying it in general comments.
Use the brief to request comparable answers from vendors. Ask the same core questions so the team can distinguish a feature from a demonstrated workflow. Keep assumptions and unanswered questions in the procurement record.
Then score responses against the same decision criteria. A simple scale such as “meets,” “needs clarification,” or “does not meet” keeps the review transparent without pretending that every requirement has equal importance. Add written notes for critical safety and operational constraints.
For product context, review WAVE’s swimmer equipment information and lifeguard alert equipment overview. Teams can also compare the operational context described for YMCA facilities, camps, and municipal facilities. Use these as starting points, then verify requirements against the actual site and current documentation.
For a fair comparison, copy each must-have requirement into a shared worksheet and provide one column per proposal. Keep the wording neutral. One row might ask whether the system can route a test alert to the identified backup recipient; another might ask what staff must do at the start and end of a shift. Record the vendor’s written answer, the demonstration evidence, and any remaining question separately.
Do not let a single overall rating conceal a gap in a critical workflow. A proposal might be easy to deploy but leave alert escalation unclear; another might provide detailed escalation information but require a site condition the facility cannot meet. Put those trade-offs in plain language for the decision maker. If different departments own safety, operations, procurement, and information technology, ask each to review the items within its remit before the team reaches a recommendation.
For example, a municipality comparing systems across two venues should not assume that the answer from one site applies to both. The facilities may have different layouts, seasons, staff coverage, or communication constraints. Use one common core brief, then attach a site-specific page to each evaluation. That preserves consistency while keeping local differences visible.
Before the questions below, list your next steps: verify site observations, identify the staff owners, agree on test scenarios, and record any open assumptions. That turns the brief into a working evaluation document rather than a one-time procurement attachment.
It is a planning document describing a facility’s needs, water and operating conditions, alert workflow, staff responsibilities, deployment constraints, and evaluation measures. It helps buyers ask consistent questions and compare proposals against shared requirements.
That depends on facility goals and supervision. The brief can evaluate swimmer wearables, lifeguard water-entry alerts, or both, while stating which events matter and how notifications fit the staff response plan.
No. Technology is an additional layer of protection that supports staff and established procedures. Lifeguards and facility personnel remain responsible for active supervision and response under facility policies.
Test realistic scenarios, alert receipt and acknowledgment, staff handoffs, and the actions that follow a notification. Include the people who will use and oversee the equipment, and record limitations or workflow changes the demonstration reveals.
Keep each unanswered item visible, name the person responsible for follow-up, and set a date for resolution. Do not mark a requirement as met until the team has evidence that supports that conclusion.
Review it when layout, programs, operating season, staffing, or emergency procedures change. A scheduled review also helps confirm that roles, equipment routines, and evaluation measures remain practical.
A clear brief gives aquatic leaders a grounded way to assess technology, ask precise questions, and plan a workflow that supports—not substitutes for—the people supervising swimmers.