What the Meeting Minutes Builder does
This builder lets you write minutes while the meeting runs and hands you a clean copy to send afterwards - as Markdown, as plain text for an email that eats formatting, as a printable page, or as calendar reminders for the actions. Type # to open an agenda item, > to record a decision and * to record an action with an owner and a date; everything else is a discussion note.
Nothing here writes for you. Every word in the output is your own text or a fixed label such as "Decision" or "Owner": there is no summarisation, no generated prose and no transcription, because minutes that nobody actually said are not minutes. What the page adds is structure and a set of checks - an action without an owner, a due date before the meeting, an agenda item with nothing recorded against it, an owner who was not in the room.
How to use it
- Fill in the meeting details: title, date, time, location, chair, minute taker, who was present and who sent apologies.
- Write the body as you go.
# Item titlestarts an agenda item, a plain line is a discussion note,> textrecords a decision, and* what | owner | 2026-09-25records an action. - Watch the checks on the right. An action with no owner is flagged as a problem while the meeting is still running, which is the only time it can be fixed.
- When the meeting ends, read the action table back to the room - that is what the format is for.
- Copy the Markdown, download the file, or generate .ics reminders for every dated action.
Reading the results
Decisions and actions are deliberately separate. A decision is something the meeting settled; an action is something a named person will do by a date. Minutes that blur the two are the usual reason nothing happens afterwards.
Action references are item.number, so action 2.1 is the first action under the second agenda item and stays traceable to the discussion that produced it.
"Owner not listed as present" is a warning, not an error. Assigning work to an absent colleague is normal - telling them is the part that gets forgotten, and the minutes should say who will.
The checks are structural. They cannot tell you whether the notes are accurate, and accuracy is the only thing that makes minutes worth keeping.
Worked example: a weekly operations meeting
Three agenda items. Under "Supplier delay on the packaging order" the note records that the October shipment slips by two weeks and that stock covers three weeks. The decision recorded is to split the order across two suppliers for Q4, and two actions follow: Sam Okafor to raise a purchase order with the second supplier by 25 September, and Tom Hayes to tell the warehouse about the new dates by 23 September.
The second item records the safety walk and one action to chase the loading bay light. The third records that nothing was raised - which is worth writing down, because an item with no note looks like an omission a month later.
The result: three items, one decision, three actions, two owners. Every action has an owner and a date, so the structural checks pass. The .ics download produces three all-day reminders, each with DTEND one day after the due date because RFC 5545 makes the end exclusive.
Had the warehouse action been typed without an owner, it would have been flagged in red while the meeting was still in the room - which is the entire point of writing minutes live rather than from memory on Friday.
Why the shorthand is three characters
Minute-takers are also participants. Anything that requires reaching for a mouse, opening a dialog or choosing from a dropdown does not get used during a real meeting, so the format is one character at the start of a line: # for an item, > for a decision, * for an action.
The action line takes the owner and date after pipes - * Rebook the support rota | Jas Sandhu | 2026-09-26 - because those are the two fields that decide whether anything happens, and leaving them to be added later means leaving them out.
What good minutes actually contain
Who was there and who was not; what was decided and by whom; what will be done, by whom, by when; and enough of the discussion to explain the decision to someone reading it in a year. Not a transcript - a transcript is what people ask for when they do not trust the minutes, and it fixes nothing.
The commonest failure is minutes that record discussion beautifully and decisions not at all. A month later nobody can tell whether the meeting agreed something or merely discussed it, and the same conversation happens again. Recording decisions separately makes that failure visible while it can still be corrected.
Limitations: what the result does not prove
- It does not transcribe, summarise or generate any text. It structures and checks what you type.
- It cannot verify accuracy. Structurally perfect minutes can still be wrong, and only the people who were there can confirm them.
- Nothing is stored. Close the tab and the minutes are gone, so copy or download them before you leave - there is no autosave and no draft recovery.
- It is not a governance record. Formal minutes for a board or a regulated body may need approval workflow, version control, signatures and retention that a browser page cannot provide.
Privacy: where your data goes
Everything you paste, type or drop is processed in this browser tab. It is not uploaded, logged, stored or sent to analytics. Session recording and tag-manager scripts are switched off on this page.
Standards and sources
- RFC 5545 - Internet Calendaring and Scheduling Core Object Specification - checked 19 Sep 2026
- ISO 15489-1:2016 - Records management: concepts and principles
Frequently asked questions
What should meeting minutes include?
The date, time and place; who attended and who sent apologies; each agenda item with enough discussion to explain what followed; the decisions reached, recorded separately; and every action with a named owner and a due date. Anything beyond that is usually padding, and a transcript is not minutes.
How do I record decisions and actions separately?
Start a decision line with > and an action line with *. A decision is what the meeting settled; an action is what one named person will do by one date. Keeping them apart is the single change that most improves whether meetings produce anything.
Can I send calendar reminders for the actions?
Yes - the .ics download creates one all-day event per dated action, with the owner in the description. It follows RFC 5545, so the end date is the day after the due date, which is how calendars represent an all-day event.
What if an action has no owner yet?
The page flags it in red immediately, which is the point: an action without a name is a wish, and the only moment it can be assigned is while everyone is still in the room. Record "to be confirmed by the chair" if nobody will take it, rather than leaving it blank.
Does this tool transcribe or summarise the meeting?
No, deliberately. There is no microphone, no transcription and no generated text - every sentence in the output is either yours or a fixed label. Minutes are a record of what people said they agreed, and inventing that text would make the record worthless.
Are minutes saved between visits?
No. There is no storage and no server, so a closed tab means lost notes. Copy the Markdown or download the file before you leave, and paste it back in if you need to edit later.
Should minutes name who said what?
Usually only for decisions, proposals and dissent. Attributing every remark turns minutes into a transcript and makes people cautious about speaking; attributing decisions and objections is what makes the record useful if the decision is later questioned.
Last reviewed by the A2Z.Tools team against the sources listed above.
