Minutes of meeting sample: a filled example you can copy

A minutes of meeting sample is more useful filled in than blank. An empty template shows you the fields; a completed one shows you the register — how much detail a discussion line needs, how a decision is phrased so it is unambiguous later, and how an action is written so the owner cannot misread it.

Below is a worked example for an ordinary project meeting, followed by the rules it demonstrates.

The sample

• Meeting: Website relaunch — weekly. Date: 12 May 2026, 10:00–10:35. Location: video call.
• Present: A. Moreau (chair), P. Ibsen, R. Sørensen, L. Haugen. Apologies: T. Berg.
• Purpose: agree the launch date and resolve the outstanding content gap.
• Discussion — launch date: staging has been stable for two weeks; the remaining risk is content for the pricing page, which is with marketing. P. Ibsen noted the payment integration still needs a production test.
• Decision: launch on 3 June, conditional on the production payment test passing by 28 May.
• Discussion — pricing content: two drafts exist; neither has been reviewed by legal.
• Decision: the shorter draft goes forward; legal review is scheduled rather than optional.
• Actions: R. Sørensen — run the production payment test by 28 May. L. Haugen — send the shorter pricing draft to legal by 15 May. A. Moreau — confirm the launch date with support and sales by 20 May.
• Open question: whether the old pricing page redirects to the new one or to the homepage — P. Ibsen to check with SEO before 22 May.
• Next meeting: 19 May, 10:00. Purpose: confirm the payment test result.

Notice what the sample does not contain: who argued for what, how long the discussion took, and any wording that would embarrass someone if forwarded. Minutes record what the meeting decided, not how the participants behaved.

The rules the sample follows

• Decisions are written as statements in the past tense with a date attached — "launch on 3 June, conditional on…" rather than "we discussed launching in June".
• Every action has one owner and a deadline. Two owners means no owner.
• Conditions are recorded explicitly. A decision that depends on something is only useful if the dependency is written down.
• Discussion is two lines at most, and only where it explains the decision.
• Open questions get their own line with a name and a date, so they do not evaporate.
• The next meeting has a purpose, not just a slot. A recurring meeting with no purpose is the one nobody prepares for.

Turning the sample into a habit

1. Create the note before the meeting from the agenda, so the headings already exist.
2. During the meeting write only decisions and actions in full sentences; everything else in keywords.
3. Ask the chair to repeat the wording of anything that will be recorded as a decision — that request is normal, not an interruption.
4. Spend five minutes afterwards turning keywords into the two-line summaries and checking every action has an owner and a date.
5. Send the same day. Minutes that arrive within the hour still change what people do.
6. Reuse the same structure every time; recognisable minutes get read, novel formats get skimmed.

In Ettex Notes, meeting notes are one of the built-in templates, so the structure above is where you start rather than something you rebuild. Checklists inside the note turn actions into items with visible progress, tags keep a meeting series together, version history shows what changed after the review pass, and notes are local-first — a bad connection in a meeting room does not cost you the record. Export to Markdown or PDF when the minutes need to leave.

A useful minutes of meeting sample is one you can copy the register from, not just the headings. Decisions as statements, actions with names and dates, and everything else kept short.