AI for executive assistants looks different from AI for freelancers. You are usually employed, working inside one organisation, and the tools you may use are decided by IT, not by you. A good plan begins with that, not with a favourite chatbot.
Your job also carries something freelancers rarely hold: your executive's calendar, inbox and half-formed decisions. That is why this guide spends as much time on boundaries as on workflows.
What AI should and should not do in EA work
- AI drafts the first version. You know what the executive would actually say.
- AI summarises long threads and documents. You catch what the summary left out.
- AI turns a transcript into minutes and actions. You confirm owners and dates.
- AI suggests a schedule shape. You know who must never be double-booked and why.
- AI never receives board papers, HR matters, legal advice or anything price-sensitive unless your organisation has approved that tool for it.
Workflow 1: the pre-meeting brief
Before a meeting, the executive needs one page: who is attending, what happened last time, what is decided today, what is open.
In your approved tool, give it the agenda, the previous minutes and the relevant email thread, and ask for a one-page brief with a short list of questions the executive may be asked. If you use Microsoft 365, Copilot in Outlook can summarise an email thread, per Microsoft's support page, and Gmail with Gemini can produce an AI Overview of a thread when smart features are on, per Google's help page. You check the brief against the source before it lands on the desk.
Workflow 2: minutes and actions
Teams meetings can produce an AI recap with action items, if transcription is on and the organisation has the right licence, according to Microsoft's Teams support page.
Whatever tool produced it, put every action in a table: action, owner, due date, source line. Write "not stated" where the transcript doesn't say. You confirm with the owners and then circulate. My post on using AI meeting notes properly goes through seven useful outputs beyond a summary.
Workflow 3: inbox and calendar triage
Start with sorting, not sending.
Agree categories with your executive: needs a decision, delegate, reply with a template, schedule, read-only. Use your approved assistant to sort and suggest, then do the acting yourself. Keep every external send, and every calendar acceptance involving a senior person, behind your own decision. If your organisation permits it, a connector between Claude and Gmail or Calendar can help answer "what haven't I replied to?", explained in Claude connectors for Gmail and calendar. That depends entirely on your employer's rules.
Workflow 4: travel and event research
AI is useful for comparing flight windows, venue options or catering shortlists from the criteria you set.
Ask for a table of options with links and the date each price or detail was checked. Open the links. Fares, availability and policies move. The brief to the executive should say "I checked these on this date", not "the AI says".
Workflow 5: board and report packs
Packs are mostly formatting, consistency and chasing.
Use AI to produce a contents list, check that headings and numbering match, draft the cover note and list which papers are still outstanding. The content of the papers, especially anything confidential, should only go through a tool your organisation has approved for that classification. If you are unsure, do the formatting check on a version with the sensitive text removed.
How this differs from freelance admin work
A virtual assistant chooses tools per client. You usually cannot. Your organisation has a licence, a security team and a policy, and your executive carries the reputational risk if something leaks. So your skill is not tool-hopping. It is getting very good with the one or two approved tools, knowing exactly where their limits are, and being the person who can explain the rules to colleagues.
It also means your best workflows are the ones that live inside Outlook, Teams, Gmail or Calendar already, with nothing extra to approve.
Getting AI use approved by your boss and IT
Many EAs fall into one of two traps: using a personal ChatGPT account without telling anyone, or being told to "use AI" with no rules.
Fix both with a one-page request:
- the three tasks you want to use it for
- the approved tool you propose (Copilot or Gemini if the organisation already pays for it)
- the information you will never enter
- what a human always checks
- who to tell if something goes wrong
Get a yes in writing from your executive and IT. Microsoft states that under enterprise data protection, prompts and responses are not used to train its foundation models, per Microsoft's privacy page, and Google makes a similar statement for Workspace in its AI privacy page. Those are claims about specific business products. A personal free account is not the same thing. See whether ChatGPT trains on your chats for the settings that matter on personal plans.
What never goes into an unapproved tool
- board and committee papers
- HR, performance and pay matters
- legal advice and anything under privilege
- price-sensitive or unannounced information
- personal details of staff, clients or the executive's family
- passwords, banking details and travel documents
If it would embarrass your executive in a newspaper, it does not go into a tool nobody approved.
The small stack worth learning
- Microsoft Copilot (Microsoft has renamed Microsoft 365 Copilot) or Gemini in Workspace: whichever your organisation provides
- The meeting recorder or transcript your organisation allows
- Your calendar and email rules: categories and templates that make AI sorting accurate
- A shared prompt library: your five best prompts, saved where you can find them
Your first build: one meeting brief
Pick next week's most routine meeting. Make the brief in your approved tool, check every name and date, and note how long it took against doing it from scratch. Do it for three meetings, then show your executive.
Then work out which task to extend next with the what to automate first test. If you want a community working through this with you, see Wright Mode.