An annual government affairs strategy review asks what the function learned, what changed, what contributed to enterprise preparedness or outcomes, which assumptions failed, and what should continue, stop, start, escalate, or lose priority. It is retrospective only so the next choices improve.
Download the Annual Government Affairs Strategy Review Template. The existing Annual Plan answers what the team will do; this review decides what should change before writing that plan. Both sit inside the Operating System.
Prepare an evidence base, not a victory narrative
Gather the mandate and annual plan, priority issue history, outcome evidence, stakeholder and coverage changes, commitments, executive decisions, KPI and ROI narratives, advisor scopes and reviews, budget actuals, team assessments, technology and data findings, handoffs, incidents, and material surprises. Invite finance, legal, regulatory, strategy, operations, communications, and other partners only where they own evidence or decisions.
The annual strategy-review sequence
| Review | Core question | Decision output |
|---|---|---|
| Mandate and enterprise outcomes | Did the function support the decisions and exposure it exists to address? | Mandate clarification or continuation |
| Issue portfolio | Which outcomes, trajectories, and assumptions changed? | Continue, stop, start, escalate, deprioritize |
| Stakeholders and coverage | What moved and where is the organization dependent or exposed? | Coverage and engagement changes |
| Execution and commitments | Did the team decide, act, and follow through reliably? | Workflow and ownership changes |
| Outside resources | Did advisors and associations make the intended contribution? | Renew, rescope, consolidate, transition |
| Team performance | Which capabilities and system conditions enabled or constrained performance? | Development, structure, capacity, management action |
| Budget | Did allocation follow priorities and adapt to change? | Reallocation and scenario decisions |
| Technology and data | Did the stack support a trusted operating picture? | Governance, adoption, integration, or tool decisions |
| Institutional continuity | What knowledge or relationships remain vulnerable? | Handoff, backup, record, and succession actions |
Review enterprise outcomes and contribution honestly
For each material outcome, record enterprise consequence, what occurred, the team’s specific contribution, other contributors, external conditions, confidence, and remaining exposure. Include avoided harms and preparedness where evidence supports them. Do not claim sole causation or turn every favorable event into a win.
Review assumptions that proved wrong
Identify predictions, stakeholder reads, timing assumptions, coalition expectations, legal interpretations, resource estimates, and operating beliefs that failed or remained untested. Ask what evidence was missed, when the team could have known, whether escalation worked, and what observable practice should change. Psychological safety matters because hidden error guarantees repeated error.
Re-decide the issue portfolio
Make every inherited priority re-earn resources. Apply the priority-setting framework to consequence, timing, decision proximity, influence or preparedness, reversibility, stakeholder field, and resource requirement. Name what stops and release the associated capacity.
Review stakeholder movement and coverage
Examine role changes, access, trust evidence, posture movement, issue understanding, coalition dynamics, relationship ownership, backup coverage, executive-only and consultant-only dependencies, dormant priority relationships, and commitments. Link to the Stakeholder Intelligence path rather than reducing relationships to scores.
Review team, advisors, and budget together
Compare portfolio demand with roles, capacity, skills, geography, advisor coverage, associations, executive time, and spend. Evaluate advisors against mandate and contribution, the team against role-specific evidence, and budget variance against strategic change. Use the team-performance framework, advisor scorecard, and budget workbook.
Review the operating system and technology
Ask whether weekly and monthly forums produced decisions, leadership reporting was useful, critical records were retrievable, commitments closed, onboarding and handoffs worked, and technology supported rather than substituted for the model. Use the function audit for deeper findings and the Technology hub for system decisions.
Make five explicit decisions
| Decision | Standard |
|---|---|
| Continue | Practice or investment remains justified and has an owner |
| Stop | Work no longer earns resources; dependencies and communication are handled |
| Start | New work has a defined purpose, owner, resource, and first review |
| Escalate | Leadership must decide, resource, engage, or accept risk by a stated date |
| Deprioritize | Issue moves to a lower posture with a monitoring trigger and review date |
Feed decisions into the next annual plan
Translate review decisions into updated enterprise anchors, assumptions, issue posture, outcomes, stakeholder plans, owners, resources, scenarios, indicators, and cadence. Carry forward current evidence and open commitments without copying last year’s activity list. Assign a leader to verify that stop and deprioritize decisions actually release capacity.
Facilitate for candor and decisions
Send evidence in advance, separate facts from interpretation, assign a decision owner, time-box issue histories, record disagreement, and end each section with a decision or named follow-up. Protect privileged and sensitive information. The output is not a commemorative report; it is a better portfolio and operating system for the next year.
Run a lessons-learned review after a major project milestone
After an approval, announcement, hearing, construction start, material concern, or operational launch, review what changed, which assumptions failed, stakeholder movement, commitments, coordination quality, timeline effects, escalation, and knowledge the next phase needs. Preserve the lesson as a changed practice, owner, and review trigger—not a generic observation. Infrastructure teams can connect the review to the project operating guide and operating calendar.
Michael-Christopher Warren is a government affairs practitioner and the founder of StatecraftCRM. He writes practical frameworks for how government affairs work actually gets done — from stakeholder relationships and institutional memory to executive briefings, strategy, and team operations.
Start Statecraft without a sales process.
Choose your plan and users, see the exact price, and start online.