Skip to content
OperatorNest

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

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.

Illustrative example

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

Trigger
A qualifying external meeting appears on the calendar.
Cadence
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 leads with the decision, promise or question likely to come up. OperatorNest gathers the calendar event, threads and notes into a private brief. The scenario below is an illustration.

For example, request briefs for external meetings longer than 20 minutes, or only client and partner calls, with delivery the night before for document checks or ten minutes ahead for a refresher. Choose the lead time.

Check identity and chronology

Confirm the invitation’s name and address against the email thread or notes before adding private history. Common names can match several contacts. If identity is uncertain, leave the history out and say why.

Put events in order. A promise made six weeks ago may have been resolved in a later thread. Cite the latest relevant message, separate open and completed items, and show any conflict between notes and email. Keep the disagreement visible.

For Sam’s 2:00 meeting with Priya at Brackenwold Studio, put the last call note about a fast handoff beside the later email promising a revised timeline by Friday, then add the plan’s current status and a thread link so Sam can address both the priority and the promise. That’s the first five minutes.

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. Leave unchecked profile claims out or mark them 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

Keep internal notes, concerns and negotiation context in the channel you named. The attendee doesn’t receive the brief. If the operator drafts a follow-up after the meeting, show the exact message and recipient for your approval before it goes out.

When an attendee is added or the meeting moves, refresh the brief and label the version, leaving a receipt that names the event, threads and notes checked and the final delivery time so you can tell whether you’re reading preparation for the old invitation or the new one. Cancel the delivery if the meeting is canceled, and record that too.

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.

  • 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.

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.