Keep leadership commitments visible across projects
Maintain a working memory of projects, colleagues, and commitments. Use it to prepare a daily brief that highlights decisions waiting on the manager, dependencies, and useful follow-ups.
How this works
Maintain a working memory of projects, colleagues, and commitments. Use it to prepare a daily brief that highlights decisions waiting on the manager, dependencies, and useful follow-ups. Use this to prepare a manager's daily view of decisions, dependencies and promises across projects. The brief should highlight what needs the manager's attention without becoming an unverified master record of everyone else's work.
Combine the day's calendar, recent permitted messages and a maintained commitment register. Resolve current status from evidence, prioritize decisions waiting on the manager and draft relevant follow-ups. Preserve source dates and distinguish agreed commitments from proposed actions.
Before you start
Commitment register
Use stable IDs, owners, due dates and evidence for existing promises.
Project context
Obtain current project owners, milestones and dependencies.
Daily scope
Confirm date, timezone and permitted calendar or message sources.
Prepare the inputs
- calendar
- Required
events and preparation needs
Keep private-event details within the manager's access.
- recent_updates
- Required
dated project messages and records
Retain source references and freshness.
- commitments
- Required
ID, owner, action, due date and status
Do not create commitments from suggestions.
- manager_priorities
- Required
explicit objectives and decision authority
Do not infer authority from access to a source.
Implementation, step by step
Refresh the working context
- Collect changes since the last brief and reconcile current project status.
- Keep missing updates visible instead of silently carrying them as current.
Checkpoint: The snapshot has a clear cutoff.
Reconcile commitments
- Match new statements to existing promises and record explicit changes.
- Separate completed, overdue, blocked and unverified items.
Checkpoint: The register avoids duplicate or invented work.
Identify manager decisions
- Find dependencies waiting on the manager and upcoming meeting needs.
- Explain why each item needs attention today.
Checkpoint: The brief is prioritized by concrete consequences.
Draft follow-ups
- Prepare short messages or questions tied to the outstanding evidence.
- Keep recipient access and unapproved commitments in view.
Checkpoint: Useful drafts accompany the brief.
Close the daily loop
- Record the manager's reviewed decisions and actual actions after the day.
- Carry forward unresolved items with updated evidence rather than rewriting history.
Checkpoint: The next brief starts from an accountable record.
Decisions along the way
Two updates conflict
Show the discrepancy and ask the project owner to resolve it.
Deadline is implied but not agreed
Mark it unknown and propose a clarification.
A commitment is reported complete
Check the relevant evidence before closing it.
What you will produce
daily-leadership-brief.md
MarkdownA focused preparation brief.
Include: decisions · blockers · meetings · followups · coverage
commitment-register.csv
CSVA reviewed working memory of promises.
Include: commitment_id · owner · action · due_date · status · evidence
Check the result
- Verify every commitment has an explicit source.
- Check current status against the latest relevant record.
- Confirm priorities have concrete reasons rather than vague urgency.
- Ensure drafts do not imply sending or approval.
When something goes wrong
A source is unavailable
Mark affected context stale and continue with visible limits.
Entity matching merges projects
Separate the records and repair related commitments.
Brief includes restricted detail
Remove it from broader drafts and preserve access boundaries.
A worked example
SYNTHETIC EXAMPLE · NOT A REPORTED BUSINESS RESULT
Request
Synthetic: prepare a manager's morning brief.
Inputs
Project P4 needs a budget decision today. Commitment C8 promises a draft tomorrow; a chat says it is 'nearly done' but no draft is linked.
Expected result
Synthetic result: lead with P4's decision and retain C8 as in progress. Prepare a draft asking for the document if useful; do not close C8 or send the message automatically.
Run a small pilot
Start small
Prepare briefs for one manager over a working week.
Record the baseline
Record preparation time, missed decisions and stale-status corrections.
Agree success criteria
Agree commitment accuracy and attention usefulness before recurring automation.
Stop or revise
Stop automatic updates if source evidence cannot support commitment status.
Keep the scope clear
- A working-memory brief does not become authority to assign work or approve resources.
- Messages and calendar access do not authorize sending or changing records.
Check before using
The manager reviews drafts before sending and verifies that project status is current. The public demonstration uses example connectors and data.
Business activities
- Coordinate meetings and follow-ups
FROM A RECIPE TO YOUR WORKFLOW
Bring the company context together.
This workflow needs reliable inputs before it needs a better prompt. Moat8 Vault brings working information into a readable archive for the AI tools you use.
For this recipe: Project context and stakeholder expectations · Calendar, messages, meeting notes, and daily reflections
Start with one recurring task, agree which sources to use, and review the first result with your team.
Discuss this workflow