[COMPANY LOGO]

Presentation Standards

The basics of building clear, consistent, professional presentations — every deck, every audience, every time.

Version [1.0]  ·  [Month Year]  ·  Owner: [Team / Department]

[Company Name]Presentation Standards
Why it matters

Consistent presentations build trust — and save everyone time

Trust

A consistent look signals professionalism and attention to detail — to clients, partners, and leadership.

Speed

Standards remove guesswork. Start from the template and proven patterns, not from a blank slide.

Clarity

When design follows shared rules, the audience focuses on the message — not on decoding the slides.

These standards apply to every deck: internal updates, client pitches, board materials, and conference talks.

[Company Name]Presentation Standards
First principles

A slide is not a document — it has one job: make one idea land

Slides support the speaker. If the audience has to read the screen to follow along, the slide has failed — send a document instead.

Focus attention

One idea on screen means one idea in everyone's head. The slide aims the room.

Present evidence

One clear chart or number proves a point faster than a paragraph ever will.

Aid memory

People forget sentences. They remember one strong image, number, or phrase.

Everything in this deck follows from this principle: one idea per slide, the headline carries the message, and detail lives in the talk track or the appendix.

[Company Name]Presentation Standards
First principles

Bad slides bury the point, good slides state it, great slides make it stick

BAD
The audience works

Topic titles, walls of text, unreadable charts. The message is in there somewhere — finding it is left as an exercise for the room.

Fails the 3-second test
GOOD
The point is clear

Follows every rule in these standards: message headlines, one idea per slide, labeled charts, a clean grid. Clear, correct, professional.

Passes the 3-second test
GREAT
The point is felt

The same rules, then distillation: fewer elements, a bigger takeaway, whitespace that aims the eye. The room remembers it tomorrow.

Passes the tomorrow test

The rules in this deck get every slide to good. Distillation — the courage to remove — is what gets to great.

[Company Name]Presentation Standards
First principles

Three tests tell you in seconds whether a slide works

The 3-second test

Show the slide to someone for three seconds. Can they tell you the point? If not, too many elements are competing.

The headline test

Read only the headlines, in order. If the story doesn't flow, your headlines are topics, not messages.

The back-row test

Stand two meters from your screen. Anything unreadable gets cut, enlarged, or moved to the appendix.

Run these per slide while building — they catch 90% of problems before review does.

[Company Name]Presentation Standards
First principles

Anatomy of a bad slide: six sins on one screen

Subscription revenue update
In Q1 subscriptions represented 41% of new revenue, rising to 55% in Q2 and reaching 62% in Q3, a trend we have been tracking over the past three quarters and expect to continue into Q4 and beyond as we expand the offering into adjacent segments and geographies, subject to the usual caveats about pipeline conversion, seasonality, and the evolving competitive landscape that we discussed at the last review.
Q1 Q2 Q3
note: figures approximate, subject to revision — see backup for details
1 2 3 4 5 6
  1. 1Topic title — "update" says nothing; no message
  2. 2Wall of text — a paragraph at 8 pt; the room reads, stops listening
  3. 3Rainbow chart + legend — no values, no units; decode it yourself
  4. 4Unaligned boxes — overlapping, rotated, off the grid
  5. 5Low-contrast fine print — 2.1:1; unreadable on a projector
  6. 6No source, no footer — nothing to trust, nothing to cite
[Company Name]Presentation Standards
First principles

Anatomy of a great slide: the same content, rebuilt

Subscriptions now drive 62% of new revenue
41%
55%
62%
Q1 Q2 Q3
Source: [Finance BI system], [Q3 2026] · % of new revenue
[Company Name][Deck name][Page]
1 2 3 4 5 6
  1. 1Headline states the message — the "so what", one line
  2. 2One chart, one point — nothing else competes
  3. 3Direct labels with units — no legend, no guessing
  4. 4One highlight — color points at the takeaway
  5. 5Source cited, footer present — numbers you can trust
  6. 6Whitespace aims the eye — empty space is doing work
[Company Name]Presentation Standards
First principles

Every good deck passes through five stages — skip one, and it shows

1
Purpose

One decision you want, written in one sentence — before the template opens.

2
Story

SCQA ordering; every slide earns its place or is cut.

3
Slides

The template plus these standards make this the fast stage.

4
Rehearsal

Out loud, once, timed — the words always change the slides.

5
Delivery

The deck supports you; you never read the deck.

Most slide problems trace back to a skipped stage — usually the Purpose sentence.

[Company Name]Presentation Standards
The golden rule

One company, one voice — always start from the official template

Never start from a blank deck or recycle an old presentation. The official template already has the right colors, fonts, logo placement, and layouts built in. [Template location / intranet link]
Do — green cards show the standard, with a good example rendered as it should look.
Don't — red cards show real mistakes, rendered deliberately badly so you can recognize them.

Everything in this deck follows its own rules — watch the headlines, footers, colors, and layout as you read.

[Company Name]Presentation Standards
What's inside

The path: first principles, five parts, and a checklist

0First principlesWhat makes a slide bad, good, or great — and three tests to tell
1The slide frameworkThe three zones, boxes, labelling, and the approved layouts
2Messaging & storyAction titles, one message per slide, the SCQA story, the appendix
3Visual standardsColor, contrast, typography, logo, and imagery
4Data & writingCharts, tables, and a consistent writing style
5Process & governanceFile naming, review and approval, the 60-second checklist

About [15] minutes end to end — or jump straight to the checklist at the back.

[Company Name]Presentation Standards

Part 1 of 5

The slide framework

  • The three zones of every slide
  • Boxes, alignment, and whitespace
  • Labelling, so nothing needs decoding
  • The approved slide layouts
[Company Name]Presentation Standards
Part 1 — The slide framework

Every slide is built on the same framework: headline, body, footer

Do
1 · Headline — the message
2 · Body — evidence in boxes 
3 · Footer — company · deck · page

Same zones, same positions, on every slide. Content stays inside the margins [1.5 cm] — nothing touches the slide edge.

Don't
Chart
random text floating near the edge…

A topic label instead of a headline, boxes overlapping zones, elements hanging off the edge, no footer.

Headline zone — one action title, max two lines Body zone — content lives in aligned boxes Footer zone — company · deck name · page number
[Company Name]Presentation Standards
Part 1 — The slide framework

Arrange all content in boxes that align to the grid

Do

Equal sizes, equal gaps, edges aligned to the grid. Parallel content gets parallel boxes — one idea per box.

Don't

Different sizes, uneven gaps, nothing aligned. The audience spends energy on the layout instead of the content.

Align every box edge to the grid — "close enough" is visible Space boxes evenly — same gutter everywhere [0.5 cm] Whitespace is a feature — empty space groups and calms; don't fill it
[Company Name]Presentation Standards
Part 1 — The slide framework

Label every element directly, so nothing needs decoding

Do
Revenue by segment, FY [2026], $M
4.2
2.6
1.4
0.9
EnterpriseMid-marketSMBOther

Values sit on the data, categories under the bars, units in the title. No cross-referencing needed.

Don't
Chart 1
Series 1Series 2Series 3Series 4

No values, no units, a legend instead of labels — the reader must bounce back and forth to decode it.

Label on the data, not in a separate legend Always show units — $, %, hours, users… Every box has a header; every icon has a caption
[Company Name]Presentation Standards
Part 1 — The slide framework

Use the approved layouts — there's one for every common slide type

Do
Title + content
Two-column
Image + text
Big number

Pick the layout from the template master — spacing, fonts, colors, and logo are already set. The same content type looks the same in every deck.

Don't

Freestyle layouts: every deck invents its own look, so the same content never looks the same twice — and every slide takes longer to build.

Same content type → same layout, in every deck Don't move the placeholders — spacing and logo are pre-set Missing a layout? Propose it to [Brand team] instead of improvising
[Company Name]Presentation Standards
Part 1 — The slide framework

Use builds deliberately — reveal one element at a time

Do
1  Reveal the headline with the message
2  Bring in the chart only when you reach it
3  Land the callout last, as the punchline

Each reveal is a decision: the room looks at exactly one new thing, on your pace. Prefer a quiet fade or appear.

Don't
"And if we add a spin here… and the logo flies in… and every bullet zooms from the corner…"

Animation for its own sake trains the room to wait for effects, not for points — and kills a projector's frame rate.

One entrance per element — and only when you say so Appear or fade; skip spins, bounces, and conveyor belts Motion with meaning — reveal sequence, show change, or build a flow
[Company Name]Presentation Standards

Part 2 of 5

Messaging & story

  • Headlines that state the message
  • One message per slide
  • The SCQA story framework
  • What belongs in the appendix
[Company Name]Presentation Standards
Part 2 — Messaging & story

Write headlines that state the message, not the topic

Do
Q3 sales grew 14%, led by enterprise accounts
An action title: a full sentence that states the "so what".

The audience gets the point even if they only read the headline. The body then proves it.

Don't
Q3 Sales
A topic label: says what's on the slide, not what it means.

"Q3 Sales" could headline any deck, any quarter, any company — it forces the audience to find the point themselves.

Full sentence, stating the takeaway — max two lines Assertion → evidence: the headline asserts, the body proves Test: if the headline fits any deck, it's a topic, not a message
[Company Name]Presentation Standards
Part 2 — Messaging & story

Give every slide one message — and let the headlines tell the story

Do
Slide 4The market is shifting to subscription pricing
Slide 5Our license revenue fell 12% in H1
Slide 6Two competitors already moved 60% of customers to subscriptions
Slide 7We recommend launching our subscription tier in Q4

Read the headlines alone, in order — the story still makes sense. One message each, so two messages = two slides.

Don't
Slide 4Overview
Slide 5Data
Slide 6More data
Slide 7Summary & appendix

Topic labels carry no message. Cramming two points onto one slide to "save a slide" just buries both.

[Company Name]Presentation Standards
Part 2 — Messaging & story

Structure the deck as a story: situation, complication, question, answer

S

Situation

The context everyone agrees on. Sets the stage without controversy.

"We grew 20% last year."

C

Complication

What changed — the problem or opportunity that demands action.

"Growth stalled in Q2."

Q

Question

The decision the audience needs to make, stated explicitly.

"How do we restart growth?"

A

Answer

Your recommendation — the main message. The rest of the deck supports it.

"Launch the mid-market tier."

✓ Do — lead with the Answer on slide 2 for executive audiences ("answer first") ✗ Don't — open with five slides of background before saying why it matters
[Company Name]Presentation Standards
Part 2 — Messaging & story

The first 30 seconds set the meeting — open with the trailer

The trailer slide: the answer and the stakes in one breath — "We're asking you to approve [X], because without it, [Y] happens."
Do
"We recommend launching in [Q4] — it's worth [$2.5M] and needs your decision by [15 Sep]. The next twenty minutes make the case."

Answer and stakes first: the room knows why it is here, and every slide after has a job.

Don't
"Hello everyone. Before we begin, a little history: our team was founded in [2019], when we started as…"

Opening with history spends the room's freshest attention on context nobody asked for yet.

Answer or stakes first — the trailer, not the table of contents Context ≤ two sentences — the past earns its slides only in the appendix
[Company Name]Presentation Standards
Part 2 — Messaging & story

Keep the main deck for the story — move the detail to the appendix

Do
Slides 1–10 · Main deckThe story: one message per slide, ending in the recommendation
Appendix divider"Appendix — backup detail"
Slides A1–A6 · BackupRaw data, methodology, detailed tables — one per likely question

The main deck carries the story; the appendix answers the deep-dive questions. Reference it: "details in appendix, p. [24]".

Don't
Slide 11Raw data export — all 34 rows
Slide 12The methodology in full
Slide 13More backup… dropped mid-story

Detail dumped mid-story loses the room — the audience came for the message, not the data. Backup is fine; buried is not.

The same standards apply to appendix slides One backup slide per question you expect to be asked Rule of thumb: "how do we know?" → appendix · "so what?" → main deck
[Company Name]Presentation Standards
Part 2 — Messaging & story

Pre-empt the objections — pair each one with its answer

Objection"Won't subscriptions cannibalize our license revenue?"
Response"The fence keeps new features subscription-first — and a customer who leaves pays either way."
Objection"What happens to cash flow if license cash becomes monthly?"
Response"Annual prepay keeps most cash upfront — we're pricing the incentive at [2] months free."
Brainstorm objections with the team before building the deck State them in the audience's words — credibility first One response slide or appendix slot per objection
[Company Name]Presentation Standards

Part 3 of 5

Visual standards

  • The brand palette and the 60–30–10 rule
  • Contrast and accessibility
  • Dark theme — when and how
  • Typography that survives the back row
  • Logo and imagery
[Company Name]Presentation Standards
Part 3 — Visual standards

Color with purpose: 60% neutral, 30% primary, 10% accent

Primary[#XXXXXX] — key data, emphasis
Secondary[#XXXXXX] — supporting data
Accent[#XXXXXX] — one highlight per slide
Neutral dark[#XXXXXX] — text
Neutral light[#XXXXXX] — backgrounds
60% neutral
30% primary
10%
Do
2.6
1.4
4.2
0.9
Q1Q2Q3Q4

Neutral bars, one highlight — color points at the takeaway.

Don't

Rainbow charts mean nothing — if everything is emphasized, nothing is.

[Company Name]Presentation Standards
Part 3 — Visual standards

Keep contrast readable: 4.5:1 for text, 3:1 for large text and graphics

Do
AaDark text on white background
15.7:1
AaWhite text on primary
6.4:1
AaDark text on accent
7.3:1

Check every text/background pair with [contrast checker tool] before presenting — projectors wash colors out.

Don't
AaLight gray text on white
2.1:1
AaWhite text on accent
2.2:1
● Fail  ● Pass — meaning by color alone

Low contrast is unreadable on a projector. And never convey meaning by color alone — add a label or icon for color-blind readers.

Body text ≥ 4.5:1 contrast ratio Large text / chart elements ≥ 3:1 Default: dark text on light backgrounds
[Company Name]Presentation Standards
Part 3 — Visual standards

Dark theme: for dim rooms and dramatic moments — never pure black

Do
Dark slides carry the same message, restyled
bg [#1B2430] white text 15.7:1 ✓ accent on dark 7.3:1 ✓

The same palette, restyled: white text, secondary and accent carrying the data — every pair still ≥ 4.5:1.

Don't
Primary headline on pure black
"Chart" pasted in from the light theme✗ breaks the theme
pure black #000000 primary on black 3.3:1 ✗

Pure black is harsh on screen, [primary] on black fails contrast, and a pasted light chart shatters the theme.

Reserve dark for titles, dividers, and dim-room keynotes Background [dark neutral #1B2430] — never #000000 Recheck every pair — [primary] fails on dark (2.4:1 ✗) Restyle charts for dark — never paste light-theme images
[Company Name]Presentation Standards
Part 3 — Visual standards

Pick the chart type by the message — a chart declares, it doesn't store

Trend — how it changes over time
Line chart, one series, time on the x-axis.
Comparison — who is bigger
Bars beat pies past two categories — always.
Composition — parts of a whole
Stacked bars, one series per color — with labels at the ends.
Target — how it stands against a goal
Bars plus a reference line — and label the line.

A chart's job is to declare a finding — the workbook's job is to store the data. Never swap those jobs.

[Company Name]Presentation Standards
Part 3 — Visual standards

Set type in two fonts — and never smaller than [18 pt] for body text

Do
ElementFontSizeWeight
Slide headline[Heading Font][28–40 pt]Bold
Box header[Heading Font][20–24 pt]Bold
Body text[Body Font][18–20 pt]Regular
Source / footer[Body Font][12–14 pt]Regular

One heading font, one body font, four sizes — that's the whole system. The template already has these styles.

Don't
Quarterly Business Review!!
Key findings & insights
Revenue Analysis Section
ANOTHER HEADING STYLE

This is the fine print that nobody in the back row can read but it contains something important about the numbers shown above and the assumptions behind them.

Five fonts, random styles, and 8 pt fine print. If it can't be read from the back row, cut it or move it to the appendix.

[Company Name]Presentation Standards
Part 3 — Visual standards

Show the logo once per slide — unchanged, with clear space

Do
[LOGO] dashed line = clear space — ½ logo height on all sides

Fixed position [top right], original colors and proportions, plain background, nothing within the clear space.

Don't
[LOGO]Stretched
[LOGO]Recolored
[LOGO]Drop shadow

Never stretch, recolor, rotate, crop, or add effects — and never place the logo on a busy photo where it can't be read.

Once per slide — the template already places it Always use the master files from [Brand asset library] — never screenshot or redraw the logo
[Company Name]Presentation Standards
Part 3 — Visual standards

Use one image style, from licensed sources only

Do
Natural proportions
Same style family

Photos from [approved image library], icons from [approved icon set] — one consistent, realistic style across the deck.

Don't
Clip art
stretched →
Distorted
watermark
Unlicensed

No clip art, no stretched photos, no watermarked or unlicensed images ("found on the internet" is not a license).

Crop, never stretch — keep the original aspect ratio Credit the source where the license requires it
[Company Name]Presentation Standards

Part 4 of 5

Data & writing

  • Charts that make one point
  • Tables designed for reading
  • A writing style that's short, active, and concrete
  • Consistent capitals, numbers, and dates
[Company Name]Presentation Standards
Part 4 — Data & writing

Give every chart one message, direct labels, and a source

Do
Enterprise drives FY [2026] revenue — $4.2M of $9.1M
4.2
2.6
1.4
0.9
EnterpriseMid-marketSMBOther
Source: [Finance BI system], extracted [1 Aug 2026] · $M

Message in the title, highlight on the takeaway, values on the bars, units and source stated.

Don't
Revenue
Ent.Mid.SMBOth.

Topic title, rainbow colors, no values, no units, no source — five standards broken in one chart.

[Company Name]Presentation Standards
Part 4 — Data & writing

Annotate the delta — the difference IS the message

Do
88%
−4 pts vs target (92%)

A bare number answers "what". The annotation answers "so what" — direction and magnitude, on the same spot.

Don't
88%

Is 88% good? Compared to what? A number without its bench means nothing — the room invents its own.

Direction + magnitude: "−4 pts", never just "lower" Annotate on the point — never in a footnote two slides later Same unit as the data — %, $, days, not vague adjectives
[Company Name]Presentation Standards
Part 4 — Data & writing

Design tables for reading, not for storing data

Do
RegionQ3 revenuevs target
North$4.2M+8%
South$2.6M+2%
West$1.4M−4%

Three columns, rounded numbers right-aligned, quiet lines, the takeaway row highlighted — readable in three seconds.

Don't
RegionRev($)TargetVarVar%YoYNotes
North423789139120003258918.3%11.2%see tab 4
South26041182550000541182.1%4.0%
West13985501455000-56450-3.9%-1.2%tbc

Seven columns, unrounded numbers, prison-bar borders, tiny type — that's a spreadsheet pasted onto a slide, not a table for reading.

≤ [6] columns — anything bigger belongs in the appendix Right-align numbers, left-align text, round per the number rules Highlight the one row the audience should remember
[Company Name]Presentation Standards
Part 4 — Data & writing

Write like you speak: short, active, concrete

Do
Leadership will cut spending in every department in Q4.10 words · active voice · one clear actor

Say who does what. Short sentences land; concrete words stick.

Don't
It has been determined by the leadership team that a reduction in expenditure is going to be implemented across all departments during the Q4 timeframe.25 words · passive voice · the actor is buried

Passive, abstract, and twice as long — the audience stops reading before the point arrives.

Active voice — "we launched", not "was launched" ≤ 20 words per sentence; bullets are fragments, not paragraphs Plain words — "use" not "utilise"; the audience's terms, not internal jargon
[Company Name]Presentation Standards
Part 4 — Data & writing

Format capitals, numbers, and dates the same way, every time

RuleStandard✓ Example
HeadlinesSentence case — capitalize the first word only"Revenue grew in Q3" (not "Revenue Grew In Q3")
NumbersSpell out one–nine; numerals for 10+; always numerals with % and units"three pilots", "12 regions", "7%"
Dates[DD Mon YYYY] — no all-numeric dates (03/04 is ambiguous)[19 Aug 2026]
Large figuresRound and abbreviate; one decimal max"$4.2M" (not "$4,237,891.43")
AbbreviationsSpell out at first use, abbreviation in brackets"Annual recurring revenue (ARR)"
TerminologyUse the approved product and team names from [Glossary]"[Product Name]" — never nicknames

Consistency in the small things is what makes a deck feel like one company wrote it.

[Company Name]Presentation Standards

Part 5 of 5

Process & governance

  • File naming, versioning, and storage
  • Review and approval before any audience
  • The 60-second pre-send checklist
[Company Name]Presentation Standards
Part 5 — Process & governance

Name and store files so anyone can find the latest version

Do
[Topic]_[Audience]_[YYYY-MM-DD]_v[##].pptx

Q3-Business-Review_Board_2026-08-19_v03.pptx

Topic, audience, date, version — sortable, searchable, and obvious which one is newest.

Don't
QBR_final_v2_FINAL_use-this-one_JBedits (2).pptx

"Final" is never final. No dates, no owner, and five copies in five inboxes — nobody knows which file is true.

One home — decks live in [shared drive / folder]; templates in [template location] Version up — v01, v02…; never "final" as a version name Share links, not attachments, so everyone opens the same file
[Company Name]Presentation Standards
Part 5 — Process & governance

Copy from the approved library — never from an old deck

Do
Start from [content library / master docs]: current logo, current language, current numbers.
If a slide is reused three times, it belongs in the library.

One source of truth means every deck inherits the latest brand and data for free.

Don't
Pulling yesterday's slide from your sent items — old logo, last quarter's numbers, already blurry.
"Where did this slide come from?" is the worst question in a review.

Every recycled deck drifts further from the truth — and further from the brand.

Re-check the brand version before every external send Fact-check anything reused — numbers age faster than layouts Propose winners to the library — [submission form / channel]
[Company Name]Presentation Standards
Part 5 — Process & governance

Review every deck before it reaches its audience

1
Self-check

Run the 60-second checklist (next slide) before showing anyone.

2
Peer review

A teammate checks message, numbers, and standards.

3
Sign-off

[Manager] for client decks; [Brand & Comms] for anything public.

4
Publish & archive

Save the final version to [location] using the naming convention.

AudienceApproval neededLead time
Internal teamSelf-check + peer reviewSame day
Client / partner+ [Manager][1] business day
Board / press / public+ [Brand & Comms team][2] business days
[Company Name]Presentation Standards
Part 5 — Process & governance

Rehearsal is part of the deck — say it before you show it

Do
One out-loud run, timed, ideally for a colleague who plays the toughest audience member.
Cut to 80% of your slot — the room asks questions in the other 20%.

The first rehearsal rewrites the deck: every stumble is a slide that needs work.

Don't
First read-along in front of the room — where you discover your own typos, live.

The audience is not your proofreader, and the room is the worst place to meet your slides.

Rehearse ≥ once for every external deck Say each action title aloud — if it doesn't sound like speech, rewrite it Slides are not a teleprompter — the audience reads faster than you speak
[Company Name]Presentation Standards
Checklist

Run the 60-second checklist before you present

Built from the official template — correct colors, fonts, logo
Every headline is a full-sentence message
One message per slide; headlines alone tell the story
All boxes aligned to the grid, evenly spaced
Every chart labeled directly — values, units, source
Brand colors only; contrast ≥ 4.5:1 for text
Dark theme? Still ≥ 4.5:1 — and never pure black
No body text under [18 pt]
Logo unchanged, with clear space
File named per convention and stored in [location]
Peer review done — sign-off for external decks
Get the template: [intranet link]  ·  Questions: [team email / channel] v[1.0] — owned by [Team], reviewed [date]

Now see the standards applied: the sample deck → sample.html

← → to navigate  ·  #N to link  ·  T training notes  ·  [ ] step points  ·  N speaker notes  ·  [Company Name] Presentation Standards v[1.0]