Start with a clear destination
The most useful meeting output is often a short record of decisions and next actions. A polished narrative may be pleasant to read but difficult to act on. Decide who needs the summary and what they should do with it. For a project team, a table of action, owner, due date, and unresolved question is a useful starting point.
Prepare the input
Use notes or a transcript you are permitted to process in your chosen tool. Remove unnecessary personal or confidential details. Add the meeting purpose and date if they are known. Identify the source as notes rather than a definitive record: a person may have missed a detail or captured a statement out of context. Keep the source available for verification.
Separate decisions from possibilities
Give the assistant explicit categories: confirmed decisions, assigned actions, proposals, and open questions. Require it to preserve uncertainty. “Friday might work” is not a Friday deadline. “We should ask Maya” is not a task Maya has accepted. Ask for an evidence excerpt alongside each action so you can trace the extraction back to the notes.
Review the important details
Read the output against the source. Confirm the spelling of owners’ names, the status of each decision, and whether dates were stated. Use “not assigned” or “not confirmed” where appropriate. If the notes disagree, flag the conflict rather than asking AI to choose a convenient answer. Have the people involved confirm consequential assignments.
Write the follow-up
Once the action table is reviewed, ask for a concise follow-up that leads with the decisions, lists next steps, and calls out questions requiring a reply. Check tone and recipients before sending. Keep sending as a separate human action while you are establishing the workflow. A correct summary sent to the wrong audience is still a failed process.
Measure whether it helps
Time the full process: preparing notes, generating the draft, reviewing, revising, and preparing the follow-up. Compare that with your normal process on a similar meeting. Record quality as well as speed. If the review takes longer because the tool keeps inventing assignments, improve the instruction or choose a simpler approach. Reuse the workflow only when it consistently helps.