Raw meeting notes have one job and usually fail at it: a week later, nobody can tell what was decided, who owes what, or whether the argument on page two ever settled. The fix is not a better note-taking app. It is asking the model for minutes, a specific document with a summary, a decision list and an action table, instead of asking it to "summarize these notes" and accepting the paragraph it hands back. Below is one full prompt that does it, a short version for recurring meetings, and a worked example so you can see the shape before you trust it with real notes.
The full prompt
Act as an experienced team assistant who writes meeting minutes that people actually use. Task: Turn my raw notes from the meeting below into structured minutes a colleague who missed the meeting can act on. Meeting: [TITLE]. Date: [DATE]. Attendees: [NAMES]. My raw notes: [PASTE NOTES OR TRANSCRIPT]. Output, in this order: 1. Summary: two or three sentences, the purpose of the meeting and what it settled. 2. Decisions: a list of what was decided, one line each. Only decisions my notes actually record. 3. Action items: a table with columns Task, Owner, Due. Take owners and dates only from my notes; where either is missing, write TBD, never a guess. 4. Open questions: anything discussed but not settled, one line each, with who raised it if my notes say. Rules: - Use only my notes. Do not add context, names, numbers or deadlines that are not in them. - Where my notes are ambiguous about whether something was decided or only proposed, put it under Open questions and mark it [UNCLEAR]. - Plain, neutral, third-person language. No opinions about the meeting or the people in it. - Keep the whole document under [600] words unless my notes run long.
Three parts of that prompt earn their place. The output order forces decisions ahead of discussion, which is the order readers need. The TBD rule stops the most dangerous failure in AI minutes, the invented deadline, which looks exactly like a real one in a tidy table. And the [UNCLEAR] marker turns the model's uncertainty into a question for the room instead of a quiet rewrite of history.
The short version, for the weekly meeting
Turn these notes from [MEETING NAME, DATE] into: a two-sentence summary, a decision list, and an action table (Task, Owner, Due, with TBD where my notes do not say). Use only the notes; mark anything ambiguous [UNCLEAR]. Notes: [PASTE].
Recurring meetings are where minutes pay off fastest, because the action table becomes the next meeting's first agenda item. Keep the short prompt saved wherever you take notes and the habit costs you one paste a week.
A worked example
Sample notes, invented for this page: "Budget review, Tue. Priya: hosting quote came in high. Marco to get second quote by Friday. Agreed to move launch checklist review to next week. Ana asked whether the trial includes support, nobody knew. Decided: freeze new tool purchases until quotes land."

The prompt turns that into a two-sentence summary (the review covered the hosting quote and agreed a purchase freeze), a decision list with the freeze and the moved checklist review, an action table with one row, Marco, second hosting quote, Friday, and an open question, whether the trial includes support, marked as Ana's. Nothing in the output is not in the notes, and the unknown stayed unknown, which is the whole test.
Adjusting it by meeting type
One-to-ones. Drop the summary to one sentence and add a fifth section, commitments from last time, checked against the notes you paste. Client meetings. Add a rule that agreed prices, dates and deliverables are quoted exactly as noted, since paraphrased numbers cause real disputes. Brainstorms. Replace Decisions with Ideas kept, and ban the action table unless owners were actually named; a brainstorm's output is options, not assignments. Standups. The short version is enough, and most weeks the honest output is an action table and nothing else.
What it does not do
It does not know what your notes left out. A decision made in the corridor afterwards, a name misheard by the transcription tool, a deadline mentioned but not written down: the prompt cannot recover any of it, and its confidence will not warn you. Read the minutes once before they circulate, especially the action table. Two minutes of checking is the price, and it is cheaper than one invented deadline reaching a client's inbox.
Where PromptPolish fits
PromptPolish has a meeting family, and its built-in requirements read like a compressed version of this page: structure the output as purpose, decisions needed, discussion points, then action items, and give every action item an owner and a due date, writing TBD where you have not supplied one. Its family is aimed at preparing agendas and notes rather than digesting a finished transcript, so for raw notes the full prompt above is the tool. For the agenda that starts the next meeting, the builder assembles the same structure in seconds; the explainer shows how, and two generations a day are free.
Minutes are a memory the whole team shares. A prompt that refuses to invent is what makes that memory safe to trust.