CRAFT: The Prompting Framework That Changes What Copilot Returns

Most people prompt Copilot the way they type into a search bar — a few words and an expectation that something useful will come back. It rarely does. Not because Copilot is weak, but because a vague question gets a vague answer.

The CRAFT framework is a five-step structure I teach in every Copilot training I run. It is not a workaround for a bad tool. It is a systematic way of giving any AI model — Copilot, ChatGPT, Gemini — enough context to produce output worth using.

C — Character

Before you tell Copilot what to do, tell it who to be. "Act as a senior HR business partner summarising a policy change for non-technical staff" gets a fundamentally different output than "summarise this policy." The character instruction sets the lens Copilot uses for the entire response.

Without it, you get average-of-the-internet output. With it, you get something tailored to your actual audience. This is the step that produces the most visible improvement in workshops, and it costs you about ten seconds.

R — Request

Be specific about what you want. Not "write an email" but "write a 150-word email that opens with the key decision, gives two supporting reasons, and ends with a clear next step." Precision in the request cuts editing time significantly. Generic requests produce generic outputs that need heavy reworking.

A — Add Context

This is the step almost everyone skips. Copilot does not know your audience, your organisation's vocabulary, or the political sensitivity of what you are working on — unless you tell it. One extra sentence of context changes the output more than any other part of the prompt.

"This is for a team in Pune with no prior AI exposure" will change the register, complexity, and assumptions in everything that follows. Context eliminates assumption. Assumption is why AI drafts often feel slightly off.

F — Format

Tell Copilot how to structure the output. Bullet points or prose? Under 150 words or a full page? Table or narrative? If you do not specify, you will spend more time reformatting than you saved generating. Format instructions take five seconds to write and routinely save twenty minutes of editing.

T — Tune

Set the tone. Formal but not stiff. Confident but not aggressive. Technical enough for the audience but no more. Tune is the instruction that stops Copilot from defaulting to generic corporate language when you need something that sounds like you actually wrote it.

What this looks like in practice

Without CRAFT: "Write a summary of last week's project update."

With CRAFT: "Act as a project manager writing for a steering committee with no operational detail. Summarise the three key decisions from last week's project update, flag one open risk, and close with a recommended next step. Use bullet points, under 200 words, formal but plain language."

Same raw material. Very different output. The second prompt takes about 45 seconds longer to write. It saves 20 minutes of editing and produces something you can send without rewriting it from scratch.

The people who get the best results from Copilot are not the most technical people in the room. They are the ones who have learned to give clear instructions. CRAFT is a repeatable structure for exactly that.

CRAFT is one of the core frameworks in our Copilot 365 training programme. If you want your team to get real value from the licences already in place, a 30-minute conversation is a good place to start.