101 AI Prompts for Executive Assistants

A practical library of 101 AI prompts for executive assistants, covering inbox management, calendar planning, meeting prep, CEO briefings, executive updates, travel planning, SOPs, and stakeholder communication.

Executive assistants do not need AI to replace judgment. They need AI to reduce repetitive work, clean up messy information, and turn scattered details into clear next steps. A great EA already knows what the executive needs before they ask. What eats the day is everything around that: the inbox, the calendar, the meeting prep, the updates, the travel, the documents, the stakeholders, and the urgent request that lands at 4:55 on a Friday.

That is exactly where AI helps, and only when the prompt is specific and you stay in control. The 101 prompts below are grouped by the real jobs of the role. Copy any one, drop in your details, and edit the result. Treat AI as a fast first-drafter and organizer, never as the final word on anything sensitive. If you are new to writing prompts, the guide to writing better AI prompts and the prompt engineering glossary entry are worth ten minutes before you start.

Quick Answer

AI prompts for executive assistants should help with inbox management, calendar planning, meeting prep, CEO briefings, executive updates, travel planning, SOP creation, stakeholder communication, and decision summaries. The best prompts give AI the goal, context, audience, tone, output format, and what not to do. Executive assistants should use AI to draft, summarize, organize, and clarify, while keeping human review for sensitive decisions and final communication.

How to Use These Prompts Safely

Every prompt below uses square brackets like [executive's name] as placeholders. Replace them with your details before running the prompt, and anonymize anything sensitive as you go.

A few habits keep this safe:

• Check your company’s AI policy before you paste anything work-related.
• Use approved or enterprise workplace AI tools where they exist, rather than a personal account.
• Anonymize sensitive information, or describe it in general terms instead of pasting the real thing.
• Review everything before it goes out on behalf of an executive. AI drafts, you decide.
• Do not paste confidential HR, legal, financial, customer, board, or personal information into public AI tools without approval.

That last point matters most. Keeping a human in the loop is not a formality, it is the difference between AI saving you time and AI creating a problem you have to clean up. For a deeper habit of checking AI output before you trust it, see make AI prove its work.

The Simple Prompt Formula for Executive Assistants

Almost every prompt on this page follows the same shape:

Task + Context + Audience + Tone + Format + Boundaries

You name what you want done, give the AI the background it needs, say who the output is for, set the tone, describe the format, and tell it what not to do. Miss any of these and you get generic output you have to rewrite.

Here is the difference in practice.

Weak:

Write an update.

Better:

Turn these project notes into a concise executive update for the CEO.
Keep it under 150 words, use a calm professional tone, separate
progress, risks, and next steps, and do not invent missing details.

Notes: [paste your notes]

The second version does not need to be clever. It just tells the AI everything a new team member would need to do the same task well. If you support one executive regularly, save their preferences once as a short portable context file and paste it into any tool instead of re-explaining every time.

Inbox Management Prompts

The inbox is where most EAs lose time. AI is good at the sorting and drafting layer here, not the deciding. Use it to triage and draft, then make the calls yourself. If email is your biggest drain, the email productivity guide pairs well with these.

1. Summarize unread emails:

Summarize this batch of unread emails so I can scan them in under a minute.

Emails: [paste subject lines and key content]

For each, give me one line: sender, what they want, and how urgent it looks.
Group them at the top by "needs a reply today" vs "can wait."

2. Identify the urgent messages:

Here are the emails in my executive's inbox from today: [paste]

Tell me which ones are genuinely time-sensitive and why.
Flag anything that mentions a deadline, a decision needed, or an external
party waiting on us. Ignore newsletters and automated notifications.

3. Group emails by action type:

Sort these emails into action buckets: reply needed, schedule/calendar,
delegate, read for information, and no action.

Emails: [paste]

Return each bucket as a short list. If something could fit two buckets,
put it in the more urgent one.

4. Draft a polite reply:

Draft a reply to this email.

Email received: [paste]
Outcome I want: [what the reply should achieve]
Tone: [warm / direct / formal]

Keep it under 90 words, clear, and easy to say yes to. I will personalize
and review before sending.

5. Turn a long email into action items:

Pull the action items out of this email.

Email: [paste]

List each task with: what needs doing, who owns it, and any deadline
mentioned. Flag anything that needs my executive's decision rather than mine.

6. Find missing information before replying:

Read this email and tell me what information is missing before I can
give a complete reply.

Email: [paste]

List the specific questions I need answered, and draft a short note asking
the sender for exactly those details if that is the fastest path.

7. Write a follow-up:

Write a follow-up to this email that hasn't had a response.

Original message: [paste or summarize]
Days since sent: [number]
Tone: friendly but clear that we still need an answer.

Under 70 words. Reference the original briefly, restate what we need, and
give an easy next step.

8. Clarify a vague request:

This email is asking me for something but it's not clear exactly what.

Email: [paste]

Tell me the most likely thing they actually need, list the two or three
interpretations, and draft a short reply that confirms what they want
without sounding like I wasn't paying attention.

9. Summarize a long thread with response options:

Summarize this email thread so my executive can read it in under 60 seconds.

Thread: [paste the chain]

Give me:
- What this thread is about (one sentence)
- The decision or request being made of my executive
- Current status and what's already been agreed
- Two brief response options they can choose from

10. Create inbox triage rules:

Help me design simple triage rules for my executive's inbox.

Typical senders and topics we get: [describe]
What my executive always wants to see immediately: [describe]
What can be handled or deferred by me: [describe]

Give me a short set of if-this-then-that rules I can apply consistently,
plus a suggested folder or label structure.

Calendar Management Prompts

The calendar is where AI can turn a chaotic week into a plan. Give it your executive’s real priorities so its suggestions match what matters, not just what fits.

11. Prioritize the week’s meetings:

Here is my executive's calendar for next week: [paste meetings with times]
Their top priorities right now: [list 2-3]

Rank the meetings by importance to those priorities. Flag any that seem
low-value or could be delegated, shortened, or declined.

12. Identify calendar conflicts:

Review this schedule and find every conflict, tight transition, or
back-to-back stretch with no break.

Schedule: [paste]

For each issue, tell me what's clashing and suggest a fix (move, shorten,
or add buffer). Note any day that has no gap for focus or lunch.

13. Create scheduling options:

I need to schedule a [length] meeting between my executive and [person/group].

My executive's availability: [paste open slots with time zone]
Their stated preferences: [mornings / no Fridays / etc.]

Give me three clean options to offer, phrased so the other party can pick
one quickly.

14. Protect focus time:

My executive needs [number] hours of protected focus time this week.

Current calendar: [paste]

Suggest where to block it, what to move to make room, and a short polite
message I can send if I need to reschedule something to create the space.

15. Run a weekly calendar review:

Act as my scheduling second-in-command and review next week's calendar.

Calendar: [paste]
Priorities: [list]

Tell me: what looks overloaded, what's missing prep time, what could be
cut, and where the risks are. End with a three-line summary of the week.

16. Suggest meetings to cut:

My executive wants fewer meetings. Here is a typical week: [paste]

Identify which recurring or one-off meetings are the best candidates to
cancel, shorten, make async, or hand to someone else. Explain your
reasoning in one line each.

17. Turn calendar chaos into a plan:

Here is a messy dump of everything on my executive's plate this week:
[paste meetings, deadlines, and to-dos in any order]

Turn it into a clear day-by-day plan. Group by day, flag the two or three
things that truly matter each day, and note anything that needs prep.

18. Write a rescheduling message:

Draft a short, polite message to reschedule a meeting.

Meeting: [what it is and with whom]
Reason: [conflict / priority shift, keep it brief and professional]
New options: [two or three alternative times]

Under 60 words. Apologize once, not three times, and make rebooking easy.

19. Build agenda-first meeting blocks:

For each of these meetings, tell me whether it has a clear purpose and
what a one-line agenda would be.

Meetings: [paste titles]

Flag any meeting with no obvious purpose so I can ask the organizer whether
it's needed, and draft that question.

20. Check which meetings need prep:

Review this week's meetings and tell me which ones my executive will need
prep or a briefing for.

Meetings: [paste]

For each one that needs prep, note what kind (background reading, talking
points, decisions to be ready for) and roughly how much lead time to allow.

Meeting Prep Prompts

Good meeting prep is what makes an executive look prepared. AI can assemble the brief from your raw material fast. If you use a notetaker like Fireflies or Fathom, you can feed its transcripts straight into these.

21. Build a pre-meeting brief:

Prepare a pre-meeting briefing for [executive's name] ahead of a meeting
with [who they're meeting].

Meeting purpose: [why this is happening]
Background: [paste relevant notes, emails, or context]
Expected outcome: [decision, update, relationship, etc.]

Format:
- Purpose (one sentence)
- Context and background (3-5 bullets)
- Key people and their likely perspective
- Questions or challenges to prepare for
- Recommended talking points
- Anything we still need before the meeting

22. Summarize background context:

My executive is meeting [person/company] and needs the backstory fast.

Everything I have: [paste emails, notes, past meeting summaries]

Give me a tight background summary: the relationship history, where things
stand now, any open issues, and what changed since we last spoke to them.

23. Prepare questions to ask:

For this meeting, suggest the smart questions my executive should ask.

Meeting purpose: [describe]
What we want to learn or achieve: [describe]

Give me 5-7 questions, ordered from opening to more pointed, that move the
conversation toward our goal without feeling like an interrogation.

24. Create an agenda:

Draft an agenda for this meeting.

Meeting: [purpose and attendees]
Topics to cover: [list]
Time available: [duration]

Structure it with time estimates per item, a clear desired outcome for
each, and a decision or next step at the end. Keep it to one screen.

25. Identify the decisions needed:

Based on this context, tell me what actually needs to be decided in this
meeting.

Context: [paste]

List each decision, who needs to make it, and what information is required
to make it well. Flag any decision that can't be made yet and why.

26. Prepare stakeholder notes:

Give me a quick profile of each person in this meeting.

Attendees and roles: [list]
What I know about them: [paste any notes]

For each: their likely priority, what they'll want from this meeting, and
one thing my executive should keep in mind when talking to them.

27. Turn documents into meeting prep:

Here is a document my executive needs to be across before a meeting: [paste]

Turn it into prep: a three-sentence summary, the five things they most need
to know, any numbers or claims worth double-checking, and two questions the
document leaves open.

28. Write talking points:

Write talking points for [executive's name] for [event / call / meeting].

Audience: [who they'll speak to]
Key messages: [list]
Topics they may be asked about: [list]
Anything to avoid: [if applicable]

Format as glanceable bullets, not a script. Group by topic.

29. Create a one-page prep doc:

Compress all of this into a single-page meeting prep sheet.

Raw material: [paste notes, context, agenda]

Include: purpose, who's in the room, three key points, the decision needed,
the main risk or objection to expect, and the outcome we want. Nothing that
doesn't fit on one page.

30. List follow-up tasks:

Turn these meeting notes into a clean summary and action list.

Raw notes: [paste notes or transcript]
Meeting: [name / purpose]
Attendees: [names and roles]

Format:
- Summary (three sentences)
- Decisions made
- Action items (owner + deadline each)
- Items for the next meeting
- Outstanding questions

CEO Briefing Prompts

A briefing that reads well but is wrong is worse than none. Use AI to structure and shorten, then check every fact yourself before it reaches the executive.

31. Daily CEO brief:

Create a short daily brief for [executive's name] from the following inputs:
[paste today's key emails, updates, calendar, and open items]

Structure:
- Top 3 things to know today
- Meetings and what each one needs from them
- Decisions waiting on them
- Anything urgent or at risk

Keep it under 200 words. Do not add anything not in the inputs.

32. Weekly executive brief:

Write a weekly brief for my executive covering the week ahead.

Inputs: [paste priorities, key meetings, deadlines, and open threads]

Sections: the week in one line, top priorities, key meetings, decisions
needed, risks to watch. End with the single most important thing for the
week. Keep it scannable.

33. Customer issue brief:

Brief my executive on a customer issue that's escalating.

What I know: [paste the details]

Give me: what happened, the current status, who's involved on both sides,
the business impact, what's been done so far, and the decision or action
we need from my executive. Stick to facts, flag anything unconfirmed.

34. Competitor update brief:

Summarize this competitor development for my executive.

Source material: [paste articles, notes, or updates]

Cover: what the competitor did, why it matters to us, likely impact, and
whether it needs a response. Separate confirmed facts from speculation.

35. Board prep brief:

Prepare a briefing to help my executive get ready for a board meeting.

Materials and updates: [paste what we have]
Audience: the board

Give a scannable one-pager: key topics, the numbers or updates to have
ready, likely questions from the board, and where the discussion could get
difficult. No backstory the board already knows.

36. Hiring pipeline brief:

Summarize where our open roles and candidates stand for my executive.

Pipeline data: [paste roles, stages, and notes]

For each role: stage, how many candidates, any at risk of dropping, and
what decision or action needs my executive's attention this week.

37. Project status brief:

Turn these project updates into a status brief for my executive.

Updates: [paste from team leads or tools]

For each project: status in one word (on track / at risk / blocked),
what changed, what's next, and anything that needs a decision. Lead with
whatever is off track.

38. Risk brief:

Based on everything here, tell my executive what the real risks are right now.

Context: [paste current situation, projects, and open issues]

List each risk with: what it is, how likely, the potential impact, and the
one action that would reduce it. Order by severity, not by how recent it is.

39. Travel day brief:

Create a brief for my executive's travel day on [date].

Itinerary and meetings: [paste]

Give a simple timeline: departure, arrivals, each meeting with purpose and
who's there, and buffer times. Flag the tightest connection and the one
meeting that matters most.

40. The “what does the CEO need to know?” brief:

Here is everything happening across the business this week:
[paste updates, emails, metrics, and open items]

Act as chief of staff and tell me the five things the CEO genuinely needs
to know, ranked. For each, one line on what it is and one line on why it
matters now. Cut everything that isn't in the top five.

Executive Update Prompts

This is the most requested skill: turning messy input into something an executive can absorb in seconds. The goal is clarity and brevity without losing anything that matters.

41. Turn messy notes into an executive update:

Turn these rough notes into a clean executive update.

Notes: [paste]
Audience: [CEO / leadership team]

Under 150 words. Separate progress, risks, and next steps. Calm,
professional tone. Do not invent details that aren't in the notes.

42. Make a status update clearer:

Rewrite this update so it's clearer and easier to scan.

Current version: [paste]

Keep every fact, cut the filler, use short sentences, and put the most
important point first. Tell me if anything is vague and needs a real number
or date.

43. Make an update shorter and more direct:

This update is too long and too soft. Make it shorter and more direct.

Current version: [paste]

Cut it by at least a third. Remove hedging words. Lead with the outcome.
Keep it professional, not blunt.

44. Use the progress / risks / asks format:

Reformat this into a progress, risks, and asks update.

Raw content: [paste]

Three clear sections. Under each, short bullets. In "asks," be specific
about what you need, from whom, and by when. If a section is empty, say so
rather than padding it.

45. Rewrite for clarity and brevity:

Rewrite this to be as clear and brief as possible without losing meaning.

Text: [paste]

Aim for half the length. Plain words. One idea per sentence. Then give me a
one-line version I could use as a subject line or Slack summary.

46. Turn Slack messages into an update:

Here are scattered Slack messages about a project: [paste]

Pull them into a single coherent update: what's happening, what's done,
what's blocked, and what's next. Ignore the chit-chat and keep only what a
leader would care about.

47. Write a Monday update:

Write a start-of-week update from these inputs: [paste priorities and plans]

Cover: the focus for the week, what's due, any risks, and what we need from
others. Keep it forward-looking and under 150 words.

48. Write a Friday recap:

Write an end-of-week recap from these inputs: [paste what happened]

Cover: what got done, what moved, what's carrying into next week, and any
wins worth naming. Positive but honest. Under 150 words.

Travel Planning Prompts

Do not paste passport numbers, payment details, personal identifiers, or sensitive travel data into public AI tools. Describe logistics in general terms and keep the sensitive details in your approved systems.

49. Build a travel itinerary:

Turn these travel details into a clean itinerary for my executive.

Details: [flights, hotel, meetings, times, cities. No personal ID numbers]

Format as a day-by-day timeline with times, locations, and confirmations.
Note time zone changes and flag any tight gaps between items.

50. Summarize flights and hotel:

Summarize this trip's logistics in a quick-reference block.

Bookings: [paste flight times, hotel name and dates. No card or passport data]

Give me: outbound flight, return flight, hotel with check-in/out, and
transfer notes. Short enough to read on a phone at the gate.

51. Create a travel brief:

Create a travel brief for my executive's upcoming trip.

Trip details: [dates, cities, purpose, key meetings]

Cover: why they're going, who they're meeting and when, where they're
staying, and the two or three things they most need to remember. One page.

52. Plan local logistics:

My executive is traveling to [city] on [dates].

Suggest practical local logistics: typical airport-to-downtown transfer
options, roughly how much travel time to allow between meeting areas, and
anything about local timing or customs worth knowing for business meetings.
Keep it general and note that I'll confirm specifics.

53. Build a packing and document checklist:

Create a pre-trip checklist for my executive's trip to [destination] for
[purpose], [number] days.

Include documents to confirm, tech and chargers, materials needed for the
meetings, and any trip-specific items. Do not ask me to store sensitive
document details here, just remind me to check them.

54. Write a travel confirmation email:

Draft a short confirmation email to [host / meeting contact] about my
executive's upcoming visit.

Details: [date, rough time, purpose]

Confirm the plan, ask for anything we still need from them (location,
parking, contact on the day), and keep it warm and brief.

55. Identify schedule risks in a trip:

Review this travel schedule for risks.

Itinerary: [paste]

Flag tight connections, meetings scheduled too soon after landing, time
zone traps, and any day with no buffer. For each, suggest a safer option.

56. Build a backup plan:

Create a simple backup plan for my executive's trip in case of delays.

Itinerary: [paste key flights and meetings]

For the two or three most likely disruption points, tell me the fallback:
who to notify, which meeting to protect, and what to move first. Keep it to
a short if-this-then-that list.

SOP Creation Prompts

The best way to make AI help repeats itself is to turn a good result into a documented process. Once a task has an SOP, you can hand it off or automate parts of it with a tool like Zapier or Make. For a dedicated set, see the SOP creation prompts.

57. Turn a repeated task into an SOP:

I do this task regularly and want to document it as an SOP.

Task: [name it]
How I currently do it, step by step: [describe]

Turn it into a clear standard operating procedure: purpose, when to use it,
numbered steps, tools needed, and a short checklist at the end. Write it so
someone else could follow it without asking me questions.

58. Improve an existing SOP:

Here is an SOP that isn't quite working: [paste]

Tighten it. Point out steps that are unclear, out of order, or missing.
Rewrite it to be easier to follow, and flag any step where mistakes are
most likely to happen.

59. Write an onboarding SOP:

Create an onboarding SOP for a new [role, e.g. junior assistant].

What they need to learn in week one: [list]
Key tools and access: [list]

Structure it as a first-week checklist with owners and links placeholders.
Keep it welcoming, not overwhelming.

60. Write an inbox SOP:

Document how I manage my executive's inbox as an SOP.

My current approach: [describe triage, labels, response rules]

Turn it into a repeatable process another assistant could follow, including
what to handle directly, what to escalate, and response-time expectations.

61. Write a calendar SOP:

Create an SOP for managing my executive's calendar.

Rules I follow: [meeting priorities, buffers, focus time, who gets access]

Write it as clear steps and standing rules, including how to handle
conflicts and reschedules and what always needs my executive's sign-off.

62. Write a meeting prep SOP:

Document our meeting prep process as an SOP.

How prep currently works: [describe]

Include: when prep starts before a meeting, what a standard brief contains,
where it gets saved, and the final check before it reaches the executive.

63. Write a travel SOP:

Create an SOP for planning executive travel.

Our usual process: [describe booking, briefing, confirmations]

Cover the steps from request to trip, what gets confirmed and when, the
briefing that's produced, and the sensitive-data handling rules. Note where
personal details must stay out of shared tools.

64. Turn a Loom or video walkthrough into an SOP:

Here is a transcript of a screen recording where I explain a task: [paste]

Convert it into a written SOP with clean numbered steps. Remove the "um"s
and tangents, keep the actual instructions, and add a short checklist so
someone can confirm they did it right.

65. Add quality checks to an SOP:

Here is an SOP: [paste]

Add a quality-control layer: the three or four things to verify before
marking the task done, the most common mistakes to avoid, and a final
review step. Keep the additions short and practical.

Stakeholder Communication Prompts

Much of the EA role is translating between people. AI can help you get the tone right, but you know the relationships, so you make the final call on wording.

66. Write a stakeholder update:

Write an update for [stakeholder group, e.g. department heads] about
[topic/project].

What's happening: [paste details]
What they need to know or do: [describe]

Keep it clear and respectful of their time. Lead with what's relevant to
them, not the full history.

67. Rewrite a message to be more diplomatic:

This message is accurate but could land badly. Make it more diplomatic
without losing the point.

Draft: [paste]
Recipient and relationship: [describe]

Keep it honest and clear, soften the edges, and remove anything that reads
as blame.

68. Write a firm but polite follow-up:

I need a follow-up that's polite but makes clear we still need this.

What we asked for: [describe]
How long it's been: [time]
Recipient: [role/relationship]

Under 80 words. Friendly opening, clear restatement of what's needed, a
specific deadline, and an easy next step.

69. Communicate a decision to multiple teams:

A decision has been made and I need to communicate it to several teams.

The decision: [describe]
Teams affected and how: [list]

Draft a clear message: what was decided, why, what changes for each team,
and who to contact with questions. Neutral, confident tone.

70. Write an alignment message:

Two teams have different understandings of [topic]. Write a message that
gets everyone aligned.

The gap: [describe what each side thinks]
The correct or agreed position: [describe]

State the shared goal, clear up the confusion without pointing fingers, and
confirm the single version everyone should work from.

71. Turn rough notes into a polished message:

Turn these rough notes into a polished, send-ready message.

Notes: [paste]
Recipient and purpose: [describe]
Tone: [professional / warm / formal]

Keep my intent, fix the structure and wording, and make it something I'd be
comfortable sending on my executive's behalf after review.

72. Write an escalation message:

I need to escalate an issue that isn't getting resolved.

The issue and its impact: [describe]
Who I'm escalating to: [role]
What I've already tried: [describe]

Draft a calm, factual escalation: what's happening, why it matters now, what
I've done, and the specific help or decision I need. No drama, just clarity.

73. Write a thank-you message:

Write a genuine thank-you note from [executive's name] to [recipient].

What they're being thanked for: [meeting, help, referral, support]
Tone: [warm and personal / brief and formal]

Under 100 words. Specific about what they did, not a template.

74. Ask for missing information:

I need to ask [person] for information without sounding pushy.

What I need and why: [describe]
Deadline: [if any]

Draft a short, friendly request that makes it easy for them to send exactly
what I need. Bullet the specific items if there's more than one.

Decision Summary Prompts

When an executive has to decide, your job is to make the choice clear, not to make it for them. These prompts organize the inputs so the decision is fast and well-informed.

75. Summarize a decision:

Summarize this decision so anyone can understand it in 30 seconds.

Context: [paste the discussion, options, and outcome]

Give me: what was decided, why, who's affected, and what happens next.
Four short lines, no jargon.

76. Compare options side by side:

Lay out these options so my executive can compare them quickly.

Options: [describe each]
What matters most in this decision: [criteria, e.g. cost, speed, risk]

Build a simple comparison against those criteria, then add a one-line
summary of the tradeoff for each option. Don't pick for them.

77. Identify the tradeoffs:

For this decision, spell out the tradeoffs clearly.

The decision: [describe]
The options: [describe]

For each option, what we gain and what we give up. End with the single
biggest tension my executive is really deciding between.

78. List the risks of a decision:

Here is a decision we're considering: [describe]

List the risks of going ahead and the risks of not going ahead. For each,
note likelihood and impact, and whether it's reversible. Keep it balanced,
not alarmist.

79. Capture owner and deadline:

Here are the decisions and actions from a discussion: [paste]

Turn them into a clean list where every item has a clear owner and a
deadline. Flag any item where the owner or deadline wasn't specified so I
can chase it down.

80. Maintain a decision log:

Add this decision to our decision log in a consistent format.

Decision: [what was decided]
Date, who decided, and why: [fill in]

Return one clean log entry: date, decision, owner, rationale, and any
follow-up. Use the same format each time so the log stays scannable.

81. Write a pros and cons summary:

Give me a clear pros and cons summary for this: [describe the choice]

What I know: [paste context]

Balanced lists, honest on both sides. Then one line on which way the
evidence leans and what would change the answer.

82. Flag what needs executive approval:

Here is a list of pending items and decisions: [paste]

Tell me which ones genuinely need my executive's approval versus which I
can handle or delegate. For the ones needing approval, note what they need
to know to decide quickly.

“Make This Executive-Ready” Prompts

“Executive-ready” usually means shorter, sharper, and calmer. Tell the AI exactly what that means for your leader and it will get much closer.

83. Make it shorter and sharper:

Make this shorter and sharper without losing anything important.

Text: [paste]

Cut the length by at least a third, remove over-explaining and repetition,
and put the key point first. Keep it professional.

84. Remove casual wording:

Rewrite this to sound more professional and polished.

Text: [paste]

Remove casual phrasing, filler, and anything too chatty. Keep it warm and
human, not stiff. Don't add corporate buzzwords.

85. Improve clarity:

This is hard to follow. Make it clear.

Text: [paste]

Restructure so one idea leads to the next, define anything ambiguous, and
tell me where the original was actually missing information.

86. Turn messy notes into polished copy:

Turn these messy notes into clean, ready-to-use copy.

Notes: [paste]
Purpose and audience: [describe]

Keep my meaning, fix the structure and grammar, and make it something I
could send or share after a quick review.

87. Make it more diplomatic and calm:

Make this message more diplomatic and calm.

Draft: [paste]

Keep the substance, remove any sharp or reactive tone, and make it read as
composed and professional even if the situation is tense.

88. Make it more confident:

This sounds tentative. Make it more confident without overpromising.

Text: [paste]

Remove hedging ("I think maybe," "just wanted to"), state things directly,
and keep it grounded in what we actually know.

89. Create three versions:

Give me three versions of this message so I can pick the best fit.

Original: [paste]
Recipient: [describe]

Version A: brief and direct. Version B: warm and relationship-focused.
Version C: formal. Same core message, different tone.

90. Turn a long text into an executive summary:

Summarize this long document into an executive summary.

Document: [paste]

Under 200 words. Lead with the single most important takeaway, then the key
points, then anything requiring a decision. Written for someone who may only
read this section.

Career Growth and Strategic Partnership Prompts

The strongest EAs act as a true partner to their executive. Use these to sharpen your own thinking, not just your output. If becoming an AI-savvy assistant is part of your goal, the use AI as a personal assistant guide is a good companion.

91. Become more strategic in your role:

I'm an executive assistant who wants to be more strategic, not just reactive.

My current responsibilities: [describe]
My executive's biggest priorities: [describe]

Suggest specific ways I could add more value: what to anticipate, what to
take off their plate, and what to start owning. Be concrete, not generic.

92. Prepare questions for your executive:

I have a short check-in with my executive coming up.

What's on my mind: [list topics or decisions I need clarity on]

Help me turn this into a tight set of questions that respects their time and
gets me the direction I need. Order them by importance in case we run short.

93. Improve your weekly 1:1:

Help me make my weekly 1:1 with my executive more useful.

How it currently goes: [describe]

Suggest a simple structure, what I should bring each week, and how to use
the time for alignment and decisions rather than status updates I could send
in writing.

94. Audit your personal workflow:

Act as a productivity coach and audit how I work.

A typical week for me: [describe main tasks and where time goes]

Point out where I'm likely losing time, what could be batched, what could be
templated, and the two or three changes that would free up the most hours.

95. Find tasks worth automating:

Here are the repetitive tasks I do most weeks: [list]

Tell me which are the best candidates to automate or template, which need a
tool versus just a saved prompt, and which should stay manual because they
need judgment. Suggest a simple first step for the top one.

96. Build a professional development plan:

Help me build a simple professional development plan for the next six months.

My role and goals: [describe]
Skills I want to grow: [list]

Give me a short plan: a few focus areas, one practical action for each, and
a way to track progress. Realistic for someone with a full-time EA workload.

5 Bonus Reusable Executive Assistant Prompts

Keep these five somewhere you can grab them in seconds. They work on almost anything that lands on your desk.

97. Clarify this request:

I've been asked to do something and I'm not fully sure what's wanted.

The request: [paste or describe]

Tell me the most likely intent, list the questions I should confirm, and
draft a short, professional clarifying message.

98. Turn this chaos into a plan:

Here is everything on my plate right now, in no order: [paste]

Organize it into a clear plan: what's urgent, what's important, what can
wait, and what I can delegate. Give me a simple order to work through today.

99. Identify what’s missing:

Review this and tell me what's missing before it's ready.

Item: [paste the draft, plan, or document]

List the gaps, unanswered questions, and anything a careful executive would
notice was left out. Then tell me the one thing to fix first.

100. Create an executive-ready summary:

Summarize this for a busy executive.

Content: [paste]

Under 150 words. Lead with what matters most, keep only what they need,
separate any decisions or actions at the end. Calm, professional tone.

101. Make this shorter, clearer, and more useful:

Improve this in three ways: shorter, clearer, and more useful.

Text: [paste]

Cut the length, sharpen the wording, and make sure the reader knows exactly
what to do next. Show me the improved version, then a one-line summary.

How to Customize These Prompts

Every prompt here is a starting point. The results get noticeably better when you add detail that’s specific to your executive and your organization. Before you run a prompt, consider adding:

• Your executive’s preferred tone and any phrases they always use or avoid
• Your company’s style and any formatting standards
• The exact audience for the output
• The deadline or urgency
• The output format you want (email, bullets, one-pager, table)
• The sensitivity level, so the AI knows what to keep general
• What not to include
• One or two examples of output you consider good, which is the fastest way to teach tone. This is called few-shot prompting

The single highest-value habit is keeping a short context file about your executive: their role, tone, priorities, and pet peeves. Paste it in with any prompt and you stop re-teaching every tool from scratch. The portable context guide walks through how to build one.

Common Mistakes Executive Assistants Make With AI Prompts

The most common mistake is giving the AI too little context and then being disappointed the output is generic. AI cannot read the room the way you can. If you would need to brief a new team member before handing them the task, the AI needs that same briefing in the prompt. A vague instruction like “make this better” gets you a vague result, because the model has to guess what “better” means to you.

The most dangerous mistake is pasting sensitive information into a public tool without checking policy first. HR records, legal matters, board materials, customer data, financials, and personal identifiers all need care. When in doubt, anonymize, describe things in general terms, or use an approved enterprise tool. A close cousin of this is asking AI to make a decision it should only support. AI can lay out options and tradeoffs, but the judgment about people, timing, and relationships stays with you and your executive.

Smaller habits cause slower leaks. Not specifying tone leaves you rewriting for voice. Not specifying format leaves you reshaping the output. Accepting a first draft without review is how errors reach an executive with your name on them. And not saving your best prompts means you rebuild the same thing every week instead of reusing what already works. The fix for most of this is boring but effective: keep a small library of proven prompts, use clear instructions, and always keep yourself in the loop before anything goes out.

Best Practices for Using AI as an Executive Assistant

A few practices separate assistants who get real value from AI from those who just experiment with it:

• Keep a library of reusable prompt templates, organized by task, with the placeholders left in.
• Create a short writing-style or context file for each executive you support, and paste it into any tool.
• Separate sensitive work from non-sensitive work, and only use approved tools for anything confidential.
• Ask the AI what context it’s missing before it drafts, instead of accepting a guess.
• Use AI to produce first drafts and organize information, never as the final authority.
• Review every important message before it goes out on someone’s behalf.
• Prefer company-approved AI tools, whether that’s ChatGPT, Claude, Gemini, or Microsoft Copilot.
• Turn any task you repeat into an SOP, then decide what parts are worth automating.

If you want to go further, the broader AI for work section, the AI tools directory, and the start here guide are good next stops. You can also browse related prompt packs for adjacent roles like consultants, managers, and project management.

Final Takeaway

AI will not replace the judgment, trust, and context that a great executive assistant brings. But it can help with the repetitive parts of the work: organizing, summarizing, drafting, clarifying, and preparing. The better your prompt, the less time you waste turning messy information into something useful. Start with a handful of these prompts on the tasks that drain you most, save the ones that work, and build from there.