Most professionals who prep for executive meetings say the same thing: it takes too long, it's mostly the same work every time, and they could do it faster if they had a better system.
Executive assistants especially feel this. Preparing a briefing for a C-suite executive isn't just "read the agenda" — it's background research on attendees, context on previous meetings, talking point suggestions, conflict checks, and often a 1-page brief the exec can read in 5 minutes. Done manually, this takes 60–90 minutes per meeting. For EAs supporting executives with 4–6 meetings per day, that math gets brutal fast.
Here's what changes when you have a solid prompt system in place.
What Meeting Prep Actually Involves (and Why It Takes So Long)
A complete meeting prep package typically includes:
- Attendee briefing: Who's in the room? What's their title, company, relationship history with the exec, and any recent news?
- Agenda context: What is the meeting trying to accomplish? What decisions need to be made?
- Talking points: 3–5 things the exec should cover, framed around the objective
- Risk flags: Any conflicts, sensitivities, or prior commitments that need to be addressed
- Next-step structure: What should be agreed on by the end of the call?
When you're building this from scratch for each meeting, you're constantly reinventing the same structure. The content changes, but the framework doesn't. That's where prompt systems come in.
The 4 Things Every Exec Briefing Should Cover
Good briefing documents follow a consistent structure:
- Purpose — What is the meeting for? (One sentence. Decision, relationship, update, pitch?)
- People — Who are the attendees and why do they matter to the exec?
- Priorities — What should the exec accomplish in this meeting?
- Preparation gaps — What does the exec need to know that they might not?
Once you have that framework locked in, the prompt job becomes filling it with accurate information — not deciding what structure to use.
Prompt 1: Generate a Meeting Brief from Agenda + Attendee Names
Here's a reusable prompt template that produces a complete briefing document:
Meeting: [Meeting title]
Date/Time: [Date and time]
Duration: [Length]
Attendees: [Name, Title, Company for each]
Agenda items: [Paste or summarize agenda]Please generate a 1-page executive briefing that covers: (1) purpose of this meeting in one sentence, (2) key information about each attendee (role, relevance to exec, any recent relevant news), (3) 4–5 suggested talking points for my executive, (4) any flags or sensitivities I should flag before the meeting, (5) a recommended outcome/next step.
Format: clean, scannable, no jargon. My exec has 5 minutes to read this.
Fill in the meeting details, paste the agenda, and the brief is ready in under 2 minutes. That's step one.
Prompt 2: Draft Talking Points from Previous Meeting Notes
The harder problem: continuity. When an exec has a standing weekly with someone, the relationship has history. The talking points for week 8 should build on what was said in weeks 1–7.
Here's the prompt:
Here are notes from the last three meetings with [Person/Team]:
[Paste meeting notes — summaries, decisions, action items]My executive has a follow-up call with them this [day]. Please draft 4–5 talking points that: (1) reference progress or open items from previous meetings, (2) advance the relationship or project, (3) close any open loops, (4) open a natural path to next steps.
Tone: professional and direct. My exec is time-constrained.
This is the prompt that most EAs say changes their workflow the most. It makes the exec look prepared and on top of things even when they haven't reviewed previous notes themselves.
Prompt 3: Flag Conflicts and Suggest Agenda Reordering
Longer or more complex meetings often have implicit conflicts: two agenda items that contradict each other, topics that should logically come before others, or a sensitive subject that's buried at the end when it should probably be addressed first.
Here's the prompt:
Here is the agenda for a [length] meeting with [attendees]:
[Paste agenda]Our primary objective for this meeting is [X].
Please: (1) identify any items that conflict with each other or create tension, (2) flag items that should probably come earlier or later based on the primary objective, (3) suggest a revised agenda order with a brief rationale for each change, (4) identify any items that seem off-scope and could be cut or tabled.
Most agenda reviews happen as a mental scan. Prompting this process externalizes the logic and often catches things that would otherwise slip through.
Before/After: 90 Minutes to 18 Minutes
Here's what a real meeting prep workflow looked like before and after implementing these prompts, based on a pattern common among EAs supporting C-suite executives:
Before:
- 15 min: Find previous meeting notes, organize them
- 20 min: Research attendees via LinkedIn and Google
- 25 min: Write briefing document from scratch
- 15 min: Draft talking points
- 10 min: Review agenda for conflicts
- 5 min: Format and send to exec
- Total: ~90 minutes per complex meeting
After:
- 5 min: Gather inputs (notes, agenda, attendee list)
- 3 min: Run 3 prompts
- 7 min: Edit, fact-check, and format output
- 3 min: Send
- Total: ~18 minutes per complex meeting
The work doesn't disappear — judgment, accuracy, and professional review still matter. The prompts eliminate the blank-page time and the structural reinvention.
Where to Go From Here
The prompts above are a starting point. The full system for executive assistants covers 6 core areas: communications, meetings, briefings, travel, people operations, and project tracking.
Building that system from scratch takes time. If you want a ready-made version with 150+ workflow templates built specifically for EA and operations roles, the Executive Assistant AI Workflow Toolkit has everything organized and ready to use from day one.
It covers every core task in the EA role — not just meetings — with prompt templates you can open, fill in, and deploy immediately.
Check it out here: https://pinzasrojas.gumroad.com/l/gxyhyn
Price: $34. Instant download. No fluff, just working systems.
