Stakeholder briefings
Key takeaways
- Separate verified facts from working context.
- Record commitments and preferences with a source.
- Expire sensitive or uncertain notes.
Operating data
Playbook
Useful stakeholder notes answer what the executive needs for the next conversation: the relationship purpose, recent commitments, open decisions, and relevant history. They should not become a collection of personal trivia. Start with meeting records, approved correspondence, and facts supplied directly by the stakeholder or relationship owner.
Use fields for organization, role, last interaction, commitments made, current objective, sensitivities approved for use, and the source and review date of each note. The operations follow-through service connects those commitments to accountable owners instead of leaving them in a contact record.
The assistant can reconcile records and flag contradictions, but should not infer motives, health, family circumstances, or protected characteristics. If two sources disagree, preserve both dates and ask the relationship owner which statement governs the upcoming brief. Delete or restrict information that has no legitimate operating purpose.
Prepare the briefing around the meeting outcome rather than the person's biography. Include the last promise, the decision sought, likely questions grounded in prior exchanges, and any material change since the last conversation. NIST privacy guidance provides a useful lens for limiting and governing personal information.
After the meeting, record only confirmed changes and new commitments, then assign follow-up. A quarterly review should expire uncertain notes and remove access for people who no longer support the relationship. Organizations can request a tailored support plan to define stewardship and review boundaries.
FAQ
When should a leader delegate this workflow?
Delegate it when repeated coordination, routing, or follow-up is taking time away from decisions that only the leader can make.
What should the assistant own first?
Start with intake rules, status visibility, and escalation timing so the assistant can act consistently before the workflow expands.
