FlowsBook a callSign inCreate free accountSign up
Roads and traffic

Road closure alerts for business: a morning note for every site

Get closures, roadworks and incidents near each depot, shop or site in one morning email or Slack note, with only the ones that are new since yesterday.

Part of the guide Location intelligence automation

By the xMap team · · 5 min read

Road closure alerts for business work best as one short note before the working day starts: for each of your depots, shops or sites, which closures, roadworks and incidents sit within a set distance, and which of them appeared since yesterday. Public traffic apps tell one driver about one trip. A business needs the same picture for every location at once, sent to the people who plan the day.

This guide is for operations managers, dispatchers, facility teams and anyone who runs more than a handful of sites. It covers what a closure record actually holds, how precise it is, how to set the distance and the timing, a made-up example, the common mistakes, and an AI employee that writes the note for you.

What a closure record holds

When xMap Flows reads incidents from online maps, each one comes back as a small record. Knowing its parts helps you decide what to send and what to ignore.

  • Kind. Road closure, Roadworks, or Incident for anything the map shows without a more specific icon. Accidents are reported as road closures for now.
  • Name, street and district. The name combines the kind with the street when it is known, such as "Roadworks on Calle de Alcala". Street and district are worked out from the position for the first 40 incidents in a run.
  • Position and accuracy. A latitude and longitude, good to roughly 150 metres, with the precision in metres alongside.
  • An incident ID that stays the same for as long as the incident lasts. This is what lets a flow tell yesterday's closure from a fresh one.
  • A small icon, the same picture the map shows, which appears on result maps and in emails.

Around each site, or across the whole city

There are two ways to look. Searching a city or a drawn area returns every incident in it, which suits a control room or a city-wide newsletter. Checking around each incoming place is usually better for a business with fixed locations: every site keeps its own fields, a count of incidents within the radius and the nearest one with its distance, such as "Road closure, 640 m".

Sites within about 25 km of each other share one search, so a cluster of branches in one metro area costs little more to check than one. Up to five such groups are checked in a run, which covers most regional networks.

Choosing the distance and the hour

The right radius depends on how your people move. A shop that only cares about its own street can use 300 to 500 metres. A depot whose vans fan out across a district might use 2 km. A school bus yard or a construction site with heavy deliveries sits somewhere between.

Timing matters as much. Closures change through the night as crews start and finish work. A note sent an hour before the first shift or the first departure catches the overnight changes while there is still time to act. A second check at midday can help teams that run afternoon rounds.

A made-up example: a bakery chain in Madrid

The figures here are invented for illustration. A bakery chain runs 14 shops and one production kitchen in Madrid. Delivery vans leave the kitchen at 05:00 and reach each shop by 06:30. Shop managers also take morning deliveries from suppliers.

The chain sets a check at 04:15 with a 1 km radius around every location. On a Tuesday the note lists three sites. The kitchen has roadworks 400 m away on the road the vans usually take, marked as new since yesterday. One shop has a closure 800 m away that has been there all week, so it appears without the new mark. Another shop shows an incident 250 m from its door, also new. The dispatcher sends the vans by another road and warns that shop's manager to expect the supplier late. The other 12 shops are not mentioned, so nobody reads a list of all-clear lines.

Mistakes that make alerts useless

  • Sending everything every morning. A long closure that runs for weeks will appear every day. Mark what is new, or people stop reading after a week.
  • Listing sites with nothing nearby. Filter out locations with no incidents in range, so the note is short on a quiet day.
  • One radius for all sites. A city-centre shop and an edge-of-town warehouse need different distances. Keep two flows, or store the radius per site in your table.
  • Sending too late. A note that arrives after the vans have left only explains the delay.
  • Reading the dot too literally. Check the street name before rerouting a whole fleet over one position.

How an AI employee sends it

In xMap Flows the alert is a small flow, run as an AI employee that does the same job every morning. It fits the wider work described in the guide to AI employees for field operations.

  1. A Schedule block starts it on working days at the hour you choose, in your local time zone.
  2. My data brings in your list of sites from a table you uploaded, with their addresses or coordinates.
  3. Traffic incidents, set to around each incoming place, adds the count and the nearest incident to every site.
  4. A Filter keeps only the sites where the count is not zero.
  5. An Email to the dispatcher, or a Slack message to the operations channel, lists the sites with their nearest closure and a map link.

If you want a separate list of each incident rather than one line per site, search the area instead and put Only new after Traffic incidents. Only new remembers each incident by its ID, so a closure that lasts a month is sent once, on the day it first appeared. The template Road closures near my depots is set up this way and checks every hour; Road closures in my city covers a whole city each morning.

Each morning the email or channel gets the short list, and the AI employee's thread in the Team inbox keeps a daily note of what it found, so anyone can scroll back to see when a closure first showed up.

Questions

How accurate are the closure positions?

Each incident's position is good to about 150 metres, and the record carries that precision in metres. The street name, added for up to 40 incidents a run, is usually the more useful part.

Can I get only new closures, not the same ones every day?

Yes. Put Only new after Traffic incidents when you list incidents for an area. Each incident keeps its ID while it lasts, so it is sent once, on the day it first appears.

Are accidents included?

Accidents are reported as road closures for now. Anything the map shows without a more specific icon comes back as Incident.

Can each site manager get their own alert?

Yes. Store each manager's email with the site in your table and send one email per item, so each manager hears only about their own location.

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.