To write meeting minutes, record the meeting’s date and purpose, the decisions people made, and the actions assigned with owners and deadlines. Do not try to reproduce every sentence. Minutes help someone understand what the group concluded and what happens next, including a person who could not attend. A brief record might say, “The group chose May 16 for the reading; Lee will reserve the room by April 3.” That is more useful than a long account of who suggested each date. Clear organization and headings make the record easier to scan. [1]
Decide what belongs in the record
Before the meeting, set up a document with the date, meeting name, purpose, attendees if needed, and headings for decisions and actions. You can also leave space for open questions. This structure keeps you from writing everything in chronological order and then struggling to find the important points afterward.
During discussion, capture the outcome and the minimum context needed to understand it. A decision may need a short reason if the reason affects later work: “Choose the library room because it is available on May 16.” Skip side comments that do not change the outcome, task, or shared understanding.
Write decisions as decisions
Use precise verbs such as approved, selected, postponed, or requested. “The date was discussed” tells a reader that conversation happened but not what the group decided. If the group made no decision, record that accurately: “The group postponed the venue choice until the access needs are confirmed.”
In an invented example, a planning group debates two dates for a spoken-word evening. The minute could read: “Decision: hold the event on May 16, pending room confirmation.” The phrase “pending room confirmation” preserves an important condition. Without it, a later reader might assume the venue was already secured.
Make action items usable
For each task, capture an owner and a deadline. “Reserve room” is incomplete if nobody knows who will do it or when. A stronger entry is: “Lee will request the library room by April 3.” If the group assigns a task to a role rather than a named person, identify the role and the process for choosing its owner.
If a deadline was not agreed, do not invent one. Write “deadline not set” or note who will propose a date. Keep unresolved questions separate from commitments so that readers do not mistake a suggestion for an assignment. Short, direct wording makes responsibilities visible at a glance.
Stay accurate without transcribing
Minutes are a record, not a performance review. Attribute a view to a person only when the attribution matters to the decision or follow-up. Otherwise, summarize the point neutrally: “Participants asked whether the courtyard would be accessible in rain.” Avoid describing a disagreement as consensus if the group left the issue open.
When a speaker’s wording is essential, use a short accurate note and make clear whose statement it was. For routine business, paraphrase. Purdue’s sentence guidance recommends clear references and active constructions where they make the actor easier to identify. [2] In minutes, “The group delayed the vote” is often clearer than “A delay was made to the vote.”
Review and circulate the record
Soon after the meeting, check names, dates, decisions, and action owners against your notes. Use headings such as “Decisions,” “Actions,” and “Open questions” so readers can locate information. W3C guidance notes that meaningful headings help users understand structure and navigate documents. [1] If a participant needs to correct a factual error, make the correction through the group’s usual process.
For the invented reading, the final notes might state: “Decision: May 16, pending room confirmation. Actions: Lee will request the library room by April 3; Sam will draft the event notice by April 5. Open question: Who will choose the readings?” A reader can see what is settled, what is assigned, and what still needs attention.
