A workable pool route fits the actual jobs into the actual day. Geographic proximity helps, but it does not resolve access windows, technician qualifications, visit duration, supplies or follow-up commitments. Check those constraints before optimizing the stop order.
Start with confirmed work and usable addresses
Build the day from scheduled service commitments, not a list of possible leads. Check the property address, pool identifier, date and assigned technician. A map pin can be geographically correct while the service entrance is on another street; keep access instructions in the appropriate private record.
Review new customers and changed addresses before including them in an automated route. A wrong starting point or duplicate stop can distort every estimate that follows. Give unconfirmed work a separate status so an office review does not accidentally become a customer promise.
Estimate the whole day, not just driving time
| Time category | What belongs in it | How to improve the estimate |
|---|---|---|
| Travel | Starting location, inter-stop travel and return travel when applicable | Compare with actual trips under relevant conditions. |
| Visit work | Agreed tasks plus known site-specific work | Use comparable completed visits; identify unusual jobs. |
| Access and setup | Parking, authorized entry and equipment preparation | Record recurring delays without exposing codes. |
| Supply and support | Planned collection, disposal and office coordination | Do not bury these in an unexplained allowance. |
| Breaks and contingency | Required breaks and reasonable uncertainty allowance | Keep them visible when reviewing capacity. |
For an illustrative day, 7 visits averaging 35 minutes consume 245 minutes. Add 110 minutes of travel, 30 minutes of breaks and 45 minutes for other work and contingency: 430 minutes, or 7 hours 10 minutes. This is planning arithmetic, not a claim about a typical technician’s productivity. Replace every assumption with your operation’s data.
Lock real constraints before changing the sequence
- Customer access windows and appointments that cannot be moved.
- Tasks requiring a particular skill, authorization or equipment.
- Known follow-up visits and dependencies such as required customer approval.
- Supplies required for confirmed work and any collection stops.
- Weather, road or access conditions that make a plan impractical.
- Technician start/end locations and the actual available workday.
Treat a shorter predicted drive as one input to a decision. A sequence that misses an access window can create a second trip and a disappointed customer. If a route optimizer proposes a change, review the affected stops and commitments before dispatching it.
Use clear exception decisions during the day
| Exception | Decision to record |
|---|---|
| Customer access unavailable | Who was contacted, whether a revisit is authorized and the stop status. |
| Work exceeds the agreed scope | What is observed, what is complete and who can authorize more work. |
| Unsafe site or weather | That work is deferred, the notification owner and the next review point. |
| Equipment or supply issue | Which stops are affected and whether reassignment is practical. |
| Plan changes | Revised order, responsible dispatcher and customer communication where needed. |
Do not mark a skipped or blocked stop completed to make the day look tidy. Those exceptions are useful planning evidence. A route record should connect to the visit report, where the completed tasks and unresolved work are documented.
Compare the plan with what actually happened
Review planned versus actual travel and visit durations using consistent start/end definitions. Separate one-off events from recurring planning errors. A longer day caused by an approved repair is different from a routine route that repeatedly exceeds capacity. Keep the denominator consistent when comparing weeks: the same stops and scope matter.
If you later publish a time- or mileage-saving claim, retain the baseline, comparison period, route changes and measurement method. Do not call the difference between two software estimates a measured operational saving. A percentage without the before-and-after conditions is not useful evidence.
Where Poolside Pro fits
Poolside Pro’s route workspace includes stop order, route detail and planning context. Its route detail supports reviewing stops and changing order or lock state when live route data is available. Review the saved result and current assignment before relying on it for dispatch. See the product walkthrough for the wider workflow.
This worksheet works independently of the software. It does not import stops, send customer messages or prove that a route is staffed. The homeowner marketplace has not launched; planning your existing customers does not create new booked demand.
Frequently asked questions
How many pools should one technician service in a day?
There is no universal count. Use the actual scope, visit duration, travel, constraints and available time to assess a workable day.
Should I optimize only for miles?
No. Include access windows, skills, service time and commitments. A shorter route may still be operationally infeasible.
How do I measure route improvements?
Compare consistent planned and actual measures over a defined period, documenting changes in stops and scope. Keep estimates separate from observed results.
Is the CSV a Poolside route import?
No. It is a standalone planning worksheet. Use the application’s supported workflow to manage real routes.
Method and verification
The checklist and worked time budget are Poolside’s planning framework. Product statements were checked against the route workspace code on October 23, 2026. No customer route data, field trial or claimed efficiency improvement is used.
Poolside creates practical worksheets and explanations for pool owners. These resources were prepared with AI assistance using the references listed in each article. Examples are illustrative; no field testing or independent technician review is claimed.
More Poolside guides →
