RESEARCH REPORT PART VIII APR 2026 ARUP DIGITAL ADVISORY WORKFLOWS

The Outlook
workflow, reclaimed.

How the advisory team should use Copilot in Outlook — to stop reacting to email and start directing it. Five distinct Outlook AI tools, six use-case workflows, and the shift from inbox-as-interruption to inbox-as-directed-queue.

The premise
Advisory consultants spend a large share of their working day in Outlook. Most use one Copilot feature (Summarise) and ignore the other four. That's the single biggest unexploited productivity opportunity in the Microsoft stack — not because Outlook Copilot is revolutionary individually, but because every feature applies twenty times a day.
5 tools
Distinct Outlook
AI surfaces
6
Use-case
workflows
High
Share of the day
spent in Outlook
Daily
Lowest-effort,
highest-frequency Copilot wins
01 / CORE SHIFT

From reacting to directing.

The mental model matters before the features do. Without it, Copilot in Outlook is a polite set of speed-ups on an inbox that's still running the show. With it, Outlook becomes the first place Copilot actually changes how the work gets done.

Most advisory consultants open Outlook in the morning and react. They scroll to the top, pick the first unread, respond or not, move to the next. The inbox sets the pace. Four hours later they haven't opened a deliverable document yet. It's the single most common complaint in consultant surveys — "I spent all morning on email and got nothing done" — and it's a direct consequence of the reactive pattern.

"Most people open Outlook and react. They let their day happen to them, chasing emails, juggling meetings, firefighting instead of leading. Copilot flips that dynamic."

Copilot in Outlook doesn't make email faster. It restructures the sequence in which email gets touched. The three shifts:

From scrolling to triaging

Old pattern: read top-to-bottom, deal with whatever appears. New pattern: ask Copilot to rank and summarise the inbox once, then work through in priority order. Five minutes at the start of the morning saves thirty later — and more importantly, the first email you touch is the most important one, not the most recent.

From drafting to directing

Old pattern: compose every reply from scratch, worry about tone, rewrite three times, send. New pattern: describe the reply in a sentence, let Copilot draft it, run Coaching for tone, send. You're not writing the email; you're directing what the email should accomplish. The model handles the prose.

From preparing-on-arrival to arriving-prepared

Old pattern: walk into a meeting, scramble through emails to remember context, spend the first ten minutes orienting. New pattern: Prepare for Meeting produces a briefing before the meeting — emails, files, chats, prior decisions, related context — so you arrive knowing what's been said and what's likely to come up. The thirty seconds of prompt work up-front saves ten minutes of awkward catching-up in the meeting.

None of this requires revolutionary AI. It requires using five features that exist in Outlook right now and that most consultants have never turned on. The return compounds because every feature applies multiple times per day across every working day.

The honest number
A consultant who uses all five Copilot-in-Outlook features daily gets meaningful time back each week — not a single dramatic save, but the aggregate of one minute here, three minutes there, across twenty or thirty email interactions a day. The features don't feel transformative individually. That's precisely why they're so underused. The evidence is in the cumulative week, not any single prompt.
02 / THE FIVE TOOLS

Five distinct Outlook AI surfaces — all underused.

"Copilot in Outlook" means at least five different features, living in different parts of the interface. Most consultants use one (Summarise). Each of the other four is high-ROI on its own. Before the workflows, the tour.

Core featureTop of threadEvery client, every platform
1 · Summary by Copilot
Click the Summarise button at the top of any email thread. Copilot extracts key points, decisions made, open questions, action items — and adds numbered citations that when clicked jump to the specific email they came from. Works on threads of any length. Auto-detects the language of the emails and summarises in that language. On new Outlook, can also summarise attachments (PDF, Word, PowerPoint) via the Summarise a file option. Works even on complex 15-reply threads where the original question has been reframed four times.
Highest-ROI moments
  • Joining a thread someone just forwarded you
  • Catching up after holiday or illness
  • Reviewing a thread before a related meeting
  • Deciding whether a thread needs your involvement at all
Works less well on
  • Encrypted or IRM-protected messages
  • Threads with heavy attachments (read them too)
  • Emails marked with MIP labels (some variants)
  • Signed/encrypted messages — feature unavailable
Compose feature/draftTone + length controls
2 · Draft with Copilot
Open a new email or reply, click the Copilot icon in the compose toolbar, select Draft with Copilot. Type your prompt — a single sentence is fine — and hit Generate. A full draft appears, which you can Keep, Discard, Regenerate, or Adjust (tone and length). Tone options: Formal, Casual, Concise, Confident, Enthusiastic. Length options: short, medium, long. On replies, Copilot reads the whole thread context so you don't have to repeat it in the prompt. Works in New Outlook for Windows, Outlook on the Web, Classic Outlook, Outlook for Mac, mobile. Does not support plain-text emails — switch to HTML in Settings first.
Use it for
  • Meeting follow-ups ("thanks for the conversation…")
  • Routine updates that are boilerplate-shaped
  • Bad-news emails where tone is hard to get right
  • Introductions and handoff emails
Not for
  • Client communications where your voice must be distinctive
  • Emails that contain judgement or opinion — draft those yourself
  • Short acknowledgments where typing is quicker
  • Plain-text-mandated threads
Most underusedAfter drafting100+ character threshold
3 · Coaching by Copilot
Write your own email draft (at least 100 characters), then click the Copilot icon → Coaching by Copilot. It reviews your message on three dimensions: tone, clarity, and reader sentiment — how the recipient will likely perceive it. Suggestions appear inline. Apply all accepts everything; individual suggestions can be accepted piecemeal. Unlike Draft (which writes for you), Coaching keeps your voice and only adjusts what lands wrong. This is the difference-maker for any emotionally-loaded email — bad news, scope pushback, declines, apologies.
When it shines
  • Any email you're putting off sending
  • Pushback on scope or timeline
  • Delivering bad news to a client
  • Declining a request or invitation
  • Emails that may be read in the wrong emotional register
Two rules
  • Draft 100+ characters first — below the threshold it won't engage
  • Apply suggestions individually, not in bulk — you want to keep your voice
  • Read the final version aloud before sending; Coaching can over-soften
Hidden gemEmail thread → meeting~1 min vs 5
4 · Schedule with Copilot
On any email thread where attendees have agreed a meeting is needed, click the Schedule with Copilot button on the ribbon (or in the compose toolbar). Copilot creates a meeting invite with attendees pre-populated from the thread, subject line derived from the discussion, a draft agenda pulled from what was debated, and sometimes a suggested pre-read or attached related files. You adjust date/time and send. The whole operation takes ~60 seconds vs 5 minutes of manual calendar juggling. For consultants who schedule several meetings a week from email threads, this single feature pays back 20+ minutes every week.
Use it every time
  • Email ends with "let's have a quick call"
  • Client asks for a workshop or working session
  • Internal thread concludes with "let's align offline"
  • Anyone suggests setting up a pre-read meeting
Always check before sending
  • The attendee list — Copilot may pull too many or too few
  • The proposed date/time slot if Copilot suggests one
  • The agenda tone — formality may need adjusting
  • Whether the pre-read it attaches is actually appropriate
Cross-appCopilot Chat in OutlookLicenced only
5 · Copilot Chat in Outlook (with Prioritize + Prepare)
Click the Copilot icon in the Outlook navigation header to open Copilot Chat beside your mail. This is where three of the most powerful features live: Prioritize my inbox (automatic High/Normal/Low tagging based on rules you define), Prepare for meeting (gathers all emails, chats, files, prior meetings related to a calendar item), and cross-app questions ("which unread emails are most important + what's the prior context on each from our Teams chats and SharePoint files?"). Requires a Microsoft 365 Copilot add-on licence, not Copilot Pro and not free Copilot Chat. Without the licence, Outlook has only Summarise/Draft/Coaching — the cross-app depth is gated.
Unique capabilities
  • Prioritize my inbox — custom rules, cross-client sync
  • Prepare for meeting — briefing pulled from Graph
  • "What's my next meeting with X, and what's on the agenda?"
  • Cross-app synthesis — emails + Teams + docs in one answer
  • Natural-language email triage actions (flag, archive, pin)
Tune Prioritize carefully
  • Use phrases not keywords ("it's from…", "mentions…")
  • Start with 3-4 rules, refine over 2 weeks
  • Rules only apply to new mail — history is not re-evaluated
  • Only works on your main inbox — not rule-filtered subfolders
The licence reality
Summary, Draft, and Coaching work with any Microsoft 365 personal, family, or Copilot Pro subscription. Prioritize my inbox, Prepare for meeting, Schedule with Copilot, and Copilot Chat in Outlook require the full Microsoft 365 Copilot add-on (the paid enterprise licence). If the advisory team has the full licence, all five tools are available — if the team is on Pro only, features 4 and 5 are unavailable and the cross-app magic doesn't work. Check your tenant licence before training the team on workflows they can't actually run.
03 / PREREQUISITES

Set up the rules once.

Unlike the Word or Excel workflows, Outlook Copilot doesn't need a branded template or clean data — it needs you to teach it what matters. Ten minutes configuring Prioritize rules and HTML compose mode up-front makes every downstream feature meaningfully better.

The ten-minute setup

1. Confirm your licence. File → Account → check for Microsoft 365 Copilot. If it's there, all five tools are available. If not, Summary/Draft/Coaching still work but Prioritize, Prepare, Schedule are unavailable. Ask IT before investing in the advanced workflows.

2. Switch compose to HTML. Settings → Mail → Compose and reply. Under message format, select HTML. Draft with Copilot does not work on plain-text compose — this is the single most common "why isn't Copilot working" question in the first week. Fix it once and forget about it.

3. Enable Prioritize my inbox. Click the arrow next to the Copilot icon at the top-right → Prioritize. A setup wizard walks you through rules. Do this on desktop — once configured, priorities sync across all clients (mobile, web, Mac).

4. Write 3-5 prioritisation rules. Use phrases, not keywords. Example rules for an Arup advisory consultant:

Mark as High priority if the message is from a director-level client contact, mentions the project code for an active engagement, contains a question the sender expects me to answer, mentions a deadline within 48 hours, or is from my line manager and marked for action.

Copilot learns over time but explicit rules beat machine learning for the first 30 days. Expect to refine the rules twice in the first fortnight — you'll notice false positives (newsletters from VIP senders marked high) and adjust.

5. Consider a few Scheduled Prompts. Go to the Microsoft 365 Copilot app → create a prompt → hover over it → Schedule this prompt. Weekday 8am inbox triage and Friday 5pm week-ahead prep are the two worth setting up first. These run automatically; the output appears as a Copilot chat when you arrive. More on this in use case 6.

None of this is mandatory — Copilot works without it. But ten minutes of upfront configuration is what separates consultants who get 30 minutes a week from Outlook Copilot from consultants who get 90.

What Prioritize won't evaluate
Prioritize only operates on your main Inbox, not on messages that get auto-routed to subfolders by rules. It also skips: mail marked low importance by sender, out-of-office notifications, meeting invites/declines, mail you sent yourself, encrypted messages, quarantine messages, and anything under ~15 words. If you have elaborate rule-based filing, Prioritize will have less to work with. Consider disabling some filtering rules in favour of letting Copilot triage — the two systems fight each other for anything routed away from the main inbox.
04 / USE CASE 1

Morning triage in under five minutes.

The workflow that changes the day. Instead of opening Outlook and scrolling from the top, ask Copilot Chat to rank the unread, synthesise what matters, and defer or skip the rest. Every consultant who adopts this habit reports the same thing: the day starts on their terms.

~5 minVery low effortCopilot ChatDaily habit
Triage first, read second
Use this when
Every single working morning — or after any extended absence. Typical scenarios: morning start, return from a 2-hour meeting, Monday after a weekend, first day back from leave, returning from a client day out.
01
Open Outlook (don't scroll yet)
02
Click the Copilot icon in the nav header
03
Paste the triage prompt
04
Review the priority ranking
05
Deal with top 3-5, defer the rest
Review my unread emails from the past 24 hours. For each unread email, give me: 1. Who sent it and their role 2. One-line summary of what they want or are telling me 3. Priority score 1-5 where: - 5 = urgent client work, time-sensitive deadline, or direct question from a director-level stakeholder - 4 = active project work requiring my attention this week - 3 = internal team comms that need a response but not urgent - 2 = FYI or informational - 1 = newsletters, distribution lists, can archive 4. Suggested action: reply now / reply today / defer / archive Group output into three buckets: - **Deal with now** (priority 4-5) - **Deal with today** (priority 3) - **Defer or archive** (priority 1-2) For any item marked "Deal with now", synthesise any related context you can find from my Teams chats, SharePoint files, or recent meetings that would help me respond well. Cite your sources. At the end, suggest the order I should respond in and flag any threads where I might be waiting on someone else.
The hardest part is trusting the ranking
The first week of this workflow, you'll second-guess Copilot's rankings — is this really more urgent than that? Two weeks in, you'll realise the rankings are better than yours because they're unbiased by who emailed most recently or whose name is in bold. The habit to build: act on the top three in the order Copilot proposes. Don't scroll past them to check if there's something "more urgent" further down. If something truly urgent is lurking, you'll see it within five emails. The discipline is the point.
05 / USE CASE 2

Joining a long thread late.

Someone adds you to an eight-reply client thread at 4pm. You have no context. Previously you'd either skim and hope, or spend ten minutes reading carefully. Summarise by Copilot collapses the decision to thirty seconds.

~30 sec - 2 minVery low effortSummarise by CopilotMultiple times daily
Catch up, contribute coherently
Use this when
You've been added to a thread in progress. Typical scenarios: CC'd on a client back-and-forth you weren't previously part of, forwarded a thread by a colleague who wants your input, returning to a thread you ignored for a day, about to reply to someone whose earlier context you've forgotten.
01
Open the thread
02
Click Summarise at the top
03
Read the summary (~30 sec)
04
Click citations to verify key claims
05
Draft reply with context

The workflow is as simple as the four-step description above, but a few subtleties matter:

Read the summary with intent. Look specifically for: what's being asked of me? what's already been decided? what's controversial in this thread? Copilot's summary will usually surface all three clearly if you look for them.

Click citations for anything you'd cite yourself. If your reply is going to reference a decision or a specific claim in the thread, click the numbered citation and verify the wording in the original email. Copilot's paraphrasing is usually accurate, but it can occasionally flatten a nuance — exactly where you don't want to be wrong.

If the thread has attachments, summarise them too. In New Outlook, the Summary by Copilot option includes Summarise a file for any attached PDF, Word, or PowerPoint. Use it for long attachments — a client proposal, a regulatory document, a technical spec. Ten seconds to summary vs fifteen minutes to read.

Then use Draft with Copilot for the reply. The thread context is already in the model's working memory. A prompt like "Draft a response confirming we can meet Thursday's deadline and asking two clarifying questions about scope" produces a well-contextualised draft that references the right prior points without being told to.

The subtle efficiency
Most consultants save the obvious time — the ten minutes of reading becomes thirty seconds of summary. The subtler win is the second-order effect on reply quality. Because Copilot surfaces "who's asked for what" and "what's already been decided" explicitly, replies drafted after a Summary tend to be more directly responsive to the actual question, and less likely to re-litigate something the group already agreed. The summary doesn't just save time — it improves the signal-to-noise of what you send back.
06 / USE CASE 3

The email you've been avoiding.

Bad news. Pushback on scope. Declining an invitation. The emails people put off for hours or days and then send half-heartedly. Coaching by Copilot is built specifically for this — and it's the single biggest advisory-grade quality improvement you can unlock in ten seconds.

~5 minLow effortDraft + CoachingHigh-stakes emails
Write it rough, coach it right
Use this when
The email feels hard to start. Typical scenarios: telling a client the answer is no, pushing back on unrealistic scope, explaining a delay, declining a senior person's invitation, apologising for a mistake, giving difficult feedback, delivering a commercial decision that won't be welcome.
01
Write the draft bluntly — don't worry about tone yet
02
Make sure you have 100+ characters
03
Click Copilot → Coaching by Copilot
04
Apply suggestions individually
05
Read aloud before sending
# Write this bluntly first — the badness is the point. # Coaching will tell you where it lands wrong. Hi Sarah, We can't hit your March 15 deadline. The team is stretched on two other engagements and the scope has grown since the kickoff. Realistically we can deliver the first phase by end of March and the full piece by mid-April. Let me know if that works. If it doesn't we'll need to talk about reducing scope or bringing in another resource, which will increase the fee. Best, [Name]
# Coaching identifies: opens too abruptly, leads with the bad news, # the "let me know if that works" reads slightly passive, and the # scope/fee sentence sounds transactional given the client relationship. Hi Sarah, Thanks for the quick follow-up yesterday — really appreciate the context on what's behind the March 15 date. I want to be straight with you about where we are. The team is working on two other engagements at the same time, and the scope has grown meaningfully since our kickoff. I don't think we can responsibly commit to delivering the full piece by March 15 without compromising quality. A realistic path that still gets you what matters most: - First phase (the [specific element they most need]) by end of March - Full piece by mid-April If the March 15 date genuinely can't move, I'd love to talk through two options with you — either a narrower scope we can confidently deliver, or bringing in an additional resource to accelerate. Both have trade-offs I'd like to walk through together rather than decide over email. Happy to jump on a call tomorrow or Thursday if useful. Best, [Name]
The only rule: read it aloud before sending
Coaching by Copilot is remarkable at softening hard edges — but occasionally it softens so much that the actual message becomes ambiguous. The reader can't tell if you're saying no, or hedging, or perhaps, maybe, it depends. Read the final version aloud before sending. If the core answer isn't clear after a single read-aloud, you've over-coached. Dial back one or two of the suggestions — keep your voice, your directness, and your actual answer intact. Coaching is a tool to sharpen tone, not to blunt meaning.
07 / USE CASE 4

Converting "let's meet" into a meeting.

The hidden gem of Outlook Copilot. Most consultants have never noticed the Schedule with Copilot button exists — and so every time an email thread ends with "let's set up a quick call," they open the calendar and build the meeting manually. Five minutes, twenty times a week. Schedule with Copilot makes it sixty seconds.

~1 minVery low effortSchedule with CopilotEmail → calendar
The thread ends with "let's set up a call"
Use this when
An email thread concludes with a meeting commitment. Typical scenarios: client asks for a follow-up call, internal thread ends with "let's align offline," workshop participant suggests a working session, request for a kickoff or a review, anyone saying "shall we meet on this?"
01
Open the email thread
02
Click Schedule with Copilot on the ribbon
03
Review the attendee list and agenda
04
Pick a date/time that works
05
Send

What Schedule with Copilot actually generates — and what you should check — before sending:

What gets pre-filled

Subject line — usually derived from the thread topic. Often fine but sometimes overly generic. Sharpen it before sending.

Attendees — everyone on the email thread by default. Always review this list — the client may have CC'd someone who doesn't actually need to be in the meeting, or an internal stakeholder who shouldn't see client-only discussions. Prune before sending.

Agenda — drafted from the thread. Copilot extracts "here's what we're meeting to discuss" from the email conversation and renders it as bullet points in the invite body. Usually accurate but sometimes too detailed for a short meeting or too vague for a substantial one.

Suggested pre-read — sometimes attached. Copilot may find a relevant document referenced in the thread and attach it. Double-check it's the right version and genuinely appropriate to share.

What Copilot can't do yet

Find the time slot that works for everyone. You still need to pick date and time. Copilot may suggest the earliest mutually-available slot based on everyone's calendars, but it doesn't definitively decide. For external attendees with calendars you can't see, you still have to propose and wait.

Handle more than two other participants cleanly. Schedule with Copilot in Outlook Chat supports up to two other people directly; beyond that, you're back to manual attendee management. For a five-person meeting, expect to do some work yourself.

Set the right duration. It usually defaults to 30 or 60 minutes. If you need 15 or 45, set it manually.

The time the feature really saves
The calendar invite itself is the visible output. The invisible output — and arguably the bigger win — is that the agenda bullets in the invite body mean attendees arrive prepared. Historically, "quick call to discuss" invites with no agenda result in meetings that spend the first 10 minutes orienting. An invite with a clear Copilot-drafted agenda creates a different meeting: attendees see the bullets before walking in, know what will be discussed, and can come with views ready. The scheduling speedup is nice; the meeting quality uplift is where the real value sits.
08 / USE CASE 5

Arriving prepared for every meeting.

The meeting before the meeting. Prepare for Meeting pulls together emails, chats, files, and prior decisions about any calendar item — and produces a briefing that lets you walk in knowing exactly what's happened so far and what's likely to come up.

~3 minVery low effortPrepare for meetingBefore every meeting
The three-minute pre-brief
Use this when
Any meeting where walking in cold would cost credibility. Typical scenarios: client meeting with a client you don't speak to weekly, internal review with stakeholders across practice areas, workshop on a topic that's had prior email discussion, steering committee with decisions you need to recall, first meeting of the week covering several projects.
01
Open the calendar item (15-30 min before the meeting)
02
Click Prepare for Meeting
03
Read the briefing — emails, files, chats, prior decisions
04
Note any specific points you need to raise
05
Walk in prepared

What Prepare for Meeting actually produces

A structured briefing with (typically) four sections:

Meeting context — subject, attendees, stated purpose. Copilot also infers the actual purpose from related emails and chats, which occasionally differs from what the organiser put in the invite.

Key related emails — the threads connected to the attendees, topic, or explicitly-referenced files. Summarised, with citations back to the original emails.

Key related files — SharePoint or OneDrive documents associated with the attendees, project, or topic. Brief description of each and whether it's changed recently.

Open items and prior decisions — what's been decided in previous meetings or threads involving these people, and what's still unresolved. This is the single most valuable section for recurring meetings.

When Prepare for Meeting struggles

The feature needs related content to work with. If a meeting has no prior email thread, no shared documents, and no previous meetings with the same attendees, Copilot's briefing will be generic and unhelpful. New meetings with new people on new topics → Prepare is of limited value. Recurring meetings with rich history → Prepare is transformative.

It also doesn't work well for external-heavy meetings where most of the attendees are outside Arup and the related context lives in their organisations, not yours. The briefing will reflect your side of the conversation only.

The deeper-briefing follow-up prompt

The default briefing is good. A targeted follow-up in Copilot Chat makes it great. After Prepare for Meeting has produced its output, ask a follow-up like:

For my 2pm meeting with [client name]: 1. What questions are they most likely to ask me? Base your answer on the topics that have come up in our prior email threads with this client. 2. What commitments have we made to them in past meetings or emails that haven't been followed through yet? I don't want to be surprised. 3. Are there any topics where our internal team has different views? I need to know where there's ambiguity before the meeting so I don't say one thing while my colleague is saying another. 4. Based on the last three meetings with this client, what seems to be their decision-making pattern? Who speaks first, what do they push back on, what do they agree to quickly? Cite the specific emails, meetings, or files for each point.
The meeting-quality compounding effect
A consultant who arrives prepared makes different contributions than one who's scrambling to catch up in the first ten minutes. Prepare for Meeting used consistently shifts where the consultant's attention goes during the meeting itself — from orientation to contribution. Over weeks, that changes how clients and colleagues perceive the consultant's quality of engagement. This is one of those compounding habits where the individual instance saves ten minutes but the behaviour change over six months reshapes relationships. Worth building as muscle memory.
09 / USE CASE 6

Scheduled prompts as standing assistants.

The feature almost no-one uses. Copilot Chat supports Scheduled Prompts — prompts that run automatically at a time and frequency you set. Used well, they turn Copilot from a tool you have to invoke into a quiet assistant that prepares your briefings before you arrive.

~10 min setupVery low effortCopilot Chat · Scheduled PromptsSet once, run forever
Have Copilot brief you before you arrive
Use this when
You find yourself running the same prompt repeatedly. Typical scenarios: you triage the inbox the same way every morning, you prepare for next week's meetings every Friday afternoon, you review the week's emails for unfinished items every Friday evening, you need to know what changed in project X's SharePoint every Monday.
01
Open the Microsoft 365 Copilot app
02
Create a new prompt (the triage one from use case 1)
03
Hover over it → Schedule this prompt
04
Pick time and frequency (e.g. weekdays 8am)
05
Optional: get email notification when it runs

Three worth building from day one

Review unread emails from the past 24 hours. For each one: sender, one-line summary, importance score 1-5, suggested action (reply now / reply today / defer / archive). Group into: Deal with now (4-5), Deal with today (3), Defer (1-2). For anything in the "Deal with now" bucket, synthesise any related context from my Teams chats or SharePoint files and draft a suggested reply. I'll edit and send. Also surface: any calendar conflicts for today, and anyone still waiting on a response I owe them from the past week.
Review next week's calendar and prepare me for the week. For each meeting next week: - Title and attendees - What it's for (from the invite and any prior context) - What pre-read exists, and whether I've looked at it - Any open items from previous meetings with these people Highlight: - Meetings where I'm currently unprepared - Any conflicts or back-to-back schedules that look painful - Action items from THIS week that I haven't closed out yet - Any client-facing meetings where I should block prep time Produce a one-page "state of the week ahead" briefing I can read on Monday morning.
Review my activity this week. From my sent emails, meetings attended, and documents I've edited: 1. What did I commit to this week that I haven't yet followed up on? Include who I committed to and by when. 2. Any emails I read but didn't reply to where the sender is likely still waiting? 3. Any draft emails I started but didn't send? 4. Any meetings where I took action items and haven't actioned them yet? Produce a "loose ends" list I can work through before logging off for the weekend.
The shift from reactive to proactive
Scheduled Prompts are the single feature in this entire chapter that changes the relationship between you and Copilot most fundamentally. Without them, Copilot is a tool you think to invoke — and you forget to invoke it exactly when you most need it. With them, Copilot arrives before you do, with the briefing already in your chat pane when you open the app. Five minutes of configuration once a week; hours of saved mental overhead. Almost nobody does this. Start.
10 / DECISION MATRIX

Which tool, when?

Six use cases, five tools, one table.

Your scenarioUse thisSurfaceTime
Start of day — triage the inboxCopilot Chat · Prioritize my inboxOutlook nav~5 min
Just added to a long email threadSummary by CopilotThread top~30 sec
Need to reply to something straightforwardDraft with CopilotCompose toolbar~1 min
Email you've been avoiding — bad news, pushbackDraft your own + Coaching by CopilotCompose toolbar~5 min
Thread ends with "let's set up a call"Schedule with CopilotThread ribbon~1 min
Walking into a meeting in 15 minPrepare for MeetingCalendar item~3 min
Catch up after 2 hours of meetingsCopilot Chat · inbox summaryOutlook nav~2 min
Every Monday, already caught upScheduled prompt · week aheadCopilot Chat0 min Monday
End of day — what didn't I finishScheduled prompt · loose endsCopilot Chat0 min trigger
Long thread with 3 PDF attachmentsSummarise + Summarise a fileNew Outlook~2 min
11 / DO'S & DON'TS

Common failures — and their fixes.

Patterns from training advisory teams on Copilot in Outlook. Almost every bad outcome maps to one of these.

Do
  • Set compose format to HTML before anything else. Draft with Copilot doesn't work in plain text.
  • Spend ten minutes configuring Prioritize rules up front. Use phrases ("it's from…", "mentions…") not single keywords.
  • Triage every morning using Copilot Chat. Don't scroll. Ask Copilot to rank, then deal with the top 3-5 in order.
  • Summarise before replying to any thread you joined mid-conversation. Click the citations to verify anything you'll quote back.
  • Use Coaching by Copilot on every emotionally-loaded email. Draft blunt first, let Coaching soften, read aloud before sending.
  • Use Schedule with Copilot every time a thread ends with "let's meet." Never manually build the invite again.
  • Prepare for Meeting 15 minutes before any meeting with meaningful prior context. Three minutes invested; ten saved in the meeting.
  • Build 2-3 scheduled prompts — morning triage, Friday week-ahead, Friday loose-ends. Setup once, compound forever.
Don't
  • Accept Coaching's "Apply all suggestions" blindly. Apply individually or you'll lose your voice and may over-soften the message.
  • Send a Draft with Copilot email without reading it carefully. Copilot can hallucinate project names, dates, or commitments.
  • Trust Prioritize in the first week. It's learning. Expect false positives; refine rules twice in the first fortnight.
  • Skip the attendee review on Schedule with Copilot invites. It defaults to everyone on the thread — sometimes that's wrong.
  • Use Prepare for Meeting on a brand-new meeting with new people. It needs prior context to work well; it'll produce a generic briefing otherwise.
  • Let scheduled prompts run on sensitive matter without thinking about outputs. They execute automatically — whoever sees your Copilot chat sees the output.
  • Forget that Prioritize doesn't work on rule-filtered subfolders. If you have aggressive filing rules, Copilot can't evaluate what it can't see.
  • Use Copilot on encrypted or IRM-protected emails. It won't work — and shouldn't. Those protections exist for a reason.
The unifying mental model
Think of Copilot in Outlook as three habits, not five features. Triage — always rank before reading. Coach — always get a reader's-ear view before sending anything emotionally loaded. Prepare — always know what's happened before walking into what's next. Every specific feature fits one of those three habits. The consultants who internalise the habits get the 90-minute weekly return. The ones who just use Summarise and nothing else get eight minutes.
Playbook implication
Outlook is where the lowest-effort, highest-frequency Copilot wins live. Every feature applies multiple times daily; a ten-minute setup pays back several minutes saved on every email triage, draft and meeting prep for every consultant who commits to the habits. Teach this chapter first — before Word, before Excel, before PowerPoint — because it's where the team will feel the difference fastest.