FlowsBook a callSign inCreate free accountSign up
Workflows by industry

How city transport teams publish a weekly roadworks list residents can use

A weekly roadworks report for the public, built from what is closed on the roads right now: grouped by district, checked by an officer, out every Monday.

Part of the guide Workflow automation

By the xMap team · · 5 min read

A useful weekly roadworks report for the public lists what is closed or being worked on now, district by district, in words a resident understands: the street, what is happening, and what changed since last week. The quickest way to produce it is to read the roadworks and closures showing on online maps each Monday morning, compare them with the week before, have a short draft written, and let an officer check it against the city's own permits before it goes out.

This article is for transport, highways and communications teams in cities and regional councils. It covers what residents want from the list, where the information comes from, a made-up example of one Monday, the mistakes that make a bulletin useless, and a flow that prepares the draft so the officer only has to check it.

What residents want from the list

People do not read a table of permit numbers. They want to know whether their street, their bus route or their child's school run is affected this week. That points to a simple shape:

  • Grouped by district, so people find their own area in seconds.
  • New this week first, then works that continue, then works that have ended.
  • The street and the nearest landmark, not coordinates.
  • What kind of disruption: a full closure, roadworks with a lane open, or an incident.
  • The same day and time each week, so people know when to look.

A short list in that order does more good than a complete one nobody opens.

Where the information comes from

Cities already hold their own records of permitted works, but those records describe what was planned, often weeks before. What residents meet is what is happening on the road today, including emergency repairs by utilities and closures by other bodies that are not in the city's system yet.

The Traffic incidents block reads closures, roadworks and other incidents showing on online maps at the moment it runs, each with its kind, street, district and position to about 150 metres. Comparing that with the permit list is also a quick way to spot works with no permit, or permits whose works have not started.

One Monday, made up

Picture a mid-sized council on the edge of Montreal with seven districts. At 06:00 on a Monday the flow finds 26 closures and roadworks across the council's area. Nine of them were not there last Monday, 14 continue, and 5 from last week have gone. The draft opens with the nine new ones, two of which are full closures on a bus corridor. Because Canada is one of the countries with population figures, the draft can also say roughly how many residents live within 500 m of each new closure, which helps the officer decide which ones deserve a separate notice.

By 09:00 the officer has removed two incidents that turned out to be minor collisions, added a works permit due to start on Wednesday that is not on the road yet, and approved the bulletin. It goes on the council's website and in the residents' newsletter. All the numbers in this example are invented.

Mistakes that make a bulletin useless

  • Publishing it raw. The roads change by the hour, and a list read at 06:00 can be wrong by noon. Say when it was read, and keep a person in the loop.
  • Covering too big an area in one search. A large area is cut into parts of about 24 km, up to 8 a run. For a big region, run one area per district instead.
  • Leaving out what has ended. Residents trust a list more when it also says which works are finished.
  • Using population figures where there are none. Residents within a distance are only available in some countries, among them Canada, France, India and Egypt, but not the United Kingdom or the United States. Leave that line out where the data does not exist.
  • Writing like an engineer. Lane restrictions, carriageway and TM layouts mean little to most readers. Say a lane is closed, or the road is shut.

The flow that prepares the draft

Built once in xMap Flows, this runs every Monday and stops for a person before anything is published. It is the same pattern as any recurring report described in workflow automation: data in, a draft written, a person approves.

  1. Schedule: every Monday at 06:00, in the city's time zone.
  2. Area of interest: the council's districts, drawn on the map or picked by name, so each incident carries its district.
  3. Traffic incidents: closures, roadworks and other incidents in each district, with street and district names.
  4. Only new on one branch: the incidents not seen before, each with first_seen. The full list goes on along a second branch.
  5. Demographics after Only new, where the country has population figures: residents within 500 m of each new closure.
  6. xMap LLM, fed by both branches and working on the whole list: a plain-English bulletin grouped by district, new works first, each with its street and kind, and a line on what ended.
  7. Approval: the duty officer reads the draft and approves or declines it from the email.
  8. Make a report: a PDF with the council's logo and a map, emailed to the communications team or saved to a Google Drive folder for the website.

The officer receives one email on Monday morning with the draft and a map, approves it, and the communications team gets the finished PDF a minute later. A copy of the list can also go to a Google Sheets tab for the team that handles complaints, so they can answer residents with the same facts.

Questions

Is this the official list of permitted works?

No. It is what shows on the roads when the flow runs, read from online maps. Treat it as a check on the city's own permits and let an officer confirm each line.

How precise are the positions?

To about 150 metres. That is enough to name the street and district, which is what a public bulletin needs.

Can residents subscribe to their own district?

One way is a flow per district, each emailing its own list. Another is a chat page residents can ask about their street, built with a Chat trigger and an AI agent.

Can the bulletin include how many people are affected?

Only in countries with population figures, such as Canada, France, India or Egypt. In the United Kingdom and the United States leave that line out.

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.