How to write an AI meeting brief people can check
Start with a filled pre-meeting brief, then learn how to connect its claims to evidence, handle conflicting sources and review it before the room relies on it.
Put this in the meeting invite: the choice, the evidence and what still needs an answer. Three headings are enough to start. Here is a worked brief for a release whose support coverage is still unsettled.
The brief, before the meeting
Should we release Thursday or wait until Tuesday?
Suppose you are arranging release coverage as well as the customer email. Adapt these sample inputs and replace the source labels with links your team can open.
- The call we need
- Choose Thursday with confirmed coverage, or Tuesday after the walkthrough. The founder makes the call at Wednesday's 10 a.m. meeting; I will update the customer email in Google Drive afterward. We need an answer before that email goes out, or customers could get a release date we cannot support.
- What we can verify
- The Linear release checklist shows the product checks complete. The Google Sheet for coverage names me for Thursday, but I have not accepted that shift: I am on a customer call then. A Slack reply still says ‘coverage sorted.’ The Google Doc walkthrough is scheduled for Monday. Sources to link: completed Linear checks; Thursday row in the Sheet; Slack reply; walkthrough plan.
- Options and open questions
- Thursday keeps the date in the draft email, if someone accepts the shift and the founder accepts the training gap. Tuesday allows the Monday walkthrough to happen first and requires the email date to change. Who will take Thursday's shift? Which questions would they be unable to answer before the walkthrough? I will bring those answers, or mark them missing, before the founder chooses.
Replace ‘I’ with your name when you adapt the brief. Keep the unconfirmed shift visible even if the Slack message sounds settled. The three headings give the meeting a specific choice to resolve without requiring a separate person to maintain a briefing process.
Check these two sentences before they travel
‘Support is ready for Thursday.’ That sentence turns a name in a spreadsheet into a commitment. Open the Thursday row and ask the person named there to confirm the shift. Until they do, write ‘Thursday coverage is unconfirmed.’ The Slack reply and the Sheet disagree; keep both links in the draft so the person checking it can resolve the conflict.
‘Tuesday is safer.’ This sentence quietly chooses for the founder. The sources establish that the walkthrough happens Monday; they do not establish how much risk it removes or what delaying costs. Write ‘Tuesday allows the planned walkthrough to finish; the customer email needs a new date.’ Ask the founder whether that trade-off is acceptable.
I would send the reviewed brief by 4 p.m. Tuesday for this Wednesday 10 a.m. meeting. That leaves time to challenge the shift assignment and ask a colleague about the training gap before everyone is in the room. For a same-day decision, aim for at least two hours beforehand and call out any answers still missing. Keep one linked Google Doc current; if you change a claim after sending it, flag the exact change in the meeting thread.
Build the next brief from the records you checked
Before asking an assistant for this brief, collect the release checks, coverage row, walkthrough plan and any conflicting decision. Put a date or version beside each link. Ask the people doing the work whether those records still apply. An edit yesterday might be a proposal; an older approved plan can still govern the release.
Give the assistant the three headings below, the approved sources and the intended audience. Ask for a source beside each claim, explicit gaps and no invented acceptance. Leave sensitive customer notes out of a wider meeting packet. Someone needs to check every resulting claim against the source before circulation.
Zeke can prepare a sourced brief from connected Google Drive documents after they have been scanned. For this example, put the checked facts and links into an appropriate Drive document; the Linear and Slack references alone do not give Zeke their contents. Updated documents need a new scan. A scheduled task can repeat the draft preparation, with a person reviewing the schedule and each draft. Scheduling does not refresh documents, continuously sync Drive or capture the entire Slack archive.
After the meeting, add the chosen date, reason and any condition to the same document. ‘Thursday, if someone accepts coverage by noon Wednesday’ still leaves work to do. Have the founder check that line and name who will update the email. A person approves any customer promise before it leaves the team.
If your problem is the Monday meeting itself, start with the weekly brief and decide which questions need a live discussion.