Meeting minutes record the meeting’s business and outcomes in a form that readers can check later. For a project meeting, this often includes decisions and agreed actions. Formal bodies may have specific rules about what to record, approval and publication. Start with those rules and the organisation’s template rather than assuming that one format guarantees compliance or successful follow-through.
Understand what meeting minutes must include
Useful project-meeting fields include title, date, time, attendees, agenda references, decisions and actions. Record owners and deadlines when agreed; otherwise label them unassigned or not yet agreed. Formal minutes may need motion wording, voting results or other details under the applicable procedure. This is not a universal minimum checklist for every board, public body or workplace.
Establish whether you are writing project notes, action minutes or formal governance minutes. Some project formats include a short discussion summary. Under Robert’s Rules of Order, minutes generally record what was done rather than summarising members’ speeches; that guidance applies within the body’s governing framework. Do not impose either approach on every meeting. Keep allegations, proposals and adopted decisions distinct.
Use plain English and explicit references. “The team reviewed the budget variance” identifies the actor and topic more clearly than “It was discussed.” Replace ASAP with an agreed date only if the meeting actually agreed one; otherwise write “Due date to be confirmed.” A stable format helps readers locate decisions and actions.
Prepare before the meeting starts
Before the meeting, review the agenda, relevant papers, previous approved minutes and the organisation’s instructions. Prepare headings and check names and terms. You may mark space for a proposed decision, but leave it unconfirmed until the meeting takes that decision. Do not prefill an expected outcome as an approved one.
Prepare terminology carefully if English is not the first language of all participants. Confirm the correct spelling of names, departments, project codes, and specialized terms. For example, a product team discussing SOC 2, ISO 27001, EBITDA, or procurement thresholds should use those terms accurately in the minutes. Small spelling errors can make records look unprofessional and can also harm findability when someone searches internal systems later. If the meeting uses recurring metrics, create a glossary or reusable list of approved terms. This is especially useful in multinational organizations where one concept may be described differently by finance, legal, and operations teams.
Choose a note-taking method that lets you separate decisions, actions and unresolved questions. If recording is permitted, follow the applicable policy and consent process, including who may access it and how it is retained. A recording can help check wording, but a transcript or automated summary still needs checking against what was actually agreed. There is no universal rule that one method is always faster or more accurate.
Write in clear, neutral, professional English
Use tense to preserve the sequence of events and follow the organisation’s style. “The committee approved the policy” records an approval that occurred; “The committee agreed to consider the policy in July” records a future consideration, not approval. A shorter sentence is useful only if it keeps the same decision and timing. Do not turn “would be revised and approved” into “approved” merely to simplify the wording.
Use neutral wording without erasing relevant facts. “The proposal was returned for further analysis” records an outcome, while “a poor explanation” adds the writer’s judgement. Record dissent, concerns or responsibility when the applicable procedure requires them. Neutral language alone does not guarantee legal protection or make an incomplete record adequate.
Identify an action owner at the level actually agreed. “Operations will submit the revised forecast by 12 May” is appropriate if the department accepted it; name an individual only if that responsibility was assigned. Ask for clarification during the meeting when possible. Do not invent a person or a deadline to fill an empty field.
Capture decisions, actions, and deadlines precisely
Separate an adopted decision from a proposal or recommendation. State the action, owner, due date and dependency when these were agreed. If no decision was reached, say so. The table below contains hypothetical examples with additional details supplied for illustration; the clearer versions are not faithful rewrites unless those details are supported by the meeting record.
| Element | Weak wording | Clear wording |
|---|---|---|
| Decision | The proposal was discussed and accepted. | The leadership team approved the supplier proposal for Q3 onboarding. |
| Action | Finance to follow up soon. | Finance will send the revised budget to all attendees by 18 April. |
| Risk | There may be timeline issues. | The launch may slip by two weeks due to vendor testing delays. |
| Open issue | More discussion is needed. | The team deferred the office relocation decision pending legal review. |
Add a precise reference to a relevant paper when useful, such as a document title and version. Check who should have access before linking or distributing it. If an agreed action is copied into a task system, keep the original wording, owner and due date consistent; a software feature does not establish that the action was authorised.
Record unresolved issues without inventing a next step. “Approval was postponed pending HR headcount data” is different from “HR will supply the data by 22 June.” Include the latter commitment only if it was made. If it was not, record the required information and that an owner or date remains to be confirmed.
Edit promptly and distribute in a usable format
Draft promptly while your notes and supporting papers are available, but follow the agreed review timetable. A 24-hour turnaround may be useful for a particular team; it is not a universal rule. Label the document Draft or Unconfirmed as appropriate, and distinguish chair review from formal approval where the organisation’s procedure does so.
Check names, dates, figures, decisions, action owners and status against the meeting record. Note an agenda item as deferred only if it was deferred, not merely because your notes are incomplete. A spelling or grammar checker can help with wording, but cannot establish whether a motion passed or a due date was agreed.
Use a clear title, date, version and status, and circulate through the organisation’s approved process to the intended recipients. A review deadline does not automatically mean minutes are approved when nobody replies. Keep a clear distinction between a working draft and the approved record. Correct an approved record through the applicable procedure and preserve the correction trail rather than silently overwriting it.
Frequently Asked Questions
What should be included in clear and informative meeting minutes?
For a project meeting, record the basic meeting details, decisions and agreed actions in the organisation’s format. Include an action owner or deadline when agreed, and mark what remains unresolved. For formal governance minutes, follow the body’s rules about motion wording, votes, discussion and approval rather than treating a general workplace checklist as sufficient.
Separate proposals, decisions and actions. A proposal discussed at a meeting has not necessarily been approved. A useful action line identifies an agreed task and owner, with a due date if one was set; an unknown field should remain explicitly unconfirmed.
How are meeting minutes different from a transcript?
A transcript attempts to reproduce spoken words; minutes record the business in the required format. Project notes may include concise discussion context, while a body following Robert’s Rules generally records what was done rather than members’ speeches. Follow the governing procedure instead of assuming that every set of minutes needs a discussion summary.
Do not turn a conversation into an apparent decision simply by shortening it. Record an approval only when it occurred, and preserve uncertainty or deferral where appropriate. If the outcome is unclear, verify it with the responsible meeting officer before presenting the draft as an accurate record.
How can I make meeting minutes easier to understand in English?
Use short, precise sentences and distinguish verbs carefully: reviewed means examined; recommended proposes a course; approved records a decision; deferred postpones it. These are not interchangeable ways to make a sentence sound more definite.
Use the organisation’s agenda or topic structure. Show decisions and agreed actions clearly and verify the facts as well as the readability. A document can be easy to read while still recording an incorrect date or outcome.
What is the best way to record decisions and action items in meeting minutes?
Record the actual decision and any required motion wording. For actions, include the agreed task, owner and deadline; label a missing owner or date as unconfirmed. Do not change “There was discussion about possibly moving the launch” to “The team approved 15 June” unless the team actually approved that date.
A hypothetical action line might read “Action: Maria to circulate the updated proposal by Friday, 20 November 2026.” Use a full date where a relative date could become ambiguous. The name and deadline in this example are illustrations, not details to add to a real meeting unless they were agreed.
When should meeting minutes be reviewed and shared after a meeting?
Use the review timetable set for the meeting. Draft promptly where possible, but do not treat 24 hours as a universal approval or circulation deadline. UCAS’s own style guide, for example, specifies a different timetable for chair review; an organisation-specific example is not a rule for all workplaces.
Before circulation, verify content, status, intended recipients and any access restrictions. Obtain the review or approval required by the organisation, and label the document accordingly. Preserve a version or correction trail so readers can distinguish a draft from the approved record and any later correction.
Minute-taking references
Compare the official Robert’s Rules FAQs, Michigan State University’s governance guidance and the UCAS style guide. These describe particular procedures and styles; apply the rules governing your own meeting.
