Copilot for Writing: Draft, Revise, and Keep Your Voice

Use Copilot for writing by giving it the audience, purpose, approved sources, and limits before you request a draft. Then revise the structure and wording in separate passes, checking facts against the originals before sharing anything. That process gives you something useful to edit without handing over your judgment or your voice.

For recurring assignments, fenbs can hold the approved writing instructions and project facts you reuse with connected assistants. This guide focuses on Microsoft Copilot for business writing, especially in Word. Microsoft Copilot and GitHub Copilot are different products; a connection available for one does not establish a connection for the other.

How do you start a useful first draft?

1. Choose one deliverable: a client update, proposal introduction, internal announcement, or short report.
2. Name the reader and the action you want that reader to take. State what they already know.
3. Supply the approved facts and identify the source for each important claim. Mark unsettled details as questions.
4. Request an outline or short draft, with a clear length and a list of facts that must stay unchanged.
5. Review before accepting the text. Correct the substance before polishing sentences.

For example, a design studio might need a client update explaining that the layout is approved but photography is still waiting on the client. The useful instruction is to request the missing images and explain the next step. A vague request for an impressive update invites unnecessary language and may hide the actual dependency.

Which Copilot writing features should you use?

Microsoft documents drafting from prompts or reference material in its Copilot in Word guide↗ (opens in a new tab). The available experience depends on your subscription, organization settings, and app version. Check that guide if your controls differ instead of assuming a missing option means you did something wrong.

Match the request to the stage of the document. Ask for an outline while the argument is unsettled. Ask for a short section when the evidence is ready. Select a paragraph for revision when its meaning is right but its wording needs work. Avoid repeatedly regenerating the entire document to fix one sentence.

If you are still choosing an assistant, see Copilot versus ChatGPT; the broader AI writing tools guide owns the tool comparison. Here, the decision is how to produce a reviewable document with the tool you already have.

What should you put in the writing instructions?

Describe observable writing choices. “Confident but approachable” can mean many things; “lead with the requested action, use short paragraphs, and avoid claims about guaranteed results” is easier to check. Include one short approved sample if you have permission to share it, and explain which qualities to keep.

Draft a client update using only the approved notes below.
Reader: a client who has already approved the layout.
Purpose: request the missing photography so production can continue.
Use a direct, courteous voice and short paragraphs.
Do not add delivery dates, promises, or new project facts.
Flag missing information after the draft.
Approved notes: [insert the minimum relevant facts]

Separate reusable instructions from today’s facts. The studio may always use plain language, while the missing photography belongs only to this project. Save that distinction in fenbs Skills and prompts and Decisions and rules, so the next assignment starts with the right instructions rather than an old client update.

How do you revise without losing your voice?

Read the draft as the recipient first. Can you identify the main point and requested action without searching? If the answer is no, change the order before changing adjectives. Then choose one edit at a time: reduce repetition, explain a technical phrase, or move the request to the opening.

Microsoft’s editing and rewriting instructions↗ (opens in a new tab) describe selecting text, requesting a change, and reviewing the result before replacing it or keeping an alternative. Use that review point deliberately. A smoother paragraph can still introduce a stronger promise or remove a qualification you need.

• For structure: put the decision first, followed by its reason and the next step.
• For clarity: explain specialist terms without adding new claims.
• For voice: remove stock greetings and phrases you would never say aloud.
• For accuracy: preserve uncertainty, ownership, conditions, and dates exactly as approved.

Keep a sentence you like and explain why it works. “This sounds like us because it asks directly without blaming the client” is useful feedback. “Make it better” gives the assistant little evidence about your preference and makes later revisions harder to judge.

What must you check before sharing the document?

Check names, figures, dates, source references, and promises against the approved material. Open references yourself and confirm they support the exact sentence beside them. Read for omissions too: a missing condition can change a statement even when every remaining word is accurate.

Use a final recipient check. Does the document tell the reader what to do, who owns the next action, and what still needs a decision? Remove comments and placeholders, inspect formatting in the delivery format, and have the appropriate person review sensitive commitments. Our guide to using AI at work explains the wider habit of keeping review attached to the work.

How to do this with fenbs

1. Create a free account and add the writing project to your kanban board.
2. Save the reusable drafting and revision instructions in Skills and prompts. Keep client details out of a general template.
3. Record approved communication rules in Decisions and rules, including who chose them and the scope they apply to.
4. Use a supported assistant from Integrations to read and update the record, or transfer the approved instructions into your Microsoft Copilot writing session yourself.
5. Save the review outcome and next step in Where we left off so the next session knows which draft still needs approval.

fenbs is useful when instructions and project decisions need to survive a change of assistant. It is not the right fit for editing a Word document in place or running Microsoft Copilot: its listed Copilot connection is GitHub Copilot. For a single short draft, a checklist beside the document may be all you need.

After the next assignment, keep only the instructions that helped and revise those that produced repeated mistakes. Explore the AI at work library for adjacent workflows. Your practical starting point is one approved prompt and one clearly stated review rule, ready before you open another blank document.