Module 2 of StartCloud's Copilot Essentials learning pathway, in six short units with a knowledge check: the four ingredients of a strong prompt (goal, context, source, expectations), before-and-after examples for meetings, email, and documents, how to iterate like a conversation, and a starter prompt toolkit.
Writing Copilot Prompts That Actually Work
Why the prompt is the whole game
Here is the thing nobody mentions when the Copilot licences get switched on: everyone gets the same tool. The person raving about it in the lunchroom and the person who quietly gave up in week two are running identical software. The difference between them is almost entirely what they type into the box.
Twenty years of Google has trained us to type three keywords and hit enter. Copilot works the other way around. Microsoft's own guidance is blunt about it: unlike traditional search, Copilot responds best to detailed prompts. Give it three words and you get something generic. Give it a proper brief and you get something you can actually use.
The good news is that writing a proper brief is not a dark art. It is a small, learnable habit, and by the end of this module you will have it, plus a set of ready-made prompts to keep within arm's reach.
Treat Copilot like a bright new hire on their first morning. Keen, quick, surprisingly capable, and with absolutely no idea what you actually meant. Say "summarise the meeting" and you will get the digital equivalent of a polite shrug. Tell it which meeting, what you missed, and what you need the summary for, and it will hand you something genuinely useful before the kettle boils.
Microsoft's training for Copilot boils a strong prompt down to four ingredients: goal, context, source, and expectations. You will not need all four every single time. A clear goal is the non-negotiable foundation, and the other three sharpen it. The more of them you include, the better the answer gets.
The one ingredient no prompt can skip. Say exactly what Copilot should produce: a summary, an email draft, a list of options, a table, a briefing. Verbs help. Draft, list, compare, rewrite.
The background that shapes the answer. What is it for, who is involved, what is going on? Preparing for a client meeting reads very differently from settling a pub argument.
Point Copilot at the right material: a specific document, your emails with someone, a meeting recording. Type / in the prompt box to reference a file, person, or meeting directly.
Tone, length, format, and audience. Under 300 words, bullet points, formal but plain English, written for someone who has not seen the detail. Say it, and you will get it.
Anatomy of a strong prompt
Here is what all four ingredients look like stitched into one everyday prompt. Nothing fancy, just a complete brief.
Draft a one-page briefing for my meeting with Redgum Earthmoving on Thursday. It is our first catch-up since they renewed their support agreement, and I want to walk in across the detail. Base it on /Redgum Renewal Proposal and my recent emails with their operations manager. Keep it under 300 words, short bullet points, plain professional tone.
That prompt takes about twenty seconds to type. The generic one it replaces takes five seconds, plus ten minutes of fixing what came back.
Theory is nice, but examples are what you will actually remember at 4pm on a Thursday. Same tool, same task, and the only thing that changes is the prompt. Steal these shapes for your own work.
Summarising a meeting
"Summarise the meeting."
Which meeting? For what? Copilot has to guess, so it summarises everything evenly and helps with nothing.
"Recap /Project Jarrah kickoff from Tuesday. I missed the second half. List the decisions made and any actions assigned to me, as bullets I can read in two minutes."
Names the meeting, explains the gap, and asks for decisions and actions in a skimmable format.
Drafting an email reply
"Reply to this email."
No position, no tone, no length. You will get something polite, vague, and twice as long as it should be.
"Draft a reply to Karen's email about the delayed delivery. We cannot ship until the 14th. Apologetic but confident tone, offer a 10 percent discount on her next order, three short paragraphs."
Gives Copilot the facts and the stance, so the draft lands close to sendable on the first go.
Turning notes into a document
"Make this into a document."
Into what kind of document, and for whom? Expect a tidy reformat of your notes rather than anything new.
"Turn my rough notes in /Ops review notes into a one-page summary for the leadership team. They have not seen the detail, so spell out the two staffing risks. Formal but plain English, with a short recommendation at the end."
Format, audience, emphasis, and tone are all spelled out, so the output is shaped for its readers.
In the Copilot prompt box, type / and pick a file, person, or meeting from the list. "Recap /Monday ops meeting" or "When is my next one-on-one with /Priya?" beats describing things from memory, because Copilot knows exactly which item you mean instead of guessing. Referencing your own emails, meetings, and chats needs the paid Microsoft 365 Copilot licence, which Module 1 covered.
Copilot's first answer is a first draft. Microsoft's own training says the real power emerges through iteration and conversation: instead of settling for the first response, refine it with follow-up prompts until it is right. The habit to build is simple. Refine, do not restart.
Copilot remembers the conversation you are in, so a follow-up can be short and natural. You do not need to repeat the whole brief, just say what to change.
- "Shorter, and lead with the budget question."
- "Make the tone warmer, this is a long-standing client."
- "Add a paragraph about timing, we need a decision by Friday."
- "Good. Now turn that into a table I can paste into the report."
One exception: when you switch to a completely different topic, start a new chat. Otherwise Copilot drags leftover context from the old conversation into the new one, like a dog bringing you the wrong ball.
The four classic mistakes
"Write a report" about what, for whom, saying what? Vague in, generic out. Name the task precisely and give it something to work with.
A message for the board and a message for the group chat are different animals. Say who will read it and the tone sorts itself out.
Summarise this, then rewrite it, then make a slide deck, and also translate it. Conflicting instructions in one prompt confuse the model. Break big jobs into steps and build with follow-ups.
The first response is a starting point, not a verdict. People who get great results push back once or twice as a matter of habit.
Copilot can be confidently wrong. Microsoft is upfront that responses may be inaccurate or incomplete, and recommends reviewing everything it generates. Check the facts, check the figures, and check the sources it cites before anything leaves your outbox with your name on it.
A starter set to keep within arm's reach. Each of these already carries the four ingredients, so all you do is swap the placeholders for your own files, people, and meetings. Once a prompt earns its place, save it somewhere handy. Copilot's Prompt Gallery lets you save and share the keepers with your team.
Catch up without the replay
For the meetings you missed, half-watched, or sat through while answering email. Swap the placeholders for your own meetings and people using the / picker.
- Recap /[meeting]. List the decisions made and any actions assigned to me.
- What did I miss in /[meeting]? I only caught the first half.
- What questions were left unanswered in /[meeting]?
- Draft an agenda for my next one-on-one with /[person], based on our recent emails and chats.
Tame the inbox
Triage, drafting, and the gentle art of making long emails shorter. State the facts and the tone, and let Copilot do the typing.
- What should be on my radar from emails last week?
- Summarise my unread emails from this week and flag anything needing a reply today.
- Draft a reply to /[person]'s email about [topic]. Friendly but firm, three short paragraphs.
- Rewrite this draft so it is half the length and easier to skim.
From rough notes to finished pages
First drafts, rewrites, and turning the scraps in your notes file into something you would happily show a client.
- Turn my notes in /[file] into a one-page summary for [audience]. Plain English, recommendation at the end.
- Draft a proposal for [client] based on /[file]. Formal tone, two pages, clear next steps.
- Rewrite this section for someone outside the project. No jargon.
- Suggest 10 titles for /[file].
That is the whole skill: a clear goal, enough context, the right source, and honest expectations, then a follow-up or two. It feels deliberate for about a week, and after that it is just how you type.
- Microsoft Learn: Write effective prompts to achieve optimal results
- Microsoft Learn: Write an effective prompt (context, goal, source, expectations)
- Microsoft Learn: Review prompting best practices
- Microsoft Learn: Craft effective prompts for Microsoft 365 Copilot
- Microsoft Learn: Application card: Microsoft 365 Copilot
Guidance was current at the time of writing (July 2026). Copilot features move quickly, so details like the / picker may vary slightly between apps and updates.
Knowledge check
5 quick questions. Get 4 right and the module is yours.
1. What are the four ingredients Microsoft recommends for a strong Copilot prompt?
2. In a prompt, what does the source ingredient mean?
3. Copilot's first draft is decent but misses a key detail. What is the best move?
4. Which of these is the strongest prompt?
5. You are mid-chat about a client proposal and now need help with something completely unrelated. What does Microsoft recommend?