How water utilities plan a day of crew visits around road closures
Meter checks, valve jobs and leak repairs across a city: how a water utility orders each crew's stops, steers round closed roads and holds outdoor work when heavy rain is due.
Part of the guide Workflow automation
A water utility plans a good day of crew visits in three moves: share the open job tickets out between crews by area, put each crew's stops in a sensible driving order from the depot, and check every stop against today's road closures and the rain forecast before anyone leaves. Done each morning, it turns a long list of tickets into one short, ordered list per van, with the awkward jobs flagged before the crew finds them.
This is for operations planners and supervisors at water and wastewater utilities, and for the contractors who run their field work: meter readers, valve and hydrant teams, leak repair gangs, drain clearing crews. It covers what goes into the plan, a worked example, the slips that cost a crew an hour, and how an AI employee in xMap Flows can draft the plan before the shift starts.
What a crew's day is built from
Most utilities already hold the hard part: the tickets. Each one has an address or a position, a job type, a priority and often a time window promised to a customer. What is missing at 6 am is the order and the context. Four questions decide the order:
- Who covers where. Crews that criss-cross the city waste the morning. Compact patches, one per crew, keep drive time down.
- Which stop comes first. Priority jobs and fixed appointments anchor the day; the rest fill in around them in the shortest loop from the depot.
- Can the van get there. A street closed for roadworks, an event or an accident can block a valve chamber completely, or add a long detour.
- Should the job wait. Excavation, chamber entry and some meter work are poor choices in a downpour, while storm drain clearing is better done before it.
None of this needs a new system. It needs the ticket list, a map of today's road incidents and a forecast, put next to each other in time for the morning briefing.
Planning the day, step by step
- Export or sync the open tickets into a table: one row per job, with an address or latitude and longitude, the job type and the priority. A sheet in Google Sheets that the dispatch team already keeps works, and so does a table in My data.
- Split the jobs between the crews on shift. Split by territory draws compact areas of about the same size, either for a number of crews or for crew names you list, and marks each job with its owner.
- Order each crew's jobs with Route planner, starting from the depot and, if you like, coming back to it. Each stop gets its place in the visit order, the distance and drive time from the stop before, and a directions link for the crew's phone.
- Check the roads. Traffic incidents, set to look around each incoming place, adds how many closures and roadworks are nearby and which is closest.
- Check the sky. Weather forecast adds the rain expected today for each stop, so a Branch can hold back the jobs that should not go ahead in heavy rain.
- Send each crew its list, and let a supervisor approve the plan first if that is how your utility works.
A worked example
Here is a made-up morning, to show the shape of it. A utility contractor in Kuala Lumpur starts the day with 46 open tickets: 30 meter checks, 10 valve inspections and 6 leak repairs, three of them urgent. Three crews are on shift, all leaving the same depot.
| Crew | Jobs given | Of which urgent | Near a closure | Held for rain |
|---|---|---|---|---|
| North | 15 | 1 | 2 | 1 |
| Centre | 17 | 1 | 4 | 0 |
| South | 14 | 1 | 1 | 2 |
Invented figures, for illustration only.
Split by territory gave the centre crew more jobs because its patch is dense and the drives between stops are short. Route planner ordered each list. Traffic incidents found closures within a few hundred metres of seven stops, four of them in the centre, where an evening street market had left lanes coned off. The forecast showed heavy rain in the south from early afternoon, so two leak repairs that need digging were held for tomorrow and a drain check took their place.
The supervisor read the three lists at 6.20, swapped one job between crews by hand, and approved. Each crew lead had the list, in order, on their phone before the vans left. A planner doing the same by hand would usually still be sorting tickets.
Mistakes that cost a crew an hour
- Trusting the drive times as live traffic. Route planner times are for usual traffic on the roads, and time spent at each stop is not added. Allow for both, especially for repair jobs that can take two hours.
- Reading a closure as exact. Incidents come from online maps with a position to about 150 metres. A closure flagged near a stop means look at the map, not that the stop is blocked.
- Forgetting the crew's start point. If crews start from home rather than the depot, plan one route per crew after the split, so each starts where the crew really is.
- Overloading a route. Route planner takes a set number of stops per route; anything past that, and jobs with no position, come out after the routes and the step says how many. Fix missing positions in the ticket list rather than dropping jobs quietly.
- Holding everything when it rains. Rain is a reason to move digging and chamber work, not drain clearing or most meter reads. Write the hold rule for job types, not for the whole day.
How an AI employee drafts the plan
In xMap Flows the morning plan can be one AI employee, built from blocks in this order:
- Schedule: every weekday at 05:45, in the utility's time zone.
- My data with the ticket table, or New rows if dispatch adds tickets to a sheet in Google Sheets through the day.
- Traffic incidents around each incoming place, then Weather forecast for each place.
- Branch: jobs with heavy rain expected and a digging job type go down the No side to a hold list; the rest carry on.
- Split by territory with the names of today's crews, then Route planner with one route for each crew, starting from the depot.
- Email one message per crew, or a WhatsApp message to each crew lead, with the ordered stops and directions links. An Approval block before it lets a supervisor say yes first.
What lands each morning: in the supervisor's inbox, the three lists and the hold list with the reason for each held job; in each crew lead's messages, their own stops in order. In the field, crews can check in at each stop from their phones, so the office sees the day move without phone calls.
Templates to start from include the weekly utility operations brief and storm drains to clear before the rain. Ask xMap can also build the flow from a sentence such as "each weekday at 5.45, split today's tickets between three crews, order each route from the depot, flag closures and hold digging jobs if heavy rain is due".
Questions
Can the plan use our own job management system?
Yes, if it can export to Google Sheets or a table, or start a flow through a webhook. The flow only needs each job's position or address, its type and its priority.
Does Route planner know about today's traffic jams?
No. It plans on usual traffic for the roads. Traffic incidents adds today's closures and roadworks next to each stop, so the planner or the flow can react to them.
What if a job has only a street address?
Addresses can be turned into positions when the table is imported. Jobs that still have no position are listed after the routes, so nobody forgets them.
Can crews report back from the field?
Yes. Each stop can be checked in from a phone with an outcome, a note and a photo, and the office sees it in Results under Visits.