Advanced Prompting with Microsoft Copilot

Moving beyond GCSE to craft smarter, sharper prompts

A practical training flow from prompt basics to confident application
GCSE recap - your foundation
Confirm the core prompt components everyone can use.
Five advanced techniques
Add repeatable moves that improve output quality.
Before vs after
See how small changes make a prompt more usable.
Common mistakes
Avoid habits that waste time or lose context.
Practice challenge and takeaways
Apply the checklist to a real prompt.
The four-part prompt foundation used throughout the session

G - Goal - What do you want Copilot to do?
C - Context - Background information that sets the scene
S - Source - Specific files, emails or data to use
E - Expectations - Format, tone and length of output

KEY MESSAGE
GCSE remains the starting point. Advanced techniques layer on top when the first response needs more
direction.

You already know GCSE

Advanced prompting reduces ambiguity when the task has nuance
A basic GCSE prompt can still fail when the task involves judgement, audience sensitivity or a specific output
format.
Common failure patterns
Too vague - Copilot fills gaps with assumptions you did not intend
Wrong structure - the content may be right, but the format is not useful
No reasoning shown - you cannot see how the answer was reached
Advanced prompting response
Role and audience set the lens before the task begins
Constraints specify length, tone, headings and exclusions
Refinement improves the output in the same thread

Why isn't GCSE always enough?

Note: These are the most common failure modes the advanced techniques address.

Technique 01 | Chain of Thought

Five Advanced Techniques

Example prompt
"Before answering, think through this step by step.

I need to decide whether to run in-person or virtual training for 40 staff. Consider cost, engagement, logistics and hybrid working policy. Show your reasoning, then recommend one option."

KEY PHRASE
"Think through this step by step" or "Show your reasoning
What it is
Ask Copilot to reason through a problem step-by-step before giving the answer. This surfaces assumptions
and helps you spot weak logic.
When to use it
Analysis, decisions and complex writing tasks with multiple competing factors.

You are asking Copilot to show its work. That means you can review and challenge the reasoning, not just accept the conclusion. Useful for judgement calls and decisions with trade-offs

Technique 02 | Role Framing
Example prompt
"You are an experienced internal communications manager who specialises in plain English and change management.

Draft a short email to staff announcing a mandatory Copilot training requirement. Tone: informative and encouraging, not jargon-heavy."
KEY PHRASE
"You are a [specific role] who [key characteristic]...
What it is
Assign Copilot an explicit role before giving the task. This shapes vocabulary, tone, depth and the lens it
use
When to use it
Drafting communications, expert reviews and tone-sensitive writing.

Without a role, Copilot defaults to a generic helpful assistant. A good role description has two parts: the expertise, and a key characteristic that shapes tone.

Technique 03 | Constraints & Formatting
Example prompt
"Write a stakeholder update on the Copilot rollout.

Max 150 words. Plain English, no acronyms. Positive but honest tone. Use three sections: Progress / Challenges / What's Next. Do not include background theory."
KEY PHRASE
"Max [X] words. [Tone]. Headings: [A], [B], [C]. Do not include [X].
What it is
Specify length, tone, structure and what to leave out. Exclusions are often as powerful as inclusions.

When to use it
Any task where the first draft is usually the wrong length, tone or shape.

Combining two or three constraint types in a single prompt makes a big difference. Telling Copilot what NOT to include is just as useful as what to include

Technique 04 | Iterative Refinement
Example follow-up
"This is good but make it shorter and more direct, aim for three short paragraphs.

Now rewrite the tone: it sounds too formal. Match the voice of this example: [paste example]."
KEY PHRASE
"Make this shorter / Rewrite the tone / Add a concrete next step
What it is
Treat Copilot as a conversation, not a one-shot oracle. Each follow-up should target exactly what is still wrong.

When to use it
Almost every task - especially longer documents, emails and structured content.

One of the biggest mindset shifts is moving from one prompt, one answer to treating Copilot like a conversation. Copilot Chat remembers context in a thread

Technique 05 | Few-Shot Examples
Example prompt
"Here is an example of the update style I use:

[This week the team completed onboarding for 12 users. One blocker remains: SharePoint access. Next step: escalate to IT by Friday.]

Now write a similar update for the Copilot rollout..."
KEY PHRASE
"Here is an example: [X]. Now do the same for: [Y]."
What it is
Show Copilot one or two examples of the output style you want. It picks up patterns in tone, format and level
of detail


When to use it
Consistent templated outputs, house style and replicating something that worked well.

Rather than describing a style in abstract terms, you paste in an actual example and ask Copilot to match it. Especially useful when you have a house style or template.

Combine GCSE with a few precise advanced layers

ROLE You are a senior project manager with experience in change management.
GOAL Write a stakeholder update email about our Copilot rollout.
CONTEXT We are at week 6 of a 12-week programme. 200 staff trained so far; target 500.
CONSTRAINTS Max 150 words. Plain English. No acronyms. Positive but honest tone.
STRUCTURE Use three short sections: Progress / Challenges / What's Next.
REASONING Before writing, note any assumptions you are making about the audience.

Advanced Prompt Anatomy

Walk through each layer. Role, Goal, Context are the GCSE foundation. Constraints, Structure, Reasoning are the advanced additions. Not every prompt needs all six layers - use what the task demands

A small amount of prompt design produces a more usable first draft

BEFORE
"Write an email about the training."


Problems
• No role - generic voice
• No context - which training and who?
• No format - could be anything
• No constraints - likely too long



AFTER
"You are an internal comms writer. Write a 120-word email to all staff announcing mandatory Copilot training
in the next 4 weeks. Positive, plain English. End with a clear call to action."

What changed
• Role assigned
• Specific audience and purpose
• Length constraint
• Tone specified
• Structural requirement

Before versus After

The task was identical. Around 30 seconds of extra thought produced a much better prompt

Coach learners away from habits that reduce output quality

MISTAKES AND THE BETTER HABIT

Overloading one prompt -> Split into separate prompts - one task at a time.
Accepting the first draft -> Treat it as a starting point - refine at least once.
Using vague modifiers -> Replace "more professional" with specific tone, audience and format instructions.
Starting a new chat -> Refine within the same thread to keep context alive.

Common Mistakes to Avoid

Quick-fire round. The third is particularly important: vague feedback produces vague improvement.

What participants should remember after the session

GCSE is your foundation
Build on it - do not replace it.

Be specific, not vague
Tell Copilot exactly what to change and how.

Add role, reasoning and constraints
These three techniques give the biggest return.

Show examples when style matters
Few-shot prompting replicates what worked before.

Treat Copilot as a conversation
Iterate within the same thread rather than starting again

Key Takeaways

Close with these five. Read each one and pause. Suggest trying at least one new technique this week.