Before each external meeting on [calendar], prepare a one-page brief [lead time] before the start. Use the event, relevant email threads, and notes in [location]. Confirm who is attending and the purpose. Include our last conversation, promises either side made, open questions, and one or two facts from linked public sources if relevant. Separate confirmed information from assumptions. If the event changes, update the brief. Send the brief only to me in [channel]. Do not share it with attendees or send a follow-up without my approval.
Meeting prep brief from calendar and conversation history
Prepare a short meeting brief with attendee context, past promises, open questions, and source links before an external call.
Copy-ready brief
Example output
Example brief for illustration only: Meeting: Sam with Priya at Brackenwold Studio, 14:00. Purpose: Review the revised onboarding timeline. History: Sam sent a proposal after the last call. Priya asked for a faster handoff and said timeline mattered more than the fee. [Prior email thread] Open item: Sam promised a revised plan by Friday; confirm it is ready before the call. Unknown: No current public update was verified for Brackenwold Studio. Status: Private brief delivered to Sam. No attendee contacted.
Trigger and cadence
- A qualifying external meeting appears on the calendar.
- Prepare the brief the evening before, or at a chosen lead time.
Inputs
- Calendar event, attendee identities, and meeting purpose.
- Relevant email threads, notes, and prior commitments.
- Public background sources when a first meeting needs context.
Steps
- Confirm the event, attendees, and start time.
- Read the relevant threads and notes for relationship history.
- Extract promises, open questions, and changed circumstances.
- Verify any public fact against its source.
- Deliver a one-page brief with links and unknowns.
Approval boundary
Preparing a private brief needs no send approval; sharing it or sending a follow-up does.
Stop conditions
- Attendee identity is ambiguous.
- The calendar event is canceled or materially changed.
- A sensitive note should not enter the brief's delivery channel.
Expected output
A one-page meeting brief with attendees, history, open items, and source references.
Receipt fields
- Event and attendee records checked.
- Threads, notes, public sources, delivery time, and any gaps.
Recovery when it fails
- Rebuild the brief if the meeting time or attendees change.
- Mark unverifiable background as unknown and keep the internal history separate.
On this page
Put the open question at the top
A meeting prep brief should tell you what decision, promise, or question is likely to come up when the call starts. It is more useful than a long biography of the attendee. OperatorNest can gather the calendar event, relevant threads, and notes, then prepare a private brief before the meeting. The scenario below is an illustration, not a live task record.
Start with a qualifying rule. You might request a brief for every external meeting longer than 20 minutes, or only for client and partner calls. Set the lead time to fit your schedule. A brief delivered the night before gives you time to fix a missing document; one sent ten minutes before the call serves as a quick refresher.
Check identity and chronology
The event invitation gives a name and address, but a common name may match several contacts. Confirm the attendee against the email thread or your notes before pulling private history into the brief. If the identity is uncertain, say so and leave that history out. A wrong relationship summary can be worse than no summary.
Put events in order. A promise made six weeks ago may have been resolved in a later thread. The brief should cite the latest relevant message and distinguish an open item from a completed one. If notes conflict with the email record, show the conflict rather than choosing whichever line seems more useful.
Say Sam meets Priya at Brackenwold Studio at 2:00. Sam’s last call note says Priya cares about a fast handoff. The later email says Sam will send a revised timeline by Friday. A concise brief puts those facts together: Priya’s priority, Sam’s promise, the current status of the revised plan, and a link to the thread. That is enough to guide the first five minutes of the call.
Use public background only when it helps
For a first meeting, a linked public page can establish the person’s current role or the company’s stated focus. For a repeat meeting, the shared history usually matters more. Do not fill the page with unverified claims from profiles or summaries. If a public source cannot be checked, leave the item out or mark it unknown.
The meeting prep use case covers the standing assistant. This workflow specifies the one-page output and the checks that keep it accurate.
Keep the brief private
Preparing a brief for you is different from sharing it with the attendee. The output may include internal notes, concerns, or negotiation context. Send it only to the channel you named. If the operator drafts a follow-up after the meeting, show the exact message and recipient for your approval before it goes out.
Calendar events change. When an attendee is added or the time moves, refresh the brief and label the version. If the meeting is canceled, stop the scheduled delivery and record that change. The receipt should show which event, threads, and notes were checked and when the final brief reached you.
Run it on a schedule
Plan the timing and missed-run behavior with the recurring task planner. For documented schedule controls across assistants, read scheduled AI tasks compared.
Related tools
- Meeting agenda generator
Build a timed agenda from your goal, attendees, meeting length, and notes. Get pre-reads, decisions, and a follow-up template in one draft.
- Meeting time zone planner
Compare working hours for people in different time zones, rank meeting slots for a chosen date, and copy an invite or shareable plan.
- AI task brief generator
Turn a rough request into a task brief with a goal, needed inputs, steps, approval points, receipt details, and a repeat schedule.
Common questions
What if an attendee has the same name as someone in my contacts?
Match the event address and thread context before using private history. If identity remains unclear, leave the history out and flag the ambiguity.
Does the brief need public research for every call?
No. For a repeat meeting, your own threads and notes may be enough. Add public background when it answers a relevant question.
What if the meeting is moved?
Recheck the event and refresh time-sensitive details before the new start. The receipt should show which version was delivered.
Keep reading
- An AI meeting prep assistant with the brief ready before you sit downIt builds a one-page brief on who you're meeting, your history with them, and open items, before every external call.
- Memory you can read, edit and deleteSee everything your operator remembers, correct it, export it or delete it, any time.
- A receipt for everything your operator doesEvery task keeps a receipt: what was asked, what ran, which model did it, what it cost, and every approval.
- An AI scheduling assistant that finds the time so you don't have toIt checks your availability, proposes times, handles the back-and-forth, and confirms the meeting once you approve.
Hand off your first task tonight.
Tell us your email and what you'd hand off first. We'll send your access details and help you set up your operator.