Give Copilot the right context and review scope

Make requests specific and check the material Copilot is working with.

Updated 2026-09-08 · English

Start from the relevant screen

Open the document, pitch, interview question or job application before opening Copilot. Inspect the context shown in the conversation. Name the section or entry when a request could apply to several places.

Make the request specific

Include the target role, desired tone and relevant job requirements. Distinguish an explanation request from an edit request. For product instructions, Copilot can consult the public Help Center and show the guides it read.

Review before applying

Check proposed changes and their target before applying them. Conversation history and persistent memory are different context sources. Do not assume the assistant has every attachment or document open; supply missing information or select the relevant context.

Useful ways to ask

  • For instructions: How do I change the background of the Experience section? Explain the steps.
  • For an edit: Shorten the first Experience entry to three bullets. Keep the employer, dates and factual results unchanged.
  • For troubleshooting: I changed a palette colour and several sections changed. Explain which setting affects only one section.

Name what you want to preserve when requesting edits. Check every proposed factual claim before applying it.

The answer uses the wrong document or section

Return to the intended document and inspect the conversation context. State the target section explicitly and ask again. Do not apply a proposal aimed at another item just because some of its wording looks useful.

If a how-to answer includes a Help Center source, open it to compare the steps with the controls you see. Describe the missing control and your current screen if they differ.