Turn meeting notes into minutes and actions
Convert rough meeting notes into clean minutes with a decisions log and an owner-and-deadline action list.
Yours to copy, change, and make your own.
Replace every [BRACKETED PLACEHOLDER] with your own material before you send it.
You are a minute-taker for a professional organisation. Below are my rough notes from a meeting. Turn them into formal minutes. Structure the output as: 1. Meeting summary (2-3 sentences) 2. Decisions made (numbered list) 3. Actions (a table with columns: action, owner, deadline) 4. Points raised but not resolved Rules: - Only include things that appear in my notes. If an owner or deadline is missing for an action, write "not assigned" rather than inventing one. - Keep the wording neutral and factual. Remove hedging, jokes, and side conversations. - Use British English. Meeting: [MEETING NAME], held [DATE] Attendees: [ATTENDEES] Notes: [PASTE YOUR ROUGH NOTES]
- [MEETING NAME]
- What the meeting is called, for example "Marketing weekly" or "Q3 budget review".
- [DATE]
- The date the meeting took place.
- [ATTENDEES]
- Names or initials of the people present.
- [PASTE YOUR ROUGH NOTES]
- Your notes, as messy as they are. Bullet points, fragments, and shorthand are all fine.
Where it shines, and where it falls over.
- Regular team meetings and project stand-ups
- Committee and working-group meetings with clear agendas
- Turning a colleague's handover notes into a shareable record
- Type attendee initials next to each point as you take notes; the model will use them to assign action owners.
- If the meeting was recorded, paste the transcript instead of notes and add "the transcript may contain transcription errors, fix obvious ones".
The model can only work with what is in your notes. If your notes are too thin, the minutes will read confidently but say very little, and colleagues who attended will spot the gaps. It also cannot tell which of two conflicting statements won the argument unless your notes make that clear.
Be careful with anything contentious or personal. Minutes of disciplinary, HR, or legal discussions should not go through a public AI tool at all, and even routine minutes should be checked against your organisation's data policy before you paste in names.
AI output is a first draft, not a finished product. You are responsible for whatever you send, publish, or decide with it.
More prompts worth exploring.
Summarise a long report into a one-page board brief
Compress a long paper into a one-page brief a board member can read in three minutes, with risks and asks up front.
Draft a first version of an AI acceptable-use policy
Produce a workable first draft of an AI usage policy for your organisation, sized to your sector and risk appetite.
Rewrite a document in plain English
Take jargon-heavy text and rewrite it so a reader with no background can follow it, without losing the meaning.