A Copilot answer is only as good as the request behind it. If you ask “write an email about the project”, you get something generic that you rewrite anyway. Ask for the same email with a recipient, a goal, a tone and a length, and you get a draft you can send after one read. That difference is what this post is about: what a good prompt contains, and what to do when the answer misses.
What a good Copilot prompt contains
Most prompts that work have four parts. You do not need all four every time, but the more you add, the less editing you do afterwards.
-
The task. The verb that says what you want: summarise, draft, rewrite, compare, list. Start here and be specific. “Summarise” and “summarise in five bullet points for a colleague who missed the meeting” send Copilot in different directions.
-
The context. Who is this for, what happened before, why does it matter. This is the part people skip most often, and it is the part that turns a generic answer into a usable one.
-
The source. Point Copilot at the file, the mail thread, the meeting or the document it should work from. Without a source it works from general knowledge, and general knowledge does not know your project.
-
The format. Length, structure and tone. Three paragraphs or a table. Formal or informal. Bullet points or prose. Say it up front instead of correcting it after.
A short way to remember it: say what you want, for whom, based on what, in what shape.
Before and after: email in Outlook
Before: “Write an email to the client about the delay.”
You get a polite, vague message that could be about any delay at any company. The tone is probably too formal or too apologetic, and you rewrite most of it.
After: “Draft a short email to our client contact explaining that the delivery moves from the end of this month to the middle of next month. Reference the mail thread below for what we already promised. Keep it factual and friendly, three paragraphs at most, and end with a proposal for a short call this week.”
What changed: the task is specific (draft a short email), the context is there (a date change, a client who already had a promise), the source is named (the thread), and the format is set (three paragraphs, a closing proposal). Now you are editing a draft instead of writing one.
Before and after: documents in Word
Before: “Make this better.”
Copilot has to guess what “better” means. It usually means shorter and more formal, which may be the opposite of what you wanted.
After: “Rewrite this section so a reader without technical background understands it. Keep every number and every date exactly as written. Cut the sentences that repeat what the introduction already says, and keep the total length roughly the same.”
What changed: you named the reader, you protected the parts that may not change, and you said what to cut. The instruction “keep every number exactly as written” is worth adding to almost any rewrite prompt; it stops small factual drift.
Before and after: summaries of meetings and threads
Before: “Summarise the meeting.”
You get a neutral recap of everything that was said, in roughly the order it was said. Useful if you missed the whole meeting, not useful if you only need your own part.
After: “Summarise this meeting in two parts: first the decisions that were made, then the action points with the person responsible for each one. Leave out the discussion that did not lead to a decision. Mark anything that was left open as open.”
What changed: you asked for a structure that matches how you will use the summary, and you told Copilot what to leave out. Asking it to mark open items is a small addition that saves a second pass.
What to do when the answer misses
The first answer is a starting point. You do not have to start over when it misses; the faster route is to correct one thing at a time.
-
Too long or too short? Say the number. “Make this half as long” or “expand this to about 300 words” works better than “shorter”.
-
Wrong tone? Name the tone and the reader. “Less formal, as if I am writing to a colleague I know well.”
-
Made something up? Point at the invented part and add the source. “The date in the second paragraph is not in the document; use the date from the file I shared.” Always check names, numbers and dates against the source yourself, because Copilot presents a wrong detail as confidently as a right one.
-
Missed the point entirely? Do not keep patching. Start a new prompt and add the part you left implicit the first time, usually the context or the source.
-
Used the wrong file? Name the file explicitly in the next prompt. Copilot works with what it can reach; if the document lives somewhere it cannot see, it will not use it.
One habit is worth building: keep the prompts that worked. A prompt you wrote once for a weekly report or a client update works again next week with two words changed. Most people who get good results with Copilot are not writing better prompts on the spot; they are reusing prompts they already proved.
Frequently asked
How long should a Copilot prompt be? As long as it takes to include the task, the context, the source and the format. For a simple summary that is one sentence. For a client email with history behind it, three or four sentences is normal and still faster than writing the mail yourself.
Do I need to be polite to Copilot? No. Clear instructions matter; “please” and “thank you” do not change the answer.
Why does the same prompt give a different answer twice? Copilot does not repeat itself word for word. If the variation matters, be stricter about format and length, which are the parts you can pin down.
What if Copilot says it cannot find the document? Check that the file is stored where Copilot can reach it and that you named it the way it is actually named. A file on your local desktop is not the same as the same file in Microsoft 365.
Better prompts are a skill, and like any skill it comes from repetition rather than from reading about it. Pick one of the before-and-after examples above, try it on a real mail or document this week, and keep the version that worked.
