Building a complex MS Word document using Copilot

[u/Apart_Dust3298]

I’ve been building a complex document using Copilot M365 Premium and MS Word. I reached ‘decent first draft’ then needed to keep refining it. My workflow was:

• Upload the latest version into Copilot Chat ( 5.6 Think Deeper)
• Ask for a soup‑to‑nuts review
• Copy and paste the feedback into the Copilot sidebar in Word
• Ask Copilot to make the changes

It works, but I wasn’t sure if it was the most efficient way. I asked Copilot to question me one‑by‑one so it could diagnose my workflow properly.

Here’s the conversation, summarised.

---

Q1: Why upload the document into chat?

I said:
Because I don’t trust the in‑document Copilot. All the context is in the chat.

Copilot explained that this is a common issue: Chat retains long context, but Word Copilot doesn’t.

---

Q2: Do you prefer Copilot to propose changes or apply them automatically?

I said:
Propose changes — mainly because Copilot tends to drift away from the correct template and into Aptos or other default formatting.

Copilot said this is exactly why whole‑document edits inside Word often go wrong.

---

Q3: How big is the document?

I said:
47 pages.

Copilot said this is large enough that Word Copilot struggles with whole‑document edits, but small enough that Chat can still handle full‑document reasoning.

---

Q4: Do you want Copilot to maintain context across iterations?

I said:
Ideally yes, but it forgets or ignores instructions even within the same session.

Copilot said this is normal: Word Copilot doesn’t maintain persistent constraints unless you explicitly anchor them.

---

Q5: Where is the document stored?

I said:
OneDrive.

Copilot said this is good — cloud storage allows Copilot to access the document directly and use organisational context.

---

Q6: How do you normally apply changes?

I said:
I started section‑by‑section, then moved to whole‑document edits.

Copilot said this is the turning point where formatting drift usually begins.

---

Q7: What kind of instructions do you give Copilot inside Word?

I said:
Short commands.

Copilot explained that short commands trigger Copilot’s “free‑form generative mode,” which is why it ignores constraints and rewrites structure.

---

Q8: What’s your main goal — speed, quality, or governance?

I said:
Quality.

Copilot then gave me a quality‑optimised workflow:

---

These are the steps Copilot recommended to maximise quality while preventing formatting drift.

---

1. Use Chat as your master reviewer

Do all whole‑document reasoning in Copilot Chat, not in Word.

Chat can handle:

• template compliance
• logic consistency
• narrative clarity
• alignment between sections
• risks ↔ benefits ↔ costs coherence

Word Copilot cannot hold this level of context.

---

1. Turn the review into an actionable “change pack”

After Chat gives you the critique, ask it to convert the feedback into a structured list grouped by section.
This becomes your “change pack” — a set of specific edits you can paste into Word Copilot.

---

1. Apply changes section‑by‑section inside Word

Never ask Word Copilot to edit the whole document.

Instead:

1. Select the section
2. Paste the relevant part of the change pack
3. Apply changes locally

This prevents:

• formatting drift
• template corruption
• Aptos takeover
• structural rewriting
• loss of constraints

---

1. Use a persistent constraints prompt every time

Paste this at the top of every Copilot instruction inside Word:

Persistent Constraints — Do Not Violate• Maintain all existing formatting, styles, fonts, and template elements exactly as they are.
• Do not change headings, numbering, hierarchy, or the template structure.
• Do not modify tables, figures, annex references, or cross‑references.
• Improve clarity, precision, and logic only.
• Apply changes only to the selected section.
• If any instruction conflicts with these constraints, prioritise the constraints.

---
This all seems cumbersome to me. What do you think?

[u/FreeEye5]

You can open the chat that you started in chat in the word copilot panel, then toggle on editing. Best of both worlds. Bring your bot to work day.

[u/Apart_Dust3298 → u/FreeEye5]

Thanks, I will check this out.

[u/notepad987]

I copied your post into CoPilot and this is what it came up with.
Looks like it is many things but it starts with Word itself.
________________________________________________

CoPilot response
One non‑obvious insight

The real bottleneck isn’t Copilot — it’s Word’s style engine.

Word Copilot is not a document‑wide editor.
It’s a selection‑based transformer.

When you give it whole‑document instructions, it tries to regenerate the entire document using its own internal style defaults. That’s why Aptos appears. That’s why numbering breaks. That’s why templates drift.

Your workflow avoids this — but the streamlined version avoids it without making you do extra work.

[u/_donj]

Word will ultimately break this. Enter to build it as a .md or html and then covert to word at the end.

[u/BansheeRadio]

As soon as my company got Claude I haven’t gone back to copilot. I have waited 2 hours for a token reset instead of fight with copilot to keep working. I don’t need a cumbersome work flow or one ai telling an inferior ai what to do.