The problem the Routes feature solves
Pool service companies visit the same pools again and again and typically on a repeating schedule (cadence). For example, Mike gets his pool cleaned every Monday, the Hendersons every second Thursday. Without Routes the office would have to create and manage each of those visits as an individual job which becomes unmanageable at any scale.
Routes flip the model: Instead of scheduling jobs one by one, the office assigns each pool to a technician on a day of the week with a repeat frequency. trackr iO generates the actual visits automatically, week after week, with no further work from the office.
The key ideas
Route stop: a pool assigned to a technician on a specific day of the week. This is the building block of the Routes feature. For example: “Pool at 12 Ocean Ave, serviced by Carlos, every Monday.”
Frequency: how often the stop repeats. Weekly, every 2 weeks, and so on.
Visit: the actual scheduled job that trackr iO generates from a route stop for a concrete date. The technician sees visits, completes them, and the history is kept per visit.
Non-routed jobs: normal one-off or recurring jobs that are not part of any route. For example. a repair or a filter replacement. These jobs continue to exist alongside routes and display in the same daily lists.
Setting up routes in the web app
Route Builder
This is where you create routes. The admin selects a technician and a weekday then adds pools to that day. The stops can be entered manually in any order. Or you can use the Optimize button to automatically calculate the most efficient driving route. A map next to the Route list displays every stop as a numbered pin which provides the admin a geographical sanity-check that the route is setup efficiently.
Route Assignments
This screen is the master view of who services what. It displays the stops for all weekdays and technicians, and it’s where ongoing changes can be made.
Two main actions here:
Edit an assignment: change the technician, the day of the week, the date the schedule starts, the date it stops (or leave it open-ended), and any weeks to skip, for example while a customer is on vacation.
Permanently move an assignment: hand a stop to a different technician and/or a different weekday from a chosen date onwards. Everything before that date stays exactly as it was, so history is never overwritten.
Bulk changes can also be applied to many stops. For example, you can move an entire day of stops to another technician if someone leaves the company.
Route Dashboard
This is the daily operations view. The admin picks a date and sees every technician's day side by side: which stops they have, in what order, and the real-time status of each stop as the day progresses. Stops can be reordered or re-optimized for that day, and the map shows where everyone is going.
What technicians see in the mobile app
The daily route
In the trackr iO mobile app, the technician sees their day as an ordered list when they open the app: Route stops in driving order, with any non-routed jobs for the day shown alongside. Each stop shows the pool, the customer, and what needs to be done. As the technician works through the day, they mark each visit with an outcome:
Completed: the service was done.
Skipped: the visit was intentionally not done this time.
No access: the technician arrived but could not get to the pool; for example, a locked gate.
These statuses flow back instantly to trackr iO desktop app which allows the office to see real-time progress on the Route Dashboard during the day.
Swipe Right
Skip Options
Defer Options
No Access
Route Dashboard on trackr iO mobile app
Admins and supervisors have a Route Dashboard inside the app as well so they can check any technician's day without opening a laptop.
Quick actions on a stop
Swiping left on a route stop reveals quick actions:
Reassign: Permanently move the stop to another technician or weekday from a chosen date.
Edit: Change the assignment settings for the stop, the same options as on the web.
Delete: Remove the stop from the route.
Which of these actions a person sees depends on their permissions described later in the section titled “Who can do what”
Non-routed jobs have their own equivalent actions: Reassign, Reschedule, and Delete.
How the scheduling engine behaves
A few rules that explain most of what people ask about trackr iO scheduling:
Visits are generated ahead automatically based on the frequency. Nobody creates them by hand.
The start date controls the first possible visit. The stop date, if set, controls the last one. With no stop date, the schedule runs indefinitely.
Skipping weeks simply produces no visit for those dates. The following visit lands back on the normal pattern.
Every change applies to future visits only. Completed history is never modified, so reports and billing always reflect what happened.
Deleting a stop removes its future visits only, for the same reason as above.
Who can do what
Admins decide what technicians can and can’t do and can decide on a per-technician basis whether they can move visits to other dates, delete work, and see or manage other technicians' work.
The same permission settings drive both the trackr iO desktop app screens and the quick actions in the mobile app. A technician with limited permissions simply does not see the actions they cannot use. A technician with no management permissions sees only their own day and works through it.
How it all fits together
A typical end-to-end flow: The office builds routes once in the Route Builder. From that point, Trackr iO generates the visits. Each morning the technicians see their day on their phone and work through it, marking task outcomes as they go. The office watches real-time progress on the Route Dashboard.
The office handles exceptions like vacations or staff changes on the Route Assignments screen.
And the routes keep running until someone changes them.