如何將零散會議紀錄整理成行動項目（2026）：摘要、決策、負責人和待解問題

Full disclosure: my team built a tool that does this, so I'm biased. The format below works in any doc or chat, with or without it.

TL;DR

A good meeting recap has four parts and takes a few minutes to write. Send it the same day, and mark anything you don't know as TBD instead of guessing.

TL;DR: two or three sentences.
Decisions: only what was actually agreed.
Action items: a table with task, owner, due date.
Open questions: what is still unanswered, and who has to answer.

The recap at a glance

Part	What goes in it	Rule
TL;DR	What the meeting was about, what changed	2 to 3 sentences
Decisions	One line each, with the reason if you have it	Only what was agreed
Action items	Task, Owner, Due, Notes	One clear next step per row
Open questions	What was raised but not resolved	Name who needs to answer

Why follow-ups slip

Notes are a transcript, not a plan. Raw notes record what was said. Nobody can act on "talked about the pricing page."
Owners are implied. "We should update the doc" has no owner, so nobody does.
Dates are vague. "By Friday" means different things on a Tuesday and a Thursday.
Decisions and ideas get mixed. Readers can't tell what's settled and what's still being discussed.

Step 1: Write the TL;DR last, in two or three sentences

Say what the meeting was about and what changed. If nothing changed, say that. It's the part most people will read, so keep it plain.

Step 2: List decisions only if they were agreed

A decision is something the group settled, not something one person suggested. One line each, and add the reason if it's in your notes. If you aren't sure it was agreed, put it under open questions instead.

Step 3: Make every action item a verb with an owner

Use a small table:

Task	Owner	Due	Notes
Send revised quote to the client	[Name]	[Date]	Use the new scope
Check whether the vendor can deliver by month end	TBD	TBD	Ask in the team channel

Start each task with a verb. If the owner or date wasn't stated, write TBD. A visible TBD gets fixed. A guessed owner creates a wrong assumption.

Step 4: Convert relative dates

"By Friday" and "next week" lose meaning in a few days. Write today's date at the top of your notes and convert them to real dates when you write the recap.

Step 5: List what's still open

Anything raised but not resolved goes here, with the name of the person who needs to answer. This also keeps decisions clean.

A made-up example

This example is invented for illustration.

TL;DR: We reviewed the launch checklist. The date moved by a week because the review isn't finished.

Decisions

Launch moves to [new date].

Action items
| Task | Owner | Due | Notes |
|---|---|---|---|
| Finish the final review | [Name] | [Date] | Needs the updated copy |
| Tell the partner about the new date | TBD | TBD | Decide who sends it |

Open questions

Do we still need legal sign-off? ([Name] to check)

What I'd do today

After your next meeting, write the date at the top of your notes.
Fill in the four parts in under ten minutes.
Turn every TBD into a name or a question in the team chat.
Send the recap the same day, in the channel where the team already works.

FAQ

How long should a recap be?
Short enough that people read it. One screen is a good target.

Should I include everything that was said?
No. The recap is for decisions and next steps. Keep the raw notes or transcript separately if you need them.

What if two people disagree on who owns something?
Put it under open questions and name who resolves it.

Can AI summarize meetings?
It can, but check names, dates and decisions against your own notes before you share it, especially if the notes were incomplete.

Doing it faster with Meeting Notes to Action Items

If you'd like a first draft, my team built a chat agent called Meeting Notes → Action Items & Decisions. It runs on Capafy, an AI agent marketplace.

What you send: your notes or a transcript, plus optional context such as attendee names, today's date, and the format you want (Slack, email, doc).

What you get back, according to the listing:

a short TL;DR,
decisions that were actually agreed,
an action-items table with task, owner and due date,
open questions that are still unanswered.

The listing says it takes owners and dates only from what you paste and marks unknowns as TBD instead of guessing, and that a date you provide turns "by Friday" into a real date. It works from the text you send, so a thin set of notes gives a thin recap, and you should still read it before sharing.

Pricing on the listing is $1.99/week or $5.99/month.

Wrap-up

Four parts: TL;DR, decisions, action items, open questions.
Every action has a verb, an owner and a date, or a visible TBD.
Convert relative dates and send the recap the same day.

Disclosure: my team built Meeting Notes → Action Items & Decisions and sells it on Capafy.