FlowsBook a callSign inCreate free accountSign up
Workflows by industry

How home service firms plan the day’s routes for their crews

Plumbers, electricians, cleaners and pest control crews lose hours to a badly ordered day. How to turn a job list into one tidy route per van before the crews leave.

Part of the guide Workflow automation

By the xMap team · · 6 min read

A home service firm plans a crew's day well when it fixes three things the evening before: which van takes which jobs, the order each van visits them in, and what on the road could upset that order in the morning. Put the next day's jobs in a table with an address for each, let the Route planner block share them between your vans from the depot and order each van's stops, and send every crew its list with directions links before 07:00. What it does not do is book the jobs: arrival windows promised to customers and the time each job takes stay with your dispatcher.

This is written for owners and dispatchers of plumbing, heating, electrical, cleaning, pest control, garden and appliance repair firms with two to twenty vans. It covers where the hours go, what the route planner works out and what it leaves to you, a made-up day in Melbourne, and the AI employee that prepares tomorrow's routes on its own.

Where a crew’s day leaks time

Most firms do not lose time on the jobs themselves. They lose it between jobs, and in a few repeated ways:

  • Zig-zagging. Jobs are taken in the order customers phoned, so a van crosses the city twice before lunch.
  • Two vans in one suburb. Each van gets a fair number of jobs, but not a fair patch, and two crews pass each other on the same street.
  • The supplier detour. A part is missing and the crew drives to a trade counter that is nowhere near the next job.
  • The surprise closure. Roadworks on the main road out of the depot add twenty minutes to every route that morning, and nobody knew.

None of these needs new software in the van. They need the list put in order before the crews start, by something that looks at every job at once.

What the route planner works out, and what it does not

Route planner takes the jobs that reach it, each with a position, and orders them from a start you pick, usually the depot. You choose between three shapes of day:

  • One route: every job in one order, for a firm with a single crew.
  • Share between reps: the jobs are split between 2 to 10 vans, each with a compact day, which suits a firm that does not care which crew goes where.
  • One route for each rep: a route per value of a field, for a firm where the jobs already carry a crew name, for example because only one technician holds a gas licence.

Each job comes back with its place in the route (visit_order), the distance and minutes from the stop before, the minutes of driving from the depot to reach it, the route's totals, and a directions link for the phone in the cab. Long routes get several links. You pick car, walking or cycling, and whether the route ends back at the depot; up to 50 stops go in a route.

When the routing service cannot plan a route (today's share is used, or a call fails), the planner still gives an order, worked out on straight lines with distances stretched to allow for roads, and every message says it is an estimate.

A made-up Tuesday in Melbourne

Say a family plumbing and gas firm in Melbourne has three vans and 27 jobs booked for Tuesday: tap repairs, two hot water units, a blocked drain in a restaurant and a dozen inspections for a property manager. The jobs sit in a table in My data, uploaded from the booking system each afternoon, with the address, the job type and a time window.

  1. At 17:00 on Monday the flow reads the table and keeps only Tuesday's jobs with a Filter.
  2. Route planner shares them between three vans from the depot in Footscray, by car, ending back at the depot.
  3. A Traffic incidents block set to check around each incoming place adds, for every job, how many closures or roadworks are within 2 km and the nearest one.
  4. One email goes to the dispatcher with the three routes, and a message per van goes to the crews' Slack channel.

In this made-up case the dispatcher sees that van 2 has the restaurant drain at stop 3 but the customer wants it after 14:00, swaps two stops by hand, and is done in ten minutes instead of the hour the whiteboard used to take. The morning closure on a bridge into the inner suburbs shows on the four jobs near it, so the crew leaves earlier.

Mistakes firms make with route planning

  • Addresses without positions. A job typed as Flat 4, behind the shop cannot be placed. When you bring a list into My data, rows are placed from their address and city columns; check the ones that failed before the evening run.
  • One huge route. Thirty jobs in one van is a plan nobody can keep. Share them between vans, or set the most stops a route may hold.
  • Ignoring the morning. A route planned at 17:00 knows nothing about a crash at 07:30. Run a short closure check again at 06:30 and only message the crews whose stops are affected.
  • Routes that drift across a city. If vans should own patches, split the city first with Split by territory, then plan one route for each territory, so each crew learns its streets and customers.

The AI employee that prepares tomorrow’s routes

Built once, the flow becomes an AI employee that works every afternoon: a Schedule on weekdays at 17:00, My data with the jobs, Filter for tomorrow, Route planner, Traffic incidents around each stop, and Email to the dispatcher. If jobs arrive in Google Sheets instead, start it with New rows and let it re-plan when late bookings land. For outdoor work, a Weather forecast block can flag the jobs where rain is expected, as the template Next week’s jobs planned around the weather does.

What lands in the inbox each evening is short: three routes, each a numbered list of addresses with driving minutes, a total for the day, the directions links, and any job with a closure nearby marked. If the routing service was not reached, the email says the order is an estimate.

Questions

Can the route planner respect customer time windows?

No. It orders stops to keep driving short, and gives driving minutes only. Keep the windows in your job list and adjust the order where a promised time does not fit.

How many jobs can go in one route?

Up to 50 stops a route. Jobs past that, or without a position, are passed on after the routes and the step says so.

Can each technician get their own route?

Yes. Choose one route for each rep and point it at the field that holds the technician's name, or let the planner share the jobs between a number of vans.

Does it use live traffic?

The route is planned on the road network, not on this morning's traffic. Add a Traffic incidents check before the crews leave to see closures and roadworks near each stop.

What if the jobs come from our booking software?

Export tomorrow's jobs to a CSV or to Google Sheets each afternoon; a New rows start or a table in My data brings them in with their positions.

Templates that do this

Read next

More on workflows by industry · Every article · Templates

Put it to work

An AI employee in xMap Flows does this on live data, on its own timetable. Start from a template or describe it in plain words.