Draft faster. Verify before sharing.
The meeting, names, and project below are fictional. No AI service is connected to this page.
From rough notes to a checked plan.
In the fictional Project Orion pilot meeting on 8 October 2026, the team agrees to use the existing signup form. Three tasks emerge, but two details are missing. A useful plan preserves those gaps instead of inventing them.
N2 · We agreed to use the existing signup form for the pilot.
N3 · Ada will draft the FAQ by 15 Oct 2026.
N4 · Ben will test the mobile signup flow. No date was agreed.
N5 · Send the pilot invite on 19 Oct 2026. No owner was named.
N6 · Open question: do we need legal review before the invite?
This is an excerpt of the downloadable fictional note set.
Decision
- Use the existing signup form for the pilot. (N2)
Open question
- Is legal review needed before the invite? (N6)
Action items
- Draft FAQ — Ada — 15 Oct 2026. (N3)
- Test mobile signup — Ben — Not specified. (N4)
- Send pilot invite — Not specified — 19 Oct 2026. (N5)
Every line is traceable to the source excerpt. The two unknown fields remain visible for follow-up.
A blank or guessed owner can make a task look assigned when it is not. Keep “Not specified” until a person confirms it.
Five steps from notes to a usable draft.
Choose notes you are allowed to process
Practice with the fictional sample first. For real meetings, check your organization’s rules, the AI service’s data settings, and any participant or client permission before uploading notes. Remove information you do not need for the task.
Ask for a structured extraction
Paste the reusable prompt and notes into your chosen AI tool. Ask for decisions, action items, open questions, and human review. Require a source line for each item; missing owners and dates must be Not specified, while ambiguous statements must be marked Needs verification.
Turn the meeting notes below into a DRAFT action plan. Rules: 1. Use only information explicitly stated in the notes. Do not invent decisions, commitments, owners, due dates, reasons, or priorities. 2. List a decision only when the notes say it was agreed or decided. 3. For each action item, include Task | Owner | Due date | Source line. If no owner or due date is stated, write exactly "Not specified" in that field. 4. List unanswered questions separately with their source lines. Do not convert a question into a decision or action. 5. If the source is ambiguous, mark the item "Needs verification" and explain what to check. 6. Finish with a short human-review checklist: compare every row with its cited line before sharing. Output sections: ## Decisions ## Action items ## Open questions ## Human review Meeting notes: [Paste the approved or fictional notes here]Separate decisions from discussion
“Use the existing signup form” is a decision in the sample. “Do we need legal review?” is an open question. If the notes say only that an option was considered, do not promote it to an agreement.
Verify each line against the source
Read the original notes beside the draft. For each output line, locate the cited source phrase, confirm the owner and date, and remove anything unsupported. In this example, Ben’s due date and the invite owner remain Not specified. Ask the team to fill those gaps rather than asking the model to guess.
Share a clearly labeled plan
Use the checked plan as a follow-up draft. Mark unresolved fields and open questions. Before sending, check the intended audience and make sure the wording does not turn a tentative idea into an assigned commitment.
Checks and common mistakes.
“Ben will test mobile signup” gives an owner, not a date. A tidy-looking date would be a fabricated commitment.
The pilot invite has a date but no named owner. Keep the owner open and ask for confirmation.
A plausible draft can still misstate the meeting. Compare every line to the original notes before sharing.