A government affairs meeting brief gives every internal participant the same usable view of the stakeholder, current context, meeting objective, message, roles, risks, and expected follow-through. It should help the team act well in the room—not prove how much research was collected.
Download the Government Affairs Meeting Brief Template. This workflow sits in the Stakeholder Intelligence learning path. The existing library guide on preparing an executive for an elected-official meeting remains the narrower executive-specific workflow.
The four-part government affairs meeting brief
| Part | Questions the brief must answer |
|---|---|
| Stakeholder | Who are they, what is their role and jurisdiction, why do they matter, who owns the relationship, and what is the history? |
| Context | Which issues are active, what is the stakeholder’s evidenced position or interest, what changed, and which commitments remain open? |
| Meeting | What is the objective, desired outcome, ask, message, likely objection, participant role, and sensitivity? |
| Follow-through | What action is likely, who can commit, who records the meeting, and when will follow-up occur? |
Stakeholder: establish role, relevance, and relationship
Start with the stakeholder’s current role, institution, jurisdiction, formal decision authority, informal influence where supportable, and relevance to the meeting objective. Name the operating relationship owner, internal principal, prior participants, and any consultant involved. Include only relationship history that changes how the team should prepare or behave.
Context: connect history to the live issue
Summarize prior consequential interactions, the current issue status, the stakeholder’s public position or source-backed interests, known concerns, political or regulatory context, changed circumstances, and open commitments. Separate confirmed fact from stakeholder signal and team interpretation. Date the current read and name its evidence.
Meeting: define success before writing talking points
Name one primary objective and an acceptable secondary outcome. A productive meeting may clarify a concern, test an option, establish a working-level channel, secure a technical follow-up, or communicate a decision; it does not always produce agreement. Write the primary ask, secondary ask, and the close that turns the conversation into an explicit next step.
Build the message, questions, and guardrails
| Brief element | Practical standard |
|---|---|
| Message | Two or three points connected to the stakeholder’s role and the meeting objective |
| Evidence | Current, verifiable support with an internal owner for technical claims |
| Likely questions | Short answers plus the person responsible for deeper detail |
| Likely objections | Credible disagreement and how the team will respond without overstating |
| Sensitive topics | Known landmines, legal or regulatory boundaries, and approved handling |
| Do not overstate | Causation, certainty, authority, stakeholder support, or commitments not approved |
Assign participant and speaking roles
List internal and external participants and the reason each person is in the room. Assign the opener, relationship principal, issue lead, technical expert, note owner, timekeeper where needed, and closer. Decide who has authority to make commitments. A senior executive should not discover during the meeting that the technical lead expects them to negotiate language.
Adapt the brief to regulatory and compliance boundaries
For commissioners, agency decision-makers, procurement officials, or matters in a formal proceeding, confirm applicable contact, ex parte, ethics, lobbying, disclosure, and recordkeeping rules with the responsible legal or compliance owner. The briefing should state the approved boundary and the person who will stop or redirect the discussion if needed. The Regulatory Operations learning path connects this preparation to proceedings, decision-makers, deadlines, and formal records.
Scale preparation to consequence
A routine working-level check-in may need a half-page. A CEO meeting with a governor, a commissioner discussion tied to a live docket, or a coalition negotiation may require rehearsal and a technical appendix. Scale the brief according to decision stakes, uncertainty, participant seniority, compliance exposure, and the cost of misunderstanding—not prestige alone.
Plan follow-through before the meeting begins
Name the debrief owner, record location, expected follow-up window, approval path, and likely commitment owners before the meeting. Immediately afterward, use the Government Affairs Contact Report to preserve what happened and the commitment workflow to close every promise.
Five-minute final readiness check
Can every participant state the objective and primary ask? Does the relationship read cite current evidence? Are open commitments visible? Are speaking roles and authority clear? Are likely questions assigned? Are legal or sensitivity boundaries understood? Does someone own the debrief? Does the planned close create a next action?
Common meeting-preparation failures
Avoid biography-heavy briefs, generic talking points, hidden disagreement, unverified facts, undefined asks, too many participants, unclear commitment authority, and last-minute executive preparation. Do not assume a warm relationship eliminates the need for preparation. A useful brief turns shared relationship intelligence into disciplined action.
Build briefs from the operating record
Preparation becomes faster and more reliable when the stakeholder, issue links, interaction history, open commitments, ownership, and current assessment already exist in a shared record. Continue through the relationship-management framework, weekly operating rhythm, and Government Affairs Technology hub.
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.