Infrastructure Development Stakeholder Register
This is a practical guide to building a stakeholder register for an infrastructure development project — a record of stakeholders, their influence and how to engage them, adapted to the realities of delivering large public or private infrastructure.
What a Stakeholder Register is
A stakeholder register is a record of stakeholders, their influence and how to engage them. For the full concept and how it works in general, see Stakeholder Register. On an infrastructure development project it plays the same role, tuned to this kind of work.
Why it matters for an Infrastructure Development project
Infrastructure Development projects live or die on delivering large public or private infrastructure. A well-built stakeholder register gives the team a shared, explicit reference for exactly that — reducing ambiguity, aligning stakeholders, and making problems visible early enough to act. Skipping it, or doing it generically, is how infrastructure development projects drift into avoidable delay and cost.
What to include
- Stakeholder name and role
- Power and interest
- Attitude
- Engagement approach
Infrastructure Development-specific considerations
Tailor the stakeholder register to the risks that most often derail infrastructure development projects:
- Long lead times
- Permits and land
- Cost inflation over long horizons
Example
On a real infrastructure development project, the stakeholder register would be shaped by delivering large public or private infrastructure. In particular, it should explicitly account for the project’s biggest risks — long lead times, permits and land, cost inflation over long horizons — rather than treating them as afterthoughts.