A stakeholder map is the working model of everyone who can affect your organization’s outcomes in front of government, scored by how much they matter and organized by what you are doing about them. Done well, it is the single most useful artifact a government affairs team owns. Done the way most teams do it, once, in a spreadsheet, then abandoned, it is a museum piece that describes a reality that no longer exists.
This guide covers how to build a stakeholder map that stays alive: why the government affairs version is fundamentally different from the project-management version, the four categories of stakeholders you are mapping, a six-step process, a scoring framework you can actually apply, and the five mistakes that turn maps into wall art.
A stakeholder map is not a contact list. A contact list tells you who exists. A stakeholder map tells you who matters, why they matter, and what you have done about it.
Why Government Affairs Stakeholder Mapping Is Different
Stakeholder mapping exists in project management too, and if you borrow that version you will build the wrong thing. The project-management map is largely static: identify the people affected by a project, plot them on a grid of power and interest, and manage their expectations until the project ships. It has a beginning and an end, the stakeholders are mostly internal or adjacent, and the goal is alignment.
The government affairs map is different in three ways that change how you build it. It is dynamic, not static: commissioners are appointed and elected out, legislators win and lose, staff move between offices, agencies, and firms, and a map built once is wrong within months. It is relationship-weighted, not just power-weighted: two commissioners with identical formal power are not equivalent if you have a decade of trust with one and have never met the other. And it is jurisdiction-specific: government affairs stakeholders live in specific bodies with specific rules, calendars, and processes, so a commissioner in one state and a legislator in another are not interchangeable nodes.
Build a project-management map for a government affairs function and you get a snapshot that is out of date, blind to relationship quality, and indifferent to jurisdiction. You need the version built for this work.
The Four Categories of Government Affairs Stakeholders
Before you map, you need to know who you are mapping. Government affairs stakeholders fall into four categories, and a complete map covers all four rather than defaulting to the obvious one.
The Stakeholder Influence Hierarchy
Width reflects formal authority over outcomes, narrowing from legislators down to coalition partners who amplify rather than decide.
Elected Officials
Legislators, city and county council members, elected executives, and in some states elected utility commissioners. These are the people who write, vote on, and sign the laws and budgets that affect you, and whose staff often matter as much as the principals. Elected officials turn over on election cycles, which makes them a moving target and makes relationships with their long-serving staff especially valuable.
Regulators and Commissioners
Public utility commissioners, state agency officials, administrative law judges, and federal regulatory bodies. These are the people who apply and interpret the rules, and in regulated industries they are frequently more consequential than legislators because they decide the specific proceedings that determine your economics.
Community Leaders and Influencers
Advocacy groups, business and trade associations, chambers of commerce, faith leaders, neighborhood and civic organizations, and the local figures whose support or opposition shapes how decision-makers perceive an issue. These stakeholders rarely hold formal authority, and teams routinely underweight them for that reason, but they shape the environment in which the formal decisions get made.
Coalition Partners and Opposition
The other organized interests in your arena: allies who file alongside you, neutrals who could go either way, and opponents who show up on the other side of every proceeding. The opposition belongs on the map every bit as much as your allies, which is a point most teams learn the hard way.
The Six-Step Stakeholder Mapping Process
Here is the process, in order. The discipline is in doing all six and then not stopping at step five.
Step One: Identify
Cast the net wide before you narrow. List everyone across all four categories who could plausibly affect your outcomes, without filtering yet for importance. It is easier to remove a stakeholder who turns out not to matter than to discover mid-proceeding that you never mapped the person who does.
Step Two: Research
For each stakeholder that survives the first cut, learn what matters: what they care about, what they have done and said on your issues, who influences them, and what their history with your organization is. This is where a name becomes a stakeholder. Skimp here and every downstream step is built on a hollow record.
Step Three: Score
Assess each stakeholder on a consistent set of dimensions so you can compare across the map. Scoring is what lets you prioritize, and the framework below gives you a repeatable way to do it. The point is not false precision. It is a shared, defensible way to say who matters most.
Step Four: Categorize
Tier your stakeholders by priority based on their scores and your active issues. A common structure is a small set of tier-one relationships that get proactive, regular engagement, a larger tier-two set you maintain, and a tier-three set you monitor. Tiering is how a team of three allocates attention across a universe of hundreds.
Step Five: Assign
Give every meaningful relationship an owner on your team. Unowned relationships are unmanaged relationships. Assignment answers the question that surfaces at the worst possible moment, when a proceeding heats up and no one is sure who actually has the relationship with the deciding commissioner.
Step Six: Maintain
This is the step that separates a living map from a dead one, and it is the step almost everyone skips. Maintenance means logging interactions as they happen, setting triggers that flag when a relationship has gone quiet, and running a periodic review, quarterly at minimum, to re-score, re-tier, and catch the turnover that has occurred since last time.
The Relationship Scoring Framework
Scoring turns a subjective sense of "who matters" into something you can compare, prioritize, and hand to a colleague. Use a simple one-to-ten scale across three dimensions.
Relationship strength measures the actual state of your connection to the stakeholder. This dimension is what the project-management grid ignores and what usually matters most, because influence flows through relationships that already exist far more reliably than through relationships you hope to build in the middle of a fight. Issue alignment measures how closely the stakeholder’s positions match your organization’s on the issues you care about, and the persuadable middle is where engagement changes outcomes. Sphere of influence measures how much the stakeholder can actually affect your outcomes, and keeps you from over-investing in agreeable people who cannot help you and under-investing in difficult people who can hurt you.
| Dimension | 1 | 5 | 10 |
|---|---|---|---|
| Relationship strength | Never engaged | Cordial, occasional contact | Deep, trusted, multi-year |
| Issue alignment | Committed opposition | Neutral or mixed | Reliable ally on core issues |
| Sphere of influence | Interested but low leverage | Meaningful voice | Can decide or move an outcome |
A one-to-ten scale gives you a shared, comparable language across the team.
The scores are not a formula that spits out a decision. They are a shared language. A stakeholder who scores low on relationship strength and high on sphere of influence is a priority to engage. One who scores high on alignment and low on influence is a friend who cannot help you much. Reading the three together is the judgment, and the framework makes that judgment explicit and comparable across a team.
The Five Most Common Stakeholder Mapping Mistakes
Most stakeholder maps fail in one of five predictable ways. Knowing them is how you avoid building a map that looks impressive and does nothing.
Building the map once and never updating it. This is the cardinal sin. A stakeholder map is a living system in a world of constant turnover, and a map that is not maintained is actively misleading, because it presents stale information with the confidence of current information.
Confusing access with alignment. A stakeholder who takes your calls is not the same as a stakeholder who agrees with you. Teams routinely score a warm, accessible relationship as if warmth meant support, and then get surprised when the friendly commissioner votes against them.
Ignoring the opposition until it is too late. The opposition belongs on the map. Teams map their allies and their targets and leave the opponents off because engaging them is uncomfortable, and then the opposition organizes a proceeding the team never saw building.
The most dangerous stakeholder is not the one who opposes you loudly. It is the one you forgot to map.
Failing to track second-degree relationships. The connections between stakeholders are often more valuable than the stakeholders themselves: the advisor who shapes a commissioner’s thinking, the association head who can reach a legislator you cannot, the former colleague who now sits on the other side. Capture who influences whom.
Not assigning ownership. An unowned relationship is a relationship that decays. Without clear ownership, relationships fall through the cracks, no one logs the interactions, and the institutional memory that ownership is supposed to build never accumulates.
How to Keep Your Stakeholder Map Current
The maintenance problem is the whole problem, so it deserves its own answer. Interaction logging is the foundation: every meaningful contact gets recorded, promptly, in a place the whole team can see. Automated alerts catch what human attention misses, flagging when a tier-one relationship has gone quiet for too long or a new proceeding pulls specific stakeholders into play. Periodic review cycles, quarterly at minimum, catch the structural changes: re-score, re-tier, add the new, and retire the departed.
Doing all three by hand across a large map is real work, which is why teams that are serious about maintenance move the map into a system built for it, where interaction logging, alerting, and scoring live together and the heatmap of relationship coverage updates as the work happens rather than being rebuilt from scratch each quarter. If you are still assembling the underlying stakeholder-management discipline this map depends on, start with what stakeholder management actually means in government affairs.
Michael-Christopher Warren spent years building and maintaining stakeholder maps inside a utility government affairs function, and built StatecraftCRM so the maintenance discipline lives in a system instead of a spreadsheet.
See how StatecraftCRM handles the work you actually do.
Set up your stakeholders, log a few real interactions, and see whether the system thinks about government affairs the way you do.