← All articles

Copilot

A better prompt starts with better context.

A practical way to move from a generic request to a useful, reviewable piece of work in Microsoft 365.

Independent explanation by Frontier AI Works. Product guidance checked 12 September 2026. Business examples are illustrative.

Describe the decision

Before asking for a summary, decide what you need to do with it. Preparing for a customer meeting calls for different information from updating a project sponsor. Tell the assistant who the work is for, what decision it supports and what a useful result looks like.

Use the right material

Point to the approved documents or notes available in your work environment. Explain which material is current and which is background. Do not assume the assistant can access a file merely because you know it exists; access and product capabilities depend on your environment.

Specify a useful shape

Try: “Using these meeting notes, draft a follow-up with decisions, actions, owners and unresolved questions. Mark missing owners as unassigned. Do not invent dates.” This makes the review easier because the structure reflects the work you need to complete.

Keep the review in the workflow

Check names, amounts, commitments and dates against the source before sharing. When the result misses the point, refine the context and output requirements. Save the pattern once it is useful, then adapt it to the next task rather than treating a prompt as a permanent recipe.

Microsoft sources and further reading

Put it into practice

AI at Work

Practical Microsoft 365 and Copilot training that turns recurring tasks into thoughtful, repeatable workflows.

Explore the programme ↗

Keep exploring.