Free tool · works now
Meeting Record Builder
Turn rough meeting notes into a record that keeps discussion, decisions, actions and open questions apart.
This is a website utility, not an app feature. It does not record audio, transcribe speech or join calls. It reorganises text you paste, in this tab, and uploads nothing.
625 characters of 40,000 allowed · 16 lines of 2,000 allowed
1 decision · 4 actions (1 with an owner, 1 with a pinned date) · 1 open question · 4 flagged lines
- Line 5: Same wording as line 12. Repeat mentions are not extra evidence. Keep one item.
- Line 6: No owner. It stays unknown until someone claims it.
- Line 7: No owner. It stays unknown until someone claims it.
- Line 7: A relative date is not pinned to the meeting date. Give it a calendar date or drop it.
- Line 12: No owner. It stays unknown until someone claims it.
- Line 12: Same wording as line 5. Repeat mentions are not extra evidence. Keep one item.
- Line 15: A marker inside a fenced block is treated as text, not structure.
## Decisions - Go with the black-and-white first printing. Agreed after Priya read the quote. (L4) ## Actions - Redo the cover grid; Owner: dana; Due: 2026-10-12; L5; note: Same wording as line 12. Repeat mentions are not extra evidence. Keep one item - Ask the printer about the volume discount; Owner: unknown; Due: no date yet; L6 - send Marco the index draft by friday; Owner: unknown; Due: no date yet; L7; note: A relative date is not pinned to the meeting date. Give it a calendar date or drop it - redo the cover grid; Owner: unknown; Due: no date yet; L12; note: Same wording as line 5. Repeat mentions are not extra evidence. Keep one item ## Open questions - Nobody knows the budget for a second print run (L8) ## Summary - 1 decision, 4 actions (1 with an owner, 1 with a pinned date), 1 open question. - 4 lines need a human check before you send this on. They carry a note inline. - Anything not marked above is discussion. Owners and dates stay unknown unless someone wrote them down. - Check (line 15): A marker inside a fenced block is treated as text, not structure
"Action","Owner","Due","Source line" "Redo the cover grid","dana","2026-10-12","L5" "Ask the printer about the volume discount","unknown","","L6" "send Marco the index draft by friday","unknown","","L7" "redo the cover grid","unknown","","L12"
Every cell is quoted. No cell needed a formula guard. The .csv download adds a byte-order mark so spreadsheets read accents and CJK correctly.
The line grammar
Four markers, one rule each. Everything the tool can decide, it decides from these rules, so the same notes always produce the same record.
| Line | Becomes |
|---|---|
! went with the B&W printing | A decision. |
+ redo the cover grid | @dana | by 2026-10-12 | An action with owner and date. |
+ ask the printer about the discount | An action. Nobody claimed it, so it says Owner: unknown. |
? nobody knows the second-run budget | An open question. |
| anything else | Discussion. Kept, never promoted. |
``` fenced blocks ``` | Inert text. Markers inside code or quotes stay text. |
Owners are written as @name (one word; put full names in the text). Dates are accepted only as by 2026-10-12 ordue 2026-10-12, and only when the date actually exists on a calendar.
What the checks mean
| Flag | What to do |
|---|---|
no-owner | An action has no name attached. It stays "Owner: unknown" until someone claims it. |
tentative | Words like might, maybe, defer or not decided sit on a decision or action line. Confirm before sending the record on. |
relative-date | Phrases like "by friday" or "next week" are not dates. Only an ISO date like 2026-10-12 is accepted. |
duplicate | The same wording appears twice. A repeat mention is not extra evidence; keep one item. |
marker-in-fence | A marker inside a fenced block stays text. Code and quoted examples never become decisions. |
unclosed-fence | A fence was never closed, so everything after it stayed discussion. Check the record. |
vague-ask | Someone, we or the team is assigned. Name one person or leave it a question. |
How to work with the output
- Paste your notes. If you never marked anything, that is fine; add markers to the lines that were decisions, actions and questions.
- Read the flags first. They are where your notes are not yet trustworthy.
- Fix the line, not the flag. Edit the text and the record rebuilds; the flags are a report, not a score to game.
- Spot-check two items against your raw notes. The export prints source line numbers for exactly this.
- Only then copy or download. Exporting is your decision, not a send button.
What this tool never does
- It does not record audio, transcribe speech or join calls. It works only with text you paste.
- It does not guess owners, dates or agreements. Unknown stays unknown, flagged for a human.
- It does not use AI. Every rule is the printed line grammar, so results are reproducible.
- It does not upload, share or keep your notes. Closing the page loses the text, on purpose.
Its limits, printed
It reads one paste at a time: 40,000 characters and 2,000 lines. It has no transcript support, no speaker turns, and no timestamps; a pasted transcript will read as one long discussion unless you mark it. Owner tokens cannot contain spaces. Duplicate detection is exact wording after normalization, not similarity. The record claims nothing about whether a marked decision was actually agreed; it only separates what you marked from what you did not. If you need that separation inside your notes app instead, the app keepsmeetings in the same Markdown note you are writing, for invited testers.
The template kit
The same method, in files, for people who prefer to keep it in their own editor. Copy freely, adapt freely, no attribution needed.
readme.mdWhat the files are and how to reuse them.meeting-record-template.mdThe blank record, fields that may stay empty marked unknown.example-notes.mdThe fictional sample meeting, raw.example-record.mdThe same notes as the tool builds them.example-actions.csvThe actions export, quoting and guards visible.
The example files are this tool's real output on the sample notes, regenerated from the same engine code the page runs (pnpm kit:meeting). The Markdown record you review above is exactly what the download button exports.
Questions
Related: recording a meeting in the app and the tool rules.
Do my notes get uploaded anywhere?
No. The record is built in your browser from the text you paste, and nothing is sent anywhere while you edit. This page loads a consent-gated visit counter; it records page views, not form contents. Close the tab and your text is gone, which is on purpose.
Can it summarise the meeting for me?
No, and that is the design. A model can hear maybe and write agreed. This tool applies only the printed line grammar: visible rules, flags on uncertain lines, and every gap left marked unknown.
Why does an action say Owner: unknown?
Because nobody wrote a name down. Add one with @name when you know who owes it, and leave it when you do not. A guessed owner in a sent record is worse than an empty field.
Does it understand “by friday”?
No. Relative wording is flagged, never converted. The only date it accepts is by or due followed by an ISO date like 2026-10-12, checked against a real calendar. A wrong guess is dated forever; a flag is fixable in one edit.
Is this the same thing the app does?
Related, not the same. The Mac app records calls and transcribes them on your machine, for invited testers. This tool needs none of that. It structures text you already have, for anyone, today, and it is a website utility, not an app feature.
What about the same action written twice?
Both lines get a duplicate flag naming the other line. Repeat mentions are not extra evidence. Merge them, or confirm both are real, before exporting.
Meetings that end in notes, not promises.
Free during the private beta. Apple silicon Macs, macOS 14 or later.