Guides
How to judge pool service software: twelve checks and a trial
Twelve capability checks for judging pool service software, plus a six-stage trial that tests offline records, billing, reporting and full export.
What to take away
- Judge a candidate on twelve capabilities, not on a brand list that goes stale between seasons.
- The first check is pool records kept separate from customer records. One owner, two pools, or a pool that changes hands will break any system that merges them.
- Run the trial on your worst accounta spa, an automated controller, a gate with no signal.
- Break the signal mid-visit and build one report from the results. Those two stages expose more than a demo ever will.
- Ask what happens to your readings and photos if you stop paying.
This is general guidance on evaluating software. It names no product and quotes no price. Confirm capabilities and terms with each vendor directly.
Why the twelve checks beat a top-ten list
Software in this category changes hands, changes pricing, and changes feature sets within a single contract term. A ranking published today misleads a reader by spring.
Your route size, your account mix, and whether you do repair work decide the answer anyway, and no ranking knows those things. What holds still is the question set.
Score candidates on the twelve below, weight them for your own operation, and the shortlist writes itself.
The twelve checks
- Pool records separate from customer records. A customer may have two pools. A pool may change owners. Merge the two and you lose the history that matters.
- Readings stored as numbers in fields, chartable over time. This is the capability most often missing.
- Products and quantities recorded per visit, so chemical cost per account is knowable.
- A photograph attached to the visit record, taken and uploaded at the pool.
- Offline capture that survives poor signal and syncs when the phone reconnects.
- Route day assignment with one controlling owner and a visible change history.
- Recurring billing with a stored payment method and automatic retry on failure.
- Quotes and repairs handled separately and tied to the pool, not floating free.
- Customer messages generated from the visit record rather than typed a second time.
- Reporting you definecompletion, callbacks, and chemical cost per stop at minimum.
- Full data export at any time, in a format you can open without the vendor.
- Per-user accounts with multi-factor authentication and immediate removal on departure.
Numbers 2, 5, and 11 are where most candidates fail, and each failure gets expensive later. The measures those capabilities feed are set out in the software and KPI guide. A system that cannot produce them turns every monthly review into an evening of manual work.
Twelve software checks
- Pool records separate from customer records
- Readings stored as chartable numbers
- Products and quantities recorded per visit
- Photograph attached to the visit record
- Offline capture that syncs on reconnect
- Route day assignment with change history
- Recurring billing with automatic retry
- Quotes and repairs tied to the pool
Run the trial in six stages
| Stage | What to do | What it reveals |
|---|---|---|
| Set up your hardest pool | Unusual surface, a spa, an automated controller | Whether the data model fits reality |
| Record a real visit at the pool | Readings, products, photograph, on the phone | Whether a technician will actually use it |
| Break the signal | Complete a record with the phone offline | Whether the day survives a dead spot |
| Produce an invoice and take a payment | Through the real payment path | Where the fees and friction sit |
| Build one report | Callbacks by cause, or chemical cost per stop | Whether reporting is real or decorative |
| Export everything | Full export, then open the file | Whether your history is portable |
Finish the sequence inside the trial period, before you migrate anything. A system that cannot survive your worst pool will not survive July.
Six-stage trial sequence
- Set up your hardest pool
- Record a real visit at the pool
- Break the signal with the phone offline
- Produce an invoice and take a payment
- Build one report
- Export everything and open the file
The stop procedure comes first
Software should follow the way you have already decided to work. If a candidate cannot express your stop procedure, your exception rules, or your package structure, it will quietly change all three.
Check the visit record against the steps your technicians are trained to perform. The app should not fight the procedure taught in hiring and training.
Then check the equipment pad. A repair call goes faster when the record carries pump model, filter type, and controller settings, which is the detail covered in the equipment and setup guide.
Whoever will use the tool belongs in the trial. A system chosen by an owner and rejected by the technicians produces worse data than paper, because it produces the appearance of records. Phone-based record keeping is now a real hiring requirement, as noted in how to hire reliable staff.
Security is part of the choice
A route system holds home addresses, gate codes, alarm details, and payment methods for every customer you have. That makes the purchase a security decision.
Vendor security questions
Does every user have a separate login?
audit trail intact
shared logins destroy the audit trail
National Institute of Standards and Technology: NIST Small Business Quick-Start Guides is written for businesses with no IT staff and sets the basics in a sensible order. Cybersecurity and Infrastructure Security Agency: Cyber Guidance for Small Businesses covers the operational side, including what to do after an incident.
Three questions for any vendor, and for yourself: does every user have a separate login, is multi-factor authentication available and enforced, and how fast can access be revoked. Shared logins destroy the audit trail. A former technician with a live account and every gate code on the route is a risk you created rather than inherited.
Records, retention, and the exit
Your service history is a business record and an asset. Export it on a schedule and keep a copy you control, so a price rise, an acquisition, or a shutdown never puts that history out of reach.
The general standard in Internal Revenue Service: What kind of records should I keep? is a system you choose that clearly shows income and expenses, with the documents behind purchases, payroll, and assets retained. Software that makes retrieval hard makes meeting that standard hard too.
Common questions
Is free software good enough to start?
For a one-truck route on paper, almost anything is an improvement. The question is whether you can export your history when you outgrow it, so check that before you enter a year of data.
Should I pick the system my supplier recommends?
Listen to the recommendation, then run your own twelve checks. A supplier's experience is worth something, and their incentives are not identical to yours.
How disruptive is switching later?
More disruptive than owners expect, mostly because of pool records and stored payment methods. That is why the export check belongs in the first evaluation rather than in the escape plan.
What if technicians resist the change?
Find out whether the resistance is habit or a genuine defect, such as a form that takes too long at the pool. A slow form is a reason to change the tool. Habit is a reason to train.
