Skip to content
TrackHeros

Guide

How to write meeting minutes: before, during and after a client call

A step-by-step guide to writing meeting minutes for freelancers and consultants who run client calls on Google Meet, Microsoft Teams or in a room: what to prepare before the call, what to capture while it runs, how to turn rough notes into minutes the same day, a worked example from a client call, and the mistakes that make minutes useless. Ends with how TrackHeros drafts them.

By · Updated 22 October 2026 · 7 min read

Meeting minutes are the short written record of a meeting that everyone in it can act on: who attended, what was decided, who will do what by when, and what is still open. This guide is for freelancers and consultants who write minutes for client calls on Google Meet, Microsoft Teams or in a room. It takes the job in order, before the call, during it and after it, then shows a worked example and the mistakes worth avoiding. For a blank document to copy, use the client meeting minutes template.

What are meeting minutes?

Meeting minutes are the agreed record of a meeting, written for everyone who attended and for people who did not. They are not a transcript, which records everything, and not your private notes, which record what you need. The difference between minutes and notes has its own page; the short version is that notes are for you and minutes are for both sides.

On a client project the minutes are also your evidence. In week eight, when someone asks why the export feature is not in the first release, the minutes from week two are the answer.

What should you do before the meeting?

Build the skeleton of the minutes before anyone joins, so that during the call you only fill gaps. Five minutes of preparation saves twenty afterwards.

  1. Open a new document named with the date, a client code and the topic, for example 2026-10-19 FINTECH weekly. Never reuse last week's file, and never one from another client.
  2. Copy the date, time, timezone and invited attendees from the calendar invitation.
  3. Turn each agenda item into a heading. If there is no agenda, write the one thing the meeting is for as the first heading and ask for other items in the first minute.
  4. Paste the open action items from the last minutes under a heading called "Carried over". Walking through them is the easiest part of the call.
  5. Decide who takes the minutes. If it is you and you are also running the meeting, read how to take notes while running the call.
  6. If you plan to record, say so in the invitation rather than in the first minute.

What do you write down during the meeting?

Four things and almost nothing else: decisions, action items, open questions, and exact figures. Everything else can be rebuilt from memory afterwards. Those four cannot.

Start each line with a letter so you can find them later: D for a decision, A for an action, Q for an open question, # for a figure or date, and a quotation mark for the client's own words. The note-taking guide has the full shorthand.

Two habits matter more than typing speed. When something sounds like a decision, say it back: "So we're keeping the go-live on 3 November, yes?" A decision nobody confirmed is a misunderstanding waiting to happen. Then, five minutes before the end, read the action items back, owner by owner. People correct a name or a date far more readily in the call than in an email the next day.

Before we go, the actions I have:
- Tom sends the staging credentials by Thursday.
- I send an estimate for partial refunds by Monday the 26th.
- Priya finds out who signs off the design, by Friday.
Anything missing, or anything I have wrong?

How do you turn rough notes into minutes?

Within the hour, in this order: decisions, then action items, then everything else. Decisions and actions are what the minutes are for, so they get your attention while the call is freshest.

  1. Copy every D line into the decisions section, one past-tense sentence each.
  2. Turn every A line into a row with one owner, an action that can be finished and a real date. Keep the spoken phrase where it might be argued about. How to write action items goes into this in detail.
  3. Turn every Q line into an open question with a name next to it.
  4. Write two or three lines under each agenda heading: what was covered and where it landed, not how the conversation went.
  5. Delete any heading with nothing under it.
  6. Check every name and figure against your # lines.
  7. Read it as the client's manager would: someone who was not there and has two minutes.

Then send it. The follow-up email guide has templates for the email it goes in.

What does a finished set of minutes look like?

Here is a thirty-minute weekly call with a fintech client about a payments integration. First, the rough notes as typed during the call.

2026-10-19 FINTECH weekly — Priya (PM), Tom (eng), me
carried: Tom staging creds -> not done, blocked on their IT
# webhook retries: 5 attempts, not 3
" refunds have to show in the dashboard the same day
D full refunds in phase 1, partial refunds phase 2
A me: estimate partial refunds, Mon
A Tom: staging creds, Thu (chasing IT)
Q who signs off design? Priya to find out
D go-live stays 3 Nov
? Tom mentioned a load test, not discussed

Then the minutes, sent forty minutes after the call.

# Minutes — Fintech client — Payments weekly

**Date:** Monday 19 October 2026, 10:00–10:30 (London), Google Meet
**Attendees:** Priya (product manager), Tom (engineer), Sam (developer)

## Summary

Full refunds stay in phase one and partial refunds move to phase two.
The 3 November go-live is unchanged. Staging access is still blocked
on the client's IT team.

## Decisions

1. Full refunds ship in phase one; partial refunds move to phase two.
2. Go-live stays on 3 November 2026.

## Action items

| Action                                | Owner | Due        |
| ------------------------------------- | ----- | ---------- |
| Send staging credentials (chasing IT) | Tom   | Thu 22 Oct |
| Send an estimate for partial refunds  | Sam   | Mon 26 Oct |
| Find out who signs off the design     | Priya | Fri 23 Oct |

## Open questions

- Is a load test needed before go-live? Raised by Tom, not discussed.
  On next week's agenda.

## Notes

- Webhook retries: the client wants five attempts rather than three.
- "Refunds have to show in the dashboard the same day" (Priya).

What changed between the two: the carried-over item became an action with a date. The "?" line became an open question rather than a decision, because nobody decided anything. The client's sentence about refunds kept its wording, because that sentence is a requirement. And nothing about how the conversation went survived.

What are the most common mistakes in meeting minutes?

Most bad minutes fail in one of a handful of ways, and each has a plain fix.

Mistake Why it hurts Fix
Writing a transcript Nobody reads it, and the decisions get lost Four things during the call, two or three lines per topic
Decisions buried in the discussion The reader cannot find what was agreed A decisions section, one sentence each
"We" or "the team" as an owner Nobody does it A person's name, or an open question
Relative dates "Next week" means something else when it is read A date, with the spoken words kept where they matter
Writing what you think was meant Minutes that say more than the meeting did Only what was said; ask when unsure
Recording who argued what Reads as blame when it is forwarded Record the outcome and who decided
Sending them days later Everyone acts on their own memory in the meantime Same day, within the hour if you can
Reusing a file from another client Another client's name in the wrong inbox A new file per meeting, with the client code in the name
No way to correct them Silence could mean agreement or that nobody read it End with a line inviting corrections by a set date

The last one is the cheapest to fix. "If I have missed or misstated anything, tell me by Wednesday" turns silence into agreement, and both sides know it. For decisions that keep being reopened, keep a decision log alongside the minutes.

How does TrackHeros write meeting minutes?

TrackHeros joins Google Meet and Microsoft Teams calls as a visible participant, records them, and writes a summary with a fixed shape: summary, decisions, discussion by topic, agenda (from the invitation, or reconstructed from the conversation and marked as such), milestones with dates, and action items. Each action item has an owner, as the name was heard, and is flagged if that person was not in the meeting; due dates are kept as spoken and resolved to a date. If the transcript could not be read reliably, the meeting page says so rather than showing an invented summary.

Each client has its own minutes template. Copy for email puts the minutes on your clipboard on every plan, and formal PDF minutes are on paid plans (pricing). Nothing is emailed to your client for you. The read-back and the final check in this guide apply to a draft from a machine as much as to your own notes. More on the minutes feature page.

Questions

Frequently asked

Who should take the minutes in a client meeting?

Whoever most needs the record to be right, which on a client project is usually the freelancer or consultant. If you are also running the meeting, say at the start that you are taking notes and keep them to short markers. On a large call, ask someone else to own the minutes and agree it before the meeting starts.

How long should meeting minutes be?

Shorter than most people write them. A one-hour client call usually fits on one page: a few lines of summary, the decisions, the action items and the open questions. A fifteen-minute check-in can be five lines. If the minutes take longer to read than the meeting took to hold, they have turned into a transcript.

Should meeting minutes record who said what?

Only where it matters: who made a decision, who owns an action, and whose words a requirement came from. Leave out who argued for which side. Minutes are forwarded to people who were not there, and an attributed disagreement reads as blame.

Do I need to record the meeting to write good minutes?

No. Good markers during the call and a write-up within the hour are enough for most meetings. A recording helps when figures, names or exact wording matter, but it has to be agreed with the people in the call, and the rules on recording differ by country and by contract.

Related

Early access

Get in early.

We’re onboarding a small group at a time so we can get it right. Join the list and we’ll reach out.

Get early accessEarly access · Google Meet and Microsoft Teams