Most people meet Copilot in Word the same way. New blank document, click the icon, type “write me a proposal,” hit Generate.

Out comes 400 words of beige. Technically correct. Completely generic. The kind of thing that could be about your business or anyone else’s.

So they shrug, decide Copilot “isn’t that good,” and go back to writing from scratch.

Here’s the thing. They weren’t using Copilot wrong. They were using the worst part of it and ignoring the best part.

A blank page is the one thing Copilot is genuinely bad at. Give it nothing and it gives you nothing — just confident, well-punctuated filler. The magic isn’t in asking it to invent. It’s in pointing it at what you already have.

What is Copilot in Word, really?

Forget the demos where someone conjures a document from a one-line prompt. That’s the party trick, not the job.

What Copilot in Word actually does well is take your material — a file, an email, a meeting, a folder — and reshape it into something new. The official term Microsoft uses is grounding. The button you press is Reference a file.

That’s the whole ballgame. You’re not asking a stranger to guess what your last client proposal looked like. You’re handing it the last one and saying “another like this.”

So the question stops being “can Copilot write?” and becomes “what do I already have that Copilot can stand on?” For most SMBs, the answer is a lot. Years of proposals, reports, policies, and SOWs sitting in OneDrive, doing nothing.

Step-by-Step: drafting from something you already have

This is the workflow I show every client. It takes about ninety seconds.

Open a new document

Start a blank document in Word, then click the Copilot icon. You’ll get the Draft with Copilot box. Don’t type your prompt yet.

Reference the file first

Click Reference a file (the paperclip), and start typing the filename. Pick the document you want Copilot to learn from — an old proposal, a strong report, a policy you’re proud of. You can attach more than one. Microsoft has the full walkthrough in Draft and add content with Copilot in Word, and the Welcome to Copilot in Word page confirms it only ever looks at the files you choose — nothing else.

Write your prompt

Now tell it what you want, and point it back at what it’s holding:

Draft a one-page proposal for Acme Pty Ltd.
Reference: /Northwind-Proposal.docx /Acme-Discovery-Notes.docx
Match the structure and tone of the Northwind proposal.
Keep it under 400 words.

Notice what’s missing? Nowhere do I explain what a proposal is. I’m not teaching Copilot to write. I’m showing it how we write and telling it to do that again.

Keep, regenerate, or bin it

Copilot drops the draft in. Keep it, Regenerate for another go, or Discard. Then you edit like a human — because you still have to.

Why this actually changes behaviour

Before: “Copilot, write me a client report.” → generic mush you rewrite anyway. After: “Copilot, write this report the way I wrote the last three.” → a first draft that already sounds like the business.

That second one is the difference between a toy and a tool.

Here’s the real win for MSPs. Grounding turns your clients’ own document history into an asset they didn’t know they had. Every good proposal becomes a template. Every solid SOP becomes a pattern. The licence they’re already paying for suddenly does something a free chatbot never can — because the free chatbot can’t see their files.

And it’s not just drafting. Flip it around and Copilot becomes a reading tool. Open a long contract, type Summarize this document, and it’ll hand back the gist with citations back to the source — chat with Copilot about your Word document covers that side. Summarize before you read. Draft from what you’ve got. Same tool, both directions.

Don’t ask Copilot to know your business. Show it.

If you’re rolling Copilot out to clients and the first thing you teach them is “type a prompt on a blank page,” you’ve handed them the weakest trick in the box and you’ll get the predictable shrug.

Teach Reference a file first. That’s where the value lives, and it’s the bit nobody stumbles onto by accident.

Reference a file isn’t there to help you write faster. It’s there to make sure what gets written already sounds like you.