AI Meeting Brief Template: A Daily Prep Workflow That Saves Time

Meeting prep eats the twenty minutes before the call — the slot you needed for thinking. An AI meeting brief replaces that scramble by pulling context from calendar, CRM, email, and project files into a five-section brief the meeting owner reviews before walking in.

The workflow runs in two stages: a heavy prep pass that gathers and organizes everything, and a short delivery pass that produces the one-page brief. The owner reviews before the meeting, and nothing leaves the draft state without that gate.

Below is the complete template. Copy the runbook into your own system, point it at your sources, and start from a real meeting tomorrow.

The short answer

• Two stages: heavy prep run gathers inputs and drafts sections; short delivery run produces the final brief.
• Four inputs: calendar, CRM notes, email, project files.
• Five-section output: attendees, context, open items, talking points, risks.
• One approval gate: the meeting owner reviews the draft before the meeting.
• One runbook: the Markdown template below is copy-paste ready.

The two-stage brief pattern

The brief is produced in two runs, not one.

Heavy prep run — scheduled ahead of the meeting (ideally the night before or early morning). This is where the agent reads the calendar to confirm the meeting, pulls CRM history for each attendee, scans relevant email threads, and reviews project files for status, blockers, and recent changes. The output is a structured draft with all five sections filled with raw material.

Short delivery run — triggered closer to meeting time (30-60 minutes before). This pass takes the prep draft, trims it to a one-page brief, flags what changed since the prep run, and marks anything the owner should review. The brief stays in draft state until the owner approves.

This split exists because context changes. A prep run at 11 p.m. captures most of what matters. A delivery run at 8:30 a.m. catches the late email and the overnight status update without rebuilding the whole brief from scratch.

What the agent reads: four inputs

Each input maps to one question the brief needs to answer.

• Calendar — who is attending, when, how long, and the meeting title or agenda if one exists.
• CRM notes — last interactions with attendees, deal stage, open commitments, relationship history.
• Email — threads with attendees in the last 7-14 days, attachments, and any action items or promises.
• Project files — status of work discussed, blockers, recent changes, deadlines tied to this meeting.

The agent reads what it needs for the brief — no more. Point it at specific sources: the calendar feed, the CRM record for the account or contact, the email label or attendee addresses, and the project folder or doc. Avoid giving it blanket access to everything. Narrow inputs produce better briefs and fewer errors.

What the owner gets: five-section output

The delivery run produces a one-page brief with five sections:

1. Attendees — name, role, relationship context, and last interaction date.
2. Context — what this meeting is about and why it was scheduled.
3. Open items — unresolved threads, commitments, and action items from prior interactions.
4. Talking points — three to five suggestions ranked by relevance and urgency.
5. Risks — anything the owner should know before walking in: stale deals, missed deadlines, sensitive topics, unanswered messages.

Keep it to one page. If a section gets too long, the agent summarizes rather than lists everything. The brief is a tool for decision-making, not a data dump.

The approval gate

The brief is a draft until the meeting owner reviews it. The owner checks three things:

• Are the right attendees and context captured?
• Are open items and talking points accurate and current?
• Are risks flagged or missed?

If something is wrong, the owner edits before the meeting. If something is missing, the owner adds it. The agent does not send the brief to attendees, change calendar entries, or modify CRM records without explicit approval. The gate exists so the owner walks in prepared — not surprised.

Copy-paste runbook template

# AI Meeting Brief — Daily Prep Runbook

## Purpose
Produce a one-page meeting brief for the meeting owner, from calendar, CRM, email,
and project files, with approval before delivery.

## Trigger
- Scheduled: 12 hours before each meeting (heavy prep run).
- Scheduled: 30-60 minutes before each meeting (short delivery run).

## Inputs
- Calendar feed (today's meetings, attendees, titles, duration).
- CRM notes for each attendee or account (last 30 days, unless older context matters).
- Email threads with attendees in the last 7-14 days.
- Project files tied to the meeting topic (status, blockers, recent changes, deadlines).

## Stage 1 — Heavy prep run

1. Read calendar. Identify each meeting with confirmed attendees.
2. For each attendee, pull CRM notes: last interaction, deal stage, open commitments.
3. Scan email for threads with attendees in the last 7-14 days. Capture action items and promises.
4. Review project files for status, blockers, and changes since the last interaction.
5. Draft five sections:
   - Attendees (name, role, last interaction)
   - Context (why this meeting was scheduled)
   - Open items (unresolved threads, commitments)
   - Talking points (3-5, ranked by relevance)
   - Risks (stale deals, missed deadlines, sensitive topics)
6. Save draft brief. Do not deliver yet.

## Stage 2 — Short delivery run

1. Load the prep draft for each meeting.
2. Re-scan email and project files for changes since the prep run.
3. Update open items, talking points, and risks with anything new.
4. Trim to one page. Summarize where sections are too long.
5. Flag items the owner should review: "Updated since prep: [item]."
6. Deliver draft to the meeting owner.

## Approval gate
- Owner reviews the draft before the meeting.
- Owner edits for accuracy, adds missing context, adjusts talking points.
- Agent does NOT send to attendees, change calendar, or modify CRM without explicit approval.

## Output format
- One page, five sections, ordered: Attendees, Context, Open items, Talking points, Risks.
- Each section: 2-5 bullets or one short paragraph.
- Flag any item updated since the prep run.

## Escalation
- If a key attendee has no CRM history: note it and ask the owner.
- If email threads are missing or ambiguous: note it and ask the owner.
- If project files are stale or inaccessible: note it and ask the owner.
- If the meeting was cancelled or rescheduled: skip the brief and log it.

## Receipt
- Brief saved to: [project folder or notes location].
- Owner review status: approved / edited / skipped.
- Items flagged for follow-up: list.

Common mistakes

• Single-stage prep. Running everything 30 minutes before the meeting means stale inputs and rushed drafts. The two-stage pattern catches overnight changes and gives the owner time to review.
• Too many inputs. Giving the agent blanket access to all email, all CRM records, and all files produces noise, not insight. Point it at the specific meeting, attendees, and project.
• No approval gate. If the brief goes straight to attendees or into a shared doc, the owner cannot catch errors before others see them. The gate is where the brief becomes reliable.
• Five-page briefs. If the brief is longer than one page, the owner will skim it. Summarize. The brief supports decisions, not exhaustive context.

Next step

If you want to see this workflow running end-to-end — calendar reading, CRM history, email scan, project file review, draft brief, and the approval packet — the Meeting Brief Follow-Up Agent demo walks through a live example. Pair it with the markdown runbooks guide for the underlying runbook structure, and the AI workflow automation article for the trigger-source-output-approval pattern this template is built on.

<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "BlogPosting",
"headline": "AI Meeting Brief Template: A Daily Prep Workflow That Saves Time",
"description": "Copy-paste AI meeting brief template with two-stage prep, approval gate, five-section output, and runbook for calendar, CRM, email, and project files.",
"datePublished": "2026-07-07",
"dateModified": "2026-07-07",
"author": {
"@type": "Organization",
"name": "Claw Empire"
},
"publisher": {
"@type": "Organization",
"name": "Claw Empire"
},
"image": "/images/blog/ai-meeting-brief-template.png",
"mainEntityOfPage": {
"@type": "WebPage",
"@id": "https://clawempire.com/blog/ai-meeting-brief-template"
}
}
</script>