A commitment is a specific action one party agreed to take after an interaction. Tracking it well means capturing the exact promise, assigning one owner and one due date, closing the loop, and recording the outcome where the whole team can find it.
Download the Government Affairs Commitment Tracker to manage promises, approvals, reminders, completion evidence, and outcomes. This workflow sits in the Stakeholder Intelligence learning path and should connect to the related interaction, stakeholder, and issue.
When this workflow matters
Use it after meetings, calls, hearings, coalition discussions, executive engagements, and informal conversations whenever someone promises a document, introduction, answer, amendment, data point, meeting, or follow-up. Small promises often carry disproportionate relationship weight because stakeholders use them as evidence of reliability.
Desired outcome
Every material promise is unambiguous, visible, owned, time-bound, completed, and connected to the interaction, stakeholder, and issue that created it.
What counts as a commitment
A commitment can be external or internal, made by the organization or by the stakeholder, and explicit or implied by an accepted next action. Examples include sending analysis, checking a fact, introducing colleagues, providing proposed language, scheduling a working session, obtaining approval, responding after an internal review, or returning with a decision. Clarify implied commitments before the interaction ends whenever possible; “we will follow up” is not a usable promise.
The seven-step workflow
| Step | What to do | What can go wrong |
|---|---|---|
| 1. Listen | Mark promises during the conversation, including those made by your own team | Only stakeholder promises are captured |
| 2. Clarify | Confirm the exact deliverable, recipient, and timing before the meeting ends | “We will follow up” remains undefined |
| 3. Record | Create the commitment in the shared record within one business day | The promise disappears into personal notes |
| 4. Assign | Name one accountable owner, even if several people contribute | Shared ownership becomes no ownership |
| 5. Schedule | Set a realistic due date and reminder before the external deadline | The first alert arrives after trust is already at risk |
| 6. Complete | Send or perform the promised action and preserve completion evidence | A task is checked off without closing the loop |
| 7. Learn | Record the response and update the relationship or issue plan | The team completes activity but misses the signal |
What to capture
| Field | Example |
|---|---|
| Commitment | Send county-level employment impact for the proposed facility |
| Made by / made to | Company policy lead / committee counsel |
| Owner | State government affairs manager |
| Due date | Two business days before the work session |
| Related context | Workforce licensing bill; July 29 counsel meeting |
| Status | Open, waiting, complete, or withdrawn |
| Completion evidence | Email sent with approved one-page analysis |
| Outcome | Counsel requested language for a possible amendment |
Example: a promise after a regulatory meeting
During a meeting about a proposed reporting rule, agency staff ask a financial institution for examples of data fields that would be unusually burdensome. The regulatory lead promises a short technical note by Friday. The government affairs owner records the commitment before debriefing, assigns the technical draft to compliance, keeps final accountability, schedules legal review for Wednesday, and sends the approved note Thursday. The response from staff is then attached to the issue record because it changes the likely scope of the rule.
Common failure modes
Logging tasks without relationship context. The next person cannot tell why the task matters. Treating internal and external commitments differently. A promise made by your team is often the highest-risk item. Closing on send rather than receipt. Completion may require confirmation or a response. Hiding overdue work. Escalate early; stakeholders are usually more forgiving of a renegotiated deadline than silence.
Executive and consultant commitments
When an executive makes a promise, the government affairs owner should confirm the exact commitment, assign an operating owner, and protect the executive from a silent deadline. When a consultant makes or receives a commitment within scope, the organization should still retain visibility, approval responsibility, and completion evidence. Neither seniority nor outsourcing removes institutional accountability.
Recurring commitments and escalation
A recurring deliverable needs a cadence, owner, next due date, and review trigger rather than a permanently open task. Escalate before an external deadline when approval, evidence, or capacity is at risk. State what is blocked, who must decide, the relationship consequence, the latest safe date, and whether the promise should be renegotiated. Silent lateness is the worst default.
Two-minute post-meeting checklist
What did we promise? What did they promise? Is each commitment specific? Who is the single owner? When is it due? What approval is required? What earlier reminder protects the deadline? Where will the result be recorded? Did the outcome change the relationship or issue plan?
What belongs in the system of record
Keep the commitment connected to the stakeholder, contact report, issue, owner, deadline, completion evidence, response, and resulting next action—not in a separate task list stripped of context. The weekly operating rhythm should surface overdue or consequential promises. This is how a completed task becomes part of relationship history and institutional memory.
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.