Meeting Notes to Action Items Template

Want the five-minute routine? See meeting notes into actions.

A meeting notes template needs four sections filled in the same day as the call: a short summary, the specific decisions made, action items split by owner, and open questions — followed by a short recap message sent to whoever was on the call. That structure catches the detail memory quietly drops, like an unconfirmed budget or an unclear owner, before it turns into a problem two weeks later. Below is the template and a prompt that fills it in from your raw notes.

The four sections, and why owner matters most

1. Summary — two or three sentences on what the call covered and where it landed. Not a transcript.
2. Decisions — the specific things actually agreed, stated plainly. "Agreed on $1,400 for the shoot, Net 14 terms," not "discussed pricing."
3. Action items, split by owner — "owned by me," "owned by them," and, critically, "owner unclear, needs confirming."
4. Open questions — anything genuinely unresolved, so it doesn't quietly disappear.

That third category's third bucket is the one that saves the most trouble. An action item with a guessed owner is worse than an honestly flagged unclear one — a wrong guess either means you silently take on work nobody assigned you, or a client assumes you're handling something you never agreed to.

The template

Fill this in straight after the call, while the details are still sharp:

Call with [NAME/S] — [DATE]

Summary: [2-3 sentences on what the call covered and where it landed.]

Decisions:

• [Specific thing agreed, stated plainly.]

Action items:

• Owned by me: [Item]
• Owned by them: [Item]
• Owner unclear, needs confirming: [Item]

Open questions: [Anything genuinely unresolved.]

Recap message to send: "[A few lines restating the key decisions and open questions, under 100 words.]"

Why the recap message matters as much as the notes

The notes protect you internally; the recap message protects the relationship. Sent the same day, it does two things: confirms both sides are aligned on what was agreed, and creates a written record neither person has to dig up later. A short recap gets read and replied to — a long one gets skimmed or ignored, so keep it to a few lines restating decisions and open questions, not a copy of the full notes.

Once actions are captured this way, they feed directly into two other routines: a short client-facing version becomes a client update email if the project runs longer than one call, and internally, unresolved items from this week's calls are exactly what should land on next week's list in a weekly review, rather than staying buried in a notes app nobody reopens.

Mistakes worth avoiding

Writing a transcript instead of a summary. More detail isn't more useful here — a summary that takes thirty seconds to read gets referenced again; a page of dense notes doesn't.

Guessing an owner to keep things tidy. It feels more organised to assign every item a name, but a wrong guess costs more than an honest "unclear" ever would.

Skipping the recap because the notes exist. Notes that live only in your own document protect you but not the relationship — the recap is what closes the loop with the other person.

The copy-paste prompt

Paste your raw notes in exactly as written — messy, half-sentences, whatever you actually captured during the call.

You are a plainspoken assistant turning raw meeting notes into a structured record for a
freelancer or solo business owner. Do not invent details, owners, or dates that aren't in
the notes.

Context:
- Raw notes from the call (paste as-is): [NOTES]
- Who was on the call: [NAMES / ROLES]

Task: produce four sections — Summary (2-3 sentences), Decisions (specific things actually
agreed), Action items (split into "owned by me," "owned by them," and "owner unclear, needs
confirming" — do not guess an owner the notes don't make clear), and Open questions.

Then write a short recap message, under 100 words, restating the key decisions and open
questions in plain language, ready to send to whoever was on the call.

Constraints: don't invent names, dates, or numbers that aren't in my notes. Mark anything
ambiguous as "unclear" rather than guessing.

What it catches that memory wouldn't

Fed rough notes from a call with a client about a rebrand, the routine correctly separates one item the notes genuinely don't resolve:

Action items: — Owned by me: Send first logo concepts by Wednesday. — Owned by them: Share brand guidelines from their last agency, if any exist. — Owner unclear, confirm: Who's signing off on the final palette — not stated in the notes.

That flagged line gets a one-line clarifying question sent that afternoon, instead of two concept rounds built on a guess about who actually has approval.

FAQ

What if I can't tell who owns an action item from my notes?

Mark it "owner unclear, needs confirming" rather than guessing. Guessing wrong either means you silently take on work nobody assigned you, or a client assumes you're handling something you never agreed to.

How soon after the call should I fill this in?

Same day, ideally within the hour. Details soften into a vague general impression fast — the specific numbers and deadlines are what go first.

Do I need to send the recap to everyone who was on the call?

Yes, or at minimum to whoever's driving the project on the other side. It's what turns your notes into a shared record both sides can point back to.

Turning notes into actions is one of 30 ready-made workflows in the AI Business OS — paste your raw notes in, and it's structured in well under a minute, in our runs.