Five trucks, one day, one board.
With several crews the constraint is no longer effort, it is coordination: who has capacity, which sold work is unscheduled, whether every crew documented the stop the same way, and what the day cost you. POOLIO is built for that visibility.
- Every tech's committed day in one dispatch grid
- Capacity and durations, with conflict warnings
- Uniform service records across all crews
- Recurring work orders generated on cadence
Coordination
What changes when you run crews
- Step 1
One view of the day
Day-by-tech, week, and mobile list views so the whole operation is legible from a phone in a parking lot.
- Step 2
Capacity, not optimism
Durations and tech capacity mean the board tells you when a day is over-committed before the crew discovers it at 4pm.
- Step 3
Coverage and reassignment
Bulk move a day's work to another tech with multi-level undo when the plan changes again.
- Step 4
Generated recurring work
Quarterly and seasonal maintenance generates from templates into the unscheduled queue rather than depending on memory.
- Step 5
Backlog you can see
Approved-but-unscheduled work has an age. Sold repairs stop quietly expiring.
- Step 6
Scoped access at scale
Technicians reach operational data for their own work only, with role checks enforced in the database.
Operational outcomes
Where multi-crew companies gain
Balanced days
Workload per tech is visible, so route creep gets corrected instead of paid for in overtime.
Scheduled sold work
Approved repairs move from the bin to a slot rather than waiting on an email chain.
Comparable service data
Chemistry and completion records are structured identically across crews.
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
Operational patterns
Route crews plus repair crews
Stable recurring blocks with repair capacity dispatched around them.
Multiple service territories
Routes organized by day and tech with per-day workload visibility.
Dedicated dispatcher
Realtime board, unscheduled bin, bulk actions, and undo for a full-time dispatch role.
High-turnover field teams
Property and pool context lives on the record, so a new tech is productive quickly.
Buyer checklist
Multi-tech checklist
- Can you see all techs' committed work in one screen?
- Is capacity enforced with warnings, not just displayed?
- Can bulk changes be undone?
- Do two dispatchers see each other's changes?
- Does recurring maintenance generate automatically?
- Is technician access restricted at the data layer?
FAQ
Frequently asked questions
How does POOLIO handle several routes running the same day?
The route dashboard shows workload per tech per day, and the dispatch board shows every tech's committed schedule in parallel columns with durations and remaining capacity — so you can see the whole day's coverage in one view rather than five.
Can two dispatchers work at the same time?
Yes. The dispatch board refreshes on a visibility-aware interval and receives realtime updates, so a second person's changes appear instead of being overwritten.
How do we keep quality consistent across crews?
Required checklist items per body of water gate stop completion, and every stop produces the same structured record — chemistry, dosages, photos, notes — regardless of which crew ran it.
Can we generate recurring maintenance work automatically?
Yes. Recurring work order templates define the work, cadence, and parts, and POOLIO generates the due work orders on schedule into the unscheduled queue for dispatch.
How do we make sure sold work gets scheduled?
Approved estimates become work orders that sit in a visible unscheduled bin with duration and age, so backlog is a queue you can work rather than a set of forgotten emails.
Bring your busiest day
We will build it on the dispatch board and show the coverage picture live.