A weekly traffic report for fleet managers: slow roads and incidents near each depot
What to put in a Monday report on the roads around your depots, how to keep the readings through the week, and how an AI employee can write and send it for you.
Part of the guide Location intelligence automation
A useful weekly traffic report for fleet managers fits on one page and answers three questions for each depot: which roads around it were slow at the hours the vans leave and return, what closures or roadworks are still there this Monday, and what changed since last week. Anything longer gets skimmed; anything without the depot's name on each line gets ignored.
This article is for transport managers, depot leads and operations directors who plan the week on Monday morning. It sets out what to measure, the difference between a Monday snapshot and a week of readings, a made-up report for a distributor with depots around Madrid, and how to have it written and sent automatically.
What belongs in the report
| Section | What it says | Where it comes from |
|---|---|---|
| Open incidents now | Closures, roadworks and incidents within a set distance of each depot this morning | Traffic incidents, around each depot |
| Slowest hours last week | For each depot, the departure or return hour with the highest average jam factor | Traffic Flow readings kept through the week |
| Worst road | The road named most often as the busiest near each depot | busiest_road in the same readings |
| Change from last week | Better, worse or the same at each depot's key hours | This week's averages against last week's |
| What to do | Two or three plain suggestions, such as an earlier start at one depot | Written by xMap AI from the figures, or by you |
A one-page structure. Each section has one line per depot.
A Monday snapshot or a week of readings
There are two ways to build the report, and they answer different questions.
The snapshot runs once on Monday at, say, 06:00. It lists the incidents around each depot and the road speeds at that moment. It is quick to set up and tells you what the week starts with, but it says nothing about how Tuesday afternoon or Thursday morning went, because live road speeds are only measured when the flow runs.
The week of readings is two flows. One runs every hour during your operating hours and writes each depot's speed, free-flow speed, jam factor and busiest road into a table. The second runs on Monday, reads the past seven days from that table and writes the report. This is the version that can say "Getafe was heavy at 07:00 on four of five days", which is the kind of line that changes a start time.
A made-up example: four depots around Madrid
Say a beverage distributor runs four depots around Madrid, with vans leaving between 06:30 and 08:00 and returning from 15:00. It has kept hourly readings within 500 m of each depot for two weeks. Monday's report reads:
| Depot | Worst hour last week | Avg jam factor then | vs week before | Open now |
|---|---|---|---|---|
| Getafe | 07:00 | 6.8 | Worse | Roadworks, 600 m |
| Alcobendas | 08:00 | 5.1 | Same | None |
| Coslada | 15:00 | 7.2 | Worse | Road closure, 300 m |
| Leganes | 07:00 | 3.9 | Better | None |
Invented figures to show the layout, not real traffic in Madrid.
Two lines stand out. Getafe's 07:00 departures have got worse and roadworks are still open nearby, so the manager moves the first wave to 06:30 for the week. Coslada has a closure 300 m away and heavy returns at 15:00, so its afternoon drivers are told to come back by the other access road. Alcobendas and Leganes need nothing. The whole report took a minute to read.
Reading it without fooling yourself
- Compare like with like. Average the same hours on the same days each week. A holiday week will look better and mean nothing.
- Look for repeats, not one bad hour. One heavy reading can be a single accident. Four of five days at the same hour is a pattern.
- Check the confidence. Each reading has a confidence from 0 to 1. Very low values early in the morning, when few vehicles are about, are worth less.
- Keep the distance the same. Changing from 500 m to 1 km halfway through will move every average.
Having an AI employee write and send it
In xMap Flows the week of readings is built from blocks you already know. The hourly flow:
- Schedule: every hour from 05:00 to 19:00 on working days.
- My data: your depots, with their positions.
- Traffic Flow: Within 500 m.
- Save to my database: one row per depot per hour in your own database.
Then the Monday flow:
- Schedule: Mondays at 06:00.
- Database query: a SELECT that averages last week's readings by depot and hour.
- Traffic incidents: around each depot, for what is open this morning.
- xMap LLM on the whole list: a short report in plain words, told to use only the figures it is given.
- Make a report or Email: the one page to the managers' inbox.
Without a database, the simpler snapshot version is a single Monday flow: depots, Traffic incidents, Traffic Flow, Email. The weekly road disruption report template is a ready start, and road speeds outside my depots, every hour is the reading half of the week-long version.
Questions
Can the report show traffic for days it did not measure?
No. Live speeds are read when a flow runs. For a week's picture, a flow has to read and keep the speeds through the week.
How many depots can it cover?
As many as your table holds; depots within 300 m of each other share one road reading. A one-page report stays readable up to about 20 depots.
Does it count trucks on the road?
No. It reports speeds and the jam factor, not vehicle counts. Counted cars by the hour are available only for roads in the United Arab Emirates.
Can it be a PDF with our logo?
Yes. Make a report turns the items into a PDF with your logo and colour, and can email it or save it to Google Drive.