PlaysbyMoat8
Back to the library
The workflow guideMarketing

Draft presentations from a shared brand system

Apply a reusable corporate design and content instruction set to make a presentation that colleagues can review and edit.

6 implementation stepsSimple

How this works

Apply a reusable corporate design and content instruction set to make a presentation that colleagues can review and edit. A reusable presentation system should preserve the logic of the argument as well as fonts and colors. A polished deck that misstates evidence, hides assumptions, or cannot be edited is not a useful handoff for colleagues.

Build a slide outline from the audience decision and approved content, then apply the shared brand system. Use available presentation tools to create editable slides where possible. Verify rendered slides and numerical claims separately from successful file generation.

Before you start

Audience decision

Define what the presentation should explain or ask the audience to approve.

Brand system

Collect approved fonts, colors, layouts, and examples.

Evidence packet

Provide the facts, charts, and assumptions behind the narrative.

Prepare the inputs

content_brief
Required

Purpose and key points

Separate essential information from optional detail.

brand_assets
Required

Approved template and files

Use actual available fonts and marks.

evidence
Required

Data and references

Retain dates and units.

slide_constraints
Required

Length and format

Specify aspect ratio and editability needs.

audience_context
Required

Knowledge and concerns

Shape explanation without inventing stakeholder views.

Implementation, step by step

  1. Structure the argument

    • Write the audience question and one main message per slide.
    • Order the narrative so evidence supports the requested decision.

    Checkpoint: A slide-by-slide outline.

  2. Map content to layouts

    • Choose appropriate text, chart, diagram, or example formats.
    • Avoid forcing every idea into the same layout or shrinking text to fit.

    Checkpoint: A layout plan.

  3. Prepare facts and visuals

    • Recalculate charts from supplied data and label assumptions clearly.
    • Use approved images or original visuals and preserve the factual meaning.

    Checkpoint: A verified content set.

  4. Build editable slides

    • Apply the available brand template and reusable components.
    • If the tool cannot create editable elements, state the limitation and supply source data separately.

    Checkpoint: A presentation draft.

  5. Review rendered output

    • Inspect every slide for clipping, contrast, hierarchy, and readable labels.
    • Check that charts, captions, and conclusions agree with the evidence.

    Checkpoint: A corrected rendered deck.

  6. Prepare the handoff

    • Deliver the editable file, any supporting data, and unresolved questions.
    • Record the version reviewed and distinguish draft status from approval.

    Checkpoint: A usable presentation package.

Decisions along the way

Required font is unavailable

Use an approved substitute or document the substitution.

A slide contains too many ideas

Split or prioritize content rather than reduce legibility.

Evidence is missing for a claim

Use a labeled assumption or leave a decision question.

What you will produce

presentation-draft

Editable deck

Enables colleagues to revise the argument and design.

Include: slide_id · message · evidence · visual · review_status

presentation-review.md

Markdown

Tracks factual and visual checks.

Include: slide_id · issue · correction · open_question

Check the result

  • Inspect every rendered slide at presentation size.
  • Recalculate chart totals and verify units.
  • Compare logo and typography use with the approved system.
  • Confirm the final file opens and required elements remain editable.

When something goes wrong

Generated slides overflow

Adjust layout and re-render the affected slides.

Charts distort the supplied data

Rebuild them from the source table.

Export loses fonts or images

Open the actual export and repair missing resources before delivery.

A worked example

SYNTHETIC EXAMPLE · NOT A REPORTED BUSINESS RESULT

Request

Draft a quarterly operations deck.

Inputs

Synthetic example. Synthetic data shows 80 completed requests and 20 pending; the brief asks for a decision on backlog review.

Expected result

Synthetic expected result. A chart represents 80/20 accurately and the decision slide asks how to address pending work. It does not label all 100 requests completed.

Run a small pilot

Start small

One short deck using several common layouts.

Record the baseline

Record creation time and reviewer corrections.

Agree success criteria

Agree factual fidelity, readability, and editability criteria.

Stop or revise

Stop delivery when the file cannot be opened or central evidence is incorrect.

Keep the scope clear

  • Brand guidance does not authorize changing company claims or strategy.
  • Creating a deck does not authorize sending it to external recipients.

Check before using

Check every claim and chart. A consistent design does not validate the underlying content.

Business activities

  • Create and publish content

Editorially adapted workflow; not independently tested.

FROM A RECIPE TO YOUR WORKFLOW

Bring the company context together.

This workflow needs reliable inputs before it needs a better prompt. Moat8 Vault brings working information into a readable archive for the AI tools you use.

For this recipe: Approved message and evidence · Brand design system · Presentation format

Start with one recurring task, agree which sources to use, and review the first result with your team.

Discuss this workflow

What does your team do?

Choose the recurring work you would like to improve.

A field guide, made for work.

Plays is a curated library of anonymized business workflows. Each recipe explains the inputs, steps, tools, and checks you can adapt to your team. These are editorial guides, not independently tested implementations.

When you share a company website, the guide may read a limited number of public pages on that website. Messages and retrieved page text are sent to our AI provider, NVIDIA, to recommend relevant workflows. Share a general description rather than confidential information.

Saved workflows and selected activities stay in this browser. Your chat history and selected company website are kept in this tab and cleared when you reload or start a new chat. The server does not store conversations. Live source monitoring is not enabled.

If you allow analytics, PostHog receives page views and actions such as workflow saves, skill downloads and link clicks. Random browser and session identifiers connect these actions without identifying you by name. Your choice and browser identifier expire after 90 days; sessions restart after 30 minutes of inactivity or 24 hours. We use local storage, not analytics cookies. Messages, company URLs, search text, full referrers and IP addresses are not sent. There are no person profiles or session recordings. You can decline or withdraw in Analytics settings; Do Not Track and Global Privacy Control keep analytics off.

Read the Plays Privacy Notice ↗