How to Choose Pool Management Software: A Demo Checklist

Make each provider show the work your team does every day: water records, staffing changes, repairs, closures, access, offline work and exports. If you don't see it work in the demo, don't count it. Then ask what the full quote includes.

What should you establish before booking demos?

List the people who enter information, the people who review it, and the decisions they make. Include a lifeguard on a phone, a supervisor visiting a pool, and a manager reviewing several sites. Write down where your current process breaks down.

Then pull the record rules. The CDC's Model Aquatic Health Code (MAHC) is a good baseline, though your health department has the final word on records and formats:

• Records are kept at least 3 years and shown to the health department on request (section 6.4.1.2.1).
• A daily inspection is done before opening and logged at the pool (section 6.4.1.3.1).
• Before opening each day, free chlorine, combined chlorine (or total bromine) and pH are tested (section 5.7.5.1). While open, free chlorine (or bromine) and pH are tested again every 2 hours with a hand-fed system, or every 4 hours with an automatic controller (sections 5.7.5.2, 5.7.5.3).

Turn those needs into demo tasks. “Show how we pull this pool's closure history from two years ago” is something you can judge. “Does it have reporting?” is not.

What should a water record demonstration show?

Ask someone to enter a practice water test on the device staff will use. Check the pool label, actual test time, tester, required readings, and units. Then ask how a supervisor sees the result and any follow-up note.

Try a missing test, a correction, and a closure record. Ask whether the first value remains available after an edit and how staff record a later check. Do not assume a tool has a correction history because the screen has an edit button.

Keep readings separate from predictions. The MAHC (section 6.3.4.6.2) says remote water monitoring systems do not replace hand testing, so any alert or forecast should sit beside real test entries, not replace them.

How should you test staffing and maintenance?

Use a made-up absence to test the staffing process. Ask how a worker requests coverage, who approves a change, and where the manager sees the decision. Confirm whether the tool keeps the original request and the final outcome.

For maintenance, enter a practice repair concern. Follow it through assignment, work notes, a parts request, and review. Ask which steps are supported and which require another tool or a manual process.

Ask about staff qualifications separately. A name on a schedule does not show that a guard's certificate is current. If a provider tracks certificates, ask to see expiry dates and who checked them.

Who can view, enter, and change information?

Ask to see the product through the roles your team needs. Check what a guard, supervisor, regional manager, and property contact can view. Have the provider show any limits on editing or access instead of relying on a broad promise about permissions.

Ask how accounts are added and removed, who controls access, and how private staff records are handled. Get written answers about data storage and backups.

For a phone workflow, clarify whether the product runs in a web browser or needs an installed app. Test it on the devices your team plans to use.

What happens without a connection?

Ask exactly which saved records remain available without a signal. Then ask which new notes, readings, or photos can be entered. Try the workflow with the connection off and watch what happens when it returns.

Check whether unfinished uploads are visible and whether original entry times remain attached. Ask what happens if staff sign out or change phones before work uploads.

Compare the answers with your own backup procedure. Our guide to paper versus digital pool logs covers record access and corrections. Software used away from a connection still needs a separate way to report urgent concerns.

Can you take your records with you?

Request a sample PDF and CSV export and open them outside the product. Check which notes, photos, dates, and other details each export contains.

Ask what transfers from your current system and what stays in its old format. Since records may need to last for years, confirm how you get them back if you stop using the service. Our guide to switching pool records shows what that review looks like. Use the morning tasks in our multiple pool site management guide to test manager access too.

What should the quote and final review cover?

Ask what the quote includes, how charges change, and what help is provided when switching. Score each provider on the same sheet. For a side-by-side look at several products, see our pool management software comparison. Mark a row “shown” only if you saw it work in the demo:

Demo task	Shown	Told only	Not offered
Enter a water test with a photo on a phone
Correct a test and see the first value
Record a closure and its reopening steps
Approve a shift coverage request
Follow a repair from report to done
Enter a test with no signal, then reconnect
Export a month of logs as PDF and CSV
Pull an old closure record

We built Poolean around this checklist. It is a web app used on phones and computers, and it keeps water tests with photos, coverage approvals, closures and reopening steps, site visits, and repairs on one record for each pool. Entries made without a signal keep their times and upload later, and you can export daily or monthly logs as a PDF or CSV. Its maintenance tools cover scheduled work, repair orders, and chemical and parts requests. To see each row of the table above in a live demo, book a 30-minute call.

The short version

• Test real tasks using clearly labeled practice records.
• Check access, corrections, and the exact offline workflow.
• Review sample exports and the plan for keeping older records.
• See each feature you need work in the demo, and get clear written pricing terms.