VMS Message Examples Drivers Understand (and Ones That Fail)

Good VMS message examples share three things: they say what is happening, when or where, and what drivers should do, in as few words and frames as possible. Messages fail when they are long, vague, clever or out of date. The approved traffic guidance scheme and your road authority's VMS guidelines set the limits and wording.

This article gives example messages that work and ones that fail, then walks through a worked night-works example from advance notice to pack-down. It is general guidance, not legal or engineering advice. Message limits, abbreviations and placement rules vary between road authorities, so check your state's current VMS guidelines and the TGS before programming a board. For hire costs and placement basics, see VMS boards explained.

Why VMS messages fail: the reading-time problem

Drivers read a VMS board while driving. They have to see it, read it, understand it and decide, all in the time it takes to pass. Here is an illustrative example calculation, assuming the board is legible from 250 metres in good conditions (a hypothetical figure; real legibility depends on the board, character size, weather and light):

The arithmetic is just distance ÷ speed: 250 ÷ 27.8 is about 9 seconds at 100 km/h. In that time the driver is also watching traffic, mirrors and the road. If the message has several frames, they may see each one only once or twice, and may catch the second frame first. That is why every message should make sense frame by frame, and why short beats complete.

VMS message examples that work

Frames are separated by a slash. These are examples of style, not approved wording; use the abbreviations and formats your road authority specifies.

Each one passes a simple test: if a driver sees only one frame, do they still learn something useful and nothing wrong?

VMS message examples that fail, and how to fix them

The most damaging failures are the last three: a board that is wrong. A driver who has been misled once tends to stop reading. Our guide to getting drivers to slow down in work zones explains why credibility matters so much.

Worked example: VMS for a week of night resurfacing

Example scenario: a contractor is resurfacing a section of a four-lane arterial road at night over five nights, with one lane closed in each direction and a full closure on the last night for the final layer at an intersection. The TGS and the road authority's approval specify two VMS boards, one on each approach, and the advance notice period. The traffic control company supplies and operates the boards.

Here is how it plays out on a typical job.

Advance notice (before the works): the boards are placed off the travel path at the positions shown on the TGS, where they are visible from well back, do not block sight lines at driveways or intersections, do not obstruct the footpath, and are protected or delineated as the TGS requires. The approved advance message runs: ROADWORK / 3–7 NOV / 8PM–5AM, and on the second board, which also warns about the closure: ROAD CLOSED / SAT 7 NOV / 8PM–5AM.

Each night of works: at the start of shift the supervisor switches to the approved works message, for example RIGHT LANE CLOSED / MERGE LEFT on the approach where that applies, and checks the board from the driver's position. The message is compared with the static signs and the arrow board. Our guide to arrow boards covers how the two work together.

The closure night: the message changes to ROAD CLOSED / DETOUR / FOLLOW SIGNS, matching the detour signs on the road closure and detour plan.

Morning: when the road reopens, the board goes back to the advance notice message for the remaining nights, or is blanked if it is the last night. A board that still says ROAD CLOSED at 7 am on a reopened road is the classic failure.

What goes wrong in this example, and the fix:

• Rain postpones night three. The supervisor's checklist for a postponement includes the boards: dates are updated to the new program the same day, through the approval process the project specifies.
• The board's battery runs flat at 2 am and the display goes blank. The mid-shift inspection catches it. A spare battery or generator, as the board's supplier specifies, is part of the equipment list.
• Someone tampers with the board's message. Boards are locked and password-protected. The supervisor resets the approved message and records the event.
• The board on the second approach is placed where it hides a side-street driver's view of oncoming traffic. The supervisor moves it within the tolerance the TGS allows, and the change is recorded.

A worked rewrite: from a paragraph to two frames

Here is how a message gets cut down on a typical job. The project manager's first draft for an advance board reads:

"Resurfacing works will be taking place on Smith Street between Jones Street and Brown Avenue from Tuesday 3 November to Saturday 7 November between 8 pm and 5 am. Please expect delays and use alternative routes where possible. We apologise for any inconvenience."

That is a notice for a letterbox drop, not a board. The rewrite goes step by step:

1. What does the driver need to decide? Whether to use this road on those nights.
2. What information changes that decision? That there is roadwork, which nights and which hours.
3. Is the location needed? The board is on Smith Street, so the street name adds nothing for drivers already on it. The cross streets are too long to read.
4. Is "resurfacing" needed? No. "Roadwork" is enough and is a word every driver recognises.
5. Are the apology and "expect delays" needed? The apology is not. "Expect delays" might be, but it pushes the message to three frames.

Result: ROADWORK / 3–7 NOV / 8PM–5AM. Two short frames on a three-line board, or one frame on some boards, depending on the board's layout and the authority's rules. The letterbox notice carries the detail; the board carries the decision.

Placing and checking the board on site

A perfect message is useless on a badly placed board. At set-up and at each inspection, the person responsible checks:

• Position matches the TGS, off the travel path, with any delineation or protection required.
• Visibility from the driver's position, from well back, not hidden by a crest, bend, parked vehicle or vegetation.
• No new hazard: the board does not block sight lines at a driveway or intersection, or obstruct the footpath.
• Message is the approved one and reads correctly in every frame.
• Brightness suits the conditions, so it is not washed out by day or glaring at night.
• Power is adequate for the shift, and the board is locked.

Writing your own messages: a checklist

Use this before any message goes to the approver or onto the board:

• One idea per message. Don't combine a closure, a detour and an event.
• What, when or where, and action. In that order of priority.
• Short frames. Fewer is better; follow your authority's frame and character limits.
• Plain words and only the abbreviations your road authority recognises.
• Unambiguous dates and times. Use day and month names rather than numeric dates.
• No questions, jokes, slogans or thanks.
• Consistent with the static signs, arrow boards and the TGS.
• Approved where the project requires message approval.
• Current: a plan for who updates or blanks the board when things change.

The VMS message log

Keep a record of every message displayed. It protects the company when a driver says they were not warned, and it supports any review of an incident.

For state guidance on VMS use at work sites, check with Transport for NSW in NSW, where TS 05492 Traffic Control at Work Sites replaced the TCAWS manual on 25 June 2026, and with Transport and Main Roads in Queensland. National guidance on temporary traffic management is published by Austroads.

Next steps

Take the failing-message table to your next toolbox talk and have the crew rewrite each message in their own words. If you run a traffic control company, the TrafWise platform includes an equipment register that tracks VMS boards with inspection and registration reminders, and QR labels let crew pull up a board's record on site.