FlowsBook a callSign inCreate free accountSign up
Roads and traffic

A daily road note for a delivery team: what to put in it and when to send it

A short note before the vans leave: closures in each zone, roads that are crawling now, and rain or wind ahead. How to write it so drivers read it, and automate it.

Part of the guide Location intelligence automation

By the xMap team · · 5 min read

A daily road note tells a delivery team, before the first van leaves, what on the roads will change their day: closures and roadworks inside each depot's delivery area, the roads around each depot that are already slow, and weather that will slow them later. Send it 30 to 45 minutes before departure, keep it to one screen, put each zone's problem first, and end every line with what to do about it. A note that only describes the roads gets skimmed; a note that says "zone 3, use the north gate" gets used.

This article is for dispatchers, operations leads and owners of courier, grocery, parcel and service fleets. It covers what belongs in the note and what does not, the order to write it in, a made-up example for three depots, the limits of the data, and how an AI employee in xMap Flows can write and send it every morning.

What belongs in the note

  • Closures and roadworks inside the area each depot covers, with the street name, so a driver recognises it.
  • Slow roads right now around each depot and the main exits: the current speed against the free-flow speed, or the jam level in words.
  • Weather ahead for the shift: rain expected and when, strong wind for high vans, heat for drivers and chilled goods.
  • What to do: leave earlier, swap the order of two drops, use another exit, hold the bikes.

Leave out what drivers cannot act on: incidents far outside their area, a list of every road that is fine, yesterday's problems that have cleared. If nothing affects a zone, one line saying so is enough, and it is reassuring.

The order and the format

  1. A first line for the whole team: the one thing that matters most today, or "a normal morning".
  2. One short block per depot or zone, worst first.
  3. In each block: what, where (street and district), and the action.
  4. A last line with when the next note comes, if you send one again at midday.

Write for a phone screen. Most drivers will read the note standing by the van, so short lines beat tables. Use the same wording every day ("closed", "roadworks", "slow", "rain from") so a quick glance finds the change.

A made-up example for three depots

The company, streets and figures here are made up. A grocery courier runs three depots in Johannesburg and sends this note at 06:15.

Today: rain from 14:00 across the city, plan afternoon drops for slower roads.
Depot East: roadworks on Main Reef Road near the depot exit, use the side gate. Roads around the depot moving at about half their usual speed.
Depot North: one closure on a street in Randburg inside your area, the drop there moves to the end of the route.
Depot South: nothing on the roads. Gusts up to 45 km/h after 15:00, keep high loads light.
Next note at 12:00.

Every line names a place drivers know and ends with an action. Depot South gets a line too, so its drivers know the note was not forgotten.

What the data can and cannot tell you

The three parts of the note come from three different kinds of data, each with its own limits.

  • Closures and roadworks come from Traffic incidents, read live from online maps with a position to about 150 metres. Accidents are reported as closures for now. An incident appears when the map shows it, so a closure set up after the note was sent will be in the next one, not this one.
  • Speeds come from Traffic Flow: the current speed, the free-flow speed and a jam factor from 0 to 10 on the roads around each place, measured at the moment the flow runs. It does not count vehicles and has no forecast of later congestion.
  • Weather comes from Weather forecast: rain, wind and temperature for the hours and days ahead.

The delivery areas themselves can be drawn with Travel area around each depot, for example 15 minutes by car, which follows the roads. Its travel times are for usual traffic, so it shows where a van normally gets to, and closures inside it are the ones that matter.

Mistakes that make drivers stop reading

  • Sending the note after the vans have left.
  • Listing every incident in the city instead of those inside each depot's area.
  • Sending speeds without a comparison. "35 km/h" means nothing without "usually 60".
  • Changing the format every week.
  • Never saying when the roads are fine.

Writing the note with an AI employee

An AI employee in xMap Flows can write and send the note every working morning.

  1. Put your depots in My data with their names and positions.
  2. Start with Schedule on weekdays at 06:00, in your own time zone.
  3. Add Travel area, 15 minutes by car around each depot, then Traffic incidents in those areas.
  4. In a second branch from the depots, add Traffic Flow on the roads within 1 km and Weather forecast for today.
  5. Add xMap LLM on the whole list, told the format above and asked to give each depot an action, using only what it was given.
  6. Send it with Email or to the drivers' Slack or WhatsApp group.

What arrives each morning is one short message in the format your drivers know: a headline, a block per depot with closures by street, how slow the roads are now against usual, the weather to plan for and what to do. Copy the flow with a midday time for a second note, and add Only new after the incidents so the midday note mentions only closures that appeared since the morning.

Questions

What time should a delivery road note go out?

About 30 to 45 minutes before the first departure, so dispatchers can change routes and drivers read it before loading.

Should the note list every road incident in the city?

No. Only those inside each depot's delivery area, drawn along the roads, and on the main exits. Everything else is noise for that team.

Can the note say how many cars are on a road?

No. Traffic Flow gives the current speed, the free-flow speed and a jam factor, not vehicle counts. Speed against usual is what matters for a delivery plan.

Can I send it to drivers on WhatsApp?

Yes. The note can go to an email list, a Slack channel or a WhatsApp group through the matching app block.

How do I avoid repeating the same closure twice a day?

Put Only new after the incidents in the midday flow, so only closures that appeared since the last run are mentioned.

Templates that do this

Read next

More on roads and traffic · 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.