team
The hardest part of taking minutes is not writing. It is that the person taking them is also supposed to be in the meeting. Attention goes to the keyboard, a decision goes past, and the notes end up as a transcript of the first twenty minutes and a blank space over the part that mattered.
Almost every fix for this is really the same fix: record less. The volume of what gets typed is the problem, and the standard that governs formal minutes says so explicitly.
The reference used by most boards and formal bodies is unambiguous. Robert's Rules of Order states that summarising matters discussed at a meeting is not merely unnecessary, it is improper: minutes are a record of what was done at a meeting, not a record of what was said.
That single line removes most of the work. It means the back and forth about whether the launch should be the 14th or the 21st does not belong in the record. Only the outcome does. It means the phrase somebody used to describe a competitor, the anecdote about the last project, and the two minutes spent on a joke are all correctly omitted.
Informal team meetings are not bound by parliamentary procedure, and the principle still holds for a practical reason. Minutes are read by people who were not there and by people who were there but have forgotten. Both groups want the same four things:
That last item is the one most teams drop, and it is the one that causes the same topic to reappear for three consecutive weeks. A line reading that pricing was deferred until the finance numbers arrive on the 30th prevents an entire meeting.
Everything that is not one of those four things is discussion, and discussion is disposable.
Minutes taken from a blank page are a race. Minutes taken by filling in a prepared structure are typing.
The agenda is the skeleton. Ten minutes before the meeting, paste it into the document and turn each item into a heading with empty space underneath. Add the fixed fields at the top: the name of the group, the date and time, where it happened, who is present, who is absent, and who is chairing. Those fields take thirty seconds when nothing is happening and are irritating to reconstruct afterwards.
Under each agenda item, pre-write the labels that will be filled in:
Typing into a waiting label is dramatically faster than composing a sentence, and the labels do something more useful than saving keystrokes. An empty Decision field at the end of an agenda item is visible. It is a prompt to ask the question out loud: so what is being decided here. A minute taker who asks that question twice per meeting is worth more to the team than one who transcribes perfectly.
If the same meeting happens weekly, the skeleton becomes a template and the preparation drops to nothing. Carrying forward unfinished items from last time turns the document into a running ledger rather than a series of unrelated files.
Attendance and the name of the chair look like formalities until something is challenged. For any group that votes, the attendance line is also the quorum record, and quorum has a property that catches people out: once established, its continued presence is only presumed until somebody points out that it is gone. A point of order about a missing quorum generally does not affect prior action, but it can invalidate prior action where there is clear and convincing proof that no quorum was present when the business was transacted.
In other words, the list of who was in the room at the moment of a vote is the evidence that the vote counted. Noting arrivals and departures during a long meeting takes a few seconds each and is the only way that list stays true.
The working rule is to write only what would survive a challenge six months later.
For each item, that is the outcome and its owner. For anything formally voted on, it is the exact wording of the motion, who moved it, and the result. Numbers, dates, amounts and names get written down verbatim, because these are the details that get misremembered and they are the ones people come back to check.
Everything else can be handled with a shorthand that costs no attention:
Two habits matter more than any note taking technique. The first is confirming out loud. When a decision seems to have been made, saying the sentence back to the room, exactly as it will be written, takes five seconds and resolves the ambiguity while everyone is still present. Half of all bad minutes are not wrong, they are a faithful record of something the room never actually agreed on.
The second is refusing to fix wording during the meeting. Spelling, grammar and sentence structure are post meeting work. Fixing them live is the single biggest cause of missing the next decision.
Automatic transcription changes what the note taker does, but it does not remove the job. A transcript is a searchable archive of everything that was said, which is the opposite of minutes. It answers the question of who said what, several thousand words at a time.
The useful combination is a transcript running in the background and a human capturing only decisions and owners in the foreground. The transcript becomes the evidence layer, consulted when somebody disputes a detail. The minutes stay short enough that people read them. A transcript pasted into an assistant afterwards can also produce a first draft of the decisions, though somebody who was in the room still has to confirm that the draft matches what happened.
Speed matters more than polish here, and there is a useful outer bound from an unexpected place. The IRS Form 990 asks whether an organization contemporaneously documented the meetings held or written actions undertaken by its governing body, and the instructions define contemporaneous as the later of the next meeting of that body, or 60 days after the meeting.
Sixty days is a compliance floor rather than a target. For working teams, the practical window is closer to one day, because the parts of the notes that need reconstructing are exactly the parts that fade first: what the acronym stood for, which of the two proposals the phrase this one referred to, whether the deadline was the end of the week or the end of the month.
The write-up itself should take fifteen minutes. Remove the topic words that were shorthand for discussion. Turn each captured decision into one sentence in the past tense with a name and a date in it. Resolve the bracketed uncertainties by asking the one person who knows. Then circulate.
Circulating quickly also creates the correction loop. People who were in the meeting will notice an error within a day and will not notice it within a month. The minutes get better because they are read while the memory is still competitive.
For any group where minutes are a formal record, the approval process has a shape worth following even in an informal setting.
Draft minutes are submitted at the following meeting. If corrections are made at that point, they are made in the text of the minutes being approved, and the minutes of the current meeting simply record that the previous minutes were approved as corrected, without repeating what the correction was.
If an error is found after minutes have already been approved, the fix is not a quiet edit. Under Robert's Rules the correction is made through the motion to Amend Something Previously Adopted, the exact wording of that motion is entered in the minutes of the meeting where it was considered, and the secretary does not rewrite the original. A marginal notation points to the corrected text or to the meeting where the correction was adopted.
The principle behind that procedure is worth keeping even for a team using a shared document: an approved record is amended visibly, not overwritten silently. A document whose history can be rewritten is not a record, and version history in a file is a weaker answer than most people assume, because nobody reads it.
Minutes are a record, and records are passive. A commitment written in a document nobody opens between meetings is a commitment that exists only at the moment it is read aloud at the start of the next one.
This is the reason so many teams have excellent minutes and poor follow through. The document is correct. It is also closed. The owner of an action item has no reason to open last week's minutes on Wednesday morning, because their work lives somewhere else entirely.
The step that fixes it is mechanical. Every action item in the minutes becomes a task in the place the team already works, with the same owner and the same date, and a link back to the minutes for context. A board where the task carries its own owner and due date does the reminding that a document cannot. What stays in the minutes is the reasoning and the decision. What leaves is the commitment.
Where a transcript or a set of notes exists in text, this handoff no longer has to be typed out by hand either. Task tools that can be driven from ChatGPT or Claude will turn a list of decisions into cards with owners and dates, which removes the last excuse for the gap between the document and the work.
Prepare the skeleton before the next meeting and add the four labels under each agenda item, because an empty Decision field forces the question that makes minutes worth writing. Then move the action items out of the document and onto a board the same day, such as a free plan that covers a team of five. Minutes that nobody has to remember to reread are the only kind that change what happens next.
No. Robert's Rules of Order states that summarising matters discussed is improper, because minutes are a record of what was done rather than what was said. Record decisions, their owners, deadlines, and the exact wording of anything formally voted on.
Within a day is the practical target, because the details that need reconstructing fade fastest. As an outer bound, the IRS instructions for Form 990 treat documentation as contemporaneous if it exists by the later of the next meeting of the governing body or 60 days after the meeting.
Not a silent edit. The formal route is the motion to Amend Something Previously Adopted, recorded with its exact wording in the minutes of the meeting where it was raised. The original text stays, with a notation pointing to the correction.
It is possible in a small team and it degrades both jobs, because chairing requires watching the room and minute taking requires watching the record. Where there is no choice, preparing the skeleton in advance and confirming each decision out loud before typing it makes the combination survivable.
No. A transcript is everything that was said, which is the opposite of minutes. It works well as the evidence layer behind a short set of minutes, and it can be used to draft the decisions, but somebody who was present still has to confirm that the draft matches what the room agreed.