Microsoft Copilot Prompting Frameworks
Microsoft Copilot can help you write emails, summarise documents, analyse information, plan meetings and complete everyday tasks. However, the quality of its responses depends partly on how clearly you explain what you need.
Microsoft publishes two different four-part prompting structures in its official guidance. Both help you organise your instructions so Copilot can better understand your task, the relevant background information and the result you expect.
This guide explains both structures, provides practical examples and links directly to Microsoft’s official documentation.
Important: The names of the elements below come from Microsoft. The labels “Framework 1” and “Framework 2”, along with the explanatory examples, are used by AI Prompts Work to make comparison easier. They are not separate branded framework names assigned by Microsoft.
Framework 1: Goal, Context, Source and Expectations
In its official guide, Get started writing prompts in Microsoft Copilot, Microsoft identifies four parts that can help you create an effective prompt:
| Element | What it means | Example |
|---|---|---|
| 1. Goal | What do you want Copilot to do? Clearly describe the task you want completed. | Write a professional email reply to a customer. |
| 2. Context | Why do you need this task completed, and who is involved? Explain the background so Copilot understands the situation. | The customer is enquiring about booking a private tour. |
| 3. Source | What information should Copilot use? Identify relevant documents, emails, websites or examples that contain the information needed. | Use the attached customer email and my writing guidelines. |
| 4. Expectations | How should Copilot respond? Explain the tone, format, level of detail or other requirements for the answer. | Write a concise, friendly and professional email that is ready to send. |
Important: Microsoft explains that a clear Goal is the only essential part. The other three parts are optional, but adding them can help Copilot provide a more relevant and specific response.
Example Prompt Using All Four Elements
Imagine you have received a customer enquiry and want Copilot to help you write a reply.
The example below uses Markdown headings to separate each element. This is an organisational choice, not a formatting requirement imposed by Microsoft.
# GOAL
Write a professional email reply to a customer.
# CONTEXT
The customer is enquiring about booking a private tour.
# SOURCE
Use the attached customer email to understand the enquiry.
Use my attached writing guidelines to follow my preferred writing style.
# EXPECTATIONS
- Keep the email concise and professional.
- Use a friendly, natural tone.
- Address the customer's questions.
- Do not invent prices or availability.
- Provide a complete, ready-to-send email.When Should You Use This Framework?
This structure is useful when you need Copilot to produce a specific result using existing information. For example, writing emails, summarising documents, creating reports, preparing presentations or reviewing information.
The Source element is particularly useful when you want Copilot to base its response on particular documents rather than relying on general knowledge.
Official source: Microsoft — Get Started Writing Prompts in Microsoft Copilot.
Framework 2: Goal, Context, Details and Data
Microsoft also documents another four-part prompt structure in its Get started with Microsoft Copilot support guide, under the section about writing effective prompts.
This version retains Goal and Context but uses Details and Data for the remaining two elements.
| Element | What it means | Example |
|---|---|---|
| 1. Goal | What are you trying to achieve? Explain the task or desired outcome. | Prepare a summary of a project meeting. |
| 2. Context | What background information is relevant? Explain the purpose and situation. | The meeting covered progress, outstanding issues and upcoming deadlines. |
| 3. Details | What specific instructions should Copilot follow? Explain exactly what the response should include or how the task should be completed. | List the main decisions, outstanding tasks, responsible people and deadlines. |
| 4. Data | What input should Copilot use to complete the task? Identify the information or data the task is based on. | Use the attached meeting transcript. |
Example Prompt Using All Four Elements
Imagine you want Copilot to review the transcript of a project meeting and prepare a summary.
# GOAL
Prepare a summary of our project meeting.
# CONTEXT
The meeting covered project progress, outstanding issues and upcoming deadlines.
The summary will be shared with the project team.
# DETAILS
- Summarise the main discussion points.
- Highlight decisions made.
- List outstanding tasks and their owners.
- Include deadlines where they are documented.
- Present action items in a table.
- Do not invent missing information.
# DATA
Use the attached meeting transcript as the source of information.When Should You Use This Framework?
This structure is useful when the task requires precise instructions and specific input data. Examples include analysing meeting transcripts, scheduling meetings, reviewing spreadsheet data or preparing action lists.
The Details element helps explain how to complete the task, while Data identifies the information Copilot should work with.
Official source: Microsoft — Get Started with Microsoft Copilot.
What Is the Difference Between the Two Frameworks?
The two structures share the same general purpose, but Microsoft uses different terminology and emphasis.
| Framework 1 | Framework 2 | Difference |
|---|---|---|
| Goal | Goal | Both identify the task or desired result. |
| Context | Context | Both provide relevant background information. |
| Source | Data | Both help identify the information Copilot should use. Source focuses on the material to reference, while Data focuses on the task input. |
| Expectations | Details | Both help make requirements clearer. Expectations focuses on the desired response, while Details focuses on specific instructions. |
Which should you use? Either can help you organise your prompts. Framework 1 is a straightforward starting point for everyday tasks. Framework 2 is another useful way to structure tasks that have detailed requirements or specific data inputs.
These are overlapping approaches, not competing technical standards. You can also include information about both the required output and detailed instructions in the same prompt.
Additional Microsoft Guidance: Copilot Studio
Microsoft also provides separate prompting guidance for Microsoft Copilot Studio, which is used to build custom prompts, agents and automated workflows.
In its Copilot Studio documentation, Microsoft explains that a prompt generally has two parts:
| Part | Meaning | Example |
|---|---|---|
| 1. Instruction | Tells the AI what action to perform. | Summarise this customer feedback in three bullet points. |
| 2. Context | Provides the information needed to produce an appropriate response. | The text contains customer feedback received during the past week. |
This two-part explanation is specific to Microsoft’s custom prompt-building guidance. It should not be confused with the four-part structures used in general Copilot prompting documentation.
Official source: Microsoft Learn — Create a Prompt in Copilot Studio.
Microsoft’s Additional Prompting Recommendations
Beyond defining the elements of a prompt, Microsoft recommends several practices for improving results:
- Be clear and specific: Explain exactly what you want Copilot to do.
- Include useful background: Provide enough context for Copilot to understand the task.
- Reference relevant information: Identify the documents, messages or data Copilot should use.
- Refine your prompt: If the first response is not suitable, follow up with more precise instructions.
- Review the response: Check important facts, figures and claims against reliable information before using them.
Official source: Microsoft — Get Better Copilot Responses with Great Prompting.
Frequently Asked Questions
Do I need to include all four elements?
No. Microsoft states that a clear Goal is sufficient to begin. Adding Context, Source and Expectations can help when a task requires greater accuracy, detail or a specific type of response.
Do I have to use Markdown headings?
No. Microsoft does not require headings such as # GOAL or # CONTEXT. They are simply a useful way to organise a longer prompt. You can write an effective prompt using ordinary sentences.
Are these official Microsoft framework names?
The individual elements are officially documented by Microsoft. However, “Framework 1” and “Framework 2” are comparison labels used in this guide. Microsoft presents them as parts or elements of effective prompting, rather than as two separately branded frameworks.
Will using a framework guarantee an accurate answer?
No. A structured prompt helps make your request clearer, but Copilot can still produce incorrect or incomplete information. Important responses should always be reviewed and verified.
Official Microsoft References
- Get Started Writing Prompts in Microsoft Copilot — Goal, Context, Source and Expectations
- Get Started with Microsoft Copilot — Goal, Context, Details and Data
- Microsoft Copilot Studio — Instruction and Context
- Get Better Copilot Responses with Great Prompting
Framework terminology and source material checked against Microsoft’s official documentation in October 2026. Explanations, tables and example prompts are adapted for educational purposes by AI Prompts Work.