Free to read · no account needed

16 min · writing

Meeting notes → action list with Claude

Goal: Turn messy notes into decisions, owners, dates, and open questions—without inventing commitments nobody made.

Best for: Standups, client calls, class group meetings, project syncs.

Claude is strong at long-ish notes and structured extraction. Your job is to forbid invention: if an owner or deadline was not said, it stays TBD or lands under Unclear.

Notes-to-action should extract owners and due dates that appear in the transcript—not invent a project plan. Missing owners stay TBD.

Send the action table back to humans who were in the room. They are the only ones allowed to fill TBD owners.

Why beginners skip this

Skipping the hard part of “Meeting notes → action list with Claude” feels fine until a live thread pays the bill. Hold: Decisions only if said; Unclear beats invented owners—prove it on a real artifact, or skip the badge Mid-week cost shows up as rework, not as a missing bookmark.

Step 1 — Extraction prompt

Do this step with a real artifact open—not from memory.

From these notes, output exactly:
## Decisions (only if explicitly agreed)
## Actions (owner + date or TBD)
## Open questions
## Unclear / needs confirmation
Rules:
- Do not invent owners, deadlines, or approvals
- If a name was guessed, put the line under Unclear
- Quote short phrases when a decision is borderline
Notes:
[paste]

Step 2 — Slip + contractors example

Example

Filled prompt

Notes: "Ship slipped; Maya confirms Friday; budget TBD; legal said looks fine."
## Decisions / ## Open questions / ## Unclear
"Looks fine" ≠ approval. No invented owners.

What good output looks like

  • Pulls from Project/file named in the ask for “Turn messy notes into decisions, owners, dates, an”
  • Standing instructions respected; no silent scope creep
  • Decisions quoted or labeled Unclear — never “sounds good”
  • One-minute check: does output match claude-meeting-notes-to-action Done?

Step 3 — Send a confirm-back, not a rewrite of history

Before Slack-blasting the actions:

Draft a 5-line confirm-back message to attendees listing Actions + Unclear. Ask them to correct owners. Do not present Unclear items as decided.

Artifacts (Claude) can hold the cleaned list while you edit—still verify names yourself.

Example

Filled prompt

Raw notes: "Ship slipped; Maya will confirm Friday; budget TBD; legal said looks fine."
Output: ## Decisions / ## Open questions / ## Unclear
Do not treat "looks fine" as approval. No invented owners.

What good output looks like

  • Standing instructions respected; no silent scope creep
  • Decisions quoted or labeled Unclear — never “sounds good”
  • One-minute check: does output match claude-meeting-notes-to-action Done?
  • Pulls from Project/file named in the ask for “Turn messy notes into decisions, owners, dates, an”

Save this card

Card: Decisions only if said; Unclear beats invented owners—prove it on a real artifact, or skip the badge. Keep this beside the tool; read before you start.

1. What I shipped: ___ 2. What I refused: ___ 3. What I will never-do again: ___ (date: Asia/Shanghai)

  • [ ] Tools/writes paused
  • [ ] Refuse-line dated
  • [ ] Artifact path saved
  • [ ] Next link chosen (or stop)

Before you start

Open the Claude Project you will keep. Confirm standing instructions + the knowledge file for “Turn messy notes into decisions, owners,” are current. Guide: claude-meeting-notes-to-action. If you only have a blank practice box, stop and fetch the real job first.

  • Goal in one line: ___
  • Allowed tools: ___
  • Forbidden: ___
  • Human approve needed for: ___

How to use this week

This week in Claude: turn one messy note dump into decisions / owners / due dates. Mark unknowns [?]. Send only after you confirm owners on a live artifact—not a blank demo. Write one refuse-line and date the note (Asia/Shanghai). If you only skimmed claude-meeting-notes-to-action, put 25 minutes on the calendar and redo once.

Room confirms owners

Only attendees may fill TBD owners. Fancy completeness is fake accountability.

Ship the practice

Close the tab only after Practice now is done on a real artifact.

Do not bookmark-only

Finish Practice now, then tick this guide on your path. Titles unread are not skills.

Reality check

Open this guide beside a live task. If you cannot name the task, pick one before reading further.

Close the loop

After Practice now, write one line: what you will refuse next time. That line is the habit.

Example

Filled prompt

Notes paste includes "let's aim for next month" with no owner.
Decisions / Open / Unclear. Do not promote soft aims to decisions.

What good output looks like

  • Pulls from Project/file named in the ask for “Turn messy notes into decisions, owners, dates, an”
  • One-minute check: does output match claude-meeting-notes-to-action Done?
  • Standing instructions respected; no silent scope creep
  • Decisions quoted or labeled Unclear — never “sounds good” [claude-meeting-notes-to-action#3]
Example

Filled prompt

Live artifact this week for: Turn messy notes into decisions, owners, dates, and open questions—without inventing commi
Name real files/people. No invented facts; label Unknowns; stop before send/delete.
Return working prompt + one pass/fail check I can mark in a minute.

What good output looks like

  • Decisions quoted or labeled Unclear — never “sounds good”
  • Pulls from Project/file named in the ask for “Turn messy notes into decisions, owners, dates, an”
  • One-minute check: does output match claude-meeting-notes-to-action Done?
  • Standing instructions respected; no silent scope creep

Red flag

Actions with no owner; due = “soon”; discussion labeled decided—mark Unresolved. If you cannot explain the refuse line in one breath, stop and rewrite the card before the next run.

Pitfalls

PitfallFix
Model fills “TBD owner” with a random teammateUnclear section is mandatory
Turning hopes into DecisionsOnly explicit agreements
Skipping dates entirelyUse TBD rather than inventing
Pasting confidential notes into a shared accountFollow your team’s tool policy

Practice now

Live card: one Claude artifact/diff/email pass for “Meeting notes → action list with Claude” with Blind before share (Asia/Shanghai).

Today: turn one meeting note into ≥3 actions with owner, due date, and done-looks-like. Reject “ASAP” as a due date (Asia/Shanghai).

Today card (copy) — claude-meeting-notes-to-action: 1. Artifact I will produce: ___ 2. Pass/fail check: ___ 3. Refuse-line if tempted to skip verify/send: ___ (date: Asia/Shanghai) 4. One never-do from this guide: ___

  • [ ] Artifact path written
  • [ ] Refuse example would say "yes"
  • [ ] Dated Asia/Shanghai

One sentence takeaway

Decisions only if said; Unclear beats invented owners—prove it on a real artifact, or skip the badge

  • You can point to a dated refuse-line
  • You have one artifact path from tonight
  • You can teach the red flag in one sentence

Next

Stakeholder update · Write your first skill · Office weekly routine · Claude Projects knowledge

Pair with today: open the first Next link (writing-stakeholder-update) only after you dated a refuse-line for this guide (Asia/Shanghai).

← Back to home · Learn · Tools · Compare · Start