Government affairs has a measurement problem, and the profession has hidden behind it for too long. The work is long-cycle, its biggest wins are invisible by nature, and its value often shows up as something bad that did not happen. All of that is true, and none of it excuses reporting a pile of activity counts and calling it performance. If you cannot show leadership what the function changed, you are one budget cycle away from being treated as overhead.
This guide lays out a measurement framework that actually demonstrates value: why government affairs is hard to measure, the vanity metrics most teams report and why they fail, and the three categories that matter, output, outcome, and relationship. It closes with how to build a leadership dashboard and structure the quarterly report.
If you cannot measure it, you cannot defend it. And if you cannot defend it, you will lose the budget when times get tight.
Why Government Affairs Is Hard to Measure, and Why That Is No Longer an Excuse
Three things make government affairs genuinely hard to measure. The cycles are long, so the relationship you build this year may not pay off until a proceeding two years from now, which breaks the tidy quarter-over-quarter reporting that other functions use. The biggest wins are often prevention, the bill that died in committee and the rule that got softened, which do not announce themselves. And attribution is messy, because an outcome usually has many causes and you can rarely prove that your engagement was the deciding one.
These are real. They are also not unique. Legal, security, and risk functions face the same prevention-and-attribution problem, and the good ones measure themselves anyway. The difference is that they decided the measurement problem was theirs to solve rather than an excuse to report activity. Government affairs has to make the same decision, because the alternative is that leadership measures the function for you, using the only thing they can see, which is cost.
The move is not to pretend the hard parts are easy. It is to measure across three categories that together tell an honest story: what your team did, what changed, and how healthy your relationship network is. No single number carries government affairs. The three categories together do.
The Vanity Metrics Most Teams Report
Walk into most government affairs reviews and you will see the same three numbers: meetings held, bills tracked, events attended. Each feels like proof of work. None demonstrates strategic value, and leadership senses it even when they cannot articulate why.
Number of meetings measures motion, not results. Fifty meetings that changed nothing is worse than five that shifted a commissioner’s posture on a rate case. Number of bills tracked measures surveillance breadth, not judgment. Leadership does not care how many bills you watched. They care whether you caught the three that mattered and did something about them. Number of events attended measures presence, not influence. Showing up is table stakes, and a calendar full of receptions is not a performance story.
The common failure in all three is that they measure input and activity while leadership is asking about impact. They answer "were you busy" when the real question is "did anything change." Report enough vanity metrics and you train leadership to see the function as a cost center that generates activity, which is exactly the framing that loses budgets.
The Framework: Output, Outcome, and Relationship
Measure government affairs across three categories, and make sure every report touches all three, because each answers a different question and none is sufficient alone.
Output metrics answer "what did the team do." They are the activity and discipline measures, and their real value is proving the function is operating with rigor and building institutional memory. They are necessary but not sufficient, and reported alone they become vanity metrics. Outcome metrics answer "what changed because of what the team did." These are the metrics that demonstrate value, and they are the ones teams most often fail to capture because they require deliberate documentation of results, including the results that were prevented. Relationship metrics answer "how healthy is the network the function runs on." They measure the state of the asset that produces future outcomes, and they are the leading indicator that tells leadership whether the function is building strength or quietly losing coverage.
The three form a chain. Output produces relationships, relationships produce outcomes, and reporting all three shows leadership not just what you achieved but that you are building the machine that will keep achieving.
Output Metrics: What Your Team Did
Output metrics establish that the function operates with discipline. Track them, report them briefly, and never let them be the whole story.
Interactions logged per month measures the discipline that builds institutional memory. Stakeholders engaged per quarter measures the breadth of active relationship work, showing how much of your mapped universe you are actually touching rather than just cataloging. Issues tracked and monitored measures coverage of your exposure. Briefings produced measures the function’s output to the rest of the organization. Reports delivered measures the reporting discipline itself, the weekly, monthly, and quarterly cadence that keeps the function visible.
The honest framing for output metrics is that they are hygiene. They prove you are running the function properly, the way a security team proves it is patching systems. They do not prove impact, and a report that stops here has not made its case.
Outcome Metrics: What Changed
Outcome metrics are where government affairs demonstrates value, and capturing them well is the difference between a function that gets funded and one that gets questioned.
Favorable regulatory decisions on tracked issues measures the core of the work for regulated industries: the proceedings that resolved in the company’s favor on issues you were actively engaged on. Tie the outcome to the engagement so the connection is visible. Unfavorable outcomes avoided or mitigated is the most important and most neglected outcome metric in the entire function. The harmful rule that got softened, the penalty that got reduced, the adverse proceeding that settled on manageable terms. Legislation influenced measures the legislative side: supported bills that passed and opposed bills that were defeated or amended favorably. Regulatory proceedings where the company’s position was adopted measures whether your advocacy actually landed in the commission’s order, the clearest signal that engagement changed a result.
The most important metric in government affairs is not how many meetings you took. It is whether the people you met with did something different because of it.
The discipline that makes outcome metrics possible is recording outcomes as they occur, especially the prevented ones. If you wait until the quarterly report to reconstruct what you avoided, you will forget most of it, because avoided harm leaves no trace unless you make one. Build the habit of logging the outcome, favorable or prevented, the moment a proceeding closes.
Relationship Metrics: The Health of the Network
Relationship metrics measure the asset that produces every future outcome, and they are the leading indicator that tells leadership whether the function is getting stronger or quietly eroding.
Relationship scores across tier-one stakeholders measure the strength of your most important relationships over time. A stable or rising set of tier-one scores means your core network is healthy. A declining trend is an early warning that shows up here long before it shows up in a lost proceeding. Interaction frequency with priority contacts measures whether you are actually maintaining the relationships you say matter most. Relationship coverage gaps measure exposure: the key stakeholders with no recent engagement, the deciding commissioner you have never met, the committee you have no line into. New relationships established per quarter measures whether the network is growing to match the company’s evolving exposure.
Relationship Strength Without Regular Logging
Relationship metrics are what let you tell leadership a forward-looking story rather than only a backward-looking one. Output and outcome describe what happened. Relationship health describes whether you are positioned for what is coming, which is the story that justifies investment rather than just reporting return. For the mapping and scoring discipline behind these numbers, see how to build and maintain a stakeholder map.
How to Build a Government Affairs Dashboard for Leadership
A leadership dashboard is not a data dump. It is a small set of numbers, chosen so that each one would change how an executive thinks, presented so the story is readable in a minute.
Build it around the three categories, weighted toward outcome and relationship. Lead with the outcomes, the favorable decisions and the avoided harm on the issues leadership cares about, because that is the value story. Support it with a compact view of relationship health, the tier-one scores and the coverage gaps, so leadership sees the state of the asset. Include a lean output section, enough to show the function is disciplined without drowning the page in activity counts.
The design principles are few and strict. Show trends, not just snapshots, because direction matters more than a single quarter’s number. Connect metrics to issues leadership already cares about, so the dashboard speaks their language rather than the function’s. And keep it short enough that a busy executive reads all of it, because a dashboard no one finishes reports nothing.
| Category | What It Answers | Report Weight | Example Measures |
|---|---|---|---|
| Outcome | What changed because of the work | Highest | Favorable decisions, harm avoided, legislation influenced |
| Relationship | Is the network healthy and positioned | High | Tier-1 scores, coverage gaps, interaction frequency |
| Output | Is the function disciplined | Supporting | Interactions logged, issues tracked, briefings produced |
The Quarterly Government Affairs Report Structure
The quarterly report is where the dashboard becomes a narrative. A structure that works, in order: open with the outcomes, the concrete results and avoided harms of the quarter tied to specific issues, because leadership should see value before process. Follow with the issue landscape, where the major issues stand and what is coming. Then the relationship health section, the state of the network and the coverage gaps you are working to close. Then a brief output summary that demonstrates discipline without dwelling on activity. Close with the asks, the resources or decisions you need from leadership, because a report that never asks for anything trains leadership to think the function needs nothing.
The report’s job is to convert a quarter of work into a case, and the case is always the same underneath: the function produced value, is building the relationships that produce future value, and operates with the discipline that makes both durable. Every metric in the framework exists to support that case. For how to translate this discipline into the weekly cadence leadership actually reads, see how to write a government affairs weekly report.
Measure the Machine, Not Just the Motion
Government affairs will always be harder to measure than sales, and that is not a reason to measure it badly. Report output, outcome, and relationship together, capture the avoided harm the moment it happens, and lead with the story of what changed. Do that consistently and the function stops being the cost line that generates activity and becomes the capability that leadership can see is worth more than it costs.
Every metric in this framework depends on the same foundation: interactions logged, issues tracked, outcomes recorded, relationships scored. A function that captures its work in a system can report all of this. A function running on memory and spreadsheets can report meetings held, and little else. If the vocabulary in this framework, regulatory posture, stakeholder tier, relationship score, is new to you, the full glossary defines all of it.
Michael-Christopher Warren spent years defending the government affairs budget line with exactly the metrics this guide describes. He built StatecraftCRM so the output, outcome, and relationship data are captured automatically rather than reconstructed every quarter.
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.