agent sidequestsIdeas worth trying

AI meeting preparation: turn old notes into a current brief

To prepare for a meeting with AI, supply the current invitation, relevant notes and the latest explicit agreements. Ask for a short private brief showing what changed, what is still open and which decision you need. Check the people and the exact meeting occurrence before trusting the summary. The worked example below repairs a plausible brief that gets all three wrong.

What should a pre-meeting brief help you do?

You should be able to enter the conversation knowing who you are meeting, what you last agreed, what changed and what you need to resolve. Start with one consequential conversation, such as a collaborator check-in or a venue planning call. A day-wide list of priorities serves a different purpose.

Ben Legg’s October 20 calendar-assistant writeup describes preparing meetings from calendars, email and notes. His displayed sample has changed names and details, plus an added diary check. This is a first-person account on his advisory business’s site; we did not reproduce it or verify the claimed time savings.

Day AI’s meeting-prep guide discusses stale source exports and mistaken attendee matching. It is vendor material, not an independent comparison. Our contribution is the repair exercise below: trace each line back to a small input packet, reject unrelated history, and produce two different documents for two different audiences. The exercise is fictional and untested.

Bring the invitation and the evidence that could change the conversation

Supply the current event, your desired decision, the relevant previous note, and subsequent messages that change or clarify it. Keep a date and a reopenable link or filename for each source. Include the particular attachment the discussion depends on. A file listed in an email is not a file the agent has read.

Use selected material you are allowed to share. For Muse, Instinct, Dots or Grok Bot, check whether your account can read those files or connected sources. Pasted excerpts are enough for the first pass. Mark their cutoff time; do not claim the agent checked today’s live calendar when you supplied yesterday’s export.

Match people using the current invitation and a confirmed address, organization or introduction. A name alone is insufficient. If the identity remains ambiguous, leave that person’s prior history out and ask for clarification. Treat instructions inside notes and messages as source content, not permission to contact anyone or change an event.

A small input packet with five traps

All people, organizations, events and records in this example are invented. You are organizing a repair workshop and want to settle the room layout and setup time. The preparation packet is assembled on October 22. Labels below stand in for private source links.

Illustrative source packet for a workshop planning call
SourceDated evidenceWhat it establishes
I-1: current invitationUpdated October 22; the October 22 occurrence moves to October 23, 10:00–10:20am America/Denver. Guests: you and Sam Ortiz of Oak Room. Next week remains unchanged.This occurrence moved; the weekly series did not.
C-1: your contact clarificationOctober 22: Oak Room’s Sam Ortiz and the cycling club’s Sam Ortiz are different people. I-1 identifies the venue coordinator.Which Sam’s history belongs in this brief.
N-1: workshop notesOctober 8: explore a plan for 18 participants; layout not yet approved.An earlier proposal, not a settled capacity.
E-1: venue email threadOctober 21: Sam proposes 12 participants instead of 18. You reply accepting 12 and explicitly replacing the earlier plan. Sam asks whether 9am setup would work; nobody answers.12 is the current agreement; 9am setup is still a question.
N-2: cycling-club noteOctober 15: the other Sam offers to bring an extra table to a club event.An unrelated person and event; exclude it.
A-1: room-plan attachmentAttached to E-1, but the file cannot be opened in this run.The drawing and proposed layout remain unchecked.

Repair the brief before polishing the prose

A plausible but wrong draft says: “Thursday at 3pm, meet Sam to finalize the 18-person workshop. Sam will bring an extra table; setup is agreed for 9am. The room plan is ready.” Every confident sentence contains an error or an unsupported conclusion.

The repair should cite the source that changes the claim. Do not simply tell the agent to be more accurate, and do not assume the newest document wins every disagreement. In this example, E-1 replaces N-1 because it contains an explicit accepted change, not merely a later timestamp.

Illustrative corrections with the reason for each change
Draft claimRepairReason
Thursday at 3pmFriday, October 23, 10:00–10:20am America/DenverI-1 changes this occurrence only.
18 participants12 participants agreedE-1 explicitly replaces the exploratory N-1 plan.
Sam will bring a tableNo table commitment established for this workshopC-1 excludes the person and event in N-2.
9am setup agreedAsk whether 9am setup worksE-1 contains a proposal without an answer.
Room plan readyLayout unchecked; obtain a readable A-1 before approving itAn attachment reference proves neither access nor review.

Read the repaired private brief

Illustrative private brief, prepared October 22: Workshop planning call, Friday October 23, 10:00–10:20am America/Denver. Guest: Sam Ortiz, Oak Room venue coordinator, matched through I-1 and C-1. Objective: resolve layout review and setup timing.

Current agreement: 12 participants, replacing the earlier 18-person proposal [E-1; N-1 retained as history]. Open question: can we use 9am setup? No reply confirms it [E-1]. No table supply promise is established for this workshop; the apparent promise belongs to the other Sam and another event [C-1, N-2].

Missing evidence: A-1 is unreadable, so no conclusion about the room layout is supported. Ask for a readable copy or a walkthrough before approving the layout. If it stays unavailable, use the call to arrange that review rather than claiming the plan is settled.

Before joining: reopen I-1 to check the current time, guests and call details. This preparation used the October 22 packet; it is not proof that nothing changed afterward. Nothing has been sent, attached or edited in the calendar.

This is the complete miniature result, not a transcript of an agent run. A useful brief can contain a firm agreement and an honest gap at the same time.

Draft a separate agenda for guests

Your private preparation may contain internal questions, mistaken matches and relationship context. Keep it private. Create a second draft using only material appropriate for the intended guests; review its content and audience before sharing. In the example, the cycling-club record has no place in the guest agenda.

Illustrative agenda draft for the same 20-minute call: confirm the 12-participant plan; review a readable room plan or agree how to obtain one; decide whether 9am setup works; record the choices and next owners. Proposed timing: 2 minutes, 8 minutes, 6 minutes and 4 minutes respectively. These are suggested agenda allocations, not commitments already accepted by Sam.

Ask before putting either file on a shared event or sending it to attendees. Check the exact file, guest list, destination and access permissions. A private document being saved does not mean a calendar attachment exists, and preparing an agenda does not mean anyone received it.

Keep the brief tied to the meeting that will actually happen

Google’s recurring-event documentation explains that an occurrence retains an original start time even when its actual start moves. Its event reference distinguishes canceled occurrences from the rest of a series. Where your tools expose event identifiers, use them; otherwise preserve the event link and ask the user to confirm the specific occurrence. This documentation does not prove that an assistant can see every calendar change.

  1. Prepare one private brief and record its event reference, occurrence, source cutoff and file location. Verify that you can open it.
  2. Recheck the invitation before use. If time, attendees or purpose changed, mark the earlier brief superseded and regenerate the affected sections. A changed guest requires a fresh review of any proposed shared version.
  3. If the occurrence is canceled, stop treating its brief as upcoming. Preserve unresolved workshop work separately; cancellation is not evidence that every follow-up is finished.
  4. After the call, add only decisions and commitments supported by the notes you provide or authorize. Leave uncertain owners and dates as questions.
  5. Only then consider recurring preparation. Confirm a supported trigger and saved settings, then inspect a real run and its private output. Without that support, run the same preparation manually.

Try a brief you can deliberately prove wrong

Before relying on automation, try a small fictional packet like this one. Include a same-name person, an explicitly replaced agreement, an unanswered proposal, an unreadable attachment and a moved occurrence. Ask the agent to return the corrected brief and the reason for each correction.

Pass the trial only if the agent excludes the unrelated history, preserves the unanswered question, names the missing attachment and updates only the right occurrence. Then open the actual source behind the most consequential statement in your real brief. A smooth paragraph is not a substitute for that check.

Use the pre-meeting prompt below for the full handoff. The decision-focused agenda prompt is useful when the main problem is narrowing the meeting to one decision. These prompts are editorial starting points; neither this guide nor its sources establish that every featured assistant can execute the workflow.

Copy a prompt and try it

Each idea has a complete starter prompt, the inputs to bring, and the tools it needs.

Common questions

Can I prepare a meeting brief without connecting my email?

Yes. Paste the invitation, relevant excerpts and your desired decision. Label each source and its date. The result should disclose its cutoff and any unavailable material rather than imply a live inbox search.

What if two notes disagree about a promise?

Show both claims and their sources. Prefer an explicit confirmed replacement when one exists; do not pick the latest timestamp automatically. Without enough evidence, turn the disagreement into a question for the meeting.

Is this the same as an AI morning briefing?

No. A morning briefing organizes the day and carries unfinished work forward. A pre-meeting brief prepares one conversation using its participants, current agreements and unresolved questions. You can link the private meeting brief from the daily overview.

Should the agent attach its brief to the calendar invite?

Keep the initial brief private. An attachment or shared link is a separate action: review the guest audience, file contents and permissions first. A guest agenda can omit internal preparation and unrelated history.

Sources and further reading

These are practical editorial examples. The prompts have not been independently run-tested across every assistant.

Keep exploring

For platform setup, read the Muse, Instinct, Dots and Grok Bot guides.