Draft a Process Design Document in Word with Copilot

What This Does

A process design document usually starts as a blank page and a pile of scattered workshop notes. Copilot in Word can draft it section by section instead, pulling directly from files already sitting in your SharePoint or OneDrive rather than requiring you to paste everything in by hand. For a document that has to follow the client's own template, this produces a structured first draft you edit rather than one you build from nothing.

Before You Start

• Your account has the Microsoft 365 Copilot add-on. In-app Copilot in Word now sits behind a paid license on top of a qualifying Microsoft 365 plan (available on some Microsoft 365 business plans; check with your firm's IT or Microsoft's pricing page). Look for a Copilot icon in the Word ribbon or sidebar.
• Your workshop notes and the client's process design document template live in the same Microsoft 365 tenant you are drafting in, the client's tenant if this is a client deliverable, since Copilot can only reference files it has permission to open there.
• Your workshop notes describe the process and the agreed gap in general terms rather than including a client's actual production data, account numbers, or employee records. Draft with placeholders where a real number or name is not yet needed.

Steps

1. Start a new document from the client's template

Open a copy of the client's process design document template in Word so the section headings and formatting are already in place. Working from the client's actual template avoids a reformatting pass later.

2. Reference your source notes instead of retyping them

In the Copilot pane, use the "/" command to reference your workshop notes file, or another document Copilot can access in your tenant, directly in your prompt rather than copying and pasting the whole thing.

3. Ask for a full first draft, section by section

Describe the gap, the target module, and the section headings you want filled in, and ask Copilot to draft the document using your referenced notes as source material.

4. Review, mark open items, and fill gaps

Read every section against what was actually discussed and decided in the workshop. Mark anything Copilot could not have known (a screenshot, an exact field name, a specific approval threshold) as an open item rather than letting a plausible-sounding placeholder stand in for it.

Real Example

Scenario: A gap was approved for auto-applying a two percent early payment discount when a Dynamics 365 Finance invoice is paid within ten days, and the client's process design document template requires Overview, Current State, Future State, Configuration Approach, Assumptions, and Open Questions sections.

What you type: "Draft a process design document for this gap: the system needs to auto-apply a two percent early payment discount when an invoice is paid within ten days. Target platform is Dynamics 365 Finance. Use my referenced workshop notes from /OTC-Workshop-Notes.docx for the current state description, and structure the document with these sections: Overview, Current State, Future State, Configuration Approach, Assumptions, Open Questions."

What you get: A structured first draft with each section filled in from the referenced notes, plus flagged gaps where a specific field name or approval threshold still needs to come from the technical team.

Tips

• Keep one reference file per workshop up to date as you go rather than assembling raw notes right before drafting. Copilot drafts better when the source file is already organized by topic.
• Ask Copilot to flag anything it inferred rather than found directly in your notes, so you know exactly what to verify before the document goes to the client.
• Reuse the same section-heading prompt across every gap in a module. Consistent phrasing keeps the tone and structure aligned across the whole document set.

Tool interfaces change. If a button has moved, look for similar AI/Copilot options in the ribbon or sidebar.