Power Platform Cloud Solutions Architect @ Microsoft | Microsoft BizApps MVP 2023 | Power Platform | SharePoint | Teams
Copilot in Word can turn rough notes and reference material into a one-page release brief, helping move scattered information into a document that is easier to review and share. It is relevant to Word users preparing product updates or other short business communications from several inputs. Damien Bird demonstrates the workflow using a fictional whisky release, combining a photo of handwritten notes, a tasting log, and the writer’s own thoughts.
The task is not simply to make handwritten notes look neater. The goal is to assemble information from different sources into a brief with a clear purpose and audience. In the example, the proposed document is for a shop team and distributors, and the subject is a new single malt called the Haar.
Copilot receives the inputs together and produces a first draft. That gives the writer a starting point for organizing the information, rather than requiring every detail to be manually transcribed and arranged before drafting. The notes, tasting log, people, and distillery in the example are fictional, and the documents are sample data.
The workflow also treats the draft as something to check, not a finished announcement to publish automatically. The writer checks the result against its sources, steps through edits before keeping them, adjusts the tone of the whole brief, and rewrites an individual line with Edit with Copilot. A further request for a second opinion provides another review step before the brief goes out.
This approach suits Word users who need to create a concise brief from several pieces of source information. The example is aimed at someone preparing a release communication for internal staff and distributors; the same basic task can apply whenever a writer needs to turn rough inputs into a structured first draft.
The stated requirement for this workflow is a Microsoft 365 Copilot license. The example begins with a photo of handwritten notes, a tasting log, and the writer’s thoughts. Those are the inputs Copilot is asked to use, so gather the relevant content before drafting and be ready to check the output against it.
Copilot can help organize and refine the writing, but the person preparing the brief still needs to verify that the draft accurately reflects the supplied information. That review matters especially for details that affect what readers understand about a product or release. Treat the generated text as a draft for the responsible writer to assess.
Gather the relevant source material: in the example, this is a photo of handwritten notes, a tasting log, and the writer’s own thoughts. The screen snip shortcut Windows + Shift + S can capture a portion of the screen to paste into the prompt.
Open Word and start a new document. The demonstration highlights the shortcut word.new as a quick way to open Word in a browser.
Give Copilot one prompt that identifies the sources and the intended output. For this example, the task is a one-page release brief based on the handwritten notes, tasting log, and personal thoughts. Naming the audience helps frame the brief’s purpose.
Read the generated draft and check it against the source information. Step through the proposed edits before keeping them, rather than accepting changes without review.
Refine the brief: change the tone across the document if needed, then use Edit with Copilot to rewrite a specific line. Ask for a second opinion as another check before the brief is sent.
Keep version history as a safety net while revising. It gives the writer a way to return to an earlier version if later changes are not wanted.
These steps make source checking part of the writing process. The first output is useful as a draft, while tone changes and line-level rewrites let the writer focus on specific improvements without starting the brief over.
The main practical constraint is that a generated draft needs review against its inputs. A polished format does not by itself establish that every statement is accurate, so compare the brief with the handwritten notes, tasting log, and any other supplied information before sharing it.
The workflow depends on having source material to give Copilot. If details needed for the brief are not in those inputs, the writer should not treat the draft as an authoritative source for them. Keep responsibility for checking the final wording with the person who owns the release communication.
Review the changes before keeping them, particularly when asking Copilot to alter the tone or rewrite an individual line. Version history provides a fallback while editing. Together, those checks offer a practical way to use Copilot as a drafting assistant while keeping control of the final document.
The workflow demonstration specifies a Microsoft 365 Copilot license. It starts with source information such as notes, a reference log, and the writer’s thoughts.
The example uses a photo of handwritten notes alongside a tasting log and the writer’s own thoughts in one prompt.
Check the draft against its sources and step through the edits before keeping them. Version history is also presented as a safety net during revisions.
The workflow changes the tone of the whole brief, uses Edit with Copilot to rewrite one line, and asks for a second opinion before sending.