Executive assistants carry the operational weight of their executive's entire world. The calendar, the inbox, the meeting prep, the stakeholders who need careful handling — all of it lands on your desk.
I've been testing these prompts against real EA workflows. Not "write me an email" fluff. These are specific, copy-paste-ready prompts that handle the exact tasks that eat your week.
Here are 41 of them.
1. Email Management
EAHowTo.com gates 120 prompts behind a $49/yr paywall. Here are 10 of the most useful email ones, free.
Prompt 1: Decline a meeting request without burning the relationship
Draft a professional email declining a meeting request from [Name] who wants to discuss [Topic]. The executive is unavailable this month. Be polite, offer a brief reason, and suggest they follow up in [timeframe] without over-explaining. Keep it under 80 words.
Prompt 2: Second follow-up to a non-responder
Write a short follow-up email to [Name] at [Company]. I sent them an email about [Topic] on [Date] and haven't heard back. Keep it 3 sentences, non-pushy, assume they're busy, and include a clear next step.
Prompt 3: Triage and summarize a long email thread
Here is an email thread: [paste thread]. Summarize it in bullet points: (1) what was decided, (2) what is still open, (3) what action needs to happen and by whom.
Prompt 4: Escalation email on behalf of executive
Write an email from [Executive Name] to [Recipient] escalating the issue of [Problem]. Tone: direct but professional, not hostile. The goal is to prompt action by [Deadline]. Don't use passive voice.
Prompt 5: Rewrite a vague email for clarity
Rewrite this email to be concise and action-oriented. Remove filler phrases, shorten to under 100 words, and make the ask unmistakable: [paste email]
Prompt 6: Thank-you after a high-stakes meeting
Draft a thank-you email from [Executive Name] to [Meeting Attendee] after our meeting today. Topics covered: [list]. Mention one specific detail that showed we listened. Keep it under 75 words, warm but professional.
Prompt 7: VIP inbox acknowledgment template
Create an email template my executive can use to acknowledge important messages from VIP contacts quickly. It should feel personal, confirm receipt, and set expectations for a full response within [timeframe]. Under 60 words.
Prompt 8: Handoff email for someone covering your role
Write an email briefing [Name] who is covering for me while I'm out [dates]. Include: what's active, what they need to watch, and how to reach [Executive Name] for urgent matters. Tone: clear and thorough, not anxious.
Prompt 9: Vendor payment follow-up
Write a professional email to [Vendor Name] following up on invoice #[Number] for $[Amount] due [Date]. This is the [first/second] reminder. Keep the tone firm but courteous. Request confirmation of payment timeline.
Prompt 10: Bullet points → polished external email
Turn these bullet points into a polished email to [Recipient Type — e.g., board member, client, press]: [list your bullets]. Keep the tone [formal/professional/warm], under 150 words, and include a clear next step.
Saves ~90 min/week across drafting, rewriting, and follow-up cycles.
2. Meeting Prep & Follow-Up
The prep before a meeting and the notes after it account for most of the invisible time EAs lose every week.
Prompt 11: Meeting brief from a calendar invite
Create a meeting brief for [Executive Name] for a [meeting type] with [Attendees] on [Date/Time]. Include: objective, key attendees and their interests, 3 questions my executive should ask, and anything to avoid.
Prompt 12: Meeting transcript → action items
Summarize this meeting transcript into: (1) key decisions, (2) action items with owners, (3) follow-up questions, (4) deadline list. Keep it structured, under 300 words: [paste transcript]
Prompt 13: Rough notes → clean meeting minutes
Here are my rough notes from today's meeting with [Attendees] about [Topic]: [paste notes]. Turn these into clean, professional meeting minutes with: attendees, decisions, action items (owner + deadline), and next meeting date.
Prompt 14: Talking points for a difficult conversation
My executive has a difficult meeting with [Name/Role] about [Issue]. Help me build 5 talking points that: stay factual, don't escalate emotion, keep the relationship intact, and move toward resolution.
Prompt 15: Pre-read document for a major meeting
Create a 1-page pre-read document for stakeholders attending [Meeting Type] on [Date]. Include: meeting purpose, background, what decisions need to be made, and what preparation attendees should do in advance.
Prompt 16: Post-meeting follow-up with clean action items
Write a follow-up email after today's meeting with [Attendees]. Include: a brief thank you, a summary of what was decided, and a clean action item list (item | owner | deadline). Tone: professional, clear, under 200 words.
Prompt 17: Reusable weekly meeting agenda template
Create a weekly [type — e.g., team sync, 1:1, project update] meeting agenda template. It should have 5-6 sections, take no more than 30 minutes, and allow 5 min at the end for decisions/next steps. Make it reusable.
Prompt 18: Cancellation notice with rescheduling offer
Draft a professional meeting cancellation notice from [Executive Name] to [Attendees] for the meeting on [Date/Time] about [Topic]. Offer to reschedule in [timeframe]. Apologize briefly without over-explaining.
Prompt 19: Summarize a report before a meeting
Summarize this report in 5 bullet points that my executive can read in 2 minutes before a meeting: [paste report or key sections]. Focus on: what matters, what's changed, what needs a decision.
Prompt 20: Post-meeting survey
Write a short 4-question post-meeting survey to send after [Meeting Type]. Questions should measure: usefulness, whether objectives were met, quality of decision-making, and one open-ended improvement question. Keep it under 5 minutes to complete.
Saves ~75 min/week on prep, note-taking, and follow-up communication.
3. Calendar & Scheduling
Scheduling sounds simple until you're managing a C-suite calendar across multiple time zones with competing priorities.
Prompt 21: Scheduling email for a complex cross-timezone meeting
Write a scheduling email to [Names] to find time for a [meeting type] with [Executive Name]. We need 60 minutes sometime in the next 2 weeks. They are in [time zones]. Offer 3 specific options and a Calendly fallback.
Prompt 22: Weekly time-blocking strategy
Here is my executive's list of recurring commitments: [list]. Build a weekly time-block framework that protects: 2 hours of deep work daily, buffer time before/after large meetings, and a daily review block. Flag any conflicts.
Prompt 23: Calendar event description
Write a calendar event description for [Event Name] on [Date/Time] at [Location or Zoom]. Include: purpose, what to prepare, dress code if applicable, and who the key contact is. Keep it under 100 words.
Prompt 24: Handle a double-booking diplomatically
My executive has a double-booking on [Date] between [Meeting A] and [Meeting B]. Help me draft an email to [lower-priority attendees] explaining the conflict, apologizing, and proposing alternatives without revealing the other commitment.
Prompt 25: Travel itinerary for handoff
Create a travel briefing for [Event/Trip] from [Date] to [Date]. Include: flights (I'll fill in details), hotel, ground transport, key contacts on-site, timezone, and a 1-page day-by-day schedule. Format it for easy mobile reading.
Prompt 26: Executive out-of-office message
Write an out-of-office message for [Executive Name] who is away [Dates]. Include: who to contact for urgent matters ([Name, role, email]), expected response time, and keep it under 60 words. Professional tone, not overly casual.
Prompt 27: Meeting request triage checklist
I receive dozens of meeting requests weekly. Create a 5-question triage checklist I can run on any new request to decide: (1) accept, (2) delegate to someone else, (3) decline, or (4) schedule for a later quarter.
Saves ~40 min/week on scheduling logistics and conflict management.
4. Stakeholder Communication
EAs are the primary buffer between executives and everyone else. Getting the tone right with different stakeholders takes skill.
Prompt 28: Board update on behalf of executive
Write a brief update for the board from [Executive Name] covering: [Topic 1], [Topic 2], [Topic 3]. Tone: confident, data-informed, forward-looking. Keep it under 200 words. Format as short paragraphs, not bullets.
Prompt 29: Client status email that manages expectations
Write a client update email from [Executive Name] to [Client Name] about [Project/Issue]. We're [behind/on track/ahead] of schedule because [reason]. Keep expectations realistic without catastrophizing. Close with next steps.
Prompt 30: Communication to HR or Legal
Draft a communication to [HR/Legal] on behalf of [Executive Name] regarding [Issue]. Tone: factual, non-accusatory, specific. Avoid assumptions. The goal is to initiate a conversation, not assign blame. Under 150 words.
Prompt 31: Town hall talking points
Create 5 talking points for [Executive Name]'s upcoming town hall on [Topic]. Each point should: be specific (no platitudes), connect to company values, and take no more than 2 minutes to deliver verbally. Add a brief note on tone for each.
Prompt 32: Thank-you to a major donor or investor
Draft a thank-you letter from [Executive Name] to [Name] for their [contribution/investment/support] of [Amount or Type] toward [Initiative]. Be specific, personal, and genuine. Avoid generic phrases. Under 200 words.
Prompt 33: Stakeholder complaint response
A stakeholder named [Name] sent this complaint: [paste complaint]. Help me draft a response from [Executive Name] that: acknowledges the concern, avoids admitting liability, explains what will happen next, and keeps the relationship intact.
Prompt 34: Double opt-in introduction email
Write an introduction email connecting [Person A, title, company] with [Person B, title, company]. They should meet because [reason]. Keep it under 80 words. Use a double-opt-in style — let both confirm before the intro is made.
Saves ~50 min/week on drafting, reviewing, and revising stakeholder communications.
5. Project Coordination
EAs routinely own projects that span multiple teams. These prompts reduce the coordination overhead that no one accounts for in job descriptions.
Prompt 35: Project status report template
Create a weekly project status report template for [Project Name]. Sections: summary (3 sentences max), milestones completed, blockers, upcoming tasks (with owners and deadlines), and budget status. Make it scannable in 90 seconds.
Prompt 36: Delegation brief for a task being handed off
Write a delegation brief for [Task Name] being handed to [Person Name]. Include: what the task is, why it matters, what success looks like, deadline, available resources, and who to contact with questions. Keep it under 200 words.
Prompt 37: Vendor selection summary
Summarize the following vendor options for [Product/Service] in a decision-ready format: [list vendors with details]. Include: pros/cons, pricing comparison, recommended choice with rationale. One page max.
Prompt 38: Cross-team coordination email
Write an email to the [Team A] and [Team B] leads coordinating the handoff of [deliverable] by [date]. Clarify: who owns what, what format the deliverable takes, and what happens if the deadline slips. Keep it direct, no jargon.
Prompt 39: Simple project tracker in markdown
Design a simple project tracker for [Project Name] with [Number] tasks. Columns needed: task, owner, status, due date, blockers. Format it as a markdown table I can paste into Notion or Google Sheets.
Prompt 40: Risk log entry for an at-risk deliverable
Write a risk log entry for [Project Name] about the risk that [Risk Description]. Include: likelihood (high/medium/low), impact (high/medium/low), current status, mitigation plan, and owner. Format for a project risk register.
Prompt 41: Project close-out summary
Write a close-out summary for [Project Name] that completed on [Date]. Include: original goal, final outcome, key wins, what we'd do differently, and lessons learned. Tone: honest and constructive. Under 300 words.
Saves ~60 min/week on coordination tasks and project documentation.
The math
- Email management: ~90 min
- Meeting prep & follow-up: ~75 min
- Calendar & scheduling: ~40 min
- Stakeholder communication: ~50 min
- Project coordination: ~60 min
Total: ~315 minutes saved per week. Call it 5 hours.
These aren't optimistic numbers. They reflect replacing first drafts, manual note-taking, and one-off template creation with prompts that produce 80%-ready output in under 60 seconds. You still review, edit, and add context — the savings come from not starting from nothing every time.
One thing worth saying clearly
ChatGPT output is a draft, not a finished product. The real advantage for EAs isn't that the AI writes perfectly — it's that you stop spending 20 minutes staring at a blank screen before you can write anything at all.
Build your own library. Add your executive's preferred phrases, your company's tone, your industry's terminology. Prompts that are tuned to your workflow outperform generic ones by a wide margin.
Want 80 more prompts across 14 workflow categories? Get the full Executive Assistant ChatGPT Toolkit at pinzasrojas.gumroad.com — use LAUNCH30 for 30% off.
Top comments (0)