An automated traffic and weather report for the morning news desk
Road closures and the day's forecast are the first thing a local audience wants at 6 am. How a newsroom gets a ready draft before the first editor sits down.
Part of the guide Workflow automation
An automated traffic and weather report for a newsroom is a short draft, written before the early shift starts, that pulls together the road closures, roadworks and incidents across the city with today's forecast, so a producer edits rather than collects. It is built from two live sources joined by an AI writer, and it can land in the editor's inbox, the newsroom chat or a shared document at whatever time the first bulletin needs it.
This piece is for local radio and TV stations, city news sites, newsletters and the morning desk of a regional paper. It covers what goes into the draft, how to keep it accurate, a worked example and how to set it up.
What the morning audience wants
Listeners and readers ask the same three questions every weekday: can I get to work, will it rain, and is anything unusual happening. A good morning note answers them in that order, names streets and districts people know, and stays short enough to be read aloud in under a minute. It does not need every pothole. It needs the closures that change a commute and the weather that changes a plan.
The two sources and what they can tell you
- Road incidents. The Traffic incidents block finds closures, roadworks and other incidents on online maps across the city right now, each with its kind, its street and district and its position. It does not say why a road is closed or how long it will stay closed, so the draft should never guess.
- The forecast. Weather forecast gives the day by day or hour by hour outlook for each city or area you list: temperature, rain, wind and UV, with a one-line summary. For a station covering several towns, list each of them and you get one row per town.
A third, optional ingredient is speed. Traffic Flow reports the current speed against the free-flow speed and a jam factor on the roads around points you choose, such as the main bridges or ring road junctions. It never counts cars, so say "slow on the bridge approach", not "heavy volumes".
Keeping it accurate
A machine-written traffic line read on air carries the station's name, so build checks into the flow rather than trusting it blindly:
- Tell the AI writer to use only the items it was given, to name each street exactly as it appears, and never to add causes, injuries or durations.
- Ask for the weather in plain words with the numbers it was given ("showers from mid-morning, up to 6 mm").
- For anything published without a human edit, put an Approval before the send, so the duty producer presses approve on the phone first.
- Keep the draft's timestamp in the first line, so nobody reads a 05:30 closure at 09:00 as current.
A worked example (made up)
Say a city news site in Melbourne sends a 6:15 newsletter and its breakfast show presenter reads a traffic and weather line at 6:30. The flow:
- Schedule: weekdays at 05:40.
- Area of interest: Melbourne, plus Geelong and Ballarat for the regional edition.
- Traffic incidents over the Area of interest: every closure, roadwork and incident with its street.
- Weather forecast for the same cities: today, hour by hour from now, rain and temperature.
- Both branches join at xMap LLM set to Work on: The whole list, with instructions to write a 120-word note in three short paragraphs: roads, weather, anything unusual.
- Email to the newsletter editor and the presenter, with the note at the top and the full list of incidents below.
A morning's draft might read: "Roads at 05:40: a closure on Hoddle Street northbound near the Victoria Parade junction, and two sets of roadworks in the CBD. Weather: cloudy, a top of 19 degrees, showers likely after 11. Nothing unusual reported in Geelong or Ballarat." The presenter adjusts the tone, checks the closure on the station's own sources, and reads it.
Mistakes to avoid
- Too much area. Searching a whole metropolitan region returns dozens of minor roadworks. Narrow the Area of interest to where your audience commutes, or filter to closures only for the on-air line.
- No human at the end. Fine for a draft in an inbox, risky for an automatic post. Keep an editor or an approval in the loop.
- Weather written as certainty. Forecasts are forecasts. Ask the writer for "likely" and "expected", never "will".
- A stale first line. Always include when the data was read.
Ready-made starting points
Three templates cover the usual versions: Morning city newsletter: roads, weather and what opened, Traffic bulletin for the radio, every 30 minutes and Morning weather script for every region. Each can be changed in one sentence to your city and your send time. For more on scheduling and joining branches, see the workflow automation guide.
Questions
Can the report go to Slack or a shared document instead of email?
Yes. Swap the Email block for the Slack app or a Google Docs or Drive step, or keep both so the presenter gets an email and the desk sees it in its channel.
Does it say why a road is closed?
No. Traffic incidents gives the kind of incident, the street, the district and the position, not the cause or how long it lasts. Tell the AI writer not to guess.
How early can it run?
Any time you set in the Schedule. Most newsrooms run it 20 to 40 minutes before the first bulletin so a producer has time to check it.
Can it cover several towns in one note?
Yes. List the towns in the Area of interest; incidents and forecasts come back per town and the writer groups them.
Will it give traffic volumes?
No. Traffic Flow reports speeds and a jam factor, never car counts, so the note should describe roads as slow or clear.