A meeting ends with useful ideas, a few decisions and several things someone needs to check. Your notes contain all three. By the time you turn them into a follow-up, it can be surprisingly easy to lose the difference.
“We could try that next month” becomes a plan. “Someone should contact the supplier” becomes a task with your colleague’s name beside it. A date mentioned during the discussion becomes a deadline nobody agreed to.
AI can help organise rough notes into a clearer draft. The important part is preserving what the meeting actually established. A well-written follow-up should make uncertainty visible enough for the people involved to resolve it.
Separate the conversation into four groups
Before asking for a polished email, ask the assistant to sort the notes:
- Decisions: what the group explicitly agreed.
- Actions: work someone agreed to do, with the owner and deadline only where the notes support them.
- Suggestions: ideas raised for consideration, without a recorded decision.
- Open questions: information or agreement still needed.
These groups give you something useful to check. You can compare each item with the original notes instead of reviewing a smooth paragraph that blends everything together.
If your notes are incomplete, a missing detail may have been agreed in the room. “Not recorded” is more accurate than “not agreed”. Check with the people involved rather than asking AI to fill the gap.
A small example: preparing a customer workshop
Imagine a fictional business planning a short customer workshop. The rough notes say:
Agreed: keep the current workshop price. Maya will ask the venue about availability. Saturday morning might work. Leon suggested a short demonstration video. Check whether the room includes a projector. No booking yet.
A useful first draft would preserve those limits:
- Decision: keep the current workshop price. The amount is not recorded in these notes.
- Action: Maya will ask the venue about availability. Deadline not recorded.
- Suggestions: Saturday morning as a possible time; a short demonstration video suggested by Leon.
- Open question recorded: does the room include a projector?
- Suggested clarification questions: who will check the projector question? Is any further approval needed before a booking is made?
Notice what stays out of the action list. The notes do not record Leon agreeing to make the video or anyone confirming Saturday. Maya’s recorded task is to ask about availability; the notes do not authorise her to book or pay for the room. The assistant can flag those gaps, but a confident sentence cannot settle them.
The questions about who will check and whether approval is needed are suggested clarifications, not recorded statements from the meeting. Label any questions AI adds so readers can distinguish them from what participants actually said.
Ask for a draft you can trace back to the notes
Try this prompt with a short, privacy-safe set of notes:
“Organise these meeting notes into decisions, agreed actions, suggestions and open questions. For each decision or action, include the wording in the notes that supports it. Include an owner or deadline only if the notes explicitly connect them to that action. Otherwise write ‘not recorded’. Keep tentative language such as ‘might’, ‘could’ and ‘suggested’. Put any clarification questions you propose in a separate section. Do not invent prices, dates, approvals or commitments. Then prepare a short follow-up draft for my review. Do not send it.”
The supporting wording makes checking easier. It does not guarantee that the assistant has interpreted the notes correctly. Compare its output with the original, especially where a sentence could commit someone’s time or your business’s money.
Use only information you are permitted to put into your chosen tool. Remove customer names, contact details, sensitive employee information and confidential terms that are unnecessary for the task. If the notes depend on protected information you cannot share, use a fictional example or do the sorting yourself.
Check the commitments before improving the tone
Read the draft once for factual accuracy before asking for a warmer or more professional version. Check names, dates, quantities and amounts against your own records. Then look for three common changes in meaning:
- A suggestion has become an agreed decision.
- A person who raised an idea has become responsible for delivering it.
- A date mentioned in conversation has become a firm deadline.
Ask whether each action is specific enough for the owner to recognise. “Follow up” is vague. “Ask the venue which Saturday mornings are available” is clearer, provided that is what was agreed. Keep unresolved details in the questions section instead of hiding them in the wording.
Once the substance is right, shorten the draft. A brief follow-up that shows the decision, next action and remaining question is often easier to use than a detailed account of the whole conversation.
Use confirmation to close the gaps
For the fictional workshop, the owner could review a message that says:
“We agreed to keep the current workshop price. Maya will ask the venue about availability; I haven’t recorded a deadline. Saturday morning and a short demonstration video are still suggestions. We still need to check whether the room includes a projector and who will find out. Please correct anything I’ve captured inaccurately and confirm the missing details before we make a booking.”
Send a follow-up only through your normal, authorised process. An unanswered message should not be treated as approval for a booking, purchase or new commitment. When people correct the summary, update the working record so the team is using the same version.
For today’s practice, take five lines of non-sensitive notes from one ordinary business discussion. Sort them into the four groups and check the result yourself. If you do not have suitable notes, write a fictional example like the one above.
Your useful result is a follow-up that makes the next step clear and leaves the right questions open for a person to answer.