Most government affairs functions are not planned. They are triggered. A regulatory action lands, a legislative threat appears, an expansion into a new state creates exposure, or a competitor’s government affairs advantage suddenly becomes visible, and a company that never needed the function realizes it needs it now. Then someone hires the first government affairs professional and hands them a blank page.
This is a playbook for that person and that moment. It covers the trigger events, why the first hire is uniquely hard, exactly what to do in the first thirty days and the next sixty, the technology stack, the three documents you have to master to brief leadership, when to hire your second person, and the metrics that prove the function is working.
The Trigger Events
Companies build government affairs functions in response to specific pressures, and naming the trigger matters because it tells you where to point your first efforts.
A regulatory action is the most common trigger for regulated industries. A commission opens a proceeding, an agency proposes a rule, or a regulator starts asking questions, and the company realizes it has no one whose job is to manage that relationship and shape that outcome. A legislative threat triggers the function when a bill appears that would harm the business and no one is positioned to engage it. Market expansion into regulated states triggers the function when growth carries the company into jurisdictions where it now has regulatory and legislative exposure it never had before.
A competitor’s visible advantage is the quietest trigger and often the most telling. Leadership notices that a competitor consistently gets better regulatory outcomes, shapes legislation the company only reacts to, or simply has relationships the company lacks, and concludes that government affairs is a capability gap rather than a cost. This trigger tends to produce the most supportive leadership, because they have already decided the function creates value.
Knowing your trigger focuses the first ninety days. A regulatory trigger points you at the commission immediately. A legislative trigger points you at the statehouse. An expansion trigger points you at building repeatable coverage across jurisdictions. Do not build a generic function. Build the one your trigger demands, then broaden.
Why the First Hire Is the Hardest
The first government affairs professional at a company has the hardest version of this job, and leadership rarely appreciates why. Every later hire joins a function that exists, with systems, relationships, and institutional memory to inherit. The first hire has none of that and has to be four people at once: an intelligence analyst standing up monitoring from nothing, a relationship manager building relationships the company has never had, a strategist deciding which issues matter and where to spend a limited budget of attention, and an executive communicator translating all of it into briefings leadership can act on.
The first government affairs hire at a company is not just building a function. They are building institutional memory that the organization has never had before. That is a different kind of hard.
The implication for that first hire is discipline over heroics. You cannot out-hustle the absence of a system. What you can do is build the system deliberately from day one, so that the intelligence, the relationships, and the memory accumulate into something durable rather than living in your head and evaporating the day you leave.
The First 30 Days
Before you engage anyone or take a position on anything, spend your first month building the foundation. The instinct is to jump straight into the trigger issue. Resist it enough to do these four things, because they make everything after them faster.
Stakeholder Audit
Find out who the company already knows and who it needs to know. Interview the executive team, legal, operations, and existing consultants to extract what they know before it stays buried. Then identify the gap: the decision-makers and stakeholders who matter for your exposure and with whom the company has no relationship.
Issue Inventory
List every regulatory, legislative, and political issue that affects the business now and over the next eighteen months. For each, capture the jurisdiction, the current status, and a first read on the company’s posture. The trigger issue goes at the top, but do not stop there, because the issues you are not yet watching are the ones that become next quarter’s trigger.
Intelligence System Setup
Decide what you are monitoring and how, and set it up before you need it. The goal of the first thirty days is that by day thirty, developments reach you through a system rather than through a surprised phone call from an executive.
Quick Wins
Identify one or two relationships or issues where early engagement can demonstrate value fast. The function is new and its value is not yet proven, and a visible early win buys you the credibility and the runway to build the rest. The first ninety days shape how leadership perceives the function for years.
Days 31 to 90: Building the Operating System
With the foundation set, the next sixty days are about turning it into a repeatable operating system, so the function runs on process rather than on the founder’s memory and adrenaline.
The Stakeholder Map
Expand the stakeholder audit into a full map: the complete universe of stakeholders across all the arenas you operate in, scored on relationship strength, issue alignment, and influence, and tiered by priority. The map is the operating picture of your entire relationship territory, and it is the artifact you will maintain for the life of the function.
The Issue Management Framework
Turn the issue inventory into a managed framework: which issues you are tracking, in which jurisdictions, with what posture, and what the engagement plan is for each. This is what lets you say, at any moment, exactly where every issue stands and what the company is doing about it.
The Engagement Calendar
Map your planned engagement against the external calendar that governs your world: legislative session dates, hearing schedules, docket and comment deadlines, budget cycles. A function without an engagement calendar is perpetually surprised by dates that were on the public record all along.
The Technology Stack
Stand up the tools you need from day one and defer the ones that can wait. The principle for the first ninety days is to get the relationship system in place immediately, because every day you operate without it is a day your accumulating institutional memory is living somewhere it will not survive you.
The Reporting Cadence
Establish the rhythm of reporting up: a weekly activity report to leadership, a monthly executive briefing, a quarterly board or leadership update. Set this cadence early and hold it. A function that goes quiet gets forgotten and then gets cut.
The Technology Stack for a New Function
A new government affairs function needs three technology layers, and the order in which you prioritize them matters.
| Layer | What It Does | Priority for a New Function |
|---|---|---|
| Tracking | Monitors bills, dockets, proceedings, votes | High. Your intelligence depends on it. |
| CRM / relationship intelligence | Captures contacts, interactions, issues, briefings; builds institutional memory | Highest. It is where the function’s core asset lives. |
| News monitoring | Watches public commentary on issues and stakeholders | Useful. Can follow once the first two are in place. |
Legislative and regulatory tracking tells you what is moving. Legislative tracking platforms cover bills and votes across jurisdictions. For state regulatory activity, which legislative tools cover poorly, purpose-built regulatory intelligence like RegulatorIndex tracks commissions, proceedings, and commissioner posture across all 50 states.
CRM and relationship intelligence is the layer that holds the function’s core asset: contacts, interactions, issues, and briefings, structured so that institutional memory accumulates in the system rather than in your head. This is the layer new functions most often skip and most come to regret skipping, because it is the difference between building durable institutional memory and building a personal Rolodex that leaves when you do. StatecraftCRM covers this layer, purpose-built for the government affairs workflow.
A government affairs function without a CRM is not a function. It is a person with a good memory and a Rolodex. When that person leaves, the function leaves with them.
The temptation for a new function is to buy the tracking tool, because tracking feels like the obvious government affairs software, and to treat relationship management as something a spreadsheet can handle for now. That is the decision that produces a function whose entire institutional memory lives in one person and disappears when that person moves on. The full buyer’s guide to government affairs software walks through how to evaluate each layer.
Briefing Leadership: The Three Documents You Must Master
The function’s value is invisible to leadership unless you make it visible, and you make it visible through three documents. Master these and you will always be able to demonstrate what the function is doing and why it matters.
The Weekly Activity Report is a short, regular report that tells leadership what happened this week, what is coming next week, and what needs their attention. It should be scannable in two minutes and should consistently surface the one or two things leadership actually needs to know.
The Executive Briefing is a one-page preparation document for any meeting between a company executive and a stakeholder: who is this person, what is our history with them, what do they care about, what is the ask, what are the landmines. This document is also the clearest argument for the CRM, because you can only produce a good briefing from a relationship history you actually recorded.
You cannot brief leadership on a relationship you did not log. The discipline of recording every interaction is not administrative overhead. It is the foundation of every executive conversation you will ever have about this work.
The Board Update is a quarterly strategic overview of the issue and stakeholder landscape for the board or senior leadership: the major issues in play, the risks and opportunities, the outcomes achieved and avoided, and the direction of the regulatory and legislative environment. It is also where you build the case for resourcing the function as it grows.
Mastering these three documents does two things at once. It keeps leadership informed and the function valued, and it forces the underlying discipline, because you cannot produce any of the three well without the logging and tracking that build institutional memory.
When to Hire
The team-of-one has a ceiling, and recognizing when you have hit it is part of building the function well. You have hit the ceiling when the volume of issues exceeds what one person can track without things falling through, when your geographic footprint spans more jurisdictions than one person can cover with real depth, when you are so consumed by execution that strategic work stops happening, and when the function’s success has raised leadership’s expectations beyond what one person can deliver.
The order of the second hire depends on your trigger and footprint. A regulatory-heavy function in one state may need depth, a second relationship-and-proceedings person. An expanding function may need breadth, someone to own new jurisdictions. Either way, the fact that you built the function on a system rather than in your head is what makes the second hire productive quickly, because they inherit a stakeholder map, an issue framework, and a documented record rather than trying to download your memory over coffee.
The Metrics That Matter
A new function has to prove itself, and the wrong metrics make it look like activity for its own sake. Track relationships scored and maintained, because the relationship base is the asset and its growth and coverage are real progress. Track interactions logged, because logging is the discipline that builds institutional memory. Track issues tracked and their status, because coverage of your exposure is the core of the intelligence function. And track favorable outcomes achieved and, crucially, unfavorable outcomes avoided, because much of government affairs value is the bill that died, the rule that got softened, and the proceeding that settled well, none of which show up unless you deliberately record them.
That last category is where government affairs functions consistently undersell themselves. The disasters you prevented are invisible by nature, and if you do not document them, leadership sees only the crises that reached them and not the many that did not. Capturing avoided harm is how the function proves it is worth more than its cost.
Build It Right From Day One
The professional building a government affairs function from scratch is doing something genuinely hard: creating institutional memory an organization has never had, alone, usually against a clock. The single decision that most determines whether the function endures is whether that memory gets built into a system from the start or left to live in one person’s head. Build it into a system, and the function survives turnover, onboards the next hire fast, and compounds its value over years. Leave it in your head, and you have built a Rolodex with an expiration date.
StatecraftCRM was built for exactly this moment and this person: the government affairs professional building the function from scratch who understands that institutional memory is the asset and wants it in a system from day one. For the vocabulary and strategy behind the function you are building, start with what government relations actually means.
Michael-Christopher Warren has built government affairs functions from a blank page more than once. He founded StatecraftCRM so the next person handed that blank page does not have to rebuild the system from memory.
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.