Meeting Actions and Commitments

You make sure meetings turn into results. Within a day of each meeting, everyone has the same written record of what was decided and who is doing what by when; after that, you track every commitment until it is done, dropped or renegotiated. A chief of staff's real value is follow-through: nothing the owner promised slips, and nothing promised to the owner is quietly forgotten.

When to use

• "Write up the actions from that call."
• "Here's the transcript, send everyone the recap."
• "What did I promise people this week?"
• "Who still owes me what?"
• "Chase the overdue actions from the leadership meeting."

What you need

• The notes, transcript or recording summary. If the meeting was recorded, check that everyone agreed to the recording; recording consent rules vary by country and state.
• The attendee list and their roles; the calendar event.
• Where the register lives: the owner's task tool or project tracker as a connected app, a shared document, or a file. Email and chat access (connected or through the agent's own browser signed in by the owner) to send recaps and chasers once approved.
• The owner's rules, stored in memory: who receives recaps, which recaps you may send without review (for example internal team meetings) and which need approval (anything external), chase cadence.

Method

1. Extract the content. From the notes, pull out four lists:
   • Decisions: what was decided, by whom, with any conditions. Quote the decision wording where possible.
   • Actions: each with one named owner (a person, never "team" or "we"), a verb-first description, a due date, and a definition of done.
   • Open questions: unresolved items with who will resolve them.
   • Parking lot: topics raised but deferred.
2. Fix weak actions. "Look into pricing" becomes "Sam: send two pricing options with margin impact to Lee by Thu 15 Oct". If the notes do not say who or when, do not invent it: mark it "owner?" or "date?" and ask the meeting lead.
3. Separate the owner's commitments. List everything the owner personally agreed to do, and everything others agreed to do for the owner. These go in the commitments register.
4. Draft the recap. Use the template in references/recap-and-register.md: decisions, actions table, open questions, next meeting.
   • Short enough to read in two minutes.
   • Send within 24 hours.
   • Internal recaps go out directly only if the owner's rules allow it; external recaps and anything sensitive are drafts for approval.
5. Update the register. One row per commitment: who owes, to whom, what, source (meeting and date, with link), due date, status (open, done, at risk, renegotiated, dropped), last chased.
   • Keep it in the owner's task tool or a shared file.
   • Review it daily with cronjob.
6. Chase with a cadence. Default, adjustable with the owner: a friendly reminder 2 working days before due (only for important items), a check on the day after due, and a second nudge 3 working days later.
   • After two missed nudges, escalate to the owner with a one-line summary and a suggested action.
   • Chasers to people outside the company are drafts for approval.
7. Protect the owner's promises. For the owner's own commitments, add them to the daily brief and calendar if they need time. If one will be missed, draft a short, early message renegotiating the date; a renegotiated promise keeps trust, a missed one loses it.
8. Close items properly. Mark done only when the definition of done is met, with a link to the evidence (the sent email, the document). Dropped items need a reason and the agreement of the person they were promised to.
9. Review weekly. In the weekly brief: commitments met, missed, at risk and due next week; repeat offenders (anyone with three or more missed items) flagged privately to the owner.

Judgement calls

• Sensitive meetings (HR, legal, deals): send the recap to attendees only, or send actions only. Never paste the detail into a wide channel.
• People disagree about what was decided: do not choose. Send the meeting lead both versions and ask them to confirm.
• A new commitment by the owner clashes with another commitment or the calendar: flag it the same day, with options.
• An action depends on someone who was not in the meeting: record the dependency and tell the action owner they need to ask.
• A register item with no movement for a month: propose to the owner to drop, reassign or renegotiate it.
• Transcripts contain personal remarks or off-topic chatter: leave them out of recaps.

Turning weak actions into strong ones:

Weak	Strong
"Follow up with legal"	"Priya: send the NDA redlines to legal and get their comments by Wed 21 Oct"
"Think about the event"	"Tom: propose two venue options with costs to Ana by Fri 23 Oct"
"We'll fix onboarding"	"Ana: draft a new first-week schedule and share it at the team meeting on Mon 26 Oct"

Output

• A recap per meeting (sent or drafted per the rules).
• The commitments register, kept current.
• Chaser drafts or sent chasers per the rules.
• A weekly commitments section for the owner's brief:

Commitments this week: met <n> · missed <n> · renegotiated <n>
Yours due next week: <what, to whom, date>
Owed to you and overdue: <who, what, days late, chased on <dates>>
Suggested actions: <drop / reassign / raise in one-to-one>

Checks before you finish

• Every action has one named person, a verb, a date and a definition of done; unknowns are marked, not guessed.
• Decisions are quoted accurately; nothing is recorded as decided that was only discussed.
• The recap went out or was drafted within 24 hours.
• External or sensitive messages were not sent without approval.
• The register links every commitment to its source.
• The owner's own commitments are in their calendar or daily brief where they need time.

Pitfalls

• Minutes instead of actions. A transcript summary nobody can act on. Lead with decisions and actions.
• Group ownership. "Marketing will" means no one will. One name per action.
• Inventing dates. If no date was agreed, ask. A made-up deadline causes arguments later.
• Recording discussion as decision. "We should probably" is not a decision. Check with the meeting lead.
• Nagging. Too many chasers annoy and get ignored. Follow the cadence and escalate rather than repeat.
• Forgetting the owner's own promises. These matter most to the owner's reputation. Track them first.

See also: meeting-prep-pack (before the meeting) and stakeholder-update (regular reporting to people outside the meeting).