How to Write a Copilot Prompt That Actually Helps

When people say Copilot is "hit or miss," it's usually not the AI — it's the ask. A vague question gets a vague answer. The good news: a few small habits make a big difference, and none of them are technical.

Give it context, not just a command

Weak: "Write an email about the project."
Strong: "Write a short, friendly email to a client updating them that the project is a week behind because of a supplier delay, reassuring them we have a plan, and asking for a 15-minute call this week."

Same task, wildly different result. The second gives Copilot the situation, the tone, and the goal.

Tell it who it's for and how long

"Explain this to a non-technical manager in three short bullets" beats "summarize this" every time. Format and audience are half the battle.

Give it an example when you can

If you have a style you like — a past email, a report format — point Copilot at it: "Write this in the same style as that document." It's much better at matching an example than guessing your taste.

Refine, don't restart

The first answer is a draft, not a verdict. "Make it shorter," "less formal," "add a line about timing" — nudging beats re-writing the whole prompt.