Heads up: this browser is blocking local storage, so your progress will not be saved after you close the page.
Lab 5 · Module 4 · Create and Calculate
Build a Presentation in PowerPoint
Step 1: why this is needed and what each entry does
Give Copilot in PowerPoint the source memo (Put the memo in OneDrive and open PowerPoint). Copilot builds slides from a file it can reach: your memo from Lab 4, or the sample memo 05A.
- OneDrive
- Copilot in PowerPoint finds files through the / picker, which lists OneDrive and SharePoint only.
- Your memo or 05A
- Either is fine. 05A exists so the lab works even if you skipped Lab 4.
Step 2: why this is needed and what each entry does
Build five slides from the memo (Generate the slides). The prompt asks for five slides that say no more than the memo. Copilot shows an outline first; you approve it before slides exist.
- Create presentation from file
- The built-in starter does the same thing. Our prompt adds the rule: no claim the memo does not make.
- The outline
- Your first checkpoint. Remove any slide topic that is not in the memo before slides are made.
Step 3: why this is needed and what each entry does
Refine one slide, nothing else (Make one change). One deliberate edit shows how Copilot changes a deck without you redoing it, and lets you check it did only that.
- Only one change
- Copilot edits can ripple. Checking the untouched slides is part of the lab.
Step 4: why this is needed and what each entry does
Compare each slide with the memo (Check every number). Slides compress. Compression is where a range becomes a single number and a maybe becomes a will.
- Numbers first
- Rounded or invented numbers are the most common slide error, and the hardest to walk back in a meeting.
Step 5: why this is needed and what each entry does
Decide what the deck can claim (Check and record). A deck is ready when no slide says more than the memo.
- Five Checks
- Source: which file. Verification: did you open it. Context: did the caveats survive. Resilience: would it still hold if the data changed. Authorized Owner: who signs off before anyone acts on it.
The prompts for this lab: copy and paste
Same prompts as in the Prompts section and the Do it steps. Paste each one whole.
Overview
What we are doing
- The situation
- A one-page project memo needs to become five slides for the directors' meeting.
- Your role
- You are presenting the project memo to department directors.
- Your task
- Use Copilot in PowerPoint to turn the memo into five slides.
- Files you need
- File 05A (05A_Sample_Memo.docx). If you did Lab 4, you can use your own memo instead.
- Done when
- You have five slides. Every claim and number on them also appears in the memo.
- Why it matters
- Slides squeeze text. When text is squeezed, a number can change or a caution can vanish. You check every slide against the memo.
Check before you finish
- Does any slide make a claim that the memo never made?
How to do it: the basic steps
5 steps, one screen each. Select the ? on a card for why the step is needed and what each entry does.
- Give Copilot in PowerPoint the source memo (Put the memo in OneDrive and open PowerPoint)
Why: Copilot builds slides from a file it can reach: your memo from Lab 4, or the sample memo 05A.
- Download 05A_Sample_Memo.docx (or use your Lab 4 memo)
- Save to OneDrive
- PowerPoint
- Blank presentation
Download 05A_Sample_Memo.docx from the Files step (or use your own memo from Lab 4) and save it to OneDrive. Open PowerPoint (work account) and start a Blank presentation.
- Build five slides from the memo (Generate the slides)
Why: The prompt asks for five slides that say no more than the memo. Copilot shows an outline first; you approve it before slides exist.
- Home
- Copilot
- Copy prompt
- Type / and pick the memo
- Send
- Generate slides
On the Home tab select Copilot to open the pane. Select Show the prompts below, copy the Create prompt, paste it, type / and pick the memo, then Send. Review the outline, then select Generate slides.
- Refine one slide, nothing else (Make one change)
Why: One deliberate edit shows how Copilot changes a deck without you redoing it, and lets you check it did only that.
- Copy prompt (Refinement)
- Send
- Check the one slide
Copy the Refinement prompt into the Copilot pane and Send. Make only this one change. Check that other slides did not change too.
- Compare each slide with the memo (Check every number)
Why: Slides compress. Compression is where a range becomes a single number and a maybe becomes a will.
- Each slide
- Each number
- Memo says?
Open the memo next to the deck. For every number and every claim on every slide, find it in the memo. Anything the memo never said gets deleted or labeled.
- Decide what the deck can claim (Check and record)
Why: A deck is ready when no slide says more than the memo.
- Any slide beyond the memo?
- Five Checks
Did any slide gain a claim the memo never made? Run the Five Checks: Source, Verification, Context, Resilience, Authorized Owner. Then mark the lab steps done.
= why the step is needed and what each entry does. Like this = something you select or click. Like this = something you type or paste.
Microsoft changes these screens often; a label on your screen may differ slightly. If a button is missing, your organization may not have turned the feature on: use the Path B steps.
Where to click
- PowerPoint
- Blank presentation
- Home
- Copilot
- your memo (or file 05A)
Watch where to click Illustration - not the actual Copilot screen
A simplified, labeled diagram of the clicks. It is not the actual Copilot screen. The step list below the player is the text version.
Do it: step by step
Check off each step as you go. Your progress saves in this browser.
Path B (Copilot Chat only)? These steps are for Path A. Use the Path B steps in the Files step instead.
Prompts: vague vs detailed
Follow the brackets. The detailed prompt is built from the four C.H.A.T. parts: [Context], [How come], [Assign task], and [Type of output]. Keep the labels when you paste it; Copilot reads them fine, and they help you check that each part is there.
Compare a vague prompt with a detailed, source-checkable prompt. The activity below separates the request from the Guardrails you need before use.
Use CHATPROMPT to shape the request: Context, How come (why you need it), Assign task, Type of output, Persona, References, Optimize, Modularize, Progression, and Transcendence (expert level: the next useful question after the checked answer). Add Guardrails separately for training-only input, source checking, limits, and the Authorized Owner.
Create prompt
Make a presentation from this.
[Context] I am presenting the project memo to department directors. [How come] Every claim and number on the slides must also appear in the memo. [Assign task] Create a five-slide presentation or outline from the memo I shared (file 05A or my own memo) for department directors. Use only information in the memo. [Type of output] Five slides: the problem, the evidence, the options, the recommendation, and next steps. For each slide, give a title and up to five bullets.
Why the detailed version works (letter by letter)
- CContext
I am presenting the project memo to department directors
- HHow come
Every claim and number on the slides must also appear in the memo
- AAssign task
Create a five-slide presentation or outline from the memo I shared
- TType of output
the problem, the evidence, the options, the recommendation, and next steps
- RReference
from the memo I shared
- GGuardrail: keep it off-limits
Use only information in the memo
Use CHATPROMPT to shape the request, as described above the first prompt.
Refinement prompt
Fix the slides.
[Context] Same presentation or outline as the Create prompt. [How come] I am making one change at a time so I can see exactly what changed. [Assign task] Reduce the text on the evidence slide. Change nothing else. [Type of output] Cut it down to three short bullets.
Why the detailed version works (letter by letter)
- CContext
Same presentation or outline as the Create prompt
- HHow come
so I can see exactly what changed
- AAssign task
Reduce the text on the evidence slide
- TType of output
to three short bullets
- OOptimize: refine and recheck
I am making one change at a time
Quiz
Self-check only. Answers stay on your device.
Path B Text Pack and downloads
Download the practice files (Path A)
Path A (full access): these downloads are for you. Save them where Copilot can reach them (OneDrive for the Office app labs). Path B: nothing to download; the files are below as text, ready to paste. Path C: nothing to download; read the text below when you check sources.
Path B (Chat only): short steps
Path B makes a five-slide outline in Copilot Chat, not a PowerPoint file. It uses the sample memo, file 05A, which is already in the Copy all text.
- Select Copy all files + create prompt below, paste it into the chat, and select Send. You get a five-slide outline, not a PowerPoint file.
- Copy Refinement prompt below and send it in the same chat.
- Compare every number and claim in the outline with the memo text below.
These prompts work on both paths. They say "I shared," which fits whether you attach or paste the files.
[Context] I am presenting the project memo to department directors. [How come] Every claim and number on the slides must also appear in the memo. [Assign task] Create a five-slide presentation or outline from the memo I shared (file 05A or my own memo) for department directors. Use only information in the memo. [Type of output] Five slides: the problem, the evidence, the options, the recommendation, and next steps. For each slide, give a title and up to five bullets.
[Context] Same presentation or outline as the Create prompt. [How come] I am making one change at a time so I can see exactly what changed. [Assign task] Reduce the text on the evidence slide. Change nothing else. [Type of output] Cut it down to three short bullets.
File 05A - Sample Memo (backup for Lab 5) (1,644 characters)
FICTIONAL TRAINING FILE - The City of Fernhollow, its staff, residents and data are invented for the CPS HR Microsoft 365 Copilot workshop. Do not use real work data. MEMORANDUM ========== TO: Department Directors · FROM: Jordan Ekwueme, Senior Analyst · DATE: October 9, 2026 · SUBJECT: Service Request Improvement Project - Phase 1 Findings and Proposed Next Steps Purpose ------- This memo shares what we learned about the growing service-request backlog and the options we propose to test. It is for information; no decision is requested today. What we found ------------- 1. The backlog doubled between January and May 2026, from 135 to 270 open requests at month end. 2. Average days to resolve rose from 6.1 days in January to 8.4 days in June. 3. About 31 percent of sampled requests (300 requests, April-May) were first sent to the wrong unit. Options we considered --------------------- - Keep the current process and add overtime (short-term relief only). - Add a single intake triage step (recommended). - Add Saturday intake hours (proposed by the Intake Lead; requires confirmation of staffing and cost). Recommendation -------------- Pilot a single intake triage step, publish a weekly backlog report, and send plain-language status updates to residents. Risks ----- Four of 22 positions are vacant; August data are incomplete; residents who do not use the portal may benefit less from portal updates. Next steps ---------- Complete design in October; pilot November 2026 to January 2027 if the Department Director approves; review results in February 2027. Exact pilot start date: requires confirmation.
Path C (Watch and verify): Check the trainer's slides against file 05A and post one added claim in the chat.
Debrief question: Which slide did Copilot add something extra to?