How to Write Meeting Minutes (+ a Template)

Good meeting minutes capture six things: attendees, agenda items discussed, decisions made, action items with owners and due dates, any formal votes, and the time of adjournment. Write them in past tense, keep opinions out, and confirm each decision before you close. With a recording and a Lens, that same structure can be drafted for you and then reviewed by a person.

Minutes are a record, not a transcript. Nobody needs every sentence someone said. What people need weeks later is a clear answer to three questions: what did we decide, who owns the follow-up, and by when. The six-part structure below is the durable skeleton that serves almost any working meeting, from a weekly standup to a project kickoff.

Not every meeting needs all six with equal weight. A casual sync may skip votes entirely and treat adjournment as a formality. A board meeting leans hard on votes and precise timing. The point is that these are the slots to reach for, so nothing important quietly falls out of the record.

Here is a fillable template you can paste into any doc and reuse. It covers all six parts and adds a short header so the minutes are searchable later. Keep the labels; replace the bracketed prompts. This same layout doubles as an informal meeting minutes template if you delete the votes row and shorten the header.

The two rows that earn their keep are the decision row and the action-item row. If you only had thirty seconds to fill this in, you would fill those. Everything else is context that helps the decisions and actions make sense to someone who was not there.

Writing good minutes is less about typing speed and more about a small routine you run before, during, and after. The routine keeps you from drowning in real time and keeps the finished record honest.

1. Before: paste the template and pre-fill the header, attendees, and the agenda. Half your minutes can exist before anyone speaks.
2. During: capture decisions and action items the moment they land, not the whole conversation. Leave discussion summaries as short stubs you will flesh out later.
3. After: clean up the language, confirm owners and dates, and send within a day while memory is fresh.

The failure mode is waiting until the end to reconstruct what was decided. By then the exact wording has blurred and you are guessing at owners. Instead, catch each decision as it settles and immediately attach a name and a date to any resulting task. An action item without an owner is a wish; an action item without a due date never gets scheduled.

A useful habit is to say the action item out loud before moving on: "So that's Priya drafting the pricing doc by Friday." This does two things at once. It confirms the commitment with the room, and it gives you a clean, quotable line to write down. A running decisions and action items log built this way is worth more than pages of narrative.

Minutes lose value fast. Sent same-day, they reinforce commitments while people still remember agreeing to them. Sent a week later, they read like archaeology and half the owners have forgotten the context. Aim to tidy and distribute within 24 hours: fix the shorthand, verify each owner and date, cut anything that reads as opinion, and confirm the decisions match what people actually agreed to.

Most workplace minutes are informal: a summary of decisions and actions, written for the team, with a friendly tone. Formal minutes are a different animal. Board and governance minutes are a legal record of the organization's decisions and often must follow a prescribed format, record motions and votes verbatim, note who moved and seconded, and be adopted at the next meeting. The bar for precision is much higher.

Here is the tension nobody admits: you cannot chair a meeting and stenograph it at the same time. The moment you drop your head to type a decision, you miss the next point, the side comment that changes it, and the nod that means everyone agreed. If you are also running the meeting, the conflict is worse, because your attention is the thing keeping the discussion on track.

So people compromise. They scribble half-notes and reconstruct the rest afterward from memory, which is exactly when the record drifts from what actually happened. Owners get misremembered. A tentative "maybe we should" hardens into a decision that was never really made. The manual approach forces a choice between being present and having a record, and neither option is good.

There is a better shape for this. Instead of typing during the meeting, you record it and let the structure be drafted afterward. Reline records your meeting bot-free: it captures your microphone and the system audio locally on your machine, so no recorder joins the call and nothing shows up in the participant list. You stay fully present because you are not typing anything.

After the meeting, the recording is transcribed in the cloud and you point a Lens at it. A Lens is a reusable output format; Reline ships with a library of Lenses, around 15 built-in formats, including a Decisions Log and an Action Items list. Run the Decisions Log Lens and it drafts the settled outcomes; run the Action Items Lens and it drafts each task with its owner and due date, grounded in what was actually said. The six-part structure you started this post with, drafted for you.

Because everything is grounded in the recording, you can click any line in the draft and jump to that moment in the audio to check it. The transcript is timestamped, so verifying a decision takes seconds, not a re-listen of the whole call. That link between draft and source is what makes review fast enough to actually do.

Minutes are a record of truth, and that is precisely why a person has to sign off before they go out. AI-drafted minutes are a strong first draft, not a final one. Cloud AI can misattribute an action item, overstate a tentative comment as a firm decision, or miss a nuance in a heated exchange. If you send the draft unread, you are publishing a record you never verified.

• Confirm each decision is real, not a maybe that got promoted to a yes.
• Check every action item has the correct owner and a realistic due date.
• Watch for misattribution, since speaker labels are energy-based "Me vs Other", not named identification.
• Cut anything that reads as opinion or editorializing before you send.

The goal is not to trust the draft blindly. It is to move the human effort from stenography, which is slow and steals your attention, to review, which is fast and is where your judgment actually adds value. You spend two minutes verifying instead of the whole meeting typing, and the record is more accurate for it.

That is the whole trick. Keep the six-part structure as your standard, use the template so nothing falls out, capture the meeting instead of transcribing it, let a Lens draft the decisions log and action items, and then read it over before you hit send. You get clean, trustworthy minutes without trading away your presence in the room, and the format does the heavy lifting every single time.