Turn messy meeting notes into action (and a follow-up that lands)
Most of a client meeting's value evaporates in the 24 hours after it. Everyone leaves nodding, nobody writes anything down, and a week later two people remember two different versions of what was agreed. The freelancers who look the most professional aren't the ones who talk best in the room — they're the ones who send the tight follow-up that afternoon.
Here's how to turn a page of messy notes into a summary, an owned action list, and an email that protects you and moves the work forward.
Separate decisions from discussion
Your notes are a soup of tangents, ideas, and half-agreements. The first job is to pull out what was actually decided. Everything else is context — keep it brief or drop it.
Turn every "we should" into an owned action
An action item without an owner and a date is a wish. Every task needs a name attached and a when — including the client's tasks, because half of what blocks your work is something they owe you.
Put assumptions and scope notes on the record
The follow-up is your cheapest insurance. If something felt like it might expand the scope, or you're proceeding on an assumption, write it down now — kindly and plainly. It's much easier to correct on day one than to argue in week six.
Write the summary as if you'll both re-read it
Two lines at the top: what we decided, what happens next. A short table or list of action items below. That's it. Nobody re-reads a wall of text; everybody re-reads three tight bullets.
Send it within 24 hours
Recall and goodwill both decay fast. A good-enough summary sent the same afternoon beats a perfect one sent three days later. Speed is the professionalism here.
Hate writing these up? That's exactly what the /meeting skill is for: paste your messy notes or a transcript and get back a clean summary, an action-item table with owners, and a ready-to-send follow-up email. It's one of the 7 skills in the pack.
Why the follow-up is the real deliverable
Clients rarely remember the meeting. They remember the email that came after it — the one that made them feel organized, on the same page, and in good hands. A tight recap does three jobs at once: it prevents "I thought you said" disputes, it catches scope drift while it's still cheap to fix, and it quietly signals that working with you is easy. That signal is often what turns a one-off gig into a repeat client.
Turning a messy transcript into a clean summary + action items + a follow-up email is exactly the kind of admin that eats an afternoon. Hand it to a Claude Code skill instead — that's /meeting, one of 7 in the Freelancer Pack.
See the Freelancer Pack — $27Common questions
What goes in the follow-up? A two-line summary, an action list with owners and dates, any scope/assumption notes, and one clear next step.
How fast should I send it? Within 24 hours — same day if you can. Recall and goodwill decay fast.
Do I include the client's tasks? Yes. Half of what blocks your work is something they owe you — put it in writing with a date.