doc-coauthoring

To co-author long-form documents with Copilot, use a three-stage workflow consisting of context gathering, section-by-section refinement, and reader testing. This pipeline applies to proposals, PRDs, design docs, RFCs, and technical specs.

Yes, you can draft proposals directly in Word or SharePoint. The co-authoring workflow guides document creation within these platforms using structured sections and stage-specific prompts to refine the content.

The best way to start writing a design doc or RFC is to tell Copilot the document type, audience, and desired impact. This initiates Stage 1: context gathering, which sets the foundation for the subsequent refinement and testing stages.

Reader testing is the third stage of the co-authoring workflow. It functions as a validation check after context gathering and section refinement, ensuring the finalized proposal, decision memo, or technical spec effectively communicates with its intended audience.

Yes, the co-authoring workflow explicitly supports decision memos and technical specs. It handles any substantial structured long-form document by applying its three-stage pipeline to gather context, refine sections, and test readability.

You should use a structured workflow for writing a document in Word when drafting substantial long-form content such as proposals, PRDs, design docs, RFCs, or decision docs. Triggers include commands like write a doc, draft a proposal, or write up the PRD.