Skip to main content
← Back to course

MCM-WD-1.1

Turn a Draft into a Funder-Ready Proposal

This video uses AI-generated narration.

Most Copilot demos show it writing from a blank page. This one shows the more common real job: you already have a draft, and it needs to be better before it goes out the door.

The starting point: a real grant proposal — one of Word's own templates, 433 words, written the normal way. Not empty, not perfect.

The request: "Suggest ways to improve this document." One click on a suggestion chip, nothing typed.

What Copilot actually does:

  • Reads the entire document before saying anything back.
  • Comes back with 9 high-impact suggestions, grouped into three categories — funding case and reader focus, program logic and funding rationale, evaluation clarity and accountability.
  • Explains why for each one. Its first suggestion, "Lead with the funding decision," comes with real reasoning: an executive summary that opens with a mission statement instead of the $50,000 ask buries the thing the funder actually needs to decide on, first.
  • On request, applies the rewrite directly in the document — not a comment in the margin, an actual edit, visible and tracked with Accept/Undo, after planning the change and verifying its own work.

Why this is the more useful demo: editing is where most people's real writing time goes, not blank-page drafting. Watching Copilot critique, justify, and then actually execute a specific improvement — live, in a document you can see — is a closer match to how editing work actually happens than a "write me an essay" prompt.

The upgrade: from a suggestion chip to an editor's brief

The one-click chip got good results because the proposal was short and its purpose was obvious. Your documents often won't be. When Copilot doesn't know who will read a document or what decision that reader has to make, it falls back on safe, generic advice: "add more detail," "consider your audience," "strengthen the conclusion." You can stop that by telling it what a real editor would ask about before starting.

Vague prompt — what most people type
Suggest ways to improve this document.
Engineered prompt
Act as a grant reviewer at a regional community foundation who reads 40 proposals a cycle and has about five minutes for each one. Review this proposal the way you would in a real scoring meeting.

1. Tell me, in one sentence, what decision this proposal asks you to make and whether that is clear within the first 100 words.
2. List the 5 weaknesses most likely to cost us points, ranked by impact. For each, quote the exact sentence that causes the problem and explain why a reviewer would mark it down.
3. Flag any claim that is not supported by a number, a source, or an example.
4. Do not rewrite anything yet. Respond in chat only.

What each part changes:

  • The role ("grant reviewer… 40 proposals… five minutes") changes the criteria. Copilot stops judging the writing as prose and starts judging whether it gets funded.
  • The decision question makes Copilot check the single most common proposal failure: an ask buried under background.
  • "Quote the exact sentence" makes the feedback checkable. You can find every point in the document, so vague advice is easy to spot and drop.
  • "Ranked by impact" and a fixed count of 5 stop the answer from becoming a laundry list. You get the fixes that matter, in the order to do them.
  • "Do not rewrite anything yet" keeps your document untouched while you decide. Copilot in Word normally opens in a mode that can edit the document; asking for chat-only feedback (or choosing a chat-only option if your version shows one) keeps diagnosis separate from surgery.
Current limitations· as of November 2026
  • Suggestions are opinions, not facts. Copilot's critique is pattern-based. It doesn't know this funder's priorities, scoring rubric, or past awards unless you give them to it. Check its advice against the actual funding guidelines.
  • It can invent supporting detail. Asked to "strengthen" a section, Copilot may add plausible statistics, outcomes, or partner names that aren't in your source. Every number in a funded proposal has to be one you can defend.
  • Edits land in your real document. When Copilot applies a rewrite, review it with the same Accept/Undo care you'd give a colleague's tracked changes. On shared documents, Copilot previews the proposed change and doesn't apply it until you approve.
  • Length matters. Microsoft notes that Copilot can only process a limited number of words per prompt. A 433-word proposal is easy; a 60-page application may get a shallower review, so review it a section at a time.
  • Availability varies. Which Copilot features appear in Word depends on your license (Microsoft 365 Copilot vs. the free Copilot Chat), your organization's settings, and the platform you're on.

▶️ Try this

Open a document you've already written — a proposal, a status update, anything with real paragraphs — and ask Copilot the same question: "Suggest ways to improve this document." Read its reasoning before you decide whether to apply anything; the explanation is often more useful than the edit itself. Then run the reviewer prompt above with the role changed to your actual reader, and compare the two lists. The second one is usually shorter, sharper, and easier to act on.

Key takeaways
  • Editing an existing draft is where Copilot in Word earns its keep. Ask for critique first and rewrites second.
  • A one-click suggestion is a fine start. A prompt that names the reader, the decision, and the format gets feedback a professional editor would recognize.
  • Ask Copilot to quote the sentence behind each criticism so you can check every point.
  • Review every applied edit like a tracked change from a colleague, and never keep a number you can't source.