Copilot prompting rules are habits for briefing Microsoft 365 Copilot properly: say what you want, why you want it, who it’s for, what shape it should come back in, and build bigger pieces in stages. The ten below are the ones I teach, each with a prompt you can adapt.
Microsoft has its own prompting guidance, and it’s a good starting point. It breaks a prompt into four parts: the goal, the context, the source Copilot should use and your expectations for the response. My rules sit on top of it and deal with what goes wrong once people use Copilot every day.
What are the 10 Copilot prompting rules?
| # | Rule | What it means | Example prompt |
|---|---|---|---|
| 1 | Set the right tone | Friendly, clear and direct, like briefing a capable colleague new to the project | “Please review this proposal and suggest improvements. My goal is to make it sound more confident for our executive audience.” |
| 2 | Be explicit | Action verb, quantity and audience | “Generate five talking points about our Q3 sales performance for the senior leadership team.” |
| 3 | Define boundaries | Limits on length, tone, structure, what to include and what to leave out | “Write a Teams message, maximum 150 words, updating the project team on our milestone. Celebratory but professional. Include one clear next step.” |
| 4 | Draft first, perfect later | Outline, refine the outline, then write section by section | “I need to write a business case for upgrading our CRM. First propose an outline with the key sections I should include.” |
| 5 | Demand structured output | Name the format you want back | “Summarise our three workstreams as a table with columns for workstream, status (red, amber or green), primary risk and next action.” |
| 6 | Explain the why | Purpose, audience and what’s different about this situation | “Write five subject lines for our managed IT service. Our differentiator is 24/7 local support. The audience is CFOs frustrated with slow response times.” |
| 7 | Control the length | Choose expert, brief or plain-English mode | “Explain the key implications of these contract changes. Be concise. Maximum five bullet points, one sentence each.” |
| 8 | Provide a scaffold | Give Copilot the headings to fill in | “Summarise this meeting using this format: attendees, key decisions, action items (who, what, by when), open questions, next meeting.” |
| 9 | Use power phrases and personas | Phrases that ask for more careful reasoning, and a role to take on | “Think step by step.” “Review your response and improve it.” “What questions should I be asking?” |
| 10 | Divide and conquer | Blueprint, section by section, then review the whole | “Create a detailed outline for an IT infrastructure upgrade proposal. Don’t write the content yet.” |
How do the rules work in practice?
Rules 1, 2 and 6 are about the brief. “Fix this document” gets a cautious, generic response because there are ten reasonable ways to fix a document and Copilot can’t tell which one you mean. Rule 6 adds the reason: a thread summary for “a manager joining the project today who needs the key decisions and any outstanding issues” tells Copilot what to pull out, where “summarise this email thread” leaves it guessing.
Rules 3, 5, 7 and 8 shape what comes back. For length I use three modes: expert asks for detail and adds “think through this step by step”, brief sets a maximum number of bullets or words, and the simplifier asks for plain English with no jargon. Scaffolds are the quickest win, because a meeting summary with fixed headings always has an action items section to fill.
Rules 4 and 10 change how you work. Ask for the outline, fix it together, then draft each section, so you catch a wrong structure early. Divide and conquer ends with a review pass for consistent tone and contradictions between sections.
Why treat Copilot as a partner instead of a one-shot tool?
The one-shot habit is to write a prompt, hit enter, hope, and start again if it’s wrong. Working with Copilot as a partner means asking questions first, looking at what already exists, then building the piece in rounds.
I showed this with a proposal and scoping agent I built, grounded in past proposals and a template. Before it wrote anything, I asked by voice for existing proposals in the fitness industry, and it found a similar sample and pulled its deliverables. Given the minutes from a Teams call with a demo client, it asked me to confirm the details before drafting. The first draft followed the template with bullets under each section, and one more round asking for a two-paragraph introduction to each section gave the second draft the depth the first was missing. I then moved it into Copilot Pages to finish with a colleague.
Hit the microphone in Copilot and talk the brief through, and you’ll give it far more context than you’d bother to type.
What does a prompt look like with all ten rules?
Here’s the board report prompt from the video. “Help me with a board report” becomes:
Act as a senior business analyst preparing for an executive review. I need a quarterly performance summary for next week’s board meeting. The board wants to understand why customer acquisition costs increased this quarter. Maximum two pages, with sections for performance highlights, key metrics (as a table), challenges and forward outlook. Confident but transparent about challenges, and no jargon, because not all board members have operational backgrounds. Use the Q3 sales data in the attached Excel file and the customer feedback summary. First, propose an outline for my review.
It has a persona, the goal and its reason, constraints, sources and a structure request, and it ends with rule 4. To bring the files in, type / in the Copilot Chat prompt box and start typing the file name.
When the full prompt is overkill
I wouldn’t write a prompt like that to find a date in an email. A one-line question is fine for a quick lookup. The rules earn their keep on work you’d otherwise hand to a colleague. Divide and conquer is for documents longer than two or three pages, multi-part presentations and analysis with several dimensions. My planning test: if you can list five or so distinct parts before you start, stage it.
If you’re pasting the same long prompt every week, save it as an agent’s instructions or a skill so the whole team gets the same brief. Building skills with Agent Builder and what SharePoint skills are cover both routes.
No prompt fixes bad source material. If Copilot is grounded in a library full of duplicate drafts, a careful brief still gets an answer built on the wrong version, so when the answers are wrong as well as vague, check the content with why Copilot can’t find your SharePoint documents.
Frequently asked questions
Does Microsoft have its own prompting framework for Copilot? Yes. Microsoft’s guidance splits a prompt into goal, context, source and expectations, and says only the goal is required. The other three add specificity, which is where most of my rules come in.
How do I add a document to a Copilot prompt? In Copilot Chat, type / and start typing the file name, then pick it from the suggestions on the Files tab. You can also choose Attach cloud files to add a file or folder from OneDrive, or upload one from your device.
Do the same rules work in Excel? Yes, with more emphasis on structure. Ask for a fixed shape, such as a one-sentence summary, three key insights and two recommended actions, so you can drop the answer straight into a report.
What’s the most useful power phrase? For me it’s “review your response and improve it” at the end of a prompt, and I sometimes ask Copilot to score its first pass out of 10 before it rewrites. “What questions should I be asking?” is a close second when you don’t know a topic well enough to write a good brief.
