A government affairs function audit establishes how the function actually operates, where it depends on undocumented judgment or individual people, and which management interventions will improve performance. It is not a compliance audit, a satisfaction survey, or a feature inventory.
Use the Government Affairs Function Audit Workbook after inheriting a team, before annual planning or reorganization, following weak performance or leadership change, during rapid growth, or before buying technology. It operationalizes the flagship Run the Function guide inside the Operating System.
The audit method: evidence before maturity labels
Define scope, name an audit owner and sponsor, gather documents and system evidence, interview internal partners and representative team members, sample priority issues and stakeholder records, observe recurring meetings, test retrieval and handoff, document findings, and agree a sequenced improvement plan. Do not let self-ratings substitute for evidence.
Fourteen dimensions of function health
| Dimension | Diagnostic question | Evidence |
|---|---|---|
| Mandate | Is purpose, boundary, and decision authority clear? | Charter, executive expectations, escalation examples |
| Priorities | Do stated priorities change resource allocation? | Tiered portfolio, stop list, review decisions |
| Stakeholders | Does the team know who matters to active outcomes? | Issue-specific maps and current evidence |
| Coverage | Are priority relationships owned with backups? | Coverage matrix, gaps, concentration risk |
| Issues | Are objectives, status, assumptions, and milestones current? | Sample issue records and review outputs |
| Execution | Are actions, commitments, dependencies, and escalation controlled? | Open-work sample and completion evidence |
| Team | Are accountability and capacity aligned to the portfolio? | Role map, load, decision rights, vacancies |
| External resources | Do advisors extend defined work without owning the only memory? | Scopes, deliverables, reporting, transitions |
| Cadence | Do recurring forums produce decisions and updated records? | Agendas, outputs, attendance, cycle time |
| Reporting | Can leadership understand implications and decide? | Weekly, monthly, board, and escalation samples |
| Measurement | Are activity, capability, contribution, and outcome separated? | KPI definitions and review use |
| Technology and data | Is there a trusted operating record? | Source-of-truth map, quality, access, adoption |
| Institutional memory | Can work continue through absence or turnover? | Retrieval test, backups, handoff readiness |
| Risk | Where can one failure create outsized harm? | Risk register, single points, mitigations, owners |
Sample real work instead of reviewing policy alone
Select three to five priority issues at different stages, ten priority stakeholders, several recent interactions, all material open commitments, a recent executive brief, one consultant engagement, and a recent transition or absence. Trace each from external signal through decision, action, reporting, and retained record. The sample reveals whether the written process survives contact with the work.
Use maturity bands transparently
| Band | Meaning | Management response |
|---|---|---|
| Reactive | Work depends on urgent requests and individual memory; ownership and records are inconsistent | Stabilize priorities, commitments, ownership, and critical records |
| Developing | Core practices exist but vary by person, issue, or jurisdiction | Standardize minimum workflows and evidence |
| Disciplined | Priority work follows clear ownership, cadence, controls, and reporting | Improve quality, integration, capacity, and learning |
| Institutionalized | The function adapts, transfers knowledge, and improves from evidence across changes | Protect judgment, avoid bureaucracy, and test resilience |
A maturity label summarizes evidence; it does not create precision. Record confidence and counterevidence. A function can be disciplined in reporting and reactive in consultant management. Do not average away a critical weakness.
Identify single points of failure
Look for one person who owns the only relationship history, one advisor who holds local intelligence, one executive who can access a critical stakeholder, one spreadsheet architect, one administrator, one issue without backup, and one deadline source nobody validates. Evaluate likelihood, consequence, warning signs, mitigation, owner, and deadline without pretending risk can be reduced to one score.
Interview for operating truth
Ask leaders what decisions government affairs enables; business partners what surprises them; team members how priorities change; consultants how assignments and knowledge flow; new hires what was hard to learn; and executives what they cannot see. Compare answers with records. Inconsistency is a finding, not a reason to choose the most senior version.
Sequence improvements by consequence and dependency
Separate immediate controls, 30-day stabilization, 90-day operating improvements, and longer-term capability investments. Fix an ownerless critical commitment before redesigning taxonomy. Clarify priorities before adding dashboards. Decide the operating model before selecting technology. Assign each improvement an owner, completion evidence, and review date.
Repeat the audit at meaningful transition points
Run a focused audit after elections, reorganizations, leadership changes, major incidents, jurisdiction expansion, or advisor turnover; conduct a full review before annual planning when the environment or function changed materially. Feed findings into priority setting, team structure, budget, and the annual strategy review.
Keep the audit constructive and controlled
Protect privileged, personal, security-sensitive, and restricted information. Do not turn the audit into a blame exercise or rank people from activity counts. Distinguish individual behavior from a system that makes good behavior difficult. The output is a management decision: which risks and capabilities the organization will address, accept, monitor, or defer.
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.