What a VP of Government Affairs Actually Needs to Track.
And Why Spreadsheets Fail.
The intelligence gap is not about data. It’s about the right data, organized for the specific mechanics of government affairs work — which no generic tool has ever been built for.
There is a version of government affairs intelligence that most teams have, and a version that actually works.
The version most teams have is a spreadsheet labeled something like stakeholders_FINAL_v3.xlsx. It has columns: Name, Title, Organization, Phone, Email, Notes. Maybe a column for Last Contact. Maybe a column for Issue. The team maintains it with the same discipline they maintain everything else that has no automatic enforcement — which is to say, inconsistently, until the sprint before a commission deadline, when someone spends two days pulling it back into coherence.
The version that actually works looks different. Not because it uses different software, necessarily — though that helps. But because it is organized around a different set of questions. The questions that actually determine outcomes in government affairs.
“The question is not who do we know. The question is what is the current state of every relationship that matters to this proceeding — with enough granularity to determine whether we can influence the outcome or not.”
The Four Things a Government Affairs Function Actually Needs to Track.
RELATIONSHIP STATE
Not just contact information — the current condition of the relationship. Strong, Good, Neutral, Opportunity, At-Risk, Negative. An actual field, updated after every meaningful interaction, visible to the whole team. Without it, the VP’s assessment of stakeholder health is a guess based on whoever was in the most recent meeting.
INTERACTION HISTORY
Every meeting, call, site visit, and hearing — logged at the time it occurs. What was discussed. What was asked. What was committed. Who attended. Without this, the institutional memory of the government affairs function is stored in the heads of current employees. When one leaves, the relationships leave with them.
ISSUE LINKAGE
Contacts linked to the specific dockets, proceedings, and legislative priorities where they are relevant. This is what allows a team to answer, in thirty seconds: “Who are all the stakeholders with a position on this rate case, and what is their current relationship temperature?” Without it, the answer requires pulling from multiple sources manually.
APPOINTMENT TRACKING
Commissioner term expirations, legislative seat changes, agency leadership transitions. For regulated industry GR, these are not background information — they are the operating environment. A team that does not track this proactively is perpetually reactive to developments that were visible months in advance.
Why the Spreadsheet Fails. Every Time.
The spreadsheet is not the problem. The spreadsheet is a symptom. The actual problem is that the government affairs function has been trying to do relationship-intensive, intelligence-dependent work with a tool that was built for tabular data storage.
Spreadsheets have no concept of relationship temperature. They have no concept of commissioner appointment cycles. They cannot tell you which stakeholders haven’t been engaged in 90 days in districts where your infrastructure footprint creates exposure. They cannot generate a meeting brief in seconds from your full interaction history with a state senator.
What spreadsheets can do is store data in rows and columns. Government affairs work is not rows and columns. It is a living network of relationships, proceedings, issues, and institutional history — all of which change constantly and all of which need to be connected to each other to be useful.
What Your Team Can Answer Right Now vs. What It Should Be Able to Answer.
| THE QUESTION | SPREADSHEET ANSWER | WHAT IT SHOULD BE |
|---|---|---|
| What is our current relationship temperature with every commissioner in this jurisdiction? | Check notes column. Hope someone updated it. Ask the person who’s been here longest. | A heatmap. Generated in seconds. Color-coded by relationship score. No asking required. |
| Which stakeholders haven’t been engaged in 90 days who are relevant to the open rate case? | Sort by last contact date. Cross-reference with the issues spreadsheet. Spend an hour on it. | A filtered view. Thirty seconds. Sorted by issue, by district, by relationship score. |
| When does Commissioner [Name]’s term expire and who appoints the replacement? | Check the website. Hope it’s current. Add a calendar reminder you’ll probably miss. | In the contact record. With an automatic alert 90 days before expiration. |
| What was discussed in the last three interactions with the Senate Majority staff? | Check email. Check the notes column. Ask Sarah — she took the last meeting. | Interaction log. Timestamped. Searchable. Sarah leaving doesn’t change anything. |
Why the Enterprise Platforms Don’t Solve This for Most Teams.
Quorum and FiscalNote are excellent products. They are also built for K Street lobbying operations with six-figure software budgets, dedicated platform managers, and implementation timelines measured in months.
The in-house government affairs team at a mid-size utility, a regional hospital system, or a growth-stage infrastructure developer is not that. These teams — three to fifteen people, serious work, limited technology budget — have been managing their most consequential relationships with tools built for selling software subscriptions.
Until recently, nobody built them a product. That’s changed.
Building the System Is Not Complicated. Building It in a Spreadsheet Is.
The four things a government affairs function needs to track are not mysteries. The problem has never been knowing what to track. It has been having a system built for the specific mechanics of this work that makes tracking it sustainable without drowning in manual maintenance.
StatecraftCRM was built for exactly this: the in-house government affairs team that has serious work to do and zero appetite for a six-month implementation project. Stakeholder CRM with relationship scoring built for GR. Heatmaps. AI briefing generation. Interaction logging. Issue tracking. Weekly activity reports generated automatically.
$59 per user per month. Free tier available. No implementation fees. No sales call required.
Explore StatecraftCRM arrow_forward