A meeting minutes example you can copy and fill in today

Most meeting minutes examples online hand you a blank table and leave you guessing what good actually looks like. This one is filled in. Below you get a complete set of minutes for a real-feeling project meeting, a blank template to paste under it, and the short list of rules that decide whether anyone reopens the doc after the call.

The argument up front: minutes are not a transcript and they are not your private notes. They are the shared record of what was decided and who owns what next. A good set of minutes is short, names a person on every action, and gets sent the same day. Length and formatting matter far less than accuracy and speed.

A complete meeting minutes example (filled in)

Here is what finished minutes for a 30-minute internal project sync look like. Copy this block, then swap in your details. It is written to be readable by someone who missed the call.

MEETING MINUTES

Meeting:   Q3 Website Redesign, Weekly Sync
Date:      Thursday, June 12, 2026, 10:00 to 10:30 AM ET
Location:  Google Meet
Recorder:  Priya Nadar
Attendees: Priya Nadar, Devin Cole, Maria Ruiz, Sam Okafor
Absent:    Jordan Lee (PTO)

1. AGENDA
   - Homepage design review
   - Launch date decision
   - Content handoff

2. DECISIONS
   D1. Launch date moved to Mon Aug 4 (was Jul 28) to allow a full QA week.
   D2. Going with Design Option B for the homepage hero.
   D3. Blog migration is out of scope for v1; revisit in Q4.

3. DISCUSSION (brief)
   - Homepage: Option B tested better in the 5-user review. Devin
     raised mobile spacing concerns; agreed to fix in build, not redesign.
   - Launch: One QA week added after the staging bug found Tuesday.
   - Content: Marketing needs final copy 3 days before the dev freeze.

4. ACTION ITEMS
   #  Owner   Action (verb-led)                          Due          Status
   A1 Maria   Send final hero copy to Devin              Fri Jun 20   In progress
   A2 Devin   Build homepage from Option B               Wed Jun 25   Not started
   A3 Sam     Book the QA week with the test team        Mon Jun 16   Not started
   A4 Priya   Update the launch date in the roadmap      Fri Jun 13   Done

5. NEXT MEETING
   Thursday, June 19, 2026, 10:00 AM ET, Google Meet

Notice what is missing: there is no word-for-word account of who said what. The discussion section is three lines because that is all anyone needs in a week. The two parts people actually return to, decisions and action items, are pulled out and labeled so you can find them in two seconds.

The blank template to paste into your doc

Strip the example down and you get a reusable shell. Paste this into Google Docs, Notion, or Confluence and fill it during or right after the call.

MEETING MINUTES

Meeting:   [Name + recurring tag, e.g. "Weekly Sync"]
Date:      [Day, Month DD, YYYY, start to end time + zone]
Location:  [Google Meet / Zoom / Room name]
Recorder:  [Your name]
Attendees: [Names present]
Absent:    [Names + reason if known]

1. AGENDA
   - [Topic]
   - [Topic]

2. DECISIONS
   D1. [What the group decided, in one sentence]
   D2. [Decision] (was [prior state], if it changed)

3. DISCUSSION (brief)
   - [Topic]: [The one or two points worth keeping]

4. ACTION ITEMS
   #   Owner    Action (verb-led)            Due           Status
   A1  [Name]   [Verb] [the thing]           [Mon DD]      Not started
   A2  [Name]   [Verb] [the thing]           [Mon DD]      Not started

5. NEXT MEETING
   [Day, Date, time, zone, location]

If you prefer a spreadsheet for the action items so you can sort and filter them, give each field its own column: ID, Owner, Action, Due date, Status, Source meeting. Our action items template breaks down why those exact columns work, and the meeting recap format guide covers the email version you send afterward.

The fields that matter, and the ones you can drop

Formal minutes (boards, nonprofits, governing bodies) carry a fixed structure for a legal reason: they become the official record and may be approved as accurate at the next meeting. Robert's Rules of Order, the standard reference for parliamentary procedure first published in 1876, advises that minutes record what was done, not what was said. That single rule fixes most bad minutes. For the formal, governance-grade version, see our board meeting minutes guide.

For everyday work meetings, here is what to keep and what to cut.

Field	Keep it?	Why
Date, time, attendees	Always	This is what makes it a record, not a note.
Decisions	Always	The single highest-value line in any minutes.
Action items (owner + due)	Always	Without these, the meeting produced nothing.
Agenda	Usually	Frames the doc; lets readers scan.
Discussion summary	Briefly	Two lines per topic. Context, not transcript.
Verbatim quotes	Rarely	Only for formal votes or sensitive disputes.
Next meeting	If recurring	Saves a scheduling round-trip.

Minutes vs. transcript vs. recap: pick the right artifact

These three get confused constantly, and using the wrong one wastes everyone's time.

Meeting minutes

• What: Structured record of decisions + actions
• Length: Half a page
• Audience: Attendees + people who missed it
• When: Sent same day

Transcript

• What: Verbatim, every word, timestamped
• Length: Thousands of words
• Audience: Almost no one, by hand
• When: Generated automatically, kept as proof

A meeting recap is the third cousin: it is usually an email or message that wraps the minutes in a sentence of context and sends them to people. The minutes are the content; the recap is the delivery. If you want the email wording, the after-meeting email guide and the meeting recap format cover it.

How to write good minutes fast

The slow way is typing while half-listening, then cleaning it up later. Here is the faster path.

1. 1

   Paste the agenda before the call

   Drop the agenda into the template. Now you only fill, not build.

2. 2

   Capture decisions and actions live

   Ignore discussion until the end. Catch the two things that matter while they happen: what was decided, who owns what.

3. 3

   Let a recorder hold the verbatim

   If you record and transcribe the call, you can stop scribbling and stay in the conversation. The transcript is your safety net.

4. 4

   Trim discussion to two lines per topic

   After the call, summarize, do not transcribe. If a point does not change a decision or an action, cut it.

5. 5

   Send the same day

   Minutes lose half their value overnight. Send before you start the next thing.

The single biggest speed-up is not taking notes by hand at all. If a tool records the call and produces a transcript plus a draft summary, your job shifts from writing to editing, which is far faster. You read the auto-summary, fix the decisions, assign owners on the actions, and send. For Google Meet, an AI notetaker like Scribbl records and transcribes from your browser without a bot joining the call, then drafts a summary with action items you can edit down to the minutes above. (For Zoom and Teams, the Team plan covers those too.) That said, for a short stand-up where nothing is decided, skip the tooling and type four lines by hand; not every meeting needs minutes at all.

For more on the writing craft itself, see how to take better meeting notes and how to write an objective summary.

Frequently asked questions

What is the difference between meeting minutes and an agenda?

The agenda is the plan made before the meeting: the list of topics you intend to cover. The minutes are the record made during and after: what was actually discussed, decided, and assigned. A useful trick is to build your minutes on top of the agenda so each topic gets a decision and an action underneath it. See our project kickoff agenda for the front half of that pairing.

How long should meeting minutes be?

Shorter than you think. For most work meetings, half a page is plenty: a header, three to five decisions, a handful of action items, and a couple of lines of context per topic. If your minutes run multiple pages, you are writing a transcript, not minutes. Formal board minutes can run longer because they must record motions and votes precisely, but even those follow Robert's Rules advice to capture what was done, not the back-and-forth.

Do I need to record decisions word for word?

No, with one exception. For everyday meetings, paraphrase the decision in one clear sentence. For formal governance meetings, motions and the exact result of any vote should be recorded precisely, because the minutes become the official record. When you are unsure, recording and transcribing the call gives you a verbatim backup so your minutes can stay short without losing the source.

Who should write the meeting minutes?

Pick one designated recorder per meeting, named at the top of the doc. It should not be the person leading the discussion, since they cannot facilitate and capture at the same time. Many teams now let an AI note taker hold the verbatim record so the human recorder only has to edit the draft into clean minutes afterward.

Should I send the minutes or post them somewhere?

Both, ideally. Send a recap message the same day so the actions land in people's inboxes, and store the canonical minutes in a shared, searchable place (a project doc, wiki, or notes folder). The send drives action; the stored copy is what people search a month later when they ask "what did we decide about the launch date?"