Meeting minutes for executive assistants: A complete playbook (with templates)

TL;DR: Executive assistant meeting minutes require a fundamentally different approach than standard note-taking. EAs translate executive shorthand into actionable documentation, manage strict confidentiality across executive team, client, and recruiting conversations, and distribute tailored versions to different audiences. Preparation before the meeting is as important as capture during it. Granola's AI notepad helps EAs stay fully present by transcribing device audio directly, with no visible participant and no announcement, so you can jot what matters and let AI fill in the supporting context afterward.

Most generic minute-taking guides describe a simple problem: Attend a meeting, write down what happened, send an email. Executive assistants face a different challenge. The meetings you document carry strategic weight and information that cannot leave the room in the wrong form. This playbook covers the full workflow, from agenda prep through distribution, including how an AI notepad fits into the process without creating the visibility problem that other tools introduce.

Why are meeting minutes different for executive assistants?

Executive assistants sit at the intersection of information flow and confidentiality. The notes you produce aren't just documentation. They're the official account of decisions made by people whose words carry strategic consequences. That raises the bar considerably beyond what most note-taking advice addresses.

Executive shorthand and context translation

Executives often use shorthand during meetings. They say "let's circle back on that" or "take that offline" and expect the EA to know what that means for the record. Your job isn't to transcribe the shorthand. It's to translate it into clear, actionable documentation.

A practical translation table:

That translation work requires you to understand the executive's priorities, their relationships with attendees, and the history behind the discussion. No automated transcript can supply that context. Granola's AI-enhanced notes feature is built around this reality: You write the translation in the notepad, and the AI fills in supporting detail from the transcript.

Confidentiality as a core requirement

Executive team meetings, client discussions, and CEO-level recruiting calls all carry information that, if documented carelessly, breaks trust or creates strategic exposure. An EA managing minutes for these meetings needs to treat the documentation process itself as a security control.

This means understanding which conversations should be documented and which should not appear in distributed minutes at all. Granola's participant privacy approach outlines how bot-free capture removes one layer of friction.

Prep doc handoff workflows

Effective minutes reduce your executive's cognitive load before the next meeting, not just after the last one. A standard handoff cycle:

1. Finalize notes within 24 hours by expanding shorthand and organizing points under the correct agenda items.
2. Synthesize action items and decisions into a one-page executive brief.
3. Attach relevant pre-reads and a summary of decisions from previous related meetings.
4. Deliver the packet at least 24 hours before the next meeting so your executive walks in with context, not questions.

The minutes become the foundation of the prep doc, not a separate artifact.

Balancing capture and participation

Many EAs are expected to do more than transcribe: They facilitate, track time, manage the agenda, and sometimes interject to clarify action items. That's difficult to do while typing continuously. The tension between capture and participation is the clearest argument for a tool that handles the transcript layer so you can focus on the facilitation layer.

Pre-meeting preparation for executive assistants

Effective minutes start before the meeting opens. EAs who prepare systematically produce better documentation and create less cognitive load for themselves during the meeting itself.

Capturing agenda items from multiple sources

Agenda items rarely arrive in one place. You're pulling from the executive's email, their calendar notes, previous meeting action items, and direct requests from other attendees. A reliable pre-meeting habit:

• Pull open action items from the last meeting and flag any that are overdue.
• Confirm the executive's desired outcomes for each agenda item, not just the topic.
• Send a brief agenda confirmation to key attendees 48 hours in advance.
• Note which agenda items are likely to generate decisions vs. discussion only.

Setting up meeting briefs

A meeting brief is a one-page document your executive reviews before each meeting starts. It should contain:

• Attendees and their roles: Names, titles, and one-sentence context on why each person is in the room.
• Agenda with time allocations: Each item with a target duration.
• Relevant prior decisions: What was decided in the last meeting on each topic.
• Open action items: What's due, who owns it, and whether it's complete.
• Pre-read summary: A two-sentence summary of any documents attendees were asked to review.

Attendee research and context gathering

For external attendees, particularly in investor, client, or recruiting meetings, create a quick reference sheet before the meeting. Include a recent headshot for visual identification, their title and organization, a one-sentence description of their relationship to the meeting topic, and any prior positions they've stated on the agenda items being discussed. Knowing who is speaking determines who owns the action item. If you can't identify speakers in the room, asking for a brief round of introductions at the start is a reasonable request.

Preparing confidential materials

For sensitive meetings, pre-reads should be shared only with attendees who have clearance for that content. Use secure document sharing rather than email attachments. Prepare a list of any acronyms or industry-specific terms that will appear in the notes so you can capture them accurately. Granola's template customization lets you set up meeting-specific structures in advance so the AI enhancement matches the format you've already defined.

In-meeting capture techniques by executive preference

No two executives want minutes formatted the same way. Part of the EA role is learning and matching your executive's preferences, then applying a consistent structure for each meeting type.

Formal minute-taking style

Investor updates and formal executive presentations require structured documentation. Use explicit section headers and bold action item labels at the start of each list entry for scanning.

A formal entry structure:

Topic: [Item]
Discussion summary: [Key points raised]
Decision: [Outcome]
Owner: [Name] | Due:[Date]

Circulating minutes to all attendees before wider distribution gives participants the opportunity to request corrections while context is fresh.

Informal conversational capture

Executive 1:1s and strategy syncs run at a different pace. The goal here is capturing decisions and priorities, not the conversation that led to them. Develop personal shorthand using abbreviations for recurring topics and initials for frequent attendees. After the meeting, expand the shorthand before distributing.

"I love that you can blend shorthand with AI notes. It's also super intuitive and super easy to use. The interface is clean and simple. I use this nearly every day for work." - Mason K. on G2

Action-oriented documentation

Regardless of meeting type, action items need a standard format across all minutes. Use the Owner / Task / Due Date structure and apply it consistently:

ACTION: [Owner] | [Specific task description] | [Due date]

This format makes action items scannable, assignable, and trackable while removing ambiguity about who is responsible. Chatting with your meetings in Granola lets you query "what were the action items?" across any meeting and get a structured answer instantly.

When to capture verbatim vs. summarize

The choice between verbatim capture and summary depends on how the content will be used:

Distribution etiquette by recipient type

Who receives the minutes is as important as what's in them. Distribution mistakes in executive meetings can break trust or confuse recipients who don't have full context.

C-suite distribution protocols

Follow these distribution standards:

• Distribute within 24 hours while context is fresh. For formal decisions with external implications, confirm with the relevant stakeholder whether they need immediate confirmation.
• Send to all attendees first for review before wider distribution.
• Use version control: Name documents with meeting date and version number (e.g., "ExecStaff_2026-05-25_v1").
• Store in a location where access can be revoked if someone leaves the organization.

Leadership team minute sharing

Leadership team minutes follow a more deliberate distribution path than regular meeting notes. Share a draft with the most senior attendee before sending to the full group. Include a cover note summarizing key decisions and action items so recipients can identify the most important sections without reading the full document. Keep the version history clean: Use date and version number in the file name (e.g., "LeadershipSync_2026-05-25_v1") so the authoritative copy is always identifiable.

External stakeholder versions

When external parties, such as clients, advisors, or prospective partners, are assigned action items in a meeting, they need a version of the notes that confirms what they committed to without exposing internal discussion. Create a stripped-down version that includes only agreed-upon assumptions, external action items, and next steps, omitting internal strategy commentary and any financial or personnel information. For confidential matters like executive compensation discussions or personnel decisions, external stakeholders should not receive minutes at all.

Internal team summaries

After an executive staff meeting, the broader team often needs a summary of decisions that affect their work. This internal brief is distinct from the official minutes. It translates executive-level decisions into what the team needs to know and do, without the formal structure or sensitive context of the full document.

Confidentiality and redaction best practices

What gets shared vs. what stays private

Off-the-record comments should not appear in official minutes, even if made by a senior leader. Document only what is agreed for inclusion: Decisions, motions, votes, and action items. Summarize general discussion at a high level without attributing specific statements to individuals.

For meetings where sensitive topics arise mid-agenda, the minutes for that section should note that a discussion took place on [topic] and document only the outcome, not the content of the discussion.

Redacting sensitive information

Before sharing notes with any audience, review them against the version you've defined for that recipient. Remove anything that falls outside the scope of what that audience needs: Internal commentary, personnel references, or financial detail that wasn't part of the agreed external discussion. What Granola can do is help you manage your notes before they leave the app, so you can review and edit content before sharing or storing.

Creating multiple versions for different audiences

A leadership or client meeting may produce two or three distinct documents: Full notes for internal participants, a stripped-down action summary for external parties with assigned tasks, and a brief for the broader team if decisions affect their work. For example, a discussion of organizational restructuring would appear in detail in internal minutes, be summarized as "Organizational planning update discussed" in broader team communications, and be omitted entirely from any external stakeholder versions. Define these versions before the meeting so you're not making those calls under time pressure afterward.

Managing sensitive information over time

The EA's role in information management extends beyond the meeting itself. Establish a consistent naming, storage, and access convention for all executive minutes so the right people can find the right document without asking you each time. When someone leaves the organization, confirm their access to shared folders and past documents is adjusted accordingly. A brief quarterly review of your storage structure prevents documents from becoming ungoverned as the organization grows.

The AI-assisted EA workflow with Granola

The most common objection to AI notepads in executive meetings isn't about accuracy. It's about the visible participant. An automated tool joining a strategy session or a CEO recruiting call changes the dynamic immediately: Counterparties grow cautious, trust drops, and candid discussion gets redirected.

Continuous capture without visible bots

Granola captures device audio directly, accessing your microphone and computer audio and transcribing in real time. No bot joins the video call, no participant list updates, and no transcription announcement appears. The meeting runs exactly as it would without any tool present.

"background without joining as a bot or recording audio means I can actually be present in conversations. No awkward 'there's a bot in this call' energy." - Aprielle D. on G2

This architecture matters most in the meetings where documentation matters most: Strategy sessions, executive recruiting, client conversations, and investor updates. Granola's participant privacy documentation explains the architectural difference in detail.

Editing during downtime between meetings

The EA workflow rarely includes time for immediate cleanup between meetings. Granola's human-in-the-loop enhancement lets you handle that during the gaps. You jot rough notes during the meeting, then click "Enhance notes" when you have a few minutes. Your notes stay in black. The AI adds supporting context from the transcript in gray. You review, edit, and delete anything that doesn't belong before the document goes anywhere.

This is the structure explained in Granola's AI-enhanced notes documentation: The human writes the frame, the AI fills in the transcript-backed detail. Your judgment about what matters controls the output.

Maintaining presence while documenting

The practical benefit for EAs is that you can focus on facilitation, relationship observation, and agenda management during the meeting instead of typing continuously. You capture decisions and action items as they happen, then Granola handles the transcript layer. After the meeting, you shape the combined output into the appropriate format for each recipient.

"What I like best about Granola is how effortlessly it handles meeting notes without disrupting the flow of the conversation. It listens directly from my device audio no bots joining calls and produces clean, structured summaries with decisions, action items, and key points." - Brahmatheja Reddy M. on G2

Protecting confidential conversations

Granola transcribes audio in real time, immediately deletes it after processing, and stores no audio files on its systems. Granola maintains SOC 2 Type 2 certification (achieved July 2025) and complies with GDPR. Third-party AI providers are never permitted to train on your data. For details, see Granola's security and privacy FAQ.

Meeting minute templates EAs actually use

Executive staff meeting template

Granola's template library includes pre-built structures you can customize for your meetings. A base template for an executive staff meeting:

EXECUTIVE STAFF MEETING

• Date: [Date] | Attendees: [Names]

DECISIONS MADE

• [Decision 1]: [Context]
• [Decision 2]: [Context]

PRIORITIES UPDATE

• [Owner]: [Key update]
• [Owner]: [Key update]

BLOCKERS ESCALATED

• [Blocker]: [Owner] needs [resource/decision] by [date]

ACTION ITEMS

• [Owner] | [Task] | [Due date]

Executive 1:1 meeting template

1:1 MEETING

• Date: [Date] | Participants: [Executive] + [EA/Report]

PRIORITIES (Executive's top 3 this week)

• 1. [Add priorities]
• 2. [Add priorities]
• 3. [Add priorities]

BLOCKERS

• [Add blockers]

DECISIONS NEEDED

• [Add decisions]

FOLLOW-UP FROM LAST MEETING

• [Item]: [Status]

ACTION ITEMS

• [Owner] | [Task] | [Due date]

Granola's writing notes documentation explains how to apply Markdown formatting within the notepad to structure these templates during live meetings. Business plan users can push finalized notes directly to Notion, Slack, HubSpot, and other tools via Granola's integrations.

These templates work in any notepad, but Granola's template customization lets you save your preferred structures so they load automatically for specific meeting types. Try Granola for free: Download the Mac or Windows app. Connecting your calendar enables automatic meeting detection. Use it in your next executive meeting to see how bot-free capture changes the dynamic.

FAQs

What's the best way to track action items across meetings?

Use a consistent Owner / Task / Due Date format in every set of minutes, then consolidate open action items into a single tracker you review at the start of each prep cycle. Granola Chat lets you query across all your meetings to pull open action items without reviewing each document manually.

How long should I keep meeting minutes?

Storage practice varies by organization, but a consistent approach works well: Keep active meeting notes accessible for the current quarter, archive the previous two to three quarters in a clearly labeled folder, and confirm with your executive or operations lead whether your organization has a defined document retention policy you should align to.

Can I use AI tools for confidential executive meetings?

Yes, with the right architecture. Granola captures device audio directly with no bot joining the call and no transcription announcement visible to other participants, which makes it suited for strategy sessions, recruiting conversations, and client meetings where a visible meeting bot would change the dynamic. Granola is SOC 2 Type 2 compliant and GDPR compliant, with audio deleted immediately after transcription.

Key terms glossary

SOC 2 Type 2: A security certification issued by an independent auditor confirming that a company's systems and processes meet the American Institute of Certified Public Accountants (AICPA) standards for data security, availability, and confidentiality. Unlike SOC 2 Type 1, which evaluates controls at a single point in time, Type 2 covers a defined audit period (typically 6 to 12 months), making it a stronger indicator of consistent security practice.

Human-in-the-loop: An AI workflow design where a human reviews, edits, and approves the AI's output before it is used or distributed. In the context of meeting notes, this means the EA writes the structural frame during the meeting, the AI fills in supporting detail from the transcript, and the EA makes the final call on what stays, what changes, and what gets deleted before the document leaves the tool.

Quorum: The minimum number of members required to be present at a meeting for decisions to be formally valid. Quorum thresholds vary by organization and are typically defined in a company's bylaws or governance documents.