Communication and engagement in transport and road safety

Communication and engagement play a critical role in transport and road safety programmes because it helps build internal alignment, understand community context, support technical delivery and clarify how stakeholders are expected to participate.

Ask most people about the role of communication and engagement in transport and road safety programmes and you will receive a range of responses. Few of them capture how much it actually shapes a programme's success. Four myths crop up consistently and each can affect how successfully a programme is delivered. This article unpacks each myth, offers a different approach and pulls together what a joined-up communication and engagement approach looks like end to end.

Myth 1: Only the community needs to be brought along

Internal alignment among practitioners and delivery teams has to come first, before the community becomes the focus.

When it comes to bringing stakeholders on the journey and getting buy-in, the community is usually the first group project teams think of. However, often the most important stakeholders are the practitioners and internal teams who are delivering the programme. Engagement starts well before a proposal reaches the public and it needs to make sense to the people delivering it. This includes engineers, planners, communication specialists, technical specialists and policy leads who are working through complex evidence and who need a shared understanding of what the programme is trying to achieve and why. If you don’t have the internal understanding and buy-in, there is no foundation to build on or a baseline for consistent delivery.

When supporting a state transport agency to develop a communication and engagement framework, Abley’s communication and engagement team addressed fragmented regional practices by taking a practitioner-led approach to support consistent delivery prior to an external rollout with local councils and stakeholders. By co-designing tools and messaging directly with internal technical and communication practitioners, this approach built a shared foundation for the people delivering the programme. The result was a consistent approach across every region, with practitioners speaking from the same playbook rather than interpreting the framework their own way. It takes buy-in from every part of the team to get a rollout right, not just the people writing the messaging.

Myth 2: There's no need to invest in a communication and engagement programme early

Communication and engagement should begin at the problem definition stage, before options are developed and before the technical direction is locked in.

It comes up in project meetings all the time: "we'll bring in comms once we're ready to talk to the community." By then, the scope is set, the options are narrowed and the technical case is locked in. If the communication and engagement process is only activated once a proposal reaches the community, the most important decisions about scope, priorities and approach have already been made without any input from the people who'll be affected by them. That's how programmes end up delayed and require rework: a design doesn't account for the local environment, or a group's longstanding concerns only come to light late, after the direction is already set, and the team has to backtrack on decisions that could have accounted for those objections from the outset.

Invest in a communication and engagement programme from the outset, at the problem definition stage, before options are even developed. That means understanding the community, mapping stakeholders and messaging development and engagement planning all happen alongside the technical work, not after it. It's a smarter way of sequencing a programme, and it changes what gets built.

The Abley team collaborated with a transport agency to develop a baseline survey before options were developed, to understand public sentiment towards a proposed change and the community's relationship to the area in question. That early research meant getting under the hood of the community's connection to the road before a single option was on the table and let the team engage directly with vocal advocates and groups beforehand. The team could also tailor communications with a real understanding of people's objections and their connection to the area, not just a guess at what might land. The result was a consultation process with far fewer surprises, because the team already knew where resistance was likely to come from and had a relationship in place to work through it. That kind of insight isn't available without that early investment.

Myth 3: Communication and engagement sits outside technical delivery

Communication and engagement should be embedded in technical delivery so evidence, policy and programme changes can be translated early as the work evolves.

Even once a communication and engagement programme is underway, it's often still treated as a separate task: something that packages up technical decisions after they've been made, rather than a function that runs alongside delivery and adapts as things change. It is also the mechanism that translates technical evidence, data and policy detail into something decision makers and stakeholders can act on with confidence and something the community can genuinely respond to.

Abley's communication and engagement team saw why this matters on a council road safety programme, where the council had to quickly change its speed limit recommendations midway through a live communication and engagement process. The team could only adapt at that pace because they were embedded in the technical programme, not sitting outside it: close enough to translate the changes for the community, stakeholders and elected members as they happened, rather than waiting for a new package of materials to be handed over. The result was strong community turnout, a level of engagement well beyond what's typical for the size of the area and elected members and decision makers who had enough context to make a confident, timely decision. None of that happens if communication and engagement is treated as separate from technical delivery, rather than part of it.

Myth 4: Every programme needs consultation

Not every programme needs consultation. The right approach depends on whether the public is being asked to help shape a decision or simply being informed about one.

The term "consultation" is often used to describe interactions with the community, but not every programme needs to seek input before a decision gets made. Sometimes the programme is seeking to inform the community of changes, where a decision has already been made and the aim is to update people on progress, not ask them to help shape it.

When a programme has support from the responsible approval authority or is planning changes that regulation already allows, such as some speed management decisions, the first step is getting clear on what the programme is trying to achieve and what the regulation permits. That clarity sets the purpose of the engagement, the role the public plays and the outcome that's intended.

• Consultation is the right approach when the public is an active contributor, and their input is sought before a decision is made.

• Inform is the right approach when the public is a recipient of updates on progress or a decision, without being asked to shape it beforehand.

This distinction changes the entire engagement strategy. Tone, voice, message structure and the call to action all follow from it. It also helps manage expectations among elected members and leaders as the objective is clear from the outset.

What this looks like end to end

Together these myths show how the role of communication and engagement can be treated as a series of disconnected tasks, rather than the backbone that supports technical delivery. A communication and engagement programme is not one thing that happens at one point in time. Instead, it starts from the first internal conversation about what a project is trying to solve through to the final conversation with the community about what's being proposed and why. The approach also needs to be deliberate about who is in that conversation and what it's trying to achieve, shaping the narrative to match the outcomes the programme is trying to deliver.

Upstream, that means bringing practitioners and internal stakeholders onto the same page before options are developed. Downstream, it means empowering stakeholders and communities to engage with technical decisions on their own terms, adjusting communication as circumstances change and being clear from the outset about whether input is being sought to help shape a decision or it’s simply an inform process.

Get the audience, the timing, the investment, the integration with technical delivery and the purpose of the engagement right, and the payoff shows up at every stage: fewer surprises, decisions made with the right people in the room at the right time and communities and stakeholders who feel part of the process and understand their role.

If you're working on a transport or road safety programme and want to understand how communication and engagement can support delivery, stakeholder alignment and community confidence, get in touch.