team
Most teams already have a meeting minutes template. It sits in a shared drive, someone fills it in during the call, and nobody opens it again. The template is rarely the problem on its own. The problem is that the document captures the conversation instead of the outcome, and then lives somewhere nobody passes on an ordinary Tuesday.
A template that survives contact with a real team does three things. It forces a decision to be written as a decision. It gives every follow-up a name and a date. And it sits close enough to the work that reading it costs less than asking someone what happened. This piece covers the fields worth keeping, a layout ready to copy, and the storage question that decides whether minutes get read at all.
There are two very different jobs hiding under the word minutes.
The first is the formal record. Board meetings, shareholder meetings, works councils and nonprofit boards keep minutes because a statute, a set of bylaws or an auditor requires them. Those minutes need attendance, quorum, the exact wording of motions, who moved and seconded, and the vote count. Requirements vary by country and by entity type, so the bylaws and local law decide the fields, not a blog post.
The second job is the working record for a team meeting. Nobody will audit it. Its only purpose is to answer four questions a week later: what was decided, what changed, who is doing what next, and what is still open. A template built for the first job is far too heavy for the second, and this is where most teams go wrong. They download a board minutes form, ask a project lead to fill in twelve fields for a thirty minute standup review, and the practice dies within a month.
Decide which job the template is doing before choosing fields. The rest of this article is about the second job, the working record, because that is the one being written every week.
A working template needs eight fields. Fewer and the record stops being useful. More and the note taker falls behind the conversation.
Meeting name and date. Use the same name every time so the records sort together. Add the date in a format that sorts correctly, such as 2026-09-22.
Attendees, and who was absent. The absent list matters more than the present list. It tells the reader who still needs to be told.
Purpose in one line. Written before the meeting, not after. If nobody can state the purpose, the meeting can usually be a message instead.
Decisions. One line each, phrased as a completed choice. "Ship the import screen on the 30th" is a decision. "Discussed the import screen" is not.
Open questions. Anything the room could not settle, with the person who will bring back the answer.
Action items. Each one needs a verb, an owner and a date. Actions without an owner belong to nobody, and actions without a date land in the same week as everything else.
Context worth keeping. One or two sentences of reasoning behind each decision. Not the transcript. Six months later the reason is the part that stops the same debate from restarting.
Next meeting. Date, and the one thing that has to be ready by then.
Notice what is absent from that list. There is no field for a chronological account of who said what. The narrative is the part that takes the longest to write and gets read the least.
The following structure works in a document, a wiki page or a card description without changes.
Meeting: Weekly delivery review Date: 2026-09-22 Attendees: A, B, C. Absent: D. Purpose: Decide the launch date for the import screen.
Decisions
Open questions
Action items
Context CSV only was chosen because the two pilot customers both export CSV, and image upload needs a storage decision that is not ready.
Next meeting: 2026-09-29. The migration answer has to be in before it starts.
Two details make this version work in practice. Decisions come before actions, because actions that do not trace back to a decision are usually someone's personal to-do list. And every action carries a date, even a rough one, so that the list can be sorted by urgency rather than by the order the conversation happened to take.
A template is only half the design. The other half is storage, and this is the part most teams never decide on purpose.
| Where minutes are stored | Strength | What breaks |
|---|---|---|
| Document file in a shared drive | Familiar, easy to format, easy to export | Hard to search across meetings, no link between an action item and the work it belongs to |
| Wiki or notes tool page | Searchable, version history, easy linking | Action items stay text, so due dates and owners are invisible unless someone copies them elsewhere |
| Chat thread | Zero friction to write | Scrolls away within days, and anyone joining later cannot reconstruct the decision |
| Card inside the project board | Action items become real tasks with owners and dates, and the record sits next to the work | Long formal minutes with strict formatting are a poor fit |
The pattern that holds up is splitting the two halves. The written record, decisions, context and open questions, goes to one durable page per meeting. The action items get created as tasks on the board the team already looks at, each linked back to that page. That way the follow-ups appear in the same place as the rest of the work, and the reasoning stays readable in one piece.
Tools that combine boards, calendar views and chat in one workspace make this split easier, because the record and the tasks do not end up in two products that never talk to each other. A feature list is worth reading with that specific question in mind: can a card hold the write-up, and can the action items be assigned and dated without leaving it.
One template for every meeting type leads to half-empty forms. Three narrow variations cover almost everything a small team runs.
The recurring team meeting. Drop the purpose line, since it is the same every week, and add a status line for anything already known to be late. Keep it to decisions, open questions and actions. Ten minutes of writing at most.
The decision meeting. Add two fields: the options that were considered and the reason the chosen one won. This is the variation worth the extra effort, because the rejected options are what stop the topic from being reopened every quarter.
The client or external meeting. Add what was promised out loud and by when, and note anything that changes scope or price. Send a short version to the client the same day, keep the internal version separate, and never merge the two documents.
For meetings that need a formal record, keep a fourth version that follows the bylaws exactly and store it where the auditor expects to find it. Mixing a statutory record into a weekly working note helps neither.
A template only pays off if it can be filled in live. Writing minutes from memory afterwards costs more time than the meeting saved, and the details that fade first are exactly the ones that matter, such as the reason a date moved.
Prepare the top of the document before the meeting starts. Meeting name, date, attendees and purpose can all be typed in advance, and the agenda can be pasted straight into the decisions section as empty headings. Starting from a half-filled page changes the note taker's job from writing to completing.
During the meeting, capture only two kinds of line. When the room settles something, type it under decisions in the present tense. When someone takes on work, type a line with a name and a date under action items. Everything else can wait. Resisting the urge to record the discussion is what keeps the note taker in the conversation rather than behind it.
Reserve the last five minutes to read the decisions and actions out loud. This single habit removes most of the disagreements that surface later, because the moment to correct a misheard date is while everyone is still in the room. It also exposes the meeting that produced no decisions at all, which is information worth having.
Two failure modes are worth naming. The first is the note taker who also owns half the agenda, which guarantees that either the notes or the argument suffers. Splitting those roles, even informally, fixes it. The second is minutes typed into a personal document and pasted somewhere shared afterwards, since the paste step gets skipped whenever the day is busy. Type directly into the place the record is going to live.
For recurring meetings, duplicate last week's record and clear the fields rather than starting from a blank template. The carried-over open questions and unfinished actions are the fastest agenda anyone can build, and the meeting starts with a review of what did not get done instead of a blank page.
Cutting fields is what makes minutes readable.
Leave out the transcript. If a recording or a transcript exists, link to it and write the decisions by hand. Automatic summaries are useful for recall, but they flatten a heated trade-off into a neutral sentence and lose the part worth keeping.
Leave out opinions attributed to individuals unless the person asked for it in the record. Minutes that read as a scoreboard make people cautious in the next meeting.
Leave out anything nobody will act on. A parking lot section that grows for eight weeks is a sign the item was never real. Delete it or turn it into a task with a date.
Leave out styling work. Colored headers and nested tables add time for the writer and nothing for the reader. Plain text with consistent field names beats a designed document, every time, because plain text is what searches well later.
Pick the one recurring meeting where follow-ups get lost most often, and change two things this week: write decisions as decisions, and create each action item as a task with an owner and a date instead of a bullet in a document. Keep the write-up wherever it already lives for now.
Once the action items live on the board the team actually opens, the minutes stop being an archive and start being the top of the work queue. Pinateca is one way to keep the write-up and its tasks in the same place, and the pricing page shows where the free tier ends if the plan is to try it with one meeting first.
Rotating the job around the team works better than assigning it permanently, because the person writing pays closer attention and everyone learns what a usable record looks like. The one person who should not write them is whoever is running the meeting, since chairing and note taking compete for the same attention.
For a working team meeting, one screen. If the record runs past that, it is usually carrying narrative that nobody will read. Formal minutes for a board or statutory meeting are a different matter and are as long as the bylaws require.
It replaces the transcript, not the record. Automatic summaries are good at recall and poor at stating what was actually decided and who owns the next step. The practical split is to let the tool keep the transcript and write the decisions and action items by hand.
The same day, ideally within an hour, while the wording of each decision is still fresh. A record that arrives three days later gets skimmed, and by then the people with actions have already started on their own interpretation.
Both, with one of them treated as the source. Keep the record in a single searchable place and send a short notice pointing to it, rather than mailing a file that then gets edited in someone's inbox copy.