In short
Lead with the decision, then show the few figures that support it.
Keep the whole executive summary page readable on a phone and send it as one link.
Check every number against its source before sharing.
If a figure changes, update the existing page so the address already sent still opens the current version.
An executive summary template works best when it answers the reader’s first question immediately: What do you need me to decide? The useful parts of the earlier template remain here: the ask, key figures, why the decision matters now, the cost of waiting, next steps, and a note for each source.
For this rewrite, the NOS Team made a fictional studio scheduling summary. The page asks for approval of a six-week pilot. Its figures are clearly marked as invented planning assumptions, not measured results.
Download the complete fictional executive summary example
What belongs on a one-page executive summary?
- The ask: one decision and the date it is needed.
- Key figures: three or four numbers with short labels.
- Why now: the reason the decision belongs on the current agenda.
- If we wait: the specific condition that continues without approval.
- Next steps and sources: dated actions, responsible roles, and the origin of each figure.
Put the ask before the background. A reader who stops after the first screen should still know the requested decision and the numbers attached to it. Keep longer evidence below, or link to a separate report.
How do you make an executive summary page?
Start with verified notes rather than prose. For every number, keep the value, label, source, and reporting period together. Mark a missing value as to confirm instead of filling the gap with a plausible figure.
We prepared one complete page and uploaded it to the approved TEST WS. Code view showed the full page and the preview together.

View showed the same summary as a reader would see it: the decision first, followed by four figures and the reason for acting.

How do you send an executive summary as a link?
Open Share and copy the share link. In the panel we used, “Anyone with the link” could read the page without signing in and could not edit it. Search indexing was off.

Open the copied address at phone width before sending it. The first public check showed the fictional initial ask and the matching 48k budget tile.

Can you update the same executive summary link?
Yes, when you edit the existing NOS page instead of creating another page. We changed the fictional cap from 48k to 44k and kept the original share address.
The first edit attempt exposed a real failure path: selecting only part of a text block left old words in place, so the new sentence was appended to the remaining text. We did not treat that screen as a finished result. We reopened the complete page in Code, replaced it with the checked version, and compared the ask with the figure tile before leaving View.

The same public address then showed the revised ask and the matching 44k budget tile.

Finished state: one phone-readable summary, one share address, and matching values in the decision sentence and metric tile.
What should you check before sending it?
- The ask: Does it name one decision and a real decision date?
- Every figure: Does the visible number match its source, unit, and period?
- Repeated values: If the budget appears twice, did both places change?
- Missing facts: Are unverified values marked to confirm instead of guessed?
- The phone view: Can the reader see the ask and core figures without pinching?
- The public link: Does the copied share address open while signed out?
How long should an executive summary page be?
There is no universal line count. Use one page as an editing constraint: keep one decision and its supporting figures together, then move detailed evidence to a linked report. If several unrelated decisions compete for the first screen, split them into separate summaries.
When not to do this
- Do not use a link that anyone can open for confidential records, personal data, or material that requires access control.
- Do not compress several independent approvals into one first screen.
- Do not present fictional, estimated, or unverified numbers as measured results.
- Do not edit only one appearance of a repeated figure; check every visible occurrence before sharing.
Using NOS for this page
NOS Workspace was used here to open the finished page in Code and View, create a read-only share link, and update the existing page. The current example stayed inside the approved TEST WS. For the wider reporting workflow, read how to share a report as a link, compare a link with an attachment, or fix the layout with the mobile HTML guide.