Turn meeting talk into a written document

Strip the repetition and jumps from spoken remarks and leave written decisions people can act on

You are a meeting-notes editor. Turn the spoken remarks below into a written document: 1) open with three lines stating what was decided, who owns it, and by when; 2) organize the body as context, discussion, decision, and action items, not in speaking order; 3) remove filler, repetition, and unfinished sentences without changing the speaker's position; 4) flag vague phrasing such as 'roughly' or 'we'll revisit' and convert it into a question that needs an answer. Do not invent anything that was not said.

[paste the transcript or your notes]

How to use

Read the first three lines first. If the decision, owner, or date is missing, a smooth body still cannot be acted on.

Good for

The discussion wandered, but the notes have to go into Slack today so people who were not there know what was decided and whether they need to act.
One key commitment is buried inside three tangents; you want it lifted out as a trackable action item instead of sitting in paragraph five.

Not for

The meeting is still running and no decision exists yet: writing it up now turns exploratory talk into a decision; keep raw notes instead.
The content is a sensitive personnel or negotiation conversation where tone carries the concession: cleaning it into written language erases those signals, so keep the original words.

Example

Input

I think the direction is fine, the schedule probably needs another look. I'll spin up a small group, maybe next week, and we can lock the API part first.

What you get

The opening three lines read 'Decided: direction approved / Owner: the speaker / When: next week, exact date to confirm', and 'maybe' is flagged rather than resolved. The body keeps only the API-schedule discussion, drops the filler, and does not commit the speaker to a date.

Common mistakes

Turning 'we'll revisit' into 'due next week': that makes a decision on the speaker's behalf, and once a written document is sent it reads as a commitment.
Adding 'and polish it into something professional': written polish smooths away hesitation and reservations, which are often the most important thing the meeting produced.

Try tweaking it like this

Change the three opening lines to five, covering decision, owner, deadline, risk, and next checkpoint, for a recurring project meeting rather than a one-off discussion.
Add 'keep three of the most informative sentences verbatim' when the record may need to show exactly what position someone took.