Copilot becomes useful the moment you stop asking it to generate generic work and start pointing it at the work you already have. Nine uses that change real work, the prompts to copy, and the pattern that makes them useful.
Microsoft’s own prompt framework has four parts: goal, context, expectations and source[1]. Source is the one people skip and it’s the one that separates Copilot from a generic chatbot. This guide gives you nine specific prompts, tells you exactly what each needs (some features require a paid add-on, some need a Microsoft Designer licence, some only work on your primary mailbox), and covers the mistakes that quietly degrade output. It also flags what’s changed: Copilot in Excel no longer requires the paid add-on, Word’s Agent Mode is now called Edit with Copilot, and the Excel Python article Microsoft used to publish has been retired.
Ask around your office what people use Copilot for and you’ll get the same three answers: tidying up an email, summarising a meeting they missed, and “I tried it once.”
Which is interesting, because the uses that save the most time are rarely the ones where Copilot writes something from scratch. They’re the ones where it reads, compares, finds, or checks something you’d otherwise have to do manually. Draft emails are short, you already know what you want to say, and the AI version usually needs as much editing as writing it yourself would have taken. That’s the least interesting thing Copilot does, and it’s the use case most likely to disappoint someone into never trying anything else.
| Most people ask Copilot to… | More useful pattern |
|---|---|
| Write an email | Find the emails that actually need a response |
| Summarize a meeting | Find commitments and unresolved decisions |
| Rewrite a draft | Tell me what’s weak, and why |
| Analyze a spreadsheet | Find what would surprise someone who knows the data |
| Summarize documents | Compare what materially changed |
| Answer a question | Answer from these sources, and show me the evidence |
The pattern behind every use in this article, compressed into one table. Author’s framing, not a Microsoft-published comparison.
Nine uses is a lot to hold in your head at once. Before the list, a quick way to tell which one is worth your first real attempt. Pick a task where:
If three or more of those are true, that’s your candidate. Match it to the closest use below rather than starting with whichever one sounds most impressive.
Each one has the prompt, what it needs, and how to adapt it. These are Future Factors’ own tested prompts rather than anything attributed to a named company, and where Microsoft publishes an official example, that’s said directly.
The pattern in this group: Copilot reads something first so you don’t have to read all of it to find the part that matters.
Everyone knows about the recap. Fewer people realise you can cross-examine the transcript afterwards, which is where the value is. Microsoft documents that “to ask questions about what was said in the meeting after it ends, there must be a meeting transcript available”[3].
Why this is useful: a recap tells you what was said. This tells you what people are now on the hook for, with a line you can point to if someone claims they never agreed to it.
Needs: live transcription turned on during the meeting. Microsoft is explicit that “if the transcript from a transcribed meeting is no longer available, Copilot will be unavailable and all previous conversation history with Copilot will be removed”[3]. Copilot also “won’t work in meetings that are hosted outside the participant’s organization”[3].
Adapt it: swap “commitments” for whatever your role needs to extract. Objections raised, for sales. Requirements mentioned in passing, for project work.
This is genuinely one of Microsoft’s own gallery prompts, and it’s better than most people’s inbox triage. The gallery lists it as: “Find emails in the past 48 hours where someone is waiting on me (asks, ping…”[5] (Microsoft’s card truncates it).
Why this is useful: inbox triage usually makes you read everything before you know what matters. This flips the process. Copilot finds the unresolved obligations first, so you start the day working on what’s actually overdue instead of whatever’s at the top of the pile.
Needs: access to work data, which requires the Copilot add-on for most surfaces. Worth knowing: Copilot in Outlook “are only available on a user’s primary mailbox. They are not available on a user’s archive mailbox, group mailboxes, or shared and delegate mailboxes”[6]. That single restriction explains a lot of “it doesn’t work for me” complaints from people who live in a shared inbox.
Microsoft’s own gallery includes: “Compare these files grouped by differences in formatting, structure, and content:”[5] Here’s the version I actually use.
Why this is useful: a formatting diff is easy to get from any tool. What’s hard to see by eye is a clause that quietly changed obligation or emphasis. This is built to catch that specifically.
Needs: in Word you can reference files with the slash key, and Microsoft states “You can choose up to 20 items for Copilot to reference,” which “can be Word, PowerPoint, PDF, or TXT files” that you have permission to access[9]. On mobile the limit drops to three[9].
Copilot Notebooks are the most underrated thing on this list. Microsoft describes them as workspaces where “Copilot doesn’t access your entire OneDrive, email, Teams chats, or the web, and only uses the references you’ve added to the notebook to generate responses”[13].
That constraint is the feature. For work where the answer needs to stay grounded in a defined set of approved material, a Notebook is usually a better fit than general chat.
Why this is useful: general chat can answer from anywhere, which is exactly the problem when you need an answer from somewhere specific. A notebook can’t wander off into the wrong document.
Needs: licensed Copilot users can add more than 300 references but “only up to the first 300 will be used for grounding,” while Copilot Chat users can add 50, all of which are used[13]. Premium sources like Teams, SharePoint and internal URLs need the paid licence; the free tier gets standard sources such as PDF, Word, Excel, PowerPoint and external URLs[13].
The pattern in this group: Copilot pressure-tests your thinking instead of replacing it.
Underused and, for anything that matters, better than Draft with Copilot. Microsoft describes Coaching by Copilot as providing “feedback on email drafts by suggesting improvements for tone, sentiment, and clarity”[7].
Why this is useful: this is one of the more interesting uses on the list because it challenges the default assumption that AI should do the work for you. Asking what’s weak preserves your judgement. Asking for a rewrite hands it over.
Needs: at least 100 characters of draft for Copilot to give useful feedback, per Microsoft’s mobile guidance[7]. Adapt it: the “don’t rewrite it, tell me what’s weak” pattern works across every app and is the single most transferable instruction in this article.
Microsoft documents that Copilot in Excel can “Identify insights: Ask Copilot questions about your data. Copilot shows insights as charts, PivotTables, summaries, trends, or outliers”[8].
Why this is useful: most people only ask Excel Copilot to do a calculation they already know how to do by hand. Asking what would surprise a daily user of the data is a genuinely different question, and it’s the one a spreadsheet won’t volunteer on its own.
Needs: Calculation Options set to Automatic, the one documented workbook requirement[2]. Worth knowing if you haven’t checked recently: Copilot in Excel no longer requires the paid add-on, so if you concluded eighteen months ago that you didn’t have it, check again[2]. The older advice to format your data as a table and turn on AutoSave first isn’t a current requirement, and “Copilot in Excel with Python” isn’t current either, that support article now redirects to Microsoft’s contact page and current documentation doesn’t mention Python at all. Also note that a checked-out file won’t work: “If your organization requires check-out for editing in SharePoint, Copilot in Excel on Windows or Mac won’t work for files from that site”[2]. Excel on iPad and iPhone are chat mode only, with edit mode still rolling out on iPad[8].
The pattern in this group: Copilot converts something you already made into a form someone else can act on.
Microsoft supports generating a presentation “based on the content of an existing Word document, with support for one file at a time,” and notes it “works best with Word documents that are smaller than 24 MB” and that using Styles in Word helps Copilot “better understand your source document structure”[10].
Why this is useful: the document already contains your thinking. This skips the part where you re-explain it to yourself in slide form.
Needs, and this is the one nobody mentions: a Microsoft Designer licence. Microsoft’s PowerPoint FAQ states that without one you get “summarization, open-ended Q&A prompting, and basic chat features,” while “adding a slide, creating a presentation about a specific topic, creating a presentation from a file, organizing the presentation, and adding an image” all require Designer[11]. If deck generation isn’t working for you, that’s usually why. Brand templates also require a Copilot licence and admin work to publish templates to your Organization Asset Library[12].
Copilot Pages is “an interactive canvas that transforms Copilot responses into editable, shareable content,” created by selecting the pencil button below a response[14]. Notably, Microsoft says it’s “available to those who have SharePoint or OneDrive storage, including ones without a Microsoft Copilot license”[14].
Use it for: the moment where Copilot has produced a decent first draft of a plan or a checklist and three people need to argue with it. Copying into a Word doc loses the thread; a Page keeps Copilot alongside the content.
Why this is useful: copying an answer into a Word doc loses the thread the moment someone wants to challenge a line in it. A Page keeps Copilot alongside the content, so the argument and the source stay in the same place.
The pattern in this group: sometimes the point isn’t to keep more, it’s to get the help without keeping anything at all.
This one surprises people and it’s genuinely useful for anything confidential. Microsoft documents that “transcription isn’t required for turning on Copilot in a meeting,” and that Copilot “can generate AI notes and tasks during the conversation without transcription and recording enabled”[4]. With the “only during the meeting” setting, “after the meeting ends, speech-to-text data that wasn’t transcribed and interactions with Copilot will no longer be available”[4].
Needs: the setting is under Online meeting options, then “Copilot and other AI,” and is now labelled “Allow Copilot and Facilitator.” Participants must select Copilot in the meeting controls to start it, and once started “it will be on for the duration”[4]. One important caveat Microsoft states directly: depending on your organisation’s Purview retention policies, prompts and responses may still be retained for compliance even with recording and transcription off[4].
Why this is useful: this is the one people assume doesn’t exist. You get live help without a transcript sitting somewhere afterwards for anyone confidential the conversation touches on.
Microsoft publishes its own framework and it’s short enough to actually remember. Its guidance states that “prompts can include four parts: the goal, context, expectations, and source,” and that “all that’s required is a clear goal,” though “you’ll often need to include more than a goal to get the results you want”[1].
| Element | What it is | Typical weak prompt | What to add |
|---|---|---|---|
| Goal | What you want back | “Summarise this” | Name the output form: a list, a table, three bullets |
| Context | Who it’s for and why | Missing entirely | The audience and what they’ll do with it |
| Expectations | Tone, length, format | Missing entirely | Length cap, tone, what to leave out |
| Source | What to ground it in | Skipped most often | A named file, meeting or thread via the slash key |
The four elements are Microsoft’s[1]. The weak-prompt column and the fixes are the author’s observations from running Copilot sessions.
Source is the element I see people skip most often, and in Microsoft 365 it’s often the difference between generic output and something grounded in your actual work. A prompt pointed at a specific file, meeting or thread produces something grounded in your organisation’s actual material. A prompt without one produces confident generic text, which is precisely what makes a sceptical colleague conclude the tool isn’t very good.
Microsoft’s own example of a goal-plus-source prompt is refreshingly plain: “Write a summary based on all emails from Sam in the past two weeks”[1]. And its goal-plus-context-plus-expectations example shows how much specificity helps: “Draft an outline of a training manual about time management. Our audience is professionals who work in a hybrid environment and constantly need to attend virtual meetings and meet deadlines. The tone of the document will be friendly and suggestive”[1].
There’s one more thing the prompts above share that isn’t in Microsoft’s framework, and I’d argue it’s the real differentiator. Each of them asks for something Copilot could get wrong in a visible way. Quote the line. Show the calculation. Say what’s missing. Say how confident you are.
Don’t just ask for an answer. Ask for the evidence that lets you check it.
Generic prompts produce output you have to trust or discard wholesale. Prompts that demand receipts produce output you can actually check in thirty seconds, and that’s the difference between a tool you rely on and a tool you play with.
Microsoft also publishes a few small mechanical hints that are worth knowing: use quotation marks, since “this helps Copilot know what to write, modify, or replace for you,” and type “new topic” when switching tasks rather than continuing a thread[15]. That second one fixes more bad output than people expect.
Every prompt above follows the same four moves. This is Future Factors’ own adaptation, distinct from Microsoft’s official framework above, and once you see the four moves you can build a prompt for anything.
Move one: name the source, specifically. Not “my emails.” This meeting, that file, these two documents. Use the slash key.
Move two: name the output form. A list. A table with these columns. Three bullets. Copilot will pick a form if you don’t, and it usually picks prose, which is the least useful option for anything you need to act on.
Move three: demand a receipt. Quote the line. Show the calculation. Cite which document. This is the move that turns unverifiable output into something you can check.
Move four: give it permission to fall short. “If the documents don’t contain enough to answer, say what’s missing.” Without this, the model may try to fill the gap instead of telling you the evidence isn’t there. With it, you get an honest boundary, and knowing where the boundary is often more useful than the answer.
Take a task you do every week that involves reading something. Then fill in this shape:
“From [named source], give me [named output form]. For each item, [receipt: quote it, show the working, cite the source]. If [the thing that might not be there] isn’t present, say so rather than guessing.”
Run it. The first version will often be close but not quite right. Then, and this is the part people skip, fix the prompt rather than fixing the output. If it gave you six items and you wanted three, don’t delete three: add “maximum three, ranked by urgency” to the prompt and run it again. Two or three rounds of that and you have something reusable.
Microsoft says the same thing more diplomatically: “Most likely, you’ll follow up on the results with another prompt. Expect some back-and-forth conversation to get the results you’re looking for”[1].
Nine individual prompts is useful. What actually changes a week is connecting a few of them to the parts of your workday where they belong. Here’s one full routine, not as a template to copy exactly, but to show what “connected” looks like.
| Time | Where | What you run |
|---|---|---|
| 8:45 AM | Outlook | The waiting-on-me prompt, sorted by how long each person has been waiting |
| 8:50 AM | Teams | Interrogate Friday’s meeting transcript for unresolved commitments |
| 9:00 AM | Copilot Chat | Turn both outputs into one short priority list for the week |
| 9:10 AM | Calendar | Prompt: “Compare my calendar this week with these priorities. Flag meetings that don’t clearly support one of them, meetings that need preparation, and places where I have no protected work time.” |
One way to connect three prompts from this article into an actual weekly pattern. Author’s routine, not a Microsoft-published workflow.
That’s more useful than owning nine prompts. You’ve connected three of them to an actual part of your workday, which is the difference between a prompt library and a habit.
Here’s the framework we use at Future Factors, and it explains why a page of great prompts often changes nothing:
Tool x Workflows x Behavior = AI-powered professional.
Think of it as multiplication, not addition. If one part is weak, it drags down the impact of the others.
Applied here specifically: having Copilot, with the right permissions and licence, is the Tool. The nine prompts above aren’t the Tool, they’re candidates for the Workflow: the one you actually attach to a specific, recurring point in your week. “I’ll use this when it comes up” isn’t a workflow. “Every Monday before I open my inbox, I run the waiting-on-me prompt” is.
Not needing to be reminded is the Behavior. It’s when your hand goes to the prompt without a decision being made, the way you don’t decide to check your calendar.
You can have Copilot, a folder full of excellent prompts, and still see very little change if none of those prompts has been attached to a recurring piece of work. So pick one prompt from the list above. Not nine. One. Attach it to the same point in your week for three weeks. If the workflow repeatedly adds no value in that window, change the workflow rather than forcing the habit. If it’s earning its place, add the second one.
If you want to do this properly across a team rather than individually, our guide to building an AI prompt library your team actually uses covers the shared version, and our piece on why most Copilot rollouts fail gets into the adoption mechanics.
These are the ones that do the most damage, in rough order.
No source. Covered above, and it’s still the biggest one. If you haven’t pointed Copilot at a file, a meeting or a thread, you’re using an expensive general chatbot. In Copilot Chat, type the slash key and start typing a name to reference “the people, file, meeting, or email you wish to link”[16]. Worth noting that on the unlicensed tier “only files are available to reference”[16].
Asking for a rewrite when you wanted a critique. If you ask Copilot to improve something, it will change it, whether or not it needed changing. Asking what’s weak and why gives you back the judgement.
The rest of the recurring mistakes are in the table below.
| What goes wrong | Likely reason | What to try |
|---|---|---|
| Generic answer | No source | Point Copilot at a file, meeting, email, or thread with the slash key |
| Missing information | Copilot can’t access that surface or content | Check what the feature can actually see, per the caveats above |
| Output gets worse over time | The thread has drifted | Type “new topic” and start fresh |
| AI changes too much | You asked it to “improve” or rewrite | Ask for critique, not a rewrite |
| Feature missing | Licence, mailbox type, or admin boundary | Check the licence reality check below before assuming it’s broken |
| Research feels shallow | Wrong tool for the task | Use Researcher or Analyst instead of ordinary chat |
A quick-reference version of the mistakes above. Author’s diagnostic, not a Microsoft-published table.
A licensing boundary causes a lot more “it doesn’t work” frustration than an actual quality problem. Worth reading once, then keeping for reference rather than re-litigating every time something doesn’t show up.
Not knowing what you’re actually licensed for. A licensing boundary causes a lot more of the frustration than a genuine quality problem. The clearest statement is Microsoft’s own: Copilot Chat “is not grounded in organizational content like files, emails, or chats as part of the chat experience, it is grounded in data from the web only,” and “access to full work data as part of Work IQ and semantic indexing is only available for users with the Microsoft 365 Copilot license”[18]. There’s one carve-out worth knowing: Copilot Chat in Outlook does reach your emails, calendar, meetings, chats and files through lexical indexing[18].
Copying a prompt gets you one result. Understanding the shape of it gets you a hundred, using the Source, Shape, Receipt, Boundary method above.
Microsoft’s own Prompt Gallery is worth twenty minutes and most people don’t know it exists. It’s filterable by function and by app, and the prompts are short enough to adapt easily. A few real ones from it: “Analyze this workbook and give me interesting data insights,” “Suggest a list of action items from this file,” “Give me 1-slide executive summary for slides,” and “What questions should I ask myself when making a decision about [changing my career]?”[5]
Treat those as starting shapes rather than finished prompts. Every one of them gets substantially better when you add a source and a receipt.
If you’re weighing Copilot against the alternatives before investing this effort, our honest comparison of ChatGPT and Copilot for work covers where each one genuinely wins, and the walkthrough on building a custom AI agent in Copilot is the natural next step once a prompt has become a weekly habit and you want it to run itself.
The prompts are the easy part. In training, the real work is helping people identify which patterns belong in their role, practise them against their own Microsoft 365 content, learn how to evaluate the output, and turn the useful ones into repeatable workflows.
The uses that change someone’s week are the ones where Copilot reads something you would otherwise read yourself. Cross-examining a meeting transcript for every commitment anyone made, with quoted lines. Running a confidential meeting with Copilot on but recording and transcription off. Finding every email where someone is waiting on you and sorting by how long. Asking Excel what would surprise someone who works with the data daily. Comparing two documents for changes in obligation rather than formatting. Building a deck from a document you already wrote. Loading a Copilot Notebook with fixed sources so answers can only come from approved material.
Here is one for a meeting transcript: “From this meeting, list every commitment anyone made, including vague ones. For each, give the person, what they committed to, whether a date was named, and quote the exact line where they said it. Then separately list anything that was raised and never resolved.” It names the source, names the output form, demands a quoted receipt for each item, and asks for a second category that a generic summary would flatten. Microsoft’s own detailed example follows the same principle: “Draft an outline of a training manual about time management. Our audience is professionals who work in a hybrid environment…”[1]
Mostly because of one missing element. Microsoft’s framework has four parts: goal, context, expectations and source[1], and source is the one nearly everyone skips. A prompt pointed at a named file, meeting or thread produces something grounded in your organisation’s real material, while a prompt without one produces confident generic text. The second differentiator is asking for a receipt: quote the line, show the calculation, cite the document. That turns output you have to trust wholesale into output you can check in thirty seconds.
Both, with conditions. Microsoft documents that Copilot in Excel can “Identify insights” and show them “as charts, PivotTables, summaries, trends, or outliers”[8], and that Copilot in Excel now works with a Copilot Chat-eligible business subscription rather than requiring the paid add-on[2]. Editing requires Calculation Options set to Automatic. For Teams, intelligent recap gives AI notes, recommended tasks, speaker timeline markers and chapters, and needs either a Teams Premium or a Copilot licence, with transcription turned on[21]. Asking questions about the meeting afterwards requires an available transcript[3].
Attach one prompt, not nine, to a fixed slot in a routine you already have. Future Factors frames adoption as Tool x Workflows x Behavior: having Copilot with the right permissions is the Tool, running one specific prompt at the same point every week is the Workflow, and not needing a reminder is the Behavior. Because they multiply, a great prompt with no fixed slot produces nothing. Attach your chosen prompt to the same point in your week for three weeks. If it repeatedly adds no value in that window, change the workflow rather than forcing the habit. If it earns its place, add a second.
Every Copilot capability, restriction and licence requirement in this article was verified against Microsoft’s own documentation on support.microsoft.com and learn.microsoft.com on 20 August 2026, because Copilot’s feature set changes on a two-week release cycle. Where a widely-repeated claim could not be confirmed in current documentation, including “Copilot in Excel with Python” and the standard advice about formatting data as a table, that is stated in the text rather than omitted quietly. The prompts are Future Factors’ own tested examples except where Microsoft’s Prompt Gallery is cited directly.
Weekly tips. Real examples. Practical help for busy professionals.
We care about your data, check out our privacy policy.