Writing effective Copilot prompts: the framework from our training courses

"Copilot doesn't get me." It is the complaint we hear most often in our training sessions — and in nine out of ten cases the problem isn't Copilot, it's the prompt. If you ask a colleague to "write something about the project", you won't get anything useful back either. In this article we share the framework we cover in every course: four building blocks that turn a vague question into a sharp instruction.

The four building blocks of a good prompt

An effective prompt contains four elements. You don't always need to spell out all four, but the more important the result, the more complete your prompt should be.

1. Goal: what do you want?

Start with what you want to come out of it: a summary, an email, an analysis, a list of action points. Be specific about the format. Not "help me with this text", but "rewrite this text into a readable introduction of no more than 100 words".

2. Context: for whom and why?

Tell Copilot what it needs to know to do the job well: the audience, the reason behind it, your role. "I'm a project manager briefing a steering committee that is short on time" produces a fundamentally different text than the same question without any context. This is the building block beginners skip most often — and the one that makes the biggest difference.

3. Source: where should the information come from?

What makes Microsoft 365 Copilot unique is that it can reach your work data. Use that: refer explicitly to documents, emails or meetings. In many apps a slash (/) lets you point directly to a specific file or a particular meeting. "Use the steering committee minutes from last Tuesday and the project plan" stops Copilot from guessing or pulling in general knowledge from the web.

4. Expectation: what should it look like?

Finish with form and tone: length, structure, register, what to include or leave out. "No more than five bullets, a businesslike but warm tone, ending with a concrete follow-up question." The more explicit your expectation, the less you'll have to correct afterwards.

Examples by app

Here is what the four building blocks look like in practice:

• Word: "Write a first draft of a project proposal (goal) for our board, who will decide on next year's budget (context). Base it on the note 'Customer portal exploration' (source). No more than two pages, with an executive summary at the top (expectation)."
• Excel: "Analyse the sales figures in this worksheet (source) and show the trend per region over the past four quarters (goal). I'll be presenting this to the sales team (context). Add a bar chart and summarise the three most striking insights (expectation)."
• Teams: "Summarise this meeting (goal) for colleagues who weren't there (context). Use the transcript (source). Structure: decisions, action points with an owner, open questions (expectation)."
• Outlook: "Draft a reply to this customer (goal) who is unhappy about the turnaround time; I want to keep the relationship healthy and give a realistic timeline (context). Use the last three emails in this thread (source). Keep it short and empathetic, ending with an offer to call (expectation)."

Three habits of people who get a lot out of Copilot

1. They have a conversation. The first output is a starting point, not a finished product: "make it shorter", "add an example", "different tone". Iterating is faster than trying to write the perfect prompt in one go.
2. They keep what works. A prompt that lands well is one you save and share with your team. That's how a prompt library grows for each job role — in our training courses every participant builds one.
3. They check the output. However good the prompt is, Copilot can make mistakes. Always verify figures, names, quotes and legal wording before they leave your desk.

Learn it in a single half-day — using your own work as practice material

You don't learn to write prompts from an article but by doing it — with your own documents, emails and meetings. That is exactly how our Copilot course is built: hands-on, tailored to each job role, with everyone leaving with their own prompt library. Schedule a no-obligation introduction and discover what a half-day of practice with your team delivers.