Word and PowerPoint with CopilotIntermediate14 min

Build Presentations from a Prompt

Turn a one-paragraph brief into a decision-driven deck: one job per slide, every claim traced to your source, on your organization's template, with approved and generated images kept in their lanes.

What you'll learn

  • Write a presentation brief that fixes the audience, decision, and ending
  • Prompt Copilot for a deck with one distinct job per slide
  • Separate evidence, interpretation, and unsupported claims on a slide
  • Start from an approved template and verify the result against it
  • Choose between approved SharePoint images and generated images

Before you start

On this page

Ask Copilot to "make a presentation about the Q3 numbers" and you may get fifteen polished slides with no clear decision. A useful deck takes its audience from a question to a conclusion. Once the brief names the decision and the evidence, Copilot can draft the structure and wording while you work on the argument.

You'll build that argument first, then fit it to your organization's template and choose visuals that suit the job. The same source discipline from the Word lessons applies here. Trace every important claim before presenting it.

A presentation builds an argument

Before you prompt anything, write a one-line-per-item presentation brief. It's the acceptance standard for whatever Copilot returns:

  • Audience: who's in the room?
  • Purpose: what should they understand, approve, or do?
  • Source boundary: what facts are allowed? (a prompt's facts, or one selected source)
  • Length: roughly how many slides?
  • Ending: what decision or action must the last slide reach?
  • Tone: concise and neutral, or warm and persuasive?

A decision deck often moves through the requested decision, current situation, evidence, interpretation, options, recommendation, constraints, and next action. Use that as a planning model, not a mandatory template. If the brief asks for approval but the draft ends with a generic summary, the narrative hasn't reached its destination.

Brief-to-deck, one job per slide· powerpoint
Bad example

Make a presentation about the reporting pilot.

Good example

Create a seven-slide decision presentation for regional operations directors. The decision: whether to approve a six-week reporting pilot. Use only the facts in this prompt (or the selected source). Sequence the slides as decision requested, current process, observed problems, trial evidence, options and proposed workflow, constraints and unresolved questions, and leadership actions. Give each slide one distinct job. Preserve every number and qualifier. Label any recommendation as presenter analysis. Don't invent a start date, owner, savings, or expected result. Flag anything unsupported as unverified.

Why this works: A seven-slide draft that progresses toward a decision, with each slide doing one job and every unsupported detail clearly flagged.

Two ways to start: from a prompt, or from a source

You can supply the facts inside the prompt or point Copilot to one selected source. Prompt-based facts work when the evidence is short and you want close control. A source file is easier when pasting the material would make the request unwieldy.

Confirm the boundary before generating. For a source-based request, check that the intended file is attached. Typing its name in the prompt doesn't attach it. For prompt-based facts, make sure nothing needed is missing. Work with one source at a time because combining several isn't something you can assume will work. In either case, treat the returned deck as a draft that still needs tracing.

One job per slide, and the claim that isn't in your source

A presentable deck needs clear slide roles and disciplined claims. If slides 3 and 4 both say "response times are bad," they repeat the same job. Combine them or give one a different purpose. Then classify each important statement:

  • Evidence: directly supported by a named source passage.
  • Interpretation: your reasoning from that evidence, and labeled as yours.
  • Recommendation: a proposed action, marked as analysis.
  • Unsupported: neither stated nor defensibly derived. This is the one to catch.

Unsupported details often sound reasonable: a start date, an owner, or a promise that "this will save two hours per person." They complete the slide visually, so they're easy to overlook. Qualifiers need the same attention. "38% of reviewed cases" covers a narrower group than "38% of cases," and "the pilot can use two agents" doesn't mean "two agents are available." If you find an unsupported detail, flag or remove that statement while keeping the source-backed request.

A plausible date or owner is still an invented fact

If your source says the owner and start date haven't been assigned, a slide that reads "Begins August 3 under the service director" is fabricating both. Remove them or mark them as unverified, and keep the supported action, like "Approve the pilot," on the slide.

Keep it on-brand: start from the approved template

An approved template defines more than the title slide. Its layouts, colors, fonts, logo position, and footers work together as a visual system. Start there so Copilot has an existing structure for the parts that vary, including titles, body copy, and visual placement.

Verify the result yourself. Compare a title slide, a content slide, and an image slide with the original template. Check the fonts, colors, layouts, and logo position. If a slide has drifted, ask Copilot to apply an existing layout from the current template while preserving the content and editable text.

Approved images or generated images?

Copilot can pull approved images from your organization's SharePoint brand libraries, and it can generate new ones from a description. They serve different jobs, and mixing them up is where decks get you in trouble:

The visual need Use Why
Official logo or identity treatment Approved SharePoint asset Identity must come from an approved, verifiable source
Exact product or campaign image Approved SharePoint asset Accuracy and approval matter
A conceptual or decorative illustration Generated image A new visual concept, no identity at stake
Exact names, numbers, dates, legal wording Editable PowerPoint text It must stay accurate and editable

In PowerPoint for the web, the Image model switcher includes FLUX.2 Flex for conceptual images. Use generation for an illustration or abstract background. Keep logos, exact products, and wording that must be correct in approved assets or editable text. A prompt that names your brand library doesn't prove an image came from it. Confirm the source before using any approved asset.

Generate a conceptual image with FLUX.2 Flex· powerpoint
Bad example

Create an image for this presentation.

Good example

Create a wide, presentation-ready illustration of a team consolidating several status reports into one clear leadership view. Use a restrained blue and teal palette that complements the current template, and keep the right third visually quiet so slide text can sit there. Do not include logos, readable words, numbers, or watermarks.

Why this works: A clean conceptual image with space reserved for your text and no baked-in words or logo-like marks. Label it "generated," and add any exact wording as separate editable text.

Keep exact wording out of the pixels

Logos, names, numbers, dates, and legal wording belong in editable PowerPoint text objects, never inside a generated image. If a generated picture comes back with garbled text or a logo-ish shape, regenerate without it and add the real wording as text you can select and correct.

Build on the approved template· powerpoint
Bad example

Make a customer update deck that looks on-brand.

Good example

Create a six-slide customer update in the current organization-approved template. Audience: regional sales leaders. Include an executive summary, three customer trends, recommended actions, and a closing slide. Preserve the current theme, layouts, fonts, colors, and editable text placeholders. Do not introduce a new visual style.

Why this works: A six-slide draft that visibly matches your template's fonts, colors, and layouts. Verify a few slides against the original before you trust it.

Verify before you present

Slides look authoritative, which makes unsupported wording especially easy to carry into a meeting. Before presenting, compare every number and qualifier with the source, label recommendations as analysis, and remove invented owners or dates. Check that the template still matches the approved original and that each image is either an approved asset or a clearly generated concept. Five minutes here prepares you to answer the question that matters in the room: "where did that number come from?"

Try it yourself

Draft a decision deck and hunt the unsupported claims

Use these four passages about a support pilot. A, current performance: median first-response time rose from 7 hours in Q1 to 11 in Q2, and 38% of reviewed cases missed the 12-hour target. B, trial: a two-week triage trial of 120 cases routed 74% without reassignment, versus a 51% baseline. C, constraints: a longer pilot can use two agents half-time. No extra budget is approved. No owner or start date is assigned. D, decision: leadership is asked to approve a six-week pilot and appoint an owner.

  1. 01

    Write a prompt for an eight-slide decision deck from these passages, one job per slide, ending on the approval request and open owner question.

  2. 02

    For a draft final slide that reads "Begin the pilot on August 3 under the service director," write the correction: what to remove and what supported action to keep.

    Hint: Passage C says no owner or start date is assigned, so both details in that slide are unsupported.

  3. 03

    Check three slides for dropped qualifiers: did "reviewed cases" become "cases," or "can use two agents" become "two agents available"?

An eight-slide outline that reaches a decision, plus a short list of the unsupported claims and dropped qualifiers you caught before they reached the room.

Key takeaways

  • A deck is an argument. Write a presentation brief before you prompt anything.
  • Give every slide one distinct job, and combine slides that repeat a job.
  • Sort claims into evidence, interpretation, recommendation, and unsupported, and catch the unsupported.
  • Preserve qualifiers: "reviewed cases" and "can use" carry meaning you can't drop.
  • Approved images come from your brand library. Generated images are for concepts, never identity or exact text.

Check your understanding

  1. 1. Your source says the pilot owner and start date haven't been assigned, but Copilot's final slide reads "Begin August 3 under the service director." What should you do?

  2. 2. A slide needs an official company logo, an exact product photo, a conceptual cloud illustration, and the text "Pilot begins 3 September." Which comes from where?

  3. 3. Slides 3 and 4 both present "response times are getting worse" with different charts. What's the problem?

  4. 4. Copilot changes your source's "38% of reviewed cases" to "38% of cases" on a slide. Why does that matter?

Frequently asked questions

Terms used in this lesson

presentation brief
A short specification (audience, purpose, source boundary, length, ending, tone) written before slide creation and used as the acceptance standard.
slide job
The single contribution a slide makes to the narrative, such as requesting a decision, presenting evidence, or recording constraints.
brand image
An organization-approved asset supplied from a SharePoint brand library, used where identity or exact accuracy matters.
FLUX.2 Flex
An image-generation model selectable via the Image model switcher in PowerPoint for the web, used for conceptual and decorative visuals.

Further reading