A client meeting minutes template for developers

Client meeting minutes are a short record that both sides can act on: who was there, what was discussed, what was decided, and who will do what by when. This guide gives developers a plain Markdown template to copy, explains what each section is for and how to write a decision and an action item, and covers sending the minutes the same day. It applies to calls on Google Meet and Microsoft Teams and to meetings in a room.

What are minutes for?

Minutes are not a transcript and they are not your private notes. A transcript records everything, which is why nobody reads it. Your notes record what you need, which is why nobody else can. Minutes sit between the two: the shortest document that lets someone who was not in the meeting understand what happened, and someone who was hold the other side to it.

That second job is the one that matters for developers. In week six, when the client asks why the dashboard is not in the first release, the minutes from week one say "Decision: API first, dashboard in phase two, agreed by both sides." Without them it is your memory against theirs, and theirs is paying.

What sections do the minutes need?

Section	What goes in it	Why it is there
Date, time, timezone	When the meeting happened, and where (Meet, Teams, in person)	Minutes get read months later, across timezones
Attendees and apologies	Names and roles; who was invited but absent	Decisions bind the people who were there
Agenda	The items, in the order they were meant to be covered	Shows what was planned, so what was skipped is visible
Discussion by topic	Two or three lines per topic: what was covered, what the client asked for	Context for the decisions, without the argument
Decisions	One sentence each, past tense	The part people search for later
Action items	Owner, action, due date, status	The part people are held to
Milestones	Named dates, and whether they moved	The project's calendar, in one place
Open questions	What nobody could answer, and who will	Stops unknowns being mistaken for decisions
Next meeting	Date, time, purpose	Saves an email

Attendees before agenda, decisions before action items, and open questions near the end where they will not be mistaken for anything firmer.

The template

Copy this into a file, or download it as client-meeting-minutes.md. It is plain Markdown, so it pastes into any notes app, renders in any repository, and converts to PDF with whatever you already use.

# Meeting minutes — [Client] — [Topic]

**Date:** [YYYY-MM-DD], [HH:MM–HH:MM] ([timezone])
**Where:** [Google Meet / Microsoft Teams / in person]
**Attendees:** [Name (role)], [Name (role)], [Name (role)]
**Apologies:** [Name (role)]
**Minutes by:** [Name]

## Agenda

1. [Item]
2. [Item]
3. [Item]

## Discussion

### [Topic 1]

- [What was covered, in two or three lines]
- [What the client asked for, in their words]

### [Topic 2]

- [What was covered]

## Decisions

1. [What was decided, and briefly why.]
2. [What was decided, and briefly why.]

## Action items

| #   | Action        | Owner  | Due          | Status |
| --- | ------------- | ------ | ------------ | ------ |
| 1   | [Verb + what] | [Name] | [YYYY-MM-DD] | Open   |
| 2   | [Verb + what] | [Name] | [YYYY-MM-DD] | Open   |

## Milestones

| Milestone | Date         | Notes                                        |
| --------- | ------------ | -------------------------------------------- |
| [Name]    | [YYYY-MM-DD] | [On track / at risk / moved from YYYY-MM-DD] |

## Open questions

- [Question] — [who will answer, by when]

## Next meeting

[YYYY-MM-DD], [HH:MM] ([timezone]) — [purpose]

Delete any section you did not use. An empty "Milestones" heading tells the reader you forgot, not that there were none.

How do you write a decision?

One sentence, past tense, with the reason if the reason will matter later. Name the alternative that was rejected when someone argued for it, because that is the person who will ask again.

Weak: "Discussed the database."

Better: "Decided to keep the existing relational database for phase one; the move to a managed cluster was deferred until load justifies it."

A decision does not carry a name unless the decision was to give someone a job, and then it is an action item. If you are not sure something was decided, it was not. Put it under open questions and ask.

How do you write an action item?

Every action item has the same shape:

[who] will [verb] [what] by [date].

"Sara will send the staging credentials by 2026-09-05." The owner is a person, not "the team" or "the client". The verb is something that can be finished: send, review, confirm, deploy, decide. The date is a date. When the meeting said "end of next week", keep those words in the notes and resolve them to a date in the table, because "end of next week" means one thing on Monday and another when the minutes are read the following Wednesday.

Heard in the meeting	Written in the minutes
"We'll get you the API docs soon"	Omar will send the payment API documentation by 2026-09-04
"Someone should look at the failing tests"	Karim will fix the failing checkout tests by 2026-09-03
"Let's revisit the timeline"	Open question: is the 15 October launch still realistic? Layla to confirm by 2026-09-08

If nobody owns it, it is not an action item. Ask in the meeting, and if there is still no owner, write it as an open question with a name next to it.

What should you leave out?

Who said what during the disagreement. The small talk. Your own opinion of the decision. Estimates you gave off the top of your head and are not ready to commit to; write "estimate to follow" instead. Anything you are unsure was said; check the recording or ask. And anything about another client, ever, even as a comparison.

Minutes are read by people who were not in the room and forwarded to people you have never met. Write for them.

How do you send the minutes?

Same day, and within the hour if you can. The value of minutes halves every day they are late, because people start acting on their own memory.

For a routine weekly call, put the minutes in the body of the email, not as an attachment. An attachment gets opened once; a body gets read on a phone in a corridor. Use the same subject line every time, "Minutes: [Client] [topic] [date]", so the thread is searchable on both sides.

Send a PDF when the meeting was formal: a kick-off, a scope change, a sign-off, anything a client will file or show to their own management. Attach it and paste the decisions and action items into the body as well.

End with one line: "If I have missed or misstated anything, tell me by Thursday and I will correct it." Silence after that is agreement, and both sides know it.

How TrackHeros does it

The summary TrackHeros writes after a meeting has 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 carries an owner and a due date. The owner is the speaker's name as heard, and if that name was not in the meeting the item is flagged for you to verify. Due dates are kept verbatim ("end of next week") and resolved to a date. If the transcript is unusable, the summary says so instead of inventing one.

The minutes are a real document with a per-client template: a heading, one of five colour themes (Slate, Navy, Forest, Plum, Amber) and a switch for every section, so a client who never wants to see the agenda never does. Empty sections are dropped. Export as PDF, or use "Copy for email", which puts HTML and plain text on the clipboard so the minutes paste into an email as formatted text with a plain-text fallback. More at /features/meeting-minutes/; the consultant's version of the same routine is at /for/consultants/, and the developer's at /for/freelance-developers/.