Major infrastructure projects rarely fail because nobody understood the engineering.
They fail because relationships deteriorate, commitments are misunderstood, concerns are dismissed and difficult conversations happen too late.
By the time the problem appears on the programme, the damage has often already been done.
A statutory consultee has hardened its position. A local authority no longer trusts the information it is receiving. A community group has moved from concern to organised opposition. A landowner feels ignored. The project team is then forced to manage a crisis that could have been prevented months earlier.
This is the trust deficit.
For major UK infrastructure projects, it is not a communications problem. It is a delivery risk.
Trust affects the programme
Trust is sometimes treated as something soft. Useful to have, but separate from the serious work of engineering, planning and construction.
That is a mistake.
A project depends on hundreds of relationships with communities, regulators, landowners, local authorities, elected representatives and delivery partners. Each relationship can influence access, consent, programme certainty and ultimately cost.
When stakeholders trust a project team, they are more likely to raise concerns early, discuss workable compromises and accept that difficult decisions have been made honestly.
When trust is missing, every interaction becomes harder. Routine questions become formal objections. Minor mistakes are interpreted as evidence of a wider problem. Commitments are challenged because the project has not demonstrated that its word can be relied upon.
Trust does not remove disagreement. It allows disagreement to be managed before it becomes a threat to delivery.
Engagement is not the same as communication
Infrastructure projects often produce large volumes of communication.
There are newsletters, consultation events, briefing documents, stakeholder databases, meeting records and engagement reports.
None of those automatically creates trust.
A project can complete every required engagement activity and still leave the people affected by it feeling ignored.
The difference lies in whether the engagement changes anything.
Good stakeholder and community engagement identifies who will be affected, understands their concerns and gives the project team enough time to respond properly. It connects engagement with engineering, consents, land, environment and programme decisions.
That means engagement cannot sit at the edge of the project as a communications function. It must be part of delivery.
Evermark Advisory’s approach is relationship-first. The purpose is not to generate more activity. It is to create better decisions, stronger relationships and greater programme certainty.
Technical credibility matters
Communities and stakeholders often raise technical questions.
Could construction affect a water supply? Why is a particular route being proposed? What environmental protections are in place? How will noise, traffic, access or land impacts be managed?
A generic answer rarely builds confidence.
Stakeholders need to know that the person speaking to them understands both the concern and the project behind it.
David Eve, Founder and CEO of Evermark Advisory, is a civil engineer with 25 years of experience across the infrastructure sector. He has worked for contractors, operated his own consultancy and worked on the client side. That gives Evermark a perspective that is unusual within stakeholder engagement and consents advisory work.
Technical credibility allows difficult questions to be answered directly. It also helps engagement teams recognise when a stakeholder concern exposes a genuine design, programme or consent risk.
That is important because the correct response is not always reassurance.
Sometimes the stakeholder is right.
Honest advice should arrive early
Projects do not benefit from advisers who simply confirm that everything is under control.
They need people who will identify when a relationship is deteriorating, when an engagement strategy is not working or when a consent position is becoming difficult to defend.
The value lies in saying it early.
Evermark’s operating principles include telling clients what is true, even when it is uncomfortable, owning work from beginning to end and building trust deliberately.
Early honesty gives the project options.
Late honesty usually gives it consequences.
A direct conversation with a statutory consultee before an issue becomes a formal objection is easier than resolving that objection during an examination. Repairing a relationship with a local authority before positions become entrenched is easier than attempting it when a programme milestone is already at risk.
The objective is not to remove every difficult conversation. It is to have those conversations while there is still time to act.
The three-sided view
Major infrastructure delivery involves clients, contractors and consultants. Each has different pressures, commercial incentives and expectations.
Many advisers understand one side extremely well.
Far fewer have worked across all three.
David’s experience includes client-side work at Transport for Greater Manchester, senior contractor roles, leadership of stakeholder engagement on HS2 and the development of his own specialist consultancy. His work on HS2 included leading a 70-person stakeholder team responsible for thousands of parliamentary commitments.
This breadth matters because technically correct advice is not always commercially useful advice.
A contractor needs to understand how an issue could affect delivery and contractual risk. A project promoter needs confidence that the consent strategy remains defensible. A consultancy needs specialist support that can integrate with its own team without creating unnecessary management overhead.
Evermark looks at the complete project environment, not just the engagement workstream.
Trust must be built before it is needed
Projects often begin investing seriously in relationships after opposition has formed or a consent issue has become urgent.
That is too late.
Trust is built through consistent behaviour over time:
- Clear information
- Commitments that are recorded and honoured
- Questions answered properly
- Bad news delivered without delay
- Stakeholders treated as people rather than entries on a database
- Advice that reflects what the project needs, rather than what is easiest to say
None of this is complicated. But it requires discipline, technical understanding and the willingness to address problems before they become comfortable topics for a board report.
The best time to build trust is before the project needs to rely on it.
Trust built into delivery
Stakeholder engagement, consents management and community relations should not be treated as supporting activities around the edges of infrastructure delivery.
They influence whether the project can secure consent, maintain access, manage commitments and keep its programme moving.
Evermark Advisory works with major infrastructure clients, contractors and consultancies to manage these risks through honest advice, technical credibility and relationship-first delivery.
Its services cover stakeholder and community engagement, Consents Management and DCO, and land and environmental services.
Trust cannot guarantee that every stakeholder will agree with a project.
It can ensure that disagreement is handled properly, risks are identified earlier and difficult issues are addressed while the project still has choices.
That is not soft work.
It is infrastructure delivery.
