Before anything else: your brief outranks this page: if it names the sections, the order or a page limit, that is the document. Fairness note: every company and figure here is invented for illustration — Northgate Community Gym does not exist.
The split in one breath
An executive summary compresses a finished document into one standalone page so a decision-maker can act without reading further. It contains the conclusions and the recommendation first, not last, written after everything else is settled. An introduction opens the document for the people who continue: it names the topic, frames the question, sets the scope, then hands off to the body. It stops exactly where the body begins.
The fastest way to feel the difference is the reader test. A managing director skimming a 30-page report reads the executive summary and decides — so it must carry the verdict, the numbers and the ask on its own. A coursemate opening your report reads the introduction to learn what they are about to read, then moves on. One page is for the reader who stops; the other is for the reader who continues.
The two pages share a name-adjacent job, so they get blended constantly: the introduction gets copied and pasted at the front. The comparison below is the antidote — six rows that separate the jobs for good.
Side by side: six rows that settle it
| Executive summary | Introduction | |
|---|---|---|
| Job | Hand over the decision: finding, verdict, recommendation. | Set up the document: topic, question, scope, direction. |
| Reader | Skimmers and deciders who may read nothing else. | Everyone who continues into the body. |
| Written when | Last, after the findings and recommendations are final. | First-ish, then revised once the body settles. |
| Contains | Conclusions and recommendations up front, with the numbers that back them. | Background, purpose and scope — promises, not verdicts. |
| Length | 5–10% of the document; one page in most business reports. | A few paragraphs to a page; grows with the document, not a fixed cut. |
| What would sink it | Withholding the verdict until the end — or pasting the introduction in. | Conclusion-dumping: spending the verdict before the body earns it. |
Read the last row twice: the two failure modes are mirror images. The summary fails by being too shy — it teases and buries the answer the reader came for. The introduction fails by being too generous — it gives away findings the body has not yet supported. A summary spoils on purpose; an introduction that spoils is broken.
The Front-Matter Assembler
Two jobs in one tool. Pick a document type and its front matter assembles in order — title page to introduction — with a one-line why for every block, including the two cases where the default bends — capstones that might want an abstract, lab reports without a contents page. Then fill the five summary slots — purpose, scope, method, key finding, recommendation — and the paragraph builds live, leading with the verdict. Nothing you type leaves your browser.
Front-Matter Assembler
A document-type picker for front-matter order + a five-slot summary builder with a live preview.
Fill a slot above and the summary starts assembling here.
Worked example — Northgate Community Gym membership report illustrative · invented
Northgate Community Gym does not exist; the report below is invented to show how the five slots sound when filled:
- Purpose: whether Northgate Community Gym should extend its weekend opening hours
- Scope: the Riverside branch, September to December
- Method: eight weeks of door-counter data, a member survey, and staff interviews
- Key finding: Sunday evenings carry the highest unmet demand in the building
- Recommendation: opening Riverside until 9 p.m. on Sundays from January, with a three-month review
“This report examines whether Northgate Community Gym should extend its weekend opening hours. The central finding is that Sunday evenings carry the highest unmet demand in the building. The report recommends opening the Riverside branch until 9 p.m. on Sundays from January, with a three-month review. The scope stops at the Riverside branch, September to December. The evidence comes from eight weeks of door-counter data, a member survey, and staff interviews.”
Five sentences, every one load-bearing: purpose anchors, the finding proves, the recommendation asks, scope and method fence off what the report does not claim. The example does not touch the fields above.
Does the executive summary come before the table of contents?
Usually, yes. The default order in business and government reports is: title page, executive summary, table of contents, introduction. The logic is reader priority — the person who opens the file may be deciding whether to read on, so the verdict comes before the map.
Two exceptions matter. Academic papers put the abstract before the contents — that is the abstract doing the summary's job; the compression page still leads. And some organizations bind the contents first as house style; writing into an existing template, the template wins. For course reports, check the department guide first: the report writing format guide walks the full front-matter zone, title-page lines included.
One rule survives every exception: the summary and the introduction never swap. The summary is the last thing you write and the first thing the reader sees; the introduction is early writing that sits after the front matter, never doing the summary's job.
The 5–10% rule and the one-page cap
An executive summary runs five to ten percent of the document's length, then stops at one page in most business settings. The percentage scales the summary to its document: a 2,000-word report earns a 100-to-200-word summary, an 8,000-word capstone lands around 400 to 800, a 40-page consulting report justifies one dense page. The cap stops the percentage from scaling too far — nobody wants a four-page summary of a 40-page report; the reader would be reading the report twice.
One-page discipline is a thinking tool, not a formatting rule. When the summary will not fit, the cause is almost never missing words — it is undecided recommendations. Five recommendations each get a sentence; the page fills; the reader remembers none of them. Cut to the one or two the evidence supports and the summary shrinks on its own.
Where the rule does not apply, the page does not exist: documents under roughly four pages get a purpose statement instead, and lab reports replace the summary with an abstract on its own tighter budget — the research paper abstract guide owns that formula.
The recommendation-first rule
In an executive summary, the conclusions and recommendations go up front — not at the summary's end. This inverts essay instinct: an essay earns its conclusion in order, and a reader who skips to the end has cheated; a report's summary exists precisely so the reader can skip everything else and still act correctly. Burying the recommendation in the summary's final paragraph is the teaser failure in slow motion.
A recommendation-first summary opens on the finding that forces the decision: "The pilot covered its setup costs by week three, so we recommend keeping the cart through spring." A teaser opens on process: "This report set out to examine the feasibility of several options." Same facts, opposite respect for the reader's time. The report writing guide drills this as bottom-line-up-front; the assembler above builds it structurally, with the "lead with the verdict" toggle showing both orders.
One boundary keeps the rule honest: recommendation-first does not mean recommendation-only. A bare "approve the budget" forces the reader to trust you blindly, and deciders do not. Verdict, then the number that justifies it, then the ask — that ordering is why the five slots run the way they do.
Written last: the front-matter workflow
Front matter is read first and written last; each block reaches its final form at a different moment. The introduction is the exception that proves it: you draft it early, because a document needs a declared destination, but you rewrite it after the body settles. The summary cannot be drafted at all until the findings stop moving.
A workable sequence, using the Northgate membership report as the running example:
Draft the introduction while planning the body
"This report examines whether Northgate should extend weekend hours at the Riverside branch, using eight weeks of door counts and a member survey." A destination, not a verdict.
Fill the title page with placeholders
Five lines, final title last. Titles drift while reports grow — "Weekend Hours Review" becomes "Feasibility of Extended Sunday Hours" only when the findings name it.
Rewrite the introduction after the body settles
The survey grew, the interviews dropped out, the scope narrowed to Riverside. The early introduction now over-promises; trim it back to what the body delivers.
Write the executive summary, then build the TOC
Summary from the final findings and recommendation; contents generated from the final headings. Both come dead last — and in that order.
The order matters because each late block depends on an earlier one: a summary written before the recommendation is chosen will guess, and a guessed verdict is the one thing a skimming reader takes away. The research paper introduction guide makes the same argument from the other side — its funnel is written last even though it reads first.
Tense: what each page is allowed to say
Tense is the cheapest way to tell the two pages apart. The executive summary reports on work that is finished, so it runs on past tense for findings — "membership fell fourteen percent on weekday mornings", "the pilot covered its costs by week three" — and present tense for the recommendation and anything still true: "the report recommends", "Sunday is the strongest day". An introduction lives before any of that happened; its natural tense is the document's own future: "this report examines", "section three compares the two options".
The diagnostic works both ways. A summary that keeps saying "will" has not been written from findings — no verdict hides in future-tense verbs. An introduction that says "we found" has conclusion-dumped, and the body has nothing left to do. Fix the tense and the job fixes itself, because each page's verbs only make sense for one moment in the document's life.
Does your report even need one?
Four front-matter traditions travel under one word — "report" — and the right answer differs by type. Run your document through this list:
Business report: yes
If the document makes a recommendation to someone who can act on it, it gets an executive summary — even a class assignment dressed as a board paper. The summary is where you prove you know who reports are for; skip it and the paper reads like an essay in a suit.
Lab report: no — abstract instead
Lab reports follow the IMRaD tradition: a neutral abstract covering purpose, method, results — no recommendations, because a lab report rarely recommends anything. Writing an "executive summary" for a titration experiment is a genre error the marker will circle. The abstract guide and the lab report guide cover this in full.
Capstone: depends on the template
Capstone programs split down the middle: academic programs usually ask for an abstract, business programs often demand an executive summary, some want both. The template decides, so ask before drafting — one email beats a rewritten front matter at submission week. The capstone project guide keeps a running list of variants.
Essay: neither
An essay is an argument experienced in order, and its introduction is the essay's own genre, not a stub waiting for a summary page. If the brief asks for a summary, the piece has quietly become a report; see report vs essay for where that line sits.
When a report needs neither
Front matter is overhead, and short documents cannot pay it. A memo, a two-page status update or an email with attachments cannot carry a summary page, a contents page and an introduction — the first paragraph does all three jobs in two lines: "This update covers the Riverside pilot's first month; the short version is that Sundays are worth opening." Purpose, finding and recommendation, compressed into one sentence.
The dividing line is a reader test, not a page count: does anyone pick this document up cold and decide something from it? If the only readers live inside the project, skip the ceremony and open with the news. If a board, a client or a marker opens it cold, give them the map and the verdict.
Four fails and their fixes
Every failure below is a real submission pattern — tap each card for the fix.
The teaser summary
"This report explores several options for improving membership…" — tap to flip
Why it fails: it withholds the verdict from the one reader who will never reach it — the skimmer stops after the summary and leaves with nothing.
The fix: verdict in the first two sentences. "Sunday evenings carry the highest unmet demand; we recommend opening Riverside until 9 p.m." Context follows, never leads.
The summary that never concludes
Two tidy paragraphs of background and scope, then it just stops — tap to flip
Why it fails: it is a longer introduction, not a summary. Without a finding and a recommendation, the reader holds a map of a country the report never entered.
The fix: minimum one finding sentence with a number and one recommendation sentence with an owner. If you cannot write them, the body is not finished.
The intro that conclusion-dumps
"The data clearly proves Sunday opening would raise revenue…" in paragraph one — tap to flip
Why it fails: it spends the verdict before the body earns it, and the reader skims eleven pages hunting for an argument they were already given.
The fix: the introduction promises, the body delivers: "This report examines whether Sunday hours would pay for themselves." Future-tense verbs, no findings, no recommendation.
The copy-paste abstract swap
A lab-style abstract pasted under "Executive Summary" — tap to flip
Why it fails: an abstract is neutral by design — method-heavy, past-tense, recommendation-free. A decider reading it learns what was measured but not what to do — the one thing they opened the page for.
The fix: rewrite for the reader who acts: keep one method clause, lead with the finding, end on the recommendation. Same document, different sentence roles.
Front matter due before the body is finished?
If the deadline arrived before the findings did, you can get a free price quote for a deadline-bound writer to help structure or draft the document — the decisions and the final say stay yours.
Quiz: five questions before you draft
Five questions from the sections above. A wrong pick reveals the right one and locks; five for five earns the confetti.
Frequently asked questions
Does the executive summary come before the table of contents?
In most business and government reports, yes: title page, executive summary, table of contents, then the introduction. The reasoning is reader priority — a skimmer who opens the file wants the verdict before the map. Two exceptions exist. Some house styles bind the contents first, and academic papers put the abstract before the contents for the same reason a summary leads: it compresses the document. The honest rule is that the summary outranks the TOC wherever both appear, and your department template outranks this page.
How long should an executive summary be?
Use the five-to-ten-percent rule, then cap it at one page. A 2,000-word business report earns a 100-to-200-word summary; an 8,000-word capstone sits near 400 to 800; a 40-page report gets one dense page, not two. When the summary overruns, cut method detail first — the reader who wants method will read the body — and never cut the recommendation to make room. One tight page beats one and a half padded ones, because the page limit is what forces you to decide what matters.
Can the executive summary and introduction share one page?
Not in the same document, and not as one blended page. They answer different questions for different readers: the summary hands over what the report found; the introduction explains what the report is about to do. In documents shorter than four pages the fix is not merging — it is dropping one. Short memos usually keep a two-line purpose statement and lose the summary; a class report under six pages often keeps the introduction and skips the summary unless the brief asks for one.
Do essays need an executive summary?
No. An executive summary belongs to documents that carry decisions — reports, proposals, feasibility studies. An essay is an argument a reader experiences in order, and its introduction sets that argument up without spoiling the conclusion; a summary page in front of an essay usually signals the writer has mixed up two genres. The exception is the brief that asks for one, which turns the piece into a hybrid: follow the brief, put the summary on its own page, and keep the essay's introduction doing introduction work.
What tense should an executive summary use?
Past tense for what the report did and found: the team examined, membership fell, the pilot covered its costs. Present tense for statements that are still true and for the recommendation: the report recommends, the branch opens. An introduction runs differently — it lives before anything has happened, so "this report will examine" is correct there and a red flag in a summary. If your summary keeps saying "will", it is an introduction wearing a summary's name; switch the verbs and the verdict will surface.
Did this page settle the summary-vs-introduction question for you?