Infrastructure stakeholder mapping answers who matters to this project, for what reason, in which institution or community, at what phase, and with what legitimate role. It extends the general Government Affairs map by adding project milestones, approvals, affected places, implementation dependencies, and time.
Use the Infrastructure Stakeholder Mapping Workbook to maintain the map, then connect it to the flagship operating guide.
Map dimensions that explain relevance
| Dimension | Question | Do not confuse it with |
|---|---|---|
| Formal authority | Can this institution or person decide, review, enforce, or implement? | Political visibility |
| Project impact | How may the project affect this stakeholder or place? | Support or opposition |
| Influence | Whose judgment or participation can shape others? | Formal power |
| Issue relevance | Which concern, benefit, dependency, or question connects them? | Generic importance |
| Decision proximity | How near are they to the next material milestone? | Permanent priority |
| Relationship context | What is the history, strength, owner, and permission? | A contact record |
Use roles that respect the stakeholder’s actual position
Useful roles include decision-maker, formal reviewer, affected stakeholder, implementation partner, influential observer, potential coalition partner, and unresolved concern. A person can occupy more than one role. Do not force everyone into supporter or opponent categories.
Re-map relevance at every project phase
| Phase | Likely mapping question | Typical change |
|---|---|---|
| Site selection | Which authorities, communities, and infrastructure dependencies shape feasibility? | High uncertainty and confidentiality |
| Early outreach | Who should be heard before positions harden? | Concerns and information needs emerge |
| Filing or permitting | Who holds formal roles and who is affected by the process? | Public records and deadlines matter |
| Public review | Which issue themes and participation needs require response? | Visibility and decision proximity rise |
| Construction | Who experiences impacts or implements commitments? | Operational owners enter |
| Operations | Which relationships and obligations continue? | Project team transitions |
Separate formal authority from informal influence
A planning official may have formal review authority; a mayor may have political influence; staff may shape administrative completeness; residents may have direct project impacts and community credibility. Record each basis instead of collapsing them into one high-medium-low score.
Capture concerns as evidence, not labels
Document the source, date, exact issue, confidence, affected milestone, unanswered question, and internal owner. Official processes can create formal avenues for public input; CEQ’s citizen guide is one federal example. The applicable local, state, or agency process controls.
Assign one coordinating relationship owner
The owner coordinates context and follow-through; ownership does not grant exclusive access or authority to make commitments. Record supporting relationships, executive involvement, subject-matter experts, and approval requirements.
Sequence engagement from relevance and readiness
Consider project knowledge, the stakeholder’s role, confidentiality, public-process constraints, internal authorization, information needs, and the effect of contacting one party before another. Early engagement should begin with learning, not a prewritten advocacy script.
Review the map against upcoming decisions
Before each material milestone, ask what changed, whose role became more consequential, which concerns lack evidence, where ownership is unclear, which commitments remain open, and what the next phase needs. Then move into the engagement plan and risk map.
Positions can change as facts, designs, impacts, leadership, and timing change. Keep sourced observations separate from internal inference, restrict sensitive information appropriately, and never use a map to bypass a lawful public process.
Michael-Christopher Warren is a government affairs practitioner and the founder of StatecraftCRM. He writes practical frameworks for how government affairs work actually gets done — from stakeholder relationships and institutional memory to executive briefings, strategy, and team operations.
Start Statecraft without a sales process.
Choose your plan and users, see the exact price, and start online.