05 — Copilot in Word: Prompts
Use these prompts to turn your AI Usage Guide draft into a formal management proposal.
Session guide: All prompts in this topic are used inside Microsoft Word, not in Copilot Chat. Use the Copilot panel (round Copilot button, bottom right of the document) for structural and document-wide prompts. Use Edit with Copilot (select the text, then click Edit with Copilot in the mini toolbar) for section-level rewrites. You do not need to start a new Copilot Chat session for this topic.
Part 1 — Reformat as a proposal
Use the Copilot Chat panel for this prompt.
This is your starting point. Run this first before making any other changes.
Reformat this document as a formal proposal to submit
to management. Add these sections if they are not
already present:
1. Executive Summary (max 150 words)
2. Business Justification: why this guideline is needed now
3. Implementation Steps: what needs to happen to roll this out
4. Expected Outcomes: what the organisation will gain
5. Approval and Sign-off section
Keep all existing content but adjust the tone to be
formal and suitable for senior management.
Part 2 — Strengthen the Executive Summary
Select the Executive Summary and use Edit with Copilot, or use the Copilot panel.
Rewrite the Executive Summary in exactly 3 sentences:
- Sentence 1: the problem this guideline addresses
- Sentence 2: the proposed solution
- Sentence 3: the expected benefit to the organisation
Keep it under 80 words. Make it compelling enough that
a busy senior manager will want to keep reading.
Part 3 — Strengthen the Business Justification
Use the inline Copilot on the Business Justification section.
The Business Justification section needs to be stronger.
Add 2 specific realistic examples of risks that Malaysian
companies have faced or could face when employees use AI
tools without formal guidelines.
Focus on data privacy risks and reputational risks.
Keep it factual and professional.
Part 4 — Add a risk section
Add a new section called "Risk of Not Having This Guideline".
Include 3 consequences for the organisation if AI usage
remains unregulated. Write each consequence as a short
paragraph covering: what could happen, why it matters,
and how it could have been prevented.
Keep the tone factual and professional, not alarmist.
Part 5 — Adjust tone and style
Use the Copilot Chat panel to apply this across the whole document.
This document will be submitted to senior management for
approval. Review the entire document and rewrite any
sections that are too informal, too casual, or too
conversational for a management submission.
Keep the language clear and easy to scan. Use formal
business English throughout. Do not make it overly
academic or difficult to read.
Part 6 — Improve the Dos and Don’ts section
Use the inline Copilot on that section.
The Dos and Don'ts section currently reads as a rules list.
Rewrite it as a set of guided principles.
For each point, add a one-sentence rationale so employees
understand why the guideline exists, not just what it says.
Keep each point to 2 to 3 sentences maximum.
Part 7 — Cross-reference with existing company policy
Use the Copilot Chat panel with the / key to reference a file.
If you have your company’s IT policy, HR policy, or data privacy policy in OneDrive, reference it here. Type / in the Chat panel and select the file.
Using the [type / and select your company policy file],
check whether any recommendations in this AI Usage Guide
conflict with our existing company policy.
List any inconsistencies and suggest how they could be
resolved so both documents align.
If you do not have a company policy file, use the workshop sample document instead:
Using the [type / and select Data_Privacy_AI_Acceptable_Use_Policy],
check whether any recommendations in this AI Usage Guide
conflict with the data privacy policy.
List any inconsistencies and suggest how to resolve them.
Part 8 — Final formatting check
Use the Copilot Chat panel.
Review the entire document for formatting consistency.
Check that:
- all headings use the same style and hierarchy
- all bullet points are parallel in structure
- the tone is consistent throughout
- no sections are significantly longer or shorter
than the others without good reason
- all section titles are clear and action-oriented
List what you changed and why.
Part 9 — Create a cover summary page
Use the Copilot Chat panel.
Create a one-page cover summary for this proposal.
Include:
- Document title
- Purpose statement in 2 sentences
- 3 key recommendations as bullet points
- Prepared by: [your name and department]
- Date: [today's date]
- A sign-off block with spaces for: name, designation,
date, and signature
Format it cleanly so it can be used as the first page
of the proposal when printed.
Part 10 — Using Track Changes
Before making final Copilot revisions, turn on Track Changes so you can review and accept or reject each change individually.
- Go to the Review tab in the ribbon
- Click Track Changes to turn it on
- Submit any remaining Copilot prompts
- Review the suggested changes one by one using Accept or Reject
This is especially useful when Copilot rewrites whole sections and you want to keep parts of the original.
Make one final pass over the document. Tighten any
sentences that are longer than 25 words. Remove any
filler phrases like "it is important to note" or
"in order to". Keep the meaning intact.
Part 11 — Prepare to send
Once you are satisfied with the proposal, save it and prepare it for Topic 06 where you will email it to your supervisor for approval.
Write a brief handover note summarising this proposal
in 5 bullet points. This will be used as the body of
an email to my supervisor requesting approval.
Include: what the document is, why it was created,
what action is needed from the reader, the deadline
for a response, and who to contact with questions.
Save this output. You will use it in Topic 06.