Every stop planned, completed, and provable.
A route is not a list of addresses. It is a promise made weekly to a few hundred customers, and the only thing that defends it is a record of what happened at each pool. POOLIO plans the week, guides the stop, and captures the proof.
- Recurring weekly and biweekly route stops by tech and day
- One-click optimization with preview and locked stops
- Per-body-of-water checklists, chemistry, and dosages
- Offline capture with dependency-ordered replay
A week on the route
How the route runs in POOLIO
- Step 1
Build the week
Assign recurring stops to a day and a tech. The route dashboard shows workload per tech so you can see who is carrying twelve stops and who is carrying five.
- Step 2
Sequence the day
Reorder by drag and drop, or run optimization and review the proposed order before applying it. Locked stops stay where they are.
- Step 3
Work the checklist
Each body of water carries its own checklist. Required items gate completion, so a stop cannot be closed with the important steps unrecorded.
- Step 4
Capture the evidence
Chemistry readings, dosages added, notes, and photos attach to the stop and become the service record the customer receives.
- Step 5
Keep working offline
Backyards kill signal. The tech view caches the day and queues every action locally, replaying it in order once the phone reconnects.
- Step 6
Close the loop
Skips, delays, and field issues raise office alerts, and an issue can be converted into a work order or estimate without retyping anything.
Operational outcomes
What the office gets back
An answer to 'were you here?'
Timestamped chemistry and photos per stop, retrievable by address and date.
Visible imbalance
Workload per tech per day, so route creep shows up before it turns into overtime.
Fewer lost issues
A cracked lid or failing pump reported at the stop becomes an office alert, not a text that scrolls away.
POOLIO organizes the work and the follow-up. Results depend on your pricing, your route, and how your team uses the system — POOLIO does not guarantee revenue outcomes.
Who it is for
Route realities POOLIO is built around
Multiple pools at one address
Pool and spa, or a community property with several bodies of water, each with its own checklist and chemistry targets.
Access constraints
Gate codes, dogs, locked equipment pads, and preferred windows live on the property record where the tech will actually see them.
Substitute techs
When someone covers a route, the record carries the context — equipment, history, quirks — instead of relying on the regular tech.
Seasonal swings
Cadence changes and one-off work sit alongside recurring stops rather than forcing a rebuild of the route.
Buyer checklist
Evaluating route features
- Does completion require the checklist items you care about?
- Can stops be locked against automatic reordering?
- Is chemistry captured as data you can trend, not as free text?
- Do photos attach to the stop and reach the customer report?
- Does the tech app degrade gracefully with no signal?
- Are skips recorded with a reason and surfaced to the office?
FAQ
Frequently asked questions
Can POOLIO optimize the order of stops on a route?
Yes. The route dashboard shows each day's workload by tech and offers one-click optimization with a preview before anything is applied. Stops you never want moved — a customer with a fixed window, for example — can be locked so optimization leaves them in place.
What happens when a tech cannot service a pool?
The tech records a skip or delay with a reason, and it lands in the service history and in the office alert feed instead of vanishing. That gives the office something concrete to send the customer and something to look at when the same address gets skipped repeatedly.
Does the technician app work without cell signal?
Yes. The technician route view prefetches the day's stops and works offline. Checklists, chemistry, dosages, notes, issue reports, and photos are queued locally and replayed in dependency order when the phone reconnects, with conflict recovery if something changed server-side.
How does a customer know their pool was serviced?
Each completed stop produces a service record with checklist items, chemistry readings, dosages, notes, and photos. That record can be sent to the customer as a service report link from their own company number or email.
Can routes differ week to week?
Yes. Recurring route stops define the normal week, and one-off work — a repair visit, a green pool recovery, an extra clean — is scheduled alongside them on the dispatch board without breaking the recurring pattern.
Bring your route to the demo
We will build a real day from your stop list and show what the tech sees on the phone.