How to Build an Executive Summary Slide (SCR Method)

Quick answer: what is the SCR method?

To build an executive summary slide, write the governing thought first, the one-sentence recommendation the whole page exists to defend, then wrap it in three bands: a situation everyone already accepts, a complication that forces a decision now, and a resolution that states the recommendation and the next step.

An executive summary slide is the single page in a corporate deck that carries a decision-maker's entire read of the argument: a governing thought stated as the title, then three short bands built on the situation-complication-resolution (SCR) structure, each led by one bold line a reader can skim in seconds. Teams use it to open a board pre-read, a steering committee update, an investment memo, or a diligence pack, whenever the audience needs the answer before committing to read the reasoning behind it. Backed by three supporting KPI tiles, it is built to be read in under a minute and to stand on its own if the author is not in the room.

When is the SCR method the right choice?

Board materials do not get read the way authors assume. A 2026 board-reporting study by the Chartered Governance Institute UK & Ireland and Board Intelligence, drawing on 1,857 directors and governance professionals across 1,676 organizations, found that 62 percent rated their own board pack "weak" or "poor," 63 percent were not confident their pack was fully read before the meeting, and 54 percent said readers struggled to find the key message inside it. As Pippa Begg, co-founder and chief executive of Board Intelligence, put it: "More data has not made boards better informed. Too often it buries the signal that matters under everything that might." SCR exists to be the exception. Use it when:

For the wider deck around this page, see the Claude PowerPoint slide design skill.

Key takeaways

• Match the resolution to how much choice the room actually has. One answer wants single-recommendation SCR; a real choice between two paths wants a decision fork in the resolution band, not two slides arguing past each other.
• Decide whether the slide has to survive without you presenting it. A page read cold, in a board pre-read or a diligence pack, needs more self-contained evidence than one you will narrate live in a steering committee.
• Do not fake precision the numbers do not have yet. If a KPI tile is still directional, bracket it and say so; a confident-looking number that later moves costs more credibility than an honest placeholder ever did.
• Weight the evidence to the stakes, not to habit. A board approving routine spend wants three tight KPI tiles; a diligence memo that has to stand alone wants more support underneath the same three bands.
• Keep the shape stable across a recurring series. A steering committee slide that reorders its bands every cycle asks the reader to relearn the page instead of just reading what changed.

The five ways to apply SCR, compared

SCR is one of four recognized executive summary structures, alongside SCQA, the so-what stack, and the 3-box layout; the executive summary slide examples compare all four with the exact wording for each. This guide goes deep on SCR specifically, because it is the default for a recommendation backed by numbers. Once SCR is the right structure, it still bends five ways depending on the decision behind it.

Single-recommendation SCR: who is it built for?

This is what most people mean when they say "the SCR method." One situation, one complication, one resolution, and the resolution states a single recommendation the room is being asked to approve: fund the program, approve the spend, ship the plan. It is the default because it is the fastest to write and the fastest to read, and because it maps directly onto the most common ask in a corporate deck, one decision, one answer.

Build the resolution first as a single sentence, then work backward: the complication is whatever makes that sentence necessary now, and the situation is whatever context the room needs before the complication will land. Three KPI tiles carry the proof. Keep every one of them tied to the recommendation itself, not to the program in general, or the tiles will read as decoration rather than evidence.

The trade-off: a single-recommendation SCR is fast to build and easy to defend, but it assumes the room has already accepted that a decision is needed at all. If that acceptance is not there yet, spend a line establishing why now, or the resolution lands on a room that has not agreed the complication is real.

SCR with a decision fork: who is it built for?

A decision fork keeps the situation and complication bands exactly as they are in the single-recommendation version, then splits the resolution band into a recommended path and a named alternative. It is built for governance that expects to see the alternative considered, an investment committee, a board with a fiduciary process, without turning the slide into a neutral menu that argues for nothing.

Give the recommended path the emphasis color and the larger share of the band; give the alternative a smaller, muted treatment and one line stating why it was not chosen. That single line matters more than it looks: a fork without a stated reason for rejecting the alternative reads as indecision, not diligence.

The trade-off: a decision fork proves the alternative was considered, but every option after your recommendation is a specific counter-argument the room can now raise by name. A plain single-recommendation SCR gives the room one thing to challenge; this version gives them two.

Recurring SCR for a steering committee update: who is it built for?

A program or governance update is not a first ask, it is one entry in a series, and the recurring version of SCR treats it that way. The situation band restates last cycle's resolution in one line, "as approved last month," the complication band names whatever has changed since then, and the resolution band carries this cycle's ask. The audience already has the background, so the situation earns a nod in one sentence rather than a paragraph.

Hold the band order, the KPI tile positions, and the emphasis color identical across every cycle. A committee that sees the same shape every time can skim straight to what changed; a committee that has to relearn the layout each cycle spends its attention on the slide instead of the decision.

The trade-off: reusing last cycle's resolution as this cycle's situation keeps the series legible, but it also means an error in one cycle propagates into the next one's setup. Audit the carried-forward line before you reuse it, do not just copy the slide.

Diligence-grade SCR: who is it built for?

A diligence-grade summary is built to be read cold, without you in the room, by someone who will act on it days or weeks later. This is not a hypothetical concern: research on board packs by Board Intelligence, working with Cambridge Judge Business School, found that more than half of boards now receive a pack of 200 or more pages, that directors read at a maximum of roughly 30 pages an hour, and that the average director still spends just shy of four hours reading a pack that would take a full working day to finish at that rate, leaving almost half of it unread. A page meant to stand alone in that pile has to carry more than the single-recommendation version.

Keep the same three bands and the same three KPI tiles, but foot-note each tile to the page or exhibit in the appendix that backs it, and reconcile every number on the slide to the full memo before it goes out. The bands still have to read as one governing thought in one pass; the appendix references are what let a reader verify that thought without asking you a follow-up question.

The trade-off: the added evidence is what lets a diligence-grade SCR stand alone, but every extra number is also something a reviewer can contest. The page still has to read as one argument, not a dense appendix wearing an SCR skin.

Early-stage SCR: who is it built for?

An early-stage summary carries a directional read before the analysis is finished: a steering group needs a first opinion, but the model is not locked. The resolution states a direction rather than a commitment, "recommend proceeding to the next phase pending final sizing," and every KPI tile is visibly marked as an estimate rather than presented as a finished number.

The discipline that matters here is not the writing, it is what happens after: this version needs a named review step before the final numbers replace the bracketed ones, with someone accountable for checking that the direction still holds once the analysis is done.

The trade-off: an early-stage SCR buys a directional read before the work is finished, but a bracketed placeholder that quietly becomes the final number, without anyone re-checking it, is exactly how an early estimate turns into a board's memory of a commitment.

How do you actually build the SCR bands?

The construction sequence is the same across all five variants above; only the evidence weight and the number of caveats change. Build the narrative before the layout.

The build sequence

What stays on the page, and what moves to the appendix

Write down everything you considered, then cut to what defends the governing thought and nothing else. The resolution keeps its single strongest reason on the page; the second and third reasons move to a backup slide. A KPI tile carries one number and one label, never a mini table. The situation states the accepted context in one line, not the history that produced it. If a fact does not change whether the reader agrees with the resolution, it belongs behind the summary, not on it.

How the summary relates to the deck behind it

An executive summary is not a preview of the deck's order, it is the deck's conclusion pulled to the front. Every body slide behind it exists to defend one line in one band. If a body slide does not map to a specific line in the situation, complication, or resolution, either cut the slide or the summary is missing a claim the deck is making elsewhere; both are worth catching before the deck goes out.

The one-page test

Read only the three bold lead lines, situation, complication, resolution, top to bottom, and skip every supporting note underneath them. If those three lines alone do not make a complete, defensible argument, the slide is leaning on you to fill a gap it should fill itself, and it will not survive being forwarded without you in the thread.

Can Oria build the executive summary slide for you?

Yes, and that is the narrow thing it is for. Oria is built for corporate documents and consulting presentations: board packs, steering committee decks, diligence exhibits, dense frameworks held to an enforced corporate template. It reaches you two ways: a PowerPoint add-in running in the task pane on Windows, macOS, and PowerPoint for the web, and a connector for Claude and ChatGPT over MCP, so the slide can be built from the chat you are already in, without opening PowerPoint. Either way the output is native, editable PowerPoint elements on your master, not a flat image.

Describe the SCR narrative in one line and Oria renders the situation, complication, and resolution bands, plus the KPI tile row and the action title, aligned to a clean grid. Every band, tile, and label stays editable afterward, so swapping a metric or rewording the resolution never means rebuilding the slide. For the narrative side of the workflow before you build, our Claude skills for executive summary writing cover getting to a defensible governing thought first.

The trade-off: Oria is built for the corporate environment and loses on highly visual work. Founder fundraising and pitch decks, launch and campaign decks, student presentations, and marketing one-pagers want visual impact more than defensible content, and a design-led tool such as Gamma, Canva, Pitch, or Beautiful.ai will beat it there and look better doing it. For the tools that carry a full deck under deadline, see the guide to the best AI for PowerPoint.

If your situation is different, build this instead

An executive summary is not always the right page, and SCR is not always the right structure for it. Route yourself honestly before you spend an hour on the wrong one.

Common executive summary slide mistakes to avoid

Most of these are structural slips, not judgement calls, which is exactly the sort of thing the answer-first discipline behind SCR was built to catch. The logic predates the slide format itself: the U.S. Army's own correspondence standard, Army Regulation 25-50, requires the main point or recommendation in the first sentence of a memo, on the same reasoning that puts the resolution's governing thought in an executive summary's title rather than its last line. For the full method behind board-ready decks, the consultant's guide to Claude covers storyline, structure, and slide design end to end.

Frequently asked questions