An 80%-finished deck is easy to trust too soon. The structure is in place, the slides look complete, and you're tired. That's when a shortening pass can change "$1.2 million approved" to "$1.2 million spent," or a summary can turn a pending decision into an approved one. Copilot can help with the final 20%, but you still need to control the scope and check every change.
Refine without breaking: bounded edits on specific slides
The Plan → Execute → Review sequence from the Word editing lesson also works for slides. Start with a one-line baseline covering the audience, requested decision, protected facts, and slides you intend to change. Then ask only for a plan.
Put a limit such as "slides 2, 4, and 6 only," in the request. It keeps a small revision from spreading. If another slide changes, recover it from the untouched original or start with a fresh working copy and a narrower request. Keep the original beside the revision so every edited number, date, and owner can be compared. Being able to undo the work helps you recover. Faithfulness still has to be checked against the original.
Summarize your deck, then audit it line by line
Copilot can summarize a presentation for a particular audience. An executive brief emphasizes decisions and risks, while a technical one emphasizes dependencies. Specify the audience, structure, length, and "use only the deck." Then audit the summary one statement at a time.
Use a simple table with the statement, supporting slide, and status: supported, unsupported, or needs qualification. Read the slide yourself. Copilot's reference helps you navigate, but the slide is the evidence. Watch for a dropped qualifier, such as "scheduled to begin October 7" becoming "begins October 7", and for conclusions the deck never reaches, such as "approval pending" becoming "approved". Correct or remove anything you can't trace before sharing.
Explain: a comprehension test for your diagrams
Select a diagram shape, right-click, and choose Explain. Copilot describes how it reads the object, which gives you a useful comprehension check. It doesn't establish whether the diagram is correct. If a decision diamond labeled "Security approval" is described without the decision or both branches, the visual may be unclear.
Re-running Explain until it agrees won't repair that ambiguity. Confirm the selected shape, then clarify the label, connectors, branch labels, and legend. "Security approval recorded?" may be clearer than the original label. After changing the diagram, run Explain once more to see whether it now reads as intended.
Rehearse with a question-evidence sheet
Before the meeting, identify the questions the deck doesn't answer. Create a question-evidence sheet with the likely question, the deck-supported answer, and its slide. Where information is missing, add the note "Not answered by this deck."
Work through budget, timing, ownership, risks, and dependencies. Use only what appears in the deck and record the supporting slide so you can find it during the discussion. If the answer isn't there, make it a follow-up for the sponsor. Don't fill the gap under pressure.
Your version of PowerPoint may include a helper for anticipating questions. If it does, review its output just as you would a summary and keep only statements you can support with a slide. Naming a gap makes you prepared. An answer without a source is much harder to defend.
Create on mobile, honestly
You may want to draft or tidy a slide from your phone between meetings. Word and PowerPoint Copilot workflows are documented for mobile, but a feature on your laptop may not appear with the same control, label, or behavior on a smaller screen.
Make the source explicit. Paste the relevant text into the prompt and tell Copilot to use only that text, since you can't assume the interaction uses the selection, current slide, or whole file. If the task isn't clearly available or its scope is unclear, complete it manually and record it as an offline task. Report only the Copilot actions you actually performed.
Practice like it's real: two role-based drills
A feature demo asks, "Can Copilot rewrite this paragraph?" A drill asks, "Can I produce a real artifact, for a specific audience, from controlled facts, and verify it?" The next two exercises cover that full job.
The cover letter. Give Copilot a candidate's actual achievements and the role's requirements, and ask it to connect them. The trap is motivation: if the source never says why the applicant wants the job, a line like "I'm excited to join your innovative company" invents both a feeling and knowledge of the company. Cut it, and replace it with a factual link between the person's experience and the stated responsibilities.
The executive update deck. Organize it around status, progress, risk, mitigation, and a clear action with an owner and deadline. The trap here is significance: if the source doesn't state a business impact, don't ask Copilot to predict one. "This launch will increase revenue" is invented unless a number in your packet says so. Copy only the relevant section of your source into each artifact, and treat every generated line as a draft to trace.
