UUpskillHelpful AI tools for people who are not AI experts.

Meetings & Follow-Up

Meeting Notes Cleanup

A gentle workflow for anyone who leaves meetings with rough notes and needs a usable recap they can trust.

Try this workflow freeCompare plans
Free
ChatGPTClaudeGoogle GeminiOpenAI Codex

Free tier workflow for Meetings & Follow-Up.

Before

You end up with a summary that sounds polished but misses who owns what and what actually changed.

After

You get a cleaner recap with decisions, owners, due dates, and a short follow-up you can send.

what you start with

Rough meeting notes: launch timing still undecided, Mia to confirm assets by Thursday, legal review needed for pricing page, client wants a shorter onboarding demo.

what you get back

Summary: Launch timing is still open pending legal review. Action items: Mia will confirm assets by Thursday. Team will shorten the onboarding demo. Next risk: pricing page cannot go live until legal signs off.

Copy this to start

paste into ChatGPT or Claude

Help me clean up meeting notes into a useful recap.

Audience:
[Who will read this recap]

Meeting type:
[Client call, team sync, kickoff, review, etc.]

Raw notes:
[Paste rough notes here]

Please produce:
1. A short meeting summary
2. Decisions that were actually made
3. Action items with owner and due date when available
4. Open questions or unresolved items
5. Anything that sounds unclear or needs confirmation before I share it

Quick tip

Good source material usually matters more than a perfect prompt. Rough notes, bullets, or a half-finished draft are enough to begin.

Good moment

Right after a meeting while the conversation is still fresh but the notes are still messy.

Best input

Rough notes, partial transcript snippets, and any obvious decisions, owners, or due dates you already caught.

What to expect

A usable recap with summary, decisions, action items, open questions, and anything that still needs checking.

Gather this first

  • Your raw notes or transcript excerpt
  • Who attended or who needs the recap
  • Any decisions you believe were made
  • Any deadlines, owners, or follow-up items you heard

Ways to use it

simple workflow

1. Paste the notes exactly as they are
Do not clean them up first. Fragments and half-finished bullets are usually enough if the workflow knows what to pull out.

2. Ask for structure, not magic
Tell the model to separate summary, decisions, action items, and open questions so it does not blend everything together.

3. Flag uncertainty on purpose
Have the draft label anything unclear instead of pretending every owner or date is certain.

4. Review the action list first
Before you share the recap, confirm owners and dates because that is where mistakes matter most.

optional plugin or advanced install

npx upskill install meeting-notes-cleanup

Best for

  • Team meetings
  • Client calls
  • Project check-ins

Review before you send

  • Discussion points are not mislabeled as final decisions.
  • Each action item has an owner when the notes support it.
  • Unclear items are marked clearly instead of guessed.
  • The recap is short enough that someone will actually read it.

Common watchouts

  • Do not let the workflow invent owners or dates that are missing.
  • If the meeting was sensitive, remove any private notes before pasting.
  • If a decision matters, verify it against the recording or your own memory.

Changelog

1.3.02026-03-21

Made action items easier to spot for people sharing recaps right after a meeting.

1.2.12026-03-06

Improved handling for half-finished notes and bullet fragments.