Business workflow guide
ChatGPT dots meeting preparation: make a decision brief
AI-assisted guidance prepared for Blue Canvas from the official sources linked below. The examples are proposed workflows, not reports of firsthand product testing.
A useful meeting brief tells you what must be decided, what evidence is available and what remains unanswered. It should not turn every message into an agenda item or treat a suggestion as an agreed action. Start with one meeting and a small, approved source pack.
Name the outcome of the meeting
OpenAI's getting-started guidance recommends describing the responsibility, providing relevant sources and identifying decisions that need your input. A meeting brief is our proposed application of that approach, not a claim that dots automatically records meetings or produces an authoritative transcript.
For a fictional project review, the desired outcome might be deciding which of two workshop formats to develop. Write that down before collecting background. A request to 'summarise everything about the project' can bury the decision under material nobody needs on the day.
Specify the intended reader and how much detail they need. A chair's private preparation notes can include unresolved questions that should not be circulated as team commitments. Keep the draft private until its audience and wording have been reviewed.
Product source: OpenAI's official documentation, checked 31 October 2026.
Create a source pack with a cut-off
Choose the approved agenda, latest project brief and relevant decision notes. Identify versions and the cut-off time for the pack. If another document arrives later, label the resulting revision instead of quietly mixing two different states of the project.
Ask the task to list which supplied sources it actually read. A missing attachment or inaccessible note should remain a gap. Do not let an earlier conversation fill the hole without being identified and approved as a source.
Remove unnecessary personal information before starting. For an initial trial, use fictional project notes with no client names or private discussions. A realistic structure is enough to test whether the brief distinguishes evidence from assumptions.
| Source | Include | Check before relying on it |
|---|---|---|
| Agenda | Purpose and proposed decisions | Is this the current meeting? |
| Project brief | Requirements and constraints | Which revision was approved? |
| Decision notes | Earlier decisions with references | Was each point agreed or merely proposed? |
| Open questions | Unanswered items affecting the decision | Does the source name an owner or deadline? |
Structure the pack around decisions
Use a short opening section for the decision required. Follow it with relevant facts, competing options and unresolved questions. Keep background material below those sections so the reader can find the point of the meeting immediately.
For each option, ask what evidence favours it and what could change the recommendation. If the sources do not establish a cost, date or owner, write 'not confirmed'. A filled-in table is not inherently better than an honest empty field.
A useful agenda item has a question and an intended outcome. 'Workshop format' is a topic; 'choose a format for the next prototype' is a decision. Do not invent an agreement just because the document contains a strong recommendation from one contributor.
Try a review-only meeting prompt
Give the task permission to prepare the pack, not to manage the meeting. Calendar changes, invitations, messages and shared-document edits are outside this example. The first deliverable stays in the task conversation for you to inspect.
Ask for a separate missing-evidence section instead of a stream of speculative answers. That section can become your preparation checklist. It also helps you decide whether the meeting has enough information to make the intended decision.
Adapt this example to your approved task
Prepare a private decision brief for [fictional meeting and purpose]. Read only [approved source list and versions], with a cut-off of [date and time zone]. Return: decision required; confirmed facts with references; options and trade-offs; open questions; and missing sources. Distinguish proposals from recorded decisions. Do not invent owners, deadlines, costs or agreements. Do not send messages, create invitations, edit shared documents, record a meeting or set up recurring work. Return the draft here for review.
Review the brief without turning it into minutes
OpenAI distinguishes preparation from action: a request to draft does not authorise sending. Keep the meeting pack and any later circulation decision separate, including the exact audience.
Check every proposed decision against the sources. Look for tentative language that became certain in the summary, a question attributed to the wrong person or an obsolete deadline copied into the opening paragraph. Open the evidence for the most consequential points yourself.
After the meeting, the preparation pack is still a preparation pack. It is not evidence of what people actually agreed. Use authorised meeting notes as a new input for any follow-up draft, label the new document clearly and keep unconfirmed actions unconfirmed. No automatic transcription or attendance capability is assumed here.
Product source: OpenAI's official documentation, checked 31 October 2026.