An executive summary page is defined by what you leave off it. Every other page in your report answers “what happened”. This one answers “what should we do about it”, and it only works if a reader can get that answer without scrolling, clicking or asking you a question.
This covers what earns a slot on the page, how to build it in Data Studio step by step (compared scorecards, a target on the tile, two comparisons on one tile, one chart, the commentary and a “data to” stamp), and the part nearly everyone skips: writing the summary itself.
What an executive summary page in a Data Studio report is
It’s a single report page, placed first, that states the headline performance, the one trend that explains it, what it means, and what happens next. Three or four numbers, one chart, a written summary, a short list of actions.
The distinction that makes it work is the one between exploratory and explanatory reporting. The rest of your report is exploratory: it lets someone dig. The summary page is explanatory: you’ve already done the digging, and you’re handing over the conclusion. So the test isn’t “is this metric interesting”. It’s “would I say this out loud in the first minute of the meeting”.
Build the summary page on day one, not the month you need it
The usual order is detail pages first, then a summary later, when somebody senior asks for one. That’s backwards, and the reason is timing rather than design. The day your contact introduces you to their boss (with no warning, usually in a meeting you didn’t schedule), the page has to be there already. The architecture that works is one holistic, top-level page covering every channel, linking out to the project pages underneath it.
The five-second rule for an executive summary page
Here is the test the rest of this article keeps returning to: if a reader can’t state the headline within about five seconds of the page loading, the page has failed.
Not “can they find the number”: can they say what it means. A page with eleven scorecards contains the answer somewhere. A page with four scorecards and a sentence is the answer. Type size sets reading order, so a finding that matters to every reader belongs in the largest type on the page, which in practice means rewriting a chart title rather than adding a paragraph (the full argument is in the dashboard design principles guide). Applied honestly, this rule removes about half of what people put on a summary page.
What earns a slot on an executive summary page
Three or four scorecards, each with a comparison
Every scorecard on this page needs a subject, a period and a comparison. A bare number is a fact rather than information: the reader silently supplies a baseline, usually the wrong one. Pick output metrics your reader is accountable for (revenue, orders, leads, conversions). Input metrics (pages published, links earned, issues fixed) matter, but they belong on the project pages, because an executive can’t act on them directly. If you can’t say why a number is on the page in one sentence, it isn’t.
One chart, and it’s almost always a time series
One. Not four. The executive question is nearly always directional: is this getting better or worse, and since when. If your one chart is a bar chart, check whether the page is trying to do a detail page’s job. The guide to Data Studio chart types covers picking one from the shape of your data.
The written summary, which is the part everyone skips
A page of charts with no words is a stats dump: it leaves the interpretation to whoever is least equipped to make it. It’s covered further down, because it’s the hardest part.
The next-steps block, owned and dated
Not “consider improving internal linking”: who is doing what, by when, and what you expect it to move. Leaving a client to work out their own next steps from a dashboard is the most common way a good analysis produces no change at all.
How to build an executive summary page in Data Studio, step by step
If the report is already shared with the client, build on a copy first. The screenshots are mine, on Google’s GA4 demo account; the worked numbers are Harbour & Fern’s, the fictional retailer from my ebook, which took £412,000 in September against a £450,000 target.
Step 1: add the page and move it to position one
- Add a page with Page › New page.
- Open Page › Manage pages. The Report pages panel lists every page in navigation order; drag the new page to the top.
- Name it for what it is, “Summary” or “This month at a glance”: the name appears in the report’s navigation.
- If the report has more than about three pages, set the navigation to a left-hand menu in Theme and layout › Layout. Tabs run out of room just as the report gets big enough to need them.
Step 2: add the scorecards and choose each comparison
A new scorecard already compares with the previous period. That’s rarely the comparison an executive needs, so set it on purpose:
- Add a scorecard per headline output and set its metric.
- In Setup, leave Comparison type on Period (in a UK-English interface it reads “Full stop”) and set the Comparison date range to Previous year for anything seasonal. December against November isn’t a comparison anyone should act on.
- For a target, set Comparison type to Value, type it in Target value, and turn on Show as progress, just under it on the Setup tab, for a progress bar.
- A tile without a target can carry a sparkline instead (Setup › Sparkline), which gives the shape as well as the headline. One tile can’t have both a sparkline and a progress bar.
- Give every tile in the row the same comparison base, and write it into the title (“Revenue, Sep vs Sep LY”). Readers assume all four tiles share whatever the first one uses.
Worked example. Harbour & Fern’s row: Revenue £412,000, up 9.6% on last September; Sessions 272,000, up 18%; Conversion rate 2.10% against 2.40%; Average order £72.13, up 6.1%. All four compare with last September. Every setting, including absolute change for rates, is in the scorecards tutorial.
Step 3: put two comparisons on the headline tile
A scorecard takes one comparison, and the headline number often needs two: on plan, and growing. I stack two scorecards so they read as one tile.
- Start with the scorecard for the comparison the reader cares about most. On a summary page that’s usually the target, with Show as progress turned on.
- Copy and paste it. On the copy, change Comparison type to Period, with Previous year as the comparison date range. For your own wording, type something like “vs Sep LY” into Style › Comparison fields › Comparison label.
- Still on the copy, turn on Style › Labels › Hide field Name, so the metric name disappears.
- Back on the original, set Style › Background and border › Background to white (or your page colour) at 100% opacity. That solid background is what covers the copy’s number.
- Drag the copy beneath the original so only its comparison line peeks out below. Right-click the copy, choose Send backward, then select both tiles and Group them.
Harbour & Fern’s revenue tile then reads 91.6% of the £450,000 target, with “+9.6% vs Sep LY” underneath. It needs a freeform report: a responsive one won’t let components overlap or be grouped. Before the report goes out, open it in view mode and download a PDF to make sure nothing shows through. The detail is in two comparisons on one tile.
Step 4: add one time series, with its own date range and the target
- Add a time series of the headline metric by month.
- Give the chart its own range: Setup › Default date range › Custom, not Auto. Auto means the connector’s default, which differs between connectors and is how two charts on one page end up showing different periods.
- Add last year as a comparison, so the shape has context.
- Draw the target. A single target goes in as a reference line (Style › Add a reference line), labelled with its basis. If the target changes month to month, add it as a second metric from a sheet instead, because one line sits at one value: see a fixed target against a moving date range.
A trend against a target answers “are we on track” at a glance; the same trend without one only answers “did it go up”.
Step 5: add the commentary, beside the chart
Insert a text box beside the chart, not underneath it. Underneath, it reads as a caption and gets skipped; beside it, it reads as the point.
The dashboard refreshes automatically; your commentary doesn’t. On the first of the month you’d be showing last month’s notes against this month’s data. Decide now how it stays current: keep the commentary as dated rows in a Google Sheet blended into the report, or at least start the box with its period (“September: …”). Then add one small line, “Commentary updated on the first and third Monday of each month”, so the reader knows when to expect new words.
Step 6: stamp how fresh the data is
Readers shouldn’t have to wonder whether they’re looking at yesterday’s numbers or last week’s. A line such as “GA4 data to 15 Oct 2026”, with the date pulled from the data source, answers that before anyone asks. In Data Studio that’s a query result variable: one value from a small query, dropped into a text box, which refreshes when new data comes in.
- Insert a text box where the stamp should sit and type “GA4 data to “.
- Type @, and in the menu that opens choose Add a variable.
- The Create variable screen opens. Call it “Data to” in Variable name and pick your GA4 data source.
- Use Date as the only dimension. Leave the metric empty.
- In Sort, make Sort #1 Date, Descending, so the newest date sits at the top of the table.
- Point the variable at that top cell: Column Date, Row 1. The Preview shows the date it will display.
- Save, place the variable in the text box and finish the sentence.
There’s no need for MAX(): sorting newest first and reading row 1 already gives you the latest date. One setting to be aware of is the variable’s own Default date range filter, which starts on Auto: Last 28 days (exclude today). The stamp shows the newest date with data in that window, which is what a freshness stamp is for, but it isn’t a record of everything the source holds. The same screen has a Conditional formatting link, so the date can turn red when it’s stale.
Step 7: link through to the detail pages
The summary works because things are missing from it, which only holds if the missing things are one click away. Link out to the project pages through the navigation or with buttons, and leave the filter controls to those pages. If one date control should apply everywhere, right-click it and choose Make report-level, so setting the summary to last quarter doesn’t leave the detail pages on last month.
How to write the summary text on an executive page
A four-part sentence pattern for report commentary
What changed → by how much → why → what we’re doing about it.
Dull as a formula, and it works, because it answers the four questions an executive asks in that order anyway. It’s also the structure to hand an AI assistant if it drafts the first version: writing client report commentary with AI without making things up.
Three real report summaries, rewritten
Weak: “Organic traffic was down this month.”
Better: “Organic sessions fell 12% month on month, driven almost entirely by the blog. Two of our top ten landing pages lost position after the March core update. We’ve rewritten both and resubmitted them; we’d expect recovery within six to eight weeks.”
Weak: “Great month for conversions, up 24%!”
Better: “Conversions rose 24%, but 18 points of that came from the brand campaign that ran 8–22 March. Underlying non-brand conversion is up 6%, which is the number to plan against. The campaign ends in April.”
Weak: “Rankings continue to improve across target keywords.”
Better: “We now rank top three for 14 of the 40 target terms, up from nine. Those 14 account for 61% of the tracked search volume, so the revenue impact should be larger than the count suggests. Next is the nine terms sitting at positions four to seven.”
Notice what the good versions do: they name a cause, they separate signal from noise, and they end with something happening. None of them runs past four sentences. Chapter 22 of my ebook, Data Storytelling in Data Studio, covers this page in full, from the five-second rule to taking it into slides.
How to write numbers inside report commentary
- Round. “Up 12%” is more usable than “up 11.87%”.
- Give the comparison in the sentence. “31,900 sessions” means nothing; “31,900 sessions, up from 28,400” means something.
- Be honest about noise. If a 4% move is within normal variance for that metric, say so rather than narrating it as a trend. Doing this every month is what makes people believe you when you say something is significant.
Writing the summary when the news is bad
Report it plainly, early, and with a route out. Most of the damage comes from our side rather than the data’s: dreading the conversation, or guessing how someone will react and bending the story to suit. If performance is down because of something on the client’s side (a migration that shipped without you, three months of recommendations not implemented, a budget cut), it still belongs in the summary, framed as a fact with a consequence and a fix rather than an accusation. And don’t hold it for the quarterly review: a conflict that surfaces once a quarter has had three months to compound.
How the summary page changes by who is reading it
| Reader | Lead with | Keep off |
|---|---|---|
| CMO or head of marketing | The outcome they present upward (revenue, pipeline or CPA), and one trend against target | Channel breakdowns: that’s what the click-through is for |
| Founder or CEO | Two or three numbers, one trend, three sentences, one decision | Anything needing a paragraph of setup, and filter controls they won’t use |
| Client contact who reports upward | Sentences they can lift verbatim, and the comparison figures they’ll be asked for | The figures you find interesting but they won’t be asked about |
The third case is the most common and the one most people get wrong: your contact isn’t the final audience, they’re going to paste your numbers into their own deck. The kindest thing you can do for them is make them look well prepared to their boss.
What to leave off an executive summary page
- Pivot tables. They reward digging, and this page is for people who won’t.
- Anything needing a paragraph to explain. If the metric needs a definition, put it on a detail page with the definition beside it.
- Daily-granularity data. Day-level detail in a monthly report is noise wearing a chart.
- Position tracking. Useful, but mis-audienced here: it invites a conversation about position 4 to 6 instead of about revenue.
- Everything you’re proud of building. The hardest cuts are the charts that took longest. They still belong on a detail page.
Taking the summary page into a slide deck
- Build at a page size that exports cleanly. If the page will end up in slides or a PDF, set a 16:9 or A4 canvas in Theme and layout before you build.
- The export captures what’s rendered. A table showing ten of four hundred rows exports as ten rows; expanding tables in a PDF download is a Data Studio Pro option. Another argument for keeping tables off this page. More in how exporting and scheduling a report works.
Executive summary mistakes that make the page get skipped
- Showing everything. It comes from a good instinct, wanting to demonstrate the work. Demonstrate it on the detail pages.
- Starting from the chart. Start from the decision the reader has to make.
- Mixed comparison bases. One tile against last month, the next against last year, and the reader can’t tell.
- No takeaway. A page that ends on a chart ends on a question. Put the answer on it.
- A narrative the data doesn’t support. A compelling story built on a correlation is more dangerous than a boring one built on a fact, because it’s more persuasive. If you’re inferring rather than measuring, say so.
Report templates to start from
Frequently asked questions
What is an executive summary page in a Data Studio report?
A single page, placed first, that answers what happened, why, and what happens next, without the reader needing to open anything else: three or four scorecards with comparisons, one chart, a written summary and a set of owned, dated actions.
How do I add a comparison to a scorecard in Data Studio?
Select the scorecard and open the Setup tab. Comparison type should be Period (it reads “Full stop” in UK English); then set the Comparison date range to previous period, or previous year for anything seasonal. A new scorecard shows the previous period by default, so check it’s the comparison you mean. For a target, choose Value and type it in Target value.
Can a scorecard show a target and last year at the same time?
Not on one tile: a scorecard takes one comparison. Stack two scorecards, the target one in front with a solid background and a copy behind showing only its previous-year comparison, then group them. It works in freeform reports, not responsive ones.
How do I show when a report’s data was last updated?
Add a text box, type @ and choose Add a variable. Use the data source’s Date dimension, sorted descending, with Column Date and Row 1, and the text box shows the latest date with data, for example “GA4 data to 15 Oct 2026”.
What should the written summary on a report actually say?
Follow a four-part pattern: what changed, by how much, why, and what you are doing about it. Three or four sentences. Longer than that and it isn’t a summary any more.