GPTPROMPTS.AI
HOW-TO GUIDE · 2026

How to Use Microsoft Copilot in PowerPoint: 2026 Guide

An 8-step workflow for building decks fast. Word-to-deck conversion, brand template integration, Designer redesign, speaker note generation, and the audit pass that turns a Copilot draft into a deck the partners will sign off on.

PowerPoint is where most knowledge work eventually lands. Strategy gets a deck. The board update is a deck. The sales pitch is a deck. The training is a deck. The all-hands is a deck. The post-mortem is a deck. Microsoft Copilot in PowerPoint is the most consequential AI productivity feature Microsoft 365 has shipped because it directly attacks the part of office work that is most time-expensive and most tedious: building slides. The 2026 version of Copilot in PowerPoint can build a 25-slide deck from a 15-page Word document in 60 to 90 seconds, redesign individual slides with PowerPoint Designer, generate 200-word speaker notes per slide, summarize a 50-slide deck someone sent you, and find the slide in a long deck that addresses a specific topic.

The 8-step workflow below is built for the way decks actually get built at work in 2026: a hybrid of Copilot generation and human editing, where Copilot does the structural and first-draft work and a human does the voice, fact-check, brand polish, and rehearsal. The first three steps are upstream investments (license setup, source document structure, Word-to-deck conversion) that compress what used to be 4 to 8 hours of slide work into 5 to 30 minutes. The middle steps are the slide-by-slide editing, speaker notes, and chart integration that turn a Copilot draft into a real deck. The final two steps are the structured review and final polish that produce a deck a senior reviewer signs off on. Every step is tuned to Copilot in PowerPoint's specific strengths (Designer integration, brand template inheritance, document grounding, in-app awareness) rather than fighting them.

Who this guide is for

  • • Managers and directors who build 5 to 15 decks per month for status updates, team reviews, and cross-functional briefings
  • • Consultants and strategy professionals at McKinsey, Bain, BCG, Big Four advisory, or boutique firms who live in PowerPoint as their primary deliverable
  • • Sales and BD teams building prospect-specific pitch decks at a cadence of 5 to 20 per week per rep
  • • Marketing and product marketing teams building enablement, campaign, and product launch decks
  • • Executives and chiefs of staff who own the board deck, all-hands deck, and key strategy presentations
  • • Training and L&D professionals building course decks, workshop materials, and onboarding presentations
  • • Investor relations and communications teams building quarterly earnings decks, investor updates, and conference presentations

Why Copilot in PowerPoint specifically (vs. ChatGPT, Claude, or Gemini)

For deck-building work, Copilot in PowerPoint has four specific advantages over alternatives. First, it builds the slide file directly. ChatGPT, Claude, and Gemini can outline a deck and write the slide content as text, but you then copy-paste into PowerPoint manually and lose 30 to 60 minutes of slide assembly time. Copilot in PowerPoint generates the .pptx file with layouts applied, brand template inherited, and Designer integration intact. Second, brand template inheritance. If your IT or design team has uploaded your organization's .potx to the tenant, Copilot uses it automatically; you do not spend 15 to 30 minutes per deck applying brand colors, logos, and fonts manually. Third, document grounding via SharePoint and OneDrive. Copilot reads the actual source documents in your cloud storage when generating slides, so the content is grounded in real material rather than inferred. Fourth, Designer integration for slide redesign. PowerPoint Designer's layout engine combined with Copilot's content awareness produces consistently better first-draft layouts than any human can produce manually under time pressure.

Where Copilot in PowerPoint loses: Claude wins on long-form structural reasoning if you are starting from scratch and need to think through what the deck should argue before any slides exist; outline first in Claude, then convert to a Word document, then run Word-to-deck. ChatGPT wins for speed of iteration on the verbal content of a single high-stakes slide (a vision statement, a market sizing claim) where the value is in the prose. Gemini wins if your organization runs on Google Workspace and the deliverable is a .gslides; the equivalent workflow inside Google Slides is materially better than fighting to produce a .pptx for a Google-native team. The deciding factor is your organization's productivity stack: Microsoft 365 organizations should use Copilot in PowerPoint as the primary deck-building tool; Google Workspace organizations should use Gemini in Slides.

The 8 steps below are tuned for Copilot in PowerPoint but the underlying deck-building logic translates across tools. The patterns that matter (structured source document, structural pass before slide pass, fact-check discipline, two-pass review) are tool-agnostic; the specific UX advantages (Word-to-deck, brand template inheritance, Designer integration, document grounding) are Copilot-specific. For paired workflows on other Office apps, see our Microsoft Copilot in Excel, Microsoft Copilot in Word, Microsoft Copilot in Outlook, and Microsoft Copilot in Teams.

The 8-Step Workflow

01

Confirm your Copilot license and tenant configuration before you start

The single most common reason people complain that Copilot in PowerPoint is disappointing is that they are using the wrong product. Confirm three things before any deck work. First, you have a Microsoft 365 Copilot license assigned to your account; you can verify in the PowerPoint title bar (the Copilot button should be present in the Home tab) or in admin portal under Licenses. Without the license, you only get the chat-only Copilot, which is materially less useful. Second, your IT or design team has uploaded your organization's brand template (.potx) to the tenant and ideally set it as default; this single change makes Copilot output 50 to 70% more usable on the first pass because brand colors, logos, and fonts apply automatically. Third, your source documents (Word, Excel, PDF) are stored in OneDrive or SharePoint in a known location, because Copilot's document grounding only works on cloud-synced files. The 30 to 60 minutes spent on this setup pays back inside the first week.

Example prompt
Quick verification checklist: (1) In PowerPoint, open the Home tab and confirm the Copilot button is visible; click it and verify the side pane opens. (2) In PowerPoint, click File then New, then look for 'Create a presentation from a file' option in the Copilot pane; if missing, your license is incomplete. (3) In PowerPoint, click Design tab then Browse for Themes; if your brand template appears, the tenant configuration is in place; if only stock themes appear, ask IT to upload your .potx to the tenant and set it as default. (4) In OneDrive or SharePoint, locate the source document you plan to convert; confirm it is in a synced cloud location with current sharing permissions for your account.
02

Structure the source Word document for clean Word-to-deck conversion

Word-to-deck conversion is the highest-leverage Copilot in PowerPoint workflow, but the output quality is determined by the source document structure. Five rules: use Heading 1 for major sections (slide-section breaks), Heading 2 for individual slide topics (slide titles), Heading 3 for sub-points (bullets). Keep Heading 2 sections roughly equal length (100 to 250 words each); short sections produce sparse slides, long sections produce overstuffed slides. Lead each Heading 2 section with the headline insight, not background; Copilot writes the slide title and headline bullet from the first paragraph. Embed any tables, charts, or images you want preserved directly in the Word document at the right point; Copilot carries them through. Write in a presentation register: short declarative sentences, key takeaways called out, jargon defined inline. A 15-page Word document drafted with this structure converts to a 20 to 30-slide deck that needs 30 minutes of cleanup; the same content drafted as flowing prose without heading hierarchy produces a deck that takes 2 to 3 hours to fix.

Example prompt
Pre-conversion checklist for the Word document: (1) Title at the top with a single Heading 1 covering it; (2) Major sections as Heading 1 (typically 3 to 6 of these per deck, 'Market context,' 'Strategic options,' 'Recommendation,' etc); (3) Each slide topic as Heading 2 (typically 4 to 8 per major section, 'Customer demand drivers,' 'Competitive response,' etc); (4) Sub-points and supporting detail as Heading 3 or as numbered/bulleted lists under the Heading 2; (5) First paragraph of each Heading 2 section is the headline insight written as a declarative sentence; (6) Any chart, table, or image embedded in place at the right point in the flow; (7) Total length 10 to 30 pages; longer than 30 pages should be split into multiple decks.
03

Run the Word-to-deck conversion and let Copilot do the structural draft

With the source Word document structured properly and saved to OneDrive or SharePoint, the conversion is fast. In PowerPoint, click File, New, then in the Copilot pane choose 'Create a presentation from a file' and select the Word document. If your tenant has a default brand template, Copilot applies it automatically; if not, specify the template explicitly in the prompt. Copilot reads the document, infers the slide structure from the heading hierarchy, picks Designer layouts for each slide, and generates the deck within 60 to 90 seconds for a 15-page Word document. The first pass output is rarely final, but it is typically 70 to 80% of the way to a usable deck: titles match the content, bullets capture the key points, layouts vary appropriately across slides, and the brand template is applied. Resist the temptation to fix individual slides during the first read-through; do a full pass through all slides first to assess structure and narrative flow, then go back and edit slide-by-slide.

Example prompt
In PowerPoint, click File, then New. In the Copilot pane that opens, click 'Create a presentation from a file.' Browse to the OneDrive or SharePoint location of your source Word document. If your tenant has a default brand template, leave the template selection on default; otherwise, use the prompt: 'create a presentation from this Word document using the [Brand Template Name] template.' Wait 60 to 90 seconds for the deck to generate. When the deck appears, do not edit individual slides yet. Instead, switch to Slide Sorter view (View tab, Slide Sorter), assess the overall narrative flow, and decide on any structural changes (slides to reorder, slides to merge, slides to delete, missing slides to add). Make those structural changes before the slide-by-slide edit pass.
04

Edit slide-by-slide for accuracy, voice, and brand fit

After the structural pass, work through each slide in order. For each slide: (1) verify the title accurately captures the slide content; (2) read the bullets and edit any that sound generic or AI-flavored; (3) verify any specific numbers, names, dates, or claims against the source document or replace with verified content; (4) check that the visual layout (Designer choice) fits the message; (5) confirm the slide adds something the deck cannot live without. For a 25-slide deck, this pass takes 60 to 120 minutes; the major time saver versus building the deck manually is that the structure, layout, and approximate content are already in place. For slides where you want to materially restructure the layout, ask Copilot 'redesign this slide with a more visual layout' or 'turn this bullet list into a comparison table' rather than reformatting manually; Copilot's redesign with Designer is faster than human formatting on most layouts. Track any open items where you need a number, a chart, or a quote you do not yet have.

Example prompt
Per-slide editing checklist (10 to 15 minutes per slide for the average slide): (1) Read the slide aloud; if the title does not capture the takeaway, rewrite it. (2) Cut any bullet that does not advance the argument. (3) For any specific number or named claim, find the source in the input document and verify; if no source, either replace or remove. (4) Apply your voice in the bullets: short, declarative, audience-aware. (5) If the layout fights the message, prompt Copilot: 'redesign this slide with a [specific layout type, comparison table / icon row / quote callout / two-column].' (6) Check that any embedded image is licensed for your use; replace stock imagery with brand imagery if the deck is going external.
05

Generate speaker notes for the deck

Once the deck is structurally and content-edited, ask Copilot to generate speaker notes for every slide. Speaker notes serve two purposes: they help the presenter prepare and they document the deck's intended message for handoff to anyone else who will deliver it. The default Copilot output is 50 to 200 words per slide, in a register suitable as prompt cards for a speaker who knows the material. For executive presentations or training decks where the speaker wants more detailed scripting, request longer notes with a specific tone. Always edit the speaker notes for: (1) accuracy on any specific numbers or names; (2) match to your speaking voice; (3) clear transitions between slides; (4) timing cues if the deck has a hard time limit. For a 25-slide deck, speaker note generation takes 30 to 60 seconds, edit pass takes 30 to 60 minutes. Total saved versus writing speaker notes from scratch: 1 to 2 hours.

Example prompt
In the Copilot pane with the deck open: 'Add speaker notes to every slide in this presentation. For each slide, write 100 to 200 words of speaker notes that expand on the bullet content without restating it verbatim. Tone: confident, conversational, audience-aware. At the end of each slide note, include a one-sentence transition phrase to the next slide. For slides containing specific numbers or named claims, do not invent additional supporting detail; reference only what is on the slide.' Then for executive or training decks where you need more: 'Now expand the speaker notes for slides [N] through [M] to 250 to 400 words each, with full talking points the presenter can deliver verbatim if needed.'
06

Add or refine charts and data visualizations using Excel + paste-link

Copilot in PowerPoint handles basic charts but underperforms on multi-series or annotated charts. The workflow that produces better results: build the chart in Excel using Excel Copilot for the analysis, finalize the formatting in Excel, then paste-link the chart into PowerPoint. Paste-link means the chart updates in the deck whenever the underlying Excel data updates, which matters for recurring decks (monthly board, quarterly business review, weekly metrics) where the chart structure stays the same but the numbers update. For one-off decks, paste-as-image is fine and prevents accidental data exposure. After the chart is in PowerPoint, ask Copilot to add the slide title that captures the headline takeaway, the bullet point that summarizes what the chart shows, and the speaker note that explains the analytical detail. This division of labor between Excel Copilot for the analysis and PowerPoint Copilot for the wrapping content produces consistently better data slides than asking PowerPoint Copilot to handle both.

Example prompt
Workflow for a chart-heavy slide: (1) In Excel, prepare the data with one chart per data set; use Excel Copilot if needed: 'analyze this data and produce a chart that shows the most important insight.' (2) In Excel, finalize the chart formatting: title, axis labels, data labels where useful, brand colors. (3) In PowerPoint, on the destination slide, click Insert, then Object, then Create from File, browse to the Excel file, check 'Link' if you want auto-update, click OK. (4) Resize and position the chart on the slide. (5) In PowerPoint Copilot pane: 'For this slide containing the chart, write a headline-takeaway slide title, one supporting bullet that summarizes the analytical insight, and a 100-word speaker note that explains the methodology and the implication.'
07

Run a structured review pass with Copilot before final polish

Before the deck ships, ask Copilot to review it for structural issues. The prompt: 'review this deck for issues; flag slides where the title does not match the content, slides with unsupported claims, slides where the layout fights the message, slides that are out of order in the narrative, slides with inconsistent specific numbers or names, slides with unclear takeaways, slides that are redundant with adjacent slides.' Copilot returns a structured review with slide numbers and specific recommendations. The review catches the issues that creep in during slide-by-slide editing (a number on slide 5 that does not match the same number on slide 18, a recommendation on slide 22 that contradicts the framing on slide 8). Address Copilot's flagged issues, then do a final manual pass for voice, brand fit, and the specifics Copilot cannot evaluate (does this match what we actually believe, does this match the audience). The two-pass review takes 30 to 60 minutes for a 25-slide deck and catches the issues that get decks sent back from senior reviewers.

Example prompt
In the Copilot pane with the deck open: 'Review this presentation for issues. Flag with slide numbers: (1) slides where the title does not match the slide content; (2) slides with claims I did not provide source documents for; (3) slides where the visual layout fights the message; (4) slides that look out of order in the narrative; (5) any specific numbers, names, dates, or claims that are inconsistent across slides; (6) slides where the takeaway is unclear; (7) slides that are redundant with adjacent slides; (8) slides that should be split because they cover too many ideas. For each issue, propose a specific fix.' After Copilot responds, work through the flagged slides and apply the fixes; ask Copilot to redo any that need redesign.
08

Final polish, fact-check, and rehearsal pass

The final pass is human work that Copilot cannot do for you. Three phases. First, fact-check every specific number, customer name, product name, date, and quote in the deck against your source documents; Copilot will sometimes invent details when filling content gaps and these need to be either verified or removed. Second, polish for voice and brand fit: read each slide aloud and edit anything that does not sound like your voice or your firm's voice. Third, rehearse the deck once with the speaker notes to surface awkward transitions, weak slides that should be cut, missing context that should be added. For an internal deck (executive update, team meeting), the final pass takes 30 to 60 minutes and is sufficient. For an external deck (board, investor, customer pitch, sales bake-off), the final pass takes 1 to 3 hours and ideally includes a review by the eventual presenter and at least one peer. The pattern that fails: shipping a Copilot-generated deck without the human pass; the pattern that works: treating Copilot output as a 75% starting draft and budgeting the final 25% to human polish.

Example prompt
Final-pass checklist: (1) Open the deck in Reading View; read every slide aloud; edit anything that sounds AI-generic or off-voice. (2) Open a side document of source materials; for every specific number, name, date, and claim in the deck, find and verify the source; replace anything unverified. (3) Run Spell Check (Review tab) and Accessibility Checker (Review tab); fix anything flagged. (4) Run the Designer pane on each slide one more time; sometimes a better layout option appears once the content is finalized. (5) Print or export to PDF and read on a different device; issues that hide in the editing view often surface in print or mobile view. (6) Rehearse with the speaker notes once, ideally to a peer; surface transitions that are awkward or slides that need to be cut. (7) For external decks, hand to the eventual presenter for final sign-off before sending.

Common Mistakes That Break Copilot Deck Output

1. Confusing the chat-only Copilot with Copilot inside PowerPoint

The chat-only Copilot at copilot.microsoft.com cannot build .pptx files, apply brand templates, or use Designer. The in-app Copilot inside PowerPoint requires a Microsoft 365 Copilot license; without that license, you only get the chat version. Confirm the license before complaining the feature is missing.

2. Running Word-to-deck conversion on an unstructured Word document

Without proper Heading 1, Heading 2, Heading 3 hierarchy, Copilot guesses at slide breaks and produces uneven decks. The 30 minutes spent restructuring the Word document with proper headings saves 2 to 3 hours of post-conversion cleanup.

3. Skipping the brand template upload and fixing branding manually per deck

Get IT to upload your organization's .potx to the tenant and set it as default. This single change makes Copilot output 50 to 70% more usable on the first pass and saves 15 to 30 minutes of branding cleanup per deck.

4. Editing slides individually before the structural pass

After Copilot generates the deck, do a full Slide Sorter view pass to assess narrative flow before editing any individual slide. Editing slides before deciding which slides to delete, merge, or reorder wastes time on slides that will not survive.

5. Trusting the deck because it looks professional

Copilot output looks polished, which masks the specific factual errors it sometimes introduces. Always fact-check every specific number, name, date, and claim before the deck ships. The pattern that fails is shipping a Copilot deck without verification; the pattern that works is treating Copilot as a junior analyst whose work gets reviewed.

6. Asking PowerPoint Copilot to handle complex chart construction

For multi-series charts, dual-axis, custom annotations, or specific formatting, build the chart in Excel using Excel Copilot and paste-link or paste-as-image into PowerPoint. PowerPoint Copilot underperforms on chart complexity beyond basic bar, column, line, pie.

7. Letting Copilot fill content gaps with placeholder text

When you ask Copilot to fill a slide where you do not have specific content, it sometimes invents customer names, ROI percentages, or quotes that look plausible. Either provide the specific content or remove the slide; do not ship invented placeholder content.

8. Skipping the rehearsal pass before high-stakes presentations

Decks that look good in editing view often have awkward transitions, weak slides, or missing context that surface only when rehearsed. Always rehearse with the speaker notes once before any external or executive-audience presentation; ideally rehearse with a peer.

Pro Tips (What Most Deck-Builders Miss)

Maintain a master deck library in SharePoint with reusable slide categories. Strategy slides, market sizing slides, customer logo slides, ROI calculation slides. When building a new deck, ask Copilot to pull specific slide types from the library: 'add a customer logo slide using the logos from the master library deck in our SharePoint Marketing folder.' This compounds across decks faster than building from scratch.

For sales pitch decks, build a master template with placeholder slides for prospect customization. Then for each prospect ask: 'customize this pitch deck for [Prospect Company] using their public information and our case study from [their Industry].' The customization compresses from 1 to 2 hours to 15 to 30 minutes per prospect deck.

Use Excel Copilot first, then PowerPoint Copilot, on data-heavy decks. Build the analysis and finalize the chart in Excel using Excel Copilot, then paste-link the chart into PowerPoint and let PowerPoint Copilot wrap the title, headline takeaway, and speaker notes around it. This division produces materially better data slides than asking PowerPoint Copilot to handle the analysis.

Ask Copilot to write speaker notes in the eventual presenter's voice. If the CEO is going to deliver the deck, prompt: 'add speaker notes written in [Name]'s voice based on [link to a recent talk transcript].' If the speaker has a public archive of talks, Copilot picks up the cadence and vocabulary; the resulting speaker notes feel authentic rather than generic.

Build a personalized deck-review prompt and reuse it. Save your own structured review prompt that flags the issues you specifically care about (board-deck conventions, your firm's style, accessibility requirements, length budgets). Reuse the prompt at the end of every deck build; consistency catches the issues a one-off review prompt misses.

For recurring decks (monthly board, quarterly QBR, weekly metrics), template once and update. Build the master deck once with all slides, brand template, and chart placeholders. For each recurring instance, ask Copilot: 'update this deck for [Period] using the latest data in [SharePoint location]. Preserve the slide structure; refresh only the numbers, charts, and commentary.' The recurring update takes 15 to 30 minutes versus 2 to 4 hours.

Use Find a Slide on long board decks before meetings. When a 60-slide deck arrives 30 minutes before a board call, ask Copilot: 'find the slide that addresses [specific topic]' and 'summarize the financial section in 5 bullets.' You arrive briefed without reading the whole deck.

Train your team on the difference between Word-to-deck and prompt-only deck generation. Word-to-deck (with a structured source) produces 70 to 80% usable output. Prompt-only ('create a deck about [topic]') produces 30 to 50% usable output because Copilot has no source document to ground on. The team should default to Word-to-deck for any deck longer than 5 slides.

Microsoft Copilot in PowerPoint Prompt Library (Copy-Paste)

Production-tested prompts for the Copilot pane inside PowerPoint. Replace bracketed variables with your specifics. Run inside PowerPoint with a Microsoft 365 Copilot license active.

Word-to-deck conversion

'Create a presentation from this Word document using the [Brand Template Name] template. Use the heading hierarchy in the document to drive slide breaks. For each major section, generate a section divider slide. For each Heading 2, generate one slide with the heading insight as the title and the supporting points as bullets. Apply Designer to vary the layouts across slides.'
'Create a presentation from this Word document. Target length: 20 to 25 slides. If the document supports more, prioritize the executive summary, recommendation, and supporting evidence sections. Skip detailed appendix material unless I prompt for it.'

Slide redesign with Designer

'Redesign this slide with a more visual layout. Current bullets are: [list]. Goal: a single-image-driven slide that conveys the headline takeaway. Apply Designer.'
'Turn this bullet list into a comparison table with columns for [Option A] and [Option B] across the dimensions [list dimensions]. Apply our brand colors.'
'Rebuild this slide as an icon-led summary with 4 quadrants. Each quadrant should capture one of the key points from the current bullets, with a representative icon and a short caption.'
'Add a visual to this text-heavy slide that supports the takeaway. The takeaway is: [statement]. Pull from Designer's stock visuals or our SharePoint image library if configured.'

Speaker notes generation

'Add speaker notes to every slide in this presentation. For each slide, write 100 to 200 words of speaker notes that expand on the bullet content without restating it verbatim. Tone: confident, conversational, audience-aware. End each note with a one-sentence transition phrase to the next slide. For slides with specific numbers or named claims, do not invent additional supporting detail.'
'Expand the speaker notes for slides [N] through [M] to 250 to 400 words each. Add full talking points the presenter can deliver verbatim if needed. Include timing cues if a slide should take more than 90 seconds to deliver.'
'Rewrite the speaker notes for the entire deck in [Executive Name]'s voice based on their recent earnings call transcript [SharePoint link or paste]. Match cadence, vocabulary, and recurring phrases.'

Deck summarization and navigation

'Summarize this presentation in 5 bullet points covering the main argument, the most important supporting evidence, the recommendation, and the open questions.'
'Find the slide that addresses [specific topic] and summarize what it says.'
'What are the top 3 risks or concerns flagged in this deck? Cite the slide numbers where each is discussed.'
'List every specific financial number cited in this deck, with the slide number where it appears. Flag any numbers that are inconsistent across slides.'

Sales and prospect customization

'Customize this pitch deck for [Prospect Company] using their public information. Update: (1) the cover slide with their company name and our deal-context tag; (2) the why-now slide with a reference to a recent public news item about them; (3) the case study slide with our [Industry] case study; (4) the ROI slide with their industry benchmark numbers; (5) the next-steps slide with a personalized close. Preserve all other slides.'
'Build a 1-slide leave-behind summary from this 20-slide pitch deck. Include: target value proposition, top 3 differentiators, ROI summary, key contact, next step. Format as a single-page printable.'

Charts and data integration

'Add a bar chart to this slide showing [data set]. Apply our brand colors. Title: [chart title]. Y-axis label: [label]. Data labels visible. Source citation in small text below the chart.'
'For this slide containing the chart, write a headline-takeaway slide title, one supporting bullet that summarizes the analytical insight, and a 100-word speaker note that explains the methodology and the implication.'

Structured review

'Review this presentation for issues. Flag with slide numbers: (1) slides where the title does not match the slide content; (2) slides with claims I did not provide source documents for; (3) slides where the visual layout fights the message; (4) slides that look out of order in the narrative; (5) any specific numbers, names, dates, or claims that are inconsistent across slides; (6) slides where the takeaway is unclear; (7) slides that are redundant with adjacent slides; (8) slides that should be split because they cover too many ideas. For each issue, propose a specific fix.'
'Run an accessibility audit on this deck. Flag: (1) slides with insufficient color contrast for the brand template; (2) images without alt text; (3) tables without column headers; (4) slides where the reading order does not match the visual order; (5) any text below 18pt that should be larger. For each, propose a fix.'

Recurring deck updates

'Update this deck for [Reporting Period] using the latest data in [SharePoint location]. Preserve the slide structure and any commentary I have already written. Refresh: (1) cover slide period; (2) all charts pulling from the source data; (3) headline metrics on the executive summary slide; (4) any text references to specific time periods. Flag any slide where the data update changes the takeaway substantively.'

Want more Copilot prompts for the Microsoft 365 suite? See our Microsoft Copilot in Excel, Microsoft Copilot in Word, Microsoft Copilot in Outlook, and Microsoft Copilot in Teams. For paired pitch deck workflows on other tools, see ChatGPT for pitch deck and Claude for writing.

Frequently Asked Questions

Related Guides

Don't stop here

What to read next

Hand-picked guides our readers explore right after this one.