LLM Meeting Brief Generator
Compile meeting context into one brief with history, actions, and decisive questions.
- Difficulty
- Easy
- Time to result
- ~days to results
- Steps
- 6
- Confidence
- 99%
The meeting brief generator starts with a calendar event and retrieves the documents, notes, and email threads most relevant to that event. It identifies participants and their roles, summarizes a small number of meaningful prior interactions, extracts open decisions and pending actions, and suggests questions that will move the discussion forward. The mechanism is selective synthesis rather than exhaustive summarization: it filters a large body of work data into the context needed for one specific conversation. The resulting artifact can be read immediately before the meeting and updated as new communications arrive. Its consistent structure also makes it reusable across every event in a selected day.
Origin
Extracted from Marketing Against The Grain, where the host uses Claude to generate detailed briefs for an upcoming day of meetings.
Core principles
- 01Strong preparation combines calendar context with prior communications and documents.
- 02A useful brief emphasizes decisions and pending actions rather than raw information.
- 03Participant roles determine which context and questions matter.
- 04Prepared questions help convert retrieved context into a productive discussion.
How to run it
- 1
Select the Meeting
Choose a calendar event and treat its title, time, description, and attendees as the starting context.
Pro tip Begin with a consequential meeting that normally requires manual preparation.
Watch out Ambiguous event titles may retrieve unrelated material unless additional context is supplied.
- 2
Identify Participants and Roles
Determine who will attend and why each person matters to the discussion. Use those roles to guide retrieval and prioritization.
Pro tip Include decision authority, ownership, and subject-matter responsibility when available.
Watch out Do not infer sensitive personal details that are irrelevant to the meeting.
- 3
Retrieve Related History
Search email, documents, previous notes, and earlier meetings for relevant interactions. Favor recent and directly related evidence.
Pro tip Limit the brief to the two or three interactions that materially affect the current meeting.
Watch out Keyword similarity alone can pull in unrelated projects or people.
- 4
Extract Open Work
List pending action items, unresolved questions, promised deliverables, and decisions that must be made. Associate owners where the source supports it.
Pro tip Separate confirmed commitments from tentative suggestions.
Watch out Never present an inferred owner or deadline as a verified commitment.
- 5
Generate Discussion Questions
Propose two or three questions that clarify uncertainty, unblock action, or produce a decision. Tie each question to the retrieved context.
Pro tip Prefer questions that change the next action over questions that merely request an update.
Watch out Generic questions dilute the value of the brief.
- 6
Assemble and Verify the Brief
Combine participants, history, actions, decisions, and questions into a concise artifact. Check consequential claims against the underlying messages or documents.
Pro tip Use the same headings for every meeting so briefs are easy to scan.
Watch out A polished synthesis can still contain retrieval or attribution errors.
In the wild
The generated brief surfaced that Rachel was finalizing a draft, Sunil was assessing technical capabilities for AI personalization, and the host needed to decide whether August features should appear in a June narrative. It also proposed questions for the discussion.
→ The host entered the meeting with participant context, pending work, a named decision, and prepared questions.
For a meeting with a new small-business sales leader, the daily artifact supplied collaboration areas, discussion points, and follow-up actions to consider.
→ A calendar event became an actionable preparation brief rather than a bare appointment.
Common mistakes
Dumping All Retrieved Context
A brief becomes unusable when it reproduces every related message instead of selecting the interactions that affect the meeting.
Omitting Pending Decisions
Background alone does not create readiness; the brief must identify what needs to be decided or advanced.
Trusting Names and Owners Blindly
Participant, owner, and deadline details should be checked against source records before consequential use.
Is it for you?
Best for
People with meeting-heavy schedules whose relevant history is distributed across calendars, email, notes, and documents.
Not ideal for
Highly confidential meetings where the model cannot be granted appropriate access to source material.
From the transcript
“And it says automatically generate meeting briefs by analyzing calendar invites, related documents, previous meeting notes, and relative email.”
“And then it gave me an example prompt for how to do this, which is like identify key participants in the roles, summarize the two…”
“and extract the three most important pending action items, suggest two to three key questions I should ask.”
From the episode
This AI Assistant Will Organize Your Life (No More Chaos)