How to Use Copilot for Executive Assistants

Define the support outcome and authority

Start with what the principal or authorised reader needs next: a decision brief, a meeting preparation pack, a reply draft, a travel comparison, a follow-up register or a status update. State the audience, deadline, time zone, confidentiality and approver. Also state what Copilot may do and may not do. Drafting an email is different from sending it; suggesting a meeting is different from booking it; listing an action is different from assigning it.

Keep a small authority map for recurring work: who may approve travel, pricing, external messages, access changes, client commitments and calendar changes. Copilot can format the map, but it cannot infer authority from a job title. If the instruction is ambiguous, return a question or NEEDS CONFIRMATION instead of guessing.

Choose the Microsoft 365 surface where the source lives

Use Outlook for email, calendar, attachments and reply context; Teams for meetings, chats and shared collaboration; Word for a controlled brief or letter; Excel for a tracker and its formulas; PowerPoint for a presentation. Microsoft documents different Copilot capabilities depending on the app, account, add-on licence and organisation settings. Confirm what the actual account can see before promising a workflow.

If Copilot cannot access a file, do not recreate the missing context from memory. Provide an approved excerpt or link, and ask it to list the sources it used. For shared or delegated mailboxes, preserve the existing mailbox owner and approval process. The tool surface is a boundary, not proof that every relevant item was searched.

Build an executive brief from evidence

A useful brief begins with the decision required, not a long summary. Ask for: decision or ask, confirmed facts, options, trade-offs, risks, dependencies, recommendation owner, deadline, unanswered questions and source links. Label proposals and recommendations as proposals. Keep numbers, dates and names beside their source.

Ask for a one-page version only after the evidence table is correct. Give it a fixed invariants list: it must not change the approved numbers, dates, owners or commitments. Compare the short version with the source-grounded draft before sending. An executive reader needs compression, but compression that removes a qualifier can change the decision.

Triage email with a human queue

Ask Copilot to group messages into decision needed, action owned by you, waiting on another person, reference and escalation. Include sender, thread subject, requested action, stated deadline, risk and source. Do not let a dramatic subject line become an automatic priority. Scan for payment instructions, access changes, legal notices, employee matters, customer incidents and confidential attachments before processing routine mail.

Use Copilot to explain why a message appears in a group, then decide the queue yourself. For ambiguous requests, draft a clarification email with the exact missing owner, date or decision. Never allow a clean inbox count to outrank an unresolved commitment.

Draft correspondence without changing the commitment

Give Copilot the recipient, purpose, approved facts, requested action, tone, length and prohibited additions. Ask it to return the draft plus a list of claims and commitments it introduced. Require placeholders for missing details. For a delicate message, ask for a direct version and a warmer version, then compare both against the approved facts.

Read the message in the real compose window. Check To, Cc, Bcc, reply-all, links, attachments, names, dates, time zones, promises and confidentiality. If the message changes a relationship, price, deadline, legal position or customer expectation, route it to the responsible person. A professional tone does not make an unauthorised promise safe.

Prepare meetings and preserve the record

Before a meeting, ask for purpose, attendees, prior decisions, open questions, documents to read, proposed agenda and decisions required. Label every item confirmed or proposed. Afterward, use available transcript, chat, notes and files to create a fact table, decision table, action register, risks and unresolved questions. Require NEEDS CONFIRMATION for missing owners, dates or unclear speech.

Compare speaker attribution and decisions with the source. Remove unnecessary personal detail and check the distribution list. The chair, meeting owner or designated minute-taker approves the record. Copilot can turn a record into a client follow-up after approval, but it should not become the record by default.

Build trackers that remain operational

For travel, events, hiring, procurement or board preparation, ask for stable columns, allowed values, owner, due date, status, source link and approval state. Keep one row per item and separate confirmed values from proposed options. In Excel, inspect formulas, ranges, dates, duplicates and totals against known examples. Do not fill a blank with a plausible value merely because a table looks incomplete.

A tracker needs an owner and a maintenance rule. Ask Copilot to identify stale rows and missing evidence, not to silently close tasks. Save the reviewed version in the team's normal location and preserve the source link so another assistant can audit why a row exists.

Protect discretion, access and personal data

Executive work often includes travel documents, health or family details, personnel matters, board material, legal advice, credentials and commercially sensitive plans. Use the approved work account, least-privilege access and the organisation's classification, retention and external-sharing rules. Copilot's permission model limits what a user can retrieve, but it does not make every retrieved detail appropriate for every recipient.

Ask for a privacy pass: what personal or confidential detail is present, who needs it, what can be removed, and whether the link permissions match the audience. Do not paste secret keys, passwords or unrelated personal data into a prompt. If a request conflicts with policy or authority, stop and escalate.

Create repeatable prompt templates and checkpoints

Save templates for inbox triage, decision briefs, meeting packs, action registers, travel comparisons and follow-up drafts. Each should contain source boundary, outcome, audience, time zone, required facts, exclusions, format and review gate. Start with a source inventory, then a structured table, then prose. This makes an error visible before it is hidden by polished writing.

At the end of each workflow, ask Copilot what it could not see, what it inferred, which claims lack a source and what needs approval. Keep the prompt, source version, final output and reviewer where the team's normal records live. Measure correction rate and missed actions, not only time saved.

Use a final send and calendar gate

Before any external or consequential action, verify recipient identity, reply-all, time zone, date, attachments, links, price, promise, approval and sensitivity. For a calendar item, check title, attendees, location, dial-in, agenda, duration, time zone and conflicts. For an email, open every attachment and link that matters. For a document, confirm version and permissions.

If Copilot proposes an action, treat it as a draft until the responsible human confirms. Record corrections and communicate them through the established channel. The assistant's role is to make the review faster and more complete, never to make the reviewer disappear.

A practical daily operating rhythm

At the start of the day, ask Copilot for a source-grounded queue from the mail, calendar and approved task context available to you. Require item, exact request, stated deadline, risk or dependency, and source. Split the result into decisions needed, actions you own, waiting items, reference and escalation. Review escalation first and open the originals for money, access, legal, personnel, customer or board matters. Do not let the assistant silently archive or reply.

Before an executive meeting, ask for a one-page pack with purpose, decisions required, confirmed facts, open questions, prior commitments and documents to read. Afterward, produce the action register and follow-ups only from approved notes or transcript. At the end of the day, ask for unresolved items and stale promises, then compare the list with the real task and calendar systems. Keep a correction log for wrong dates, missing attachments, incorrect names, unsupported assumptions, permission mistakes and actions that were not agreed. If errors recur because the source is ambiguous, improve the agenda, naming convention or approval rule instead of adding a more dramatic prompt.

Keep a principal-specific playbook without overfitting

A useful playbook records stable preferences that the principal or team has explicitly approved: preferred meeting buffers, time-zone conventions, document naming, briefing length, escalation channels, accessibility needs and phrases that should not be used. Store these instructions in the approved location and review them when the role, policy or calendar changes. Do not ask Copilot to infer private preferences from old email or treat a past exception as a permanent rule.

For each recurring workflow, keep a sample input, expected output shape, prohibited action and approval owner. Test the template on a synthetic or low-risk example before using it for a board meeting, client response or travel booking. Ask Copilot to show which playbook rule it applied and where the source context came from. This gives the assistant speed without turning a hidden memory into authority. The human assistant remains responsible for noticing when a familiar workflow is unusual and stopping for a fresh decision.

Make the approval state obvious

Use visible status values such as DRAFT, NEEDS OWNER, WAITING FOR APPROVAL, READY TO SEND and COMPLETED. Keep proposed text separate from the approved version, and never let a copied chat response look like the official record. A clear status reduces the chance that a colleague forwards a draft or assumes a calendar hold is a confirmed commitment. Ask Copilot to preserve the status label in every shortened version and to flag any sentence that could be mistaken for an approval. Status is part of the content, not decoration. It tells the next person what they may safely do.