04 — Copilot Pages: Prompts
Use these prompts to build, refine, and finalise your AI Usage Guide draft in Copilot Pages.
How this topic connects to Topic 03: At the end of Topic 03 you produced a structured research outline using the consolidation prompt. That outline is your starting point here.
If you are still in the same Copilot Chat session from Topic 03: click … under your consolidation response → Edit in Pages → Add to new page and skip straight to Part 3.
If you closed that session: paste your outline into a new Copilot Chat, run the Part 2 prompt below, then click … under the response → Edit in Pages → Add to new page.
If you did not complete Topic 03: run the Part 2 prompt directly in Copilot Chat. It will generate a draft from scratch.
Session guide: Parts 1 and 2 run in Copilot Chat. Parts 3 onwards run inside Copilot Pages using the Copilot panel. Stay in the same Page for all refining work.
Part 1 — Rename your chat session
Before continuing, rename your Copilot Chat session so it is easy to find later.
In the left sidebar, hover over the chat under Chats, click the three dots (…), choose Rename, and rename it to:
AI Usage Guide Draft - [your department]
Examples:
AI Usage Guide Draft - HR
AI Usage Guide Draft - Finance
AI Usage Guide Draft - Operations
Renaming the session makes it easy to return to the same conversation if you close the browser or switch devices. It also makes the “Recent pages” list in Copilot much easier to navigate.
Part 2 — Generate your first draft in Copilot Chat
Run this in Copilot Chat, then click Edit in Pages on the response.
Option A — If you have your Topic 03 research outline:
Paste your outline into the chat first, then submit this prompt:
Using the research outline above, create a structured first draft
of an AI Usage Guide for my department.
Include these sections:
1. Introduction and Purpose
2. Scope: who this guide applies to
3. Approved AI Tools
4. Dos and Don'ts
5. Data Privacy Rules and PDPA Obligations
6. Human Review and Accountability
7. How to Report Issues or Mistakes
8. Review and Update Schedule
Write each section with real content based on the research above.
Keep the language clear and suitable for non-technical staff.
Aim for 600 to 800 words total. Use pages for this task.
Option B — If you are starting from scratch:
Create a structured first draft of an AI Usage Guide for
[your department] at a mid-sized Malaysian company.
Include these sections:
1. Introduction and Purpose
2. Scope: who this guide applies to
3. Approved AI Tools
4. Dos and Don'ts
5. Data Privacy Rules and PDPA Obligations
6. Human Review and Accountability
7. How to Report Issues or Mistakes
8. Review and Update Schedule
Write each section with real content suitable for non-technical staff.
Reference PDPA 2010 in the Data Privacy section.
Aim for 600 to 800 words total.
Once the draft appears, click … under the response → Edit in Pages → Add to new page. All remaining prompts in this topic should be run inside Copilot Pages.
Part 3 — Review and improve the overall structure
Run this inside Copilot Pages using the Copilot panel.
Review this AI Usage Guide draft and improve the structure.
Make the document easier to read by:
- improving the section headings to be clearer and more action-oriented
- grouping related ideas together
- removing any repeated points
- converting long paragraphs into shorter paragraphs or bullet points where appropriate
- making the flow more logical for an employee reading this for the first time
Do not remove any important policy, privacy, or risk information.
Part 4 — Rewrite the Introduction
Rewrite the Introduction section so it opens with a short
one-sentence workplace scenario showing why having an AI
guideline matters.
After the scenario, explain the purpose of the guide in 2
to 3 sentences.
Keep the tone professional, warm, and suitable for
non-technical staff. Avoid jargon.
Part 5 — Strengthen the Dos and Don’ts section
The Dos and Don'ts section is too generic. Rewrite it with
at least 3 specific examples relevant to [your department].
Format it as a table with two columns: Do and Do Not.
Keep each point to 1 to 2 sentences. Include the reason
behind each point so employees understand why, not just what.
Part 6 — Add department-specific examples
Add a new section called "Examples of AI Use in [your department]".
Include at least 5 practical examples of how AI tools can
help with real tasks in this department.
For each example, include:
- the task name
- how AI can assist
- what the employee must check before using the output
Keep examples realistic for a Malaysian corporate workplace.
Part 7 — Strengthen the Data Privacy section
The Data Privacy section needs more depth. Improve it by:
1. Adding a paragraph explaining why PDPA 2010 matters
specifically when employees use AI tools.
2. Adding a clear list of information employees must never
enter into any AI tool, including:
- personal data of employees or customers
- IC numbers, passport numbers, or any government ID
- salary, bank account, or financial details
- confidential business strategies or unpublished financials
- client contracts or legally privileged information
- passwords or system credentials
Keep the wording practical and easy to understand for
non-technical staff.
Part 8 — Add Human Review and Accountability
Add a section called "Human Review and Accountability".
Explain that AI tools assist employees but do not replace
human judgement. Include guidance on:
- always reviewing AI output before using it
- checking facts and verifying sources independently
- reviewing tone and appropriateness for the audience
- watching for signs of hallucination or inaccuracy
- confirming that all final decisions remain with a human
- not copy-pasting AI output directly without reading it first
Keep the tone practical and non-technical. Use short
paragraphs or a bullet list.
Part 9 — Add a FAQ section
Add a short FAQ section at the end of the guide with the
title "Frequently Asked Questions".
Write 6 questions that a new employee might ask on their
first week using AI tools at work. For each question,
write a clear, direct answer in 2 to 3 sentences.
The questions should cover: what is allowed, what is not
allowed, what to do if something goes wrong, whether AI
output can be trusted, and how to get help.
Part 10 — Final polish
Do a final review of the entire document. Check for:
1. Consistency: same tone and style throughout
2. Clarity: no unexplained jargon or acronyms
3. Completeness: nothing important missing for a staff-facing policy
4. Length: is any section too long or too short?
5. Formatting: are headings, lists, and paragraphs used consistently?
List what you changed and why. Then show the improved version.
Part 11 — Create a Mermaid decision flowchart
This part is done in Copilot Chat, then pasted into Pages manually.
Run this prompt in Copilot Chat to generate the diagram code:
Create a Mermaid flowchart for the decision an employee should
make before using an AI tool for a work task.
The flowchart should include these decision points:
1. Does the task involve confidential or personal data?
2. Is the AI tool approved by the organisation?
3. Is manager approval required for this type of use?
4. Is the task suitable for AI assistance?
5. Has the output been reviewed before use?
Use clear, short labels on each node. End with either
"Proceed with AI assistance" or "Do not use AI for this task".
Give me the raw Mermaid code only, no explanation.
To insert the diagram into your Pages document:
- In your Copilot Page, place your cursor where you want the diagram
- Type
/to open the insert menu - Select Mermaid
- Select the sample code inside the block and paste the Mermaid code Copilot generated over it
- The diagram renders below the code. Use Display options (top right of the block) to switch between Code, Preview, and Horizontal split view
If the diagram does not render: check that the language selector at the top right of the block is set to Mermaid and not to “code” or left blank. This is the most common reason it does not work.
Part 12 — Prepare for export
Run this final check before exporting to Word:
This document will be exported to Microsoft Word and submitted
to management as a formal proposal. Review it one more time with
that audience in mind.
Suggest any final changes that would make it more suitable for
senior management review. Focus on:
- the executive summary or introduction
- the professional tone throughout
- anything that looks incomplete or informal
- any section that needs strengthening before it goes to a manager
Once you are satisfied with the draft:
- Click the … menu at the top right of your Page
- Select Export
- Choose Document (Word)
You will use this Word document in Topic 05 to reformat it as a formal management proposal.