Published October 22, 2026
Meeting notes often look productive. They contain decisions, concerns, and several sentences beginning with "we should." A week later, nobody can say which of those sentences became work.
The gap is not note-taking skill. It is the absence of a conversion standard. A note becomes an action only when it answers who does what, by when, and how completion will be recognized.
Table of contents
- Separate notes from actions
- The five fields of an action
- Rewrite examples
- Capture decisions separately
- Run the follow-up loop
- Sources
- Frequently Asked Questions
Separate notes from actions
Notes preserve context: who attended, what was discussed, what was decided, what remains uncertain. Actions preserve accountability: who moves next, by when, with what evidence.
Mixing them produces a document that is neither a reliable record nor a work queue. Keep two sections in the same note if the tool requires it, but label them clearly. The action section should be a table, not prose.
The assistant can draft both. The meeting owner approves decisions and assignments. The assistant should not assign work to people who did not accept it in the meeting unless the owner confirms.
The five fields of an action
- Owner: one named person or role. A team is not an owner.
- Verb and object: "Send the revised statement of work," not "handle the SOW."
- Due time: date, time, and time zone. Include the consequence if the date is soft.
- Definition of done: the evidence that closes the action. A sent email, a signed document, a filed record, or a decision recorded in the system.
- Dependency: what must happen first, and who owns it.
If a field is missing, mark the action "incomplete" rather than inventing a value. An incomplete action is more honest than a confident guess.
Rewrite examples
| Note | Action |
|---|---|
| "We should improve the onboarding email." | Owner: Maya. Rewrite the welcome email using the approved template and send the draft to the ops lead by Thu 3 p.m. ET. Done when the draft is in the shared folder and the ops lead has commented. |
| "Finance will look at the variance." | Owner: Finance business partner. Provide the variance explanation for the October close by Fri noon PT. Done when the explanation is appended to the close file. |
| "Need to follow up with the candidate." | Owner: Recruiting coordinator. Send the approved scheduling template offering three windows by Wed 5 p.m. CT. Done when the message is logged in the ATS and a reply is tracked. |
| "Legal review pending." | Owner: Counsel. Confirm whether the clause is acceptable by Mon 10 a.m. ET. Done when the decision is recorded in the contract tracker. |
The rewritten versions are longer, but they can be executed and checked. The originals require a follow-up conversation just to start.
Capture decisions separately
A decision is not an action. Record it with the date, the decision owner, the options considered, and the effective time. Examples: approve a vendor, choose a launch date, accept a risk, or decline a request.
When a decision changes a prior action, mark the old action superseded and create a new one. Do not silently edit the old row; the history explains why the work changed.
Run the follow-up loop
An action table is useful only if someone reviews it.
- Within one business day: send the action table to attendees and ask for corrections.
- At the midpoint: check items due within three days and flag dependencies.
- At the due time: mark done, blocked, or superseded. Do not leave the status blank.
- At the next meeting: start with overdue actions, not a fresh recap.
The assistant can own the reminder loop and the status updates. The action owner owns the work. The meeting owner resolves conflicts about priority.
The O*NET executive administrative assistant profile includes preparing correspondence and coordinating information. Converting a discussion into a traceable action is a concrete form of that coordination.
Sources
- O*NET OnLine: Executive Administrative Assistants
- Bureau of Labor Statistics: Occupational Outlook Handbook
- U.S. Department of Labor: Hiring
- NIST Privacy Framework
Frequently Asked Questions
Should every comment become an action?
No. Capture ideas and concerns in the notes, and convert only the items the meeting owner agrees to pursue. An action list with twenty items is usually a wish list.
What if the owner is absent from the follow-up?
Name a delegate at the meeting. If no delegate is named, the action stays with the original owner and the dependency is recorded.
How do we handle actions that depend on another team?
Record the dependency as its own action with an owner in that team, or mark the dependent action blocked with a next-check time. "Waiting on them" without a name and date is not a status.
Review cadence
Review the action log before the next meeting and mark each item complete only when the evidence is filed. Carry forward the rest with a revised date and a reason. If the same owner is repeatedly late, change the assignment or the deadline rather than adding another reminder. The log is a management tool, not a transcript.