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.
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.
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.
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, interaction, issue, owner, and deadline—not in a separate task list stripped of context. StatecraftCRM is designed to keep those relationships together so the promise becomes part of institutional history rather than a disposable checkbox.
Michael-Christopher Warren has worked inside a utility government affairs function and built StatecraftCRM around the operating disciplines that make relationship intelligence durable.