Skip to content
The title slide and first slides of the Reliability Review Deck template

Reliability Review Deck

Presentation template for Google Slides and PowerPoint

Make a copy in Google Slides
Price
Free
Slides
10
Style
Minimal
Difficulty
Beginner
Updated
November 12, 2026

Every slide (10)

Overview

Engineering leaders need to know whether delivery is getting faster and safer, and SRE teams need to see where reliability is slipping before customers notice. This deck brings those views together: the SLO overview, the error budget each service has used, the incidents behind any spend and the actions for the next period. Each slide labels what was measured and what is judgement, so the trend can carry the message.

The sample reviews five services over one quarter, with 99.94% attainment on the checkout API, two SEV1 incidents and a time to restore that fell by 12%. Replace the services, targets, budgets and incidents with your own data, name the data source on the first slide, and keep the action list to three items, each with an owner.

Useful for

  • An SRE lead preparing the quarterly reliability review for the VP of engineering and the CTO
  • An engineering manager checking whether a service's error budget was spent by a single release
  • A platform lead deciding whether to pause feature work to fund reliability fixes this month

What's included

  • Cover slide and SLO overview with three headline figures and a caption
  • Columns slide explaining each SLO, how it is measured and who owns it
  • Error budget table listing each service, its target, budget used and status
  • Error budget stats slide with spend figures and a one-line caption
  • Incident timeline with five dated events and a short note for each
  • Actions process with owned steps and a make-it-yours guide

How to use it

  1. 1

    Click Make a copy in Google Slides, then confirm on the Google page. The copy is saved to your own Google Drive.

  2. 2

    Replace the four headline figures with your last four quarters of data, and name the data source on the first slide.

  3. 3

    Update the error budget table with your services, targets and budget used, then flag any service that is off track.

  4. 4

    Link each incident to its postmortem, and drop any incident below your severity threshold.

  5. 5

    Delete the guide slide, then share the deck with engineering leadership or present it at the review.

What you need

Requirements

  • A Google account with access to Google Slides

Works with

  • Google Slides
  • Microsoft PowerPoint (File → Download → .pptx)

Questions

Are Marlowe Green Labs, the services and the figures real?

No. Marlowe Green Labs, the services, the people named, the SLO targets and every incident in the deck are fictional sample data. Replace them with your own monitoring and incident records before you present the deck.

How should SLOs be measured for the review?

State the window, the event definition and the data source on each slide, for example a 30-day rolling window over successful checkout requests. Medians and p90 values show the spread better than averages, which can hide a long tail.

Should the deck name individual engineers?

No. The review should show team and service trends rather than rank people, because named comparisons change how people behave. Name the owning team on each action and keep commentary to what the data supports.

  • #sre-review
  • #slo-report
  • #error-budget-template
  • #reliability-metrics
  • #incident-review
  • #engineering-metrics
  • #google-slides-template

More engineering metrics report templates

See all 8

Also in Developer workflows

All developer workflows templates
Get this template

Preparing your template…