A government affairs annual plan is a set of explicit choices about which policy outcomes matter, where the team will concentrate attention, how stakeholders and actions connect to those outcomes, and how leadership will know whether the plan is working.
The desired outcome
The team should finish with a small portfolio of priority issues, a defined outcome and strategy for each, named owners, stakeholder coverage, decision points, resource assumptions, leading indicators, and a cadence for revising the plan as the environment changes.
The eight-step planning workflow
| Step | Core question | Output |
|---|---|---|
| 1. Anchor | Which enterprise goals, risks, and decisions should government affairs support? | Business alignment statement |
| 2. Scan | What political, legislative, regulatory, and stakeholder changes matter? | Assumptions and scenarios |
| 3. Prioritize | Where can attention materially change or prepare for an outcome? | Tiered issue portfolio |
| 4. Define | What observable policy or operating result do we seek? | Outcome and guardrails per issue |
| 5. Map | Who can decide, influence, enable, or block the result? | Issue-specific stakeholder map |
| 6. Design | What sequence of engagement, analysis, coalition, and internal action is plausible? | Strategy and 90-day actions |
| 7. Resource | Who owns the work and what budget, expertise, or executive access is required? | Owners and capacity plan |
| 8. Measure | What evidence will tell us to continue, change, escalate, or stop? | Indicators and review cadence |
Make priority a real constraint
A list of twenty “top priorities” is an inventory, not a plan. Separate enterprise-critical issues from active watch items and background monitoring. Name what the team will do less of to protect capacity for the highest-value work. The point of prioritization is to change resource allocation.
Example: multi-state infrastructure approvals
An infrastructure company expects permit decisions in four states while a fifth considers legislation affecting local siting. The plan identifies two enterprise-critical outcomes, maps decision-makers and community influence around each jurisdiction, assigns one accountable lead per state, schedules executive engagement only where it adds leverage, and creates an escalation trigger if local opposition changes a permitting timeline.
Turn the annual plan into a living operating cadence
Review actions and commitments weekly, issue movement monthly, portfolio priority quarterly, and strategic assumptions whenever an election, leadership change, ruling, crisis, or material business decision changes the environment. Annual planning sets direction; it should not lock the team into stale assumptions.
Common failure modes
Starting with a calendar of activities. Meetings and events are means, not objectives. Copying last year’s issue list. Continuity matters, but every priority must re-earn resources. Separating legislative and relationship plans. Outcomes depend on both. Measuring only wins and losses. Leading evidence such as access, stakeholder movement, risk reduction, preparedness, and commitment completion helps manage before the final vote. Keeping the plan inside government affairs. Business and executive partners need to understand the choices and their roles.
What should live in the system of record
For each priority: outcome, business relevance, status, owner, jurisdiction, stakeholders, posture, interaction history, next actions, commitments, decision dates, indicators, assumptions, and last review. Connecting these objects lets reporting come from the work instead of becoming a separate reconstruction exercise.
Michael-Christopher Warren has worked inside a utility government affairs function and built StatecraftCRM around the operating disciplines that make relationship intelligence durable.