To write a report: open with an executive summary that states the conclusion in the first sentences, prove it through Findings and Analysis, and close with Recommendations that name an owner and a date for every action. Reports differ from essays because the reader jumps — sections and headings carry the argument instead of flowing prose. The planner below tailors that six-part spine to your report kind and your reader, and every example on this page is invented for illustration.
Before you build anything: your assignment brief and its rubric decide the required sections, their order and their weight — this page teaches the craft that fits inside whatever structure the brief demands, and when the two disagree, the brief wins. Every report, number and sample sentence here is illustrative: invented situations with [bracketed] placeholders instead of real figures.
The six-part spine of report writing
Almost every report — a business report, a progress update, an evaluation, an incident write-up, a market scan, a research-style report — hangs on the same six sections: executive summary, introduction, findings, analysis, recommendations, conclusion. The names flex between courses and workplaces; the jobs do not. Each section exists because a different kind of reader question lands there: what should I do? is answered in the summary and the recommendations, what did you observe? in the findings, why did it happen? in the analysis, and why should I trust you? in the introduction and the sourcing behind it.
That is also what separates writing a report from essay writing. An essay is a flowing argument meant to be read front to back; a report is a structure meant to be entered anywhere. A manager reads the summary and the recommendations and skips the middle. An instructor grades section by section against the rubric. A client checks whether the scope was honored and what it cost. The writer who buries the point at the end of a long buildup is writing for a reader who does not exist. Build the spine first, put the sections in the order the reader checks them, and the report assembles itself around the decision you are asking for.
The planner below does that shaping for you. Choose the report kind, choose who will read it, name the topic in five words or fewer, and it returns the six-section skeleton with each section’s job, its share of the length, and the first thing your specific reader checks in it.
Report structure planner
Report kind + reader + topic → a six-section skeleton with jobs, length shares and reader-specific tips.
The shares below are a starting split, not a rule — your rubric and word count override them. The example report is invented and labeled illustrative.
Drafting to the shares? The word counter turns each percentage into a live budget, and the outline guide does the same budgeting for argument-driven papers.
The executive summary: written last, read first
The executive summary is the most-read paragraph you will write, and the one most often done badly. The failure pattern is predictable: the writer finishes the report, copies the introduction, and calls it a summary. But an introduction promises what the report will do; a summary hands over what the report found and what should happen next. They are different paragraphs with different jobs, and a reader can tell within one sentence.
A summary that stands alone carries three things in one paragraph: context (what was examined and why, in one clause), a headline finding (the single result everything else supports), and the recommendation (the decision you are asking for). Nothing else. No section-by-section tour, no "the report will discuss", no forward references — a reader who stops after the summary should still make the right call. Keep it to roughly a tenth of the report’s length; for a class-sized paper that is one tight paragraph, and the discipline of that limit is the point.
Write it last, even though it sits first. You cannot summarize findings that are still moving. The draft sequence that works: finish Findings and Analysis, decide the recommendation, then compress the whole report into one paragraph that leads with the decision. For example — invented, illustrative — a summary for a campus coffee-cart pilot might read:
"The four-week coffee-cart pilot tested whether a second outlet would ease canteen queues. The cart averaged [the daily figure from the tally sheet] cups and covered its [set-up cost] by week three. We recommend keeping the cart at the quad entrance through spring and reviewing price points in April." — context, headline finding, recommendation. One paragraph, no teasers.
One more test before you commit to it: read the summary aloud and count how many sentences carry a number, a name or a date. A summary built from adjectives — significant, positive, promising — collapses the moment a skeptical reader asks "how much?". Replace each adjective with the figure from your findings, or with an honest bracketed placeholder while you draft, and the paragraph starts earning trust it has not yet asked for.
Findings vs analysis vs recommendations: the three-way blur
The most common structural mistake in student and workplace reports is letting three different sentence types blur into one section. The test is simple. A finding reports what was observed: numbers, dates, counts, events — sentences a camera could have recorded. Analysis explains why the observations look the way they do: causes, constraints, patterns. A recommendation says what to do: actions, owners, dates. "The cart averaged [X] cups a day" is a finding. "Monday sales dipped because the location loses foot traffic after 10 a.m." is analysis. "Move the cart to the quad entrance" is a recommendation.
The blur matters because each sentence type carries a different burden of proof. A finding needs a source or a measure — a tally sheet, a log, a citation. Analysis needs reasoning a reader can follow, and it must not introduce brand-new observations that never appeared in the findings. Recommendations must follow from your findings, not from generic advice that could attach to any report. When an instructor or a manager pushes back with "says who?", they are usually pointing at a finding with no source, an analysis with no logic, or a recommendation with no owner.
Practical discipline: draft the three types in three separate passes and color-code them, even mentally. Findings first (what did we observe), analysis second (why did it look like that), recommendations third (what follows). Then check the recommendations reference findings by name — "because the pilot covered its [set-up cost] by week three" — so the chain from evidence to action stays visible. The sorter below drills exactly this judgment on eight illustrative sentences.
Finding, analysis or recommendation?
Eight sentences from one invented pilot. Sort each — the why-line explains the observed-vs-explained-vs-asked signal.
Sentence 1 of 8 · 0 correct so far
Match the structure to the report kind
The six-part spine holds across report types, but the balance shifts with the kind you are writing and the kind of evidence it carries. A progress report lives or dies on status clarity; an incident report lives or dies on the timeline; a market report lives or dies on dated, sourced observation. Writing a report without checking which kind your brief actually asks for is how sections end up doing the wrong jobs — a "discussion" that secretly wants to be analysis, an introduction that absorbs the summary’s work.
Check the vocabulary of the brief for the kind, then weight the sections accordingly. Six common kinds, all covered by the planner at the top of this page:
| Report kind | The reader’s core question | Section that matters most |
|---|---|---|
| Business report | What should we decide, and what does it cost? | Recommendations — each with owner, cost line, date |
| Progress report | Where does the work stand against the plan? | Findings as status: done, in progress, not started |
| Evaluation report | Did it meet its aims? | Findings measured against each stated aim |
| Incident or event report | What happened, in order, and what prevents a repeat? | The dated timeline — facts only, no interpretation inside it |
| Market or competitor report | What is changing around us? | Findings: dated, sourced observations, no forecasts inside them |
| Research-style report | What does the evidence answer? | Analysis — how findings agree, conflict or fall short |
Two of those kinds share borders with other guides on this shelf. The research-style report is the documented-argument cousin — the research paper walkthrough covers the sourcing-heavy version, and the lab variant has its own conventions entirely: the science-class version runs method, results and discussion in a fixed order. And when the assignment is a case analysis rather than a report, the case study guide shows the contrast — narrative diagnosis there, decision document here.
Whatever the kind, the business report format lesson transfers: sections with informative headings, a summary that stands alone, and recommendations that a busy person could action without reading anything else. That shape is what "professional report" means in practice — not vocabulary, not fonts: decisions made easy for a skimming reader.
Bottom line up front: the drill
Front-loading has a military shorthand — BLUF, bottom line up front — and it is the single fastest upgrade to report writing. The instinct it fights is chronological storytelling: background, method, more background, and the point somewhere around the final paragraph. Reports reverse it. The point goes first; the proof follows; the background waits where curious readers can find it.
You can feel the difference in summaries. A buried lede makes the reader do archaeology: every sentence is fine, individually, but the conclusion arrives last and everything before it reads like a toll. The drill below runs five invented summaries where the point arrives last. Pick the rewrite that opens with the bottom line — and notice what each wrong option does instead.
The BLUF drill — five buried ledes
Each summary is well written and perfectly useless until its last sentence. Rewrite the opening.
Round 1 of 5 · 0 correct so far
Headings that carry meaning
Headings are the part of report writing most writers never draft and every reader uses. A skimming reader moves heading to heading and reads a paragraph only when one of them earns it — which means a vague heading does not merely fail to help, it actively misroutes attention. "Overview" could sit over any paragraph in any report ever written; it promises nothing and therefore gets skipped.
The fix is to give each heading the section’s actual point. For example (illustrative): Sales fell [X%] in Q3 beats Sales overview, because a skimmer absorbs the finding without opening the section. The habit generalizes: subject + the verb + the result. A heading that states a claim also disciplines the paragraph under it — if the section cannot support the heading, you have found a structural bug while it was still cheap.
Three before-and-after pairs below. Both panels carry a why-line, because knowing why the strong heading works is what lets you write the next one unaided.
"Sales overview"
Why it fails: it names a topic, not a point. It could sit above a table, a complaint, a triumph — the skimmer has no reason to stop, so the section’s work is wasted on readers who most need it.
"Sales fell [X%] in Q3 — the return window explains most of it"
Why it works: subject, verb, result, cause. The skimmer takes the finding and the headline cause in one sweep, and the paragraph below merely has to prove the heading — which keeps the section honest too.
"Discussion"
Why it fails: "Discussion" is a container word. Every section discusses something. Used alone it tells the reader nothing about what changed, what broke or what it means — the three things they opened the report to learn.
"Delivery delays trace to the supplier switch, not the weather"
Why it works: it settles the question the reader actually holds ("why were we late?") and separates cause from the excuse everyone expects. The reader can now choose, accurately, whether they need the detail below.
"Background"
Why it fails: background sections invite dumping — every fact the writer found, arranged in the order it was found. The heading signals "no decision-relevant content here", which is usually self-fulfilling.
"How the cart fits the existing catering contract"
Why it works: it scopes the background to the one piece the reader must know. A heading that names its slice keeps the section short, because anything outside the slice visibly belongs somewhere else.
Sourcing, numbers and appendix discipline
Reports run on evidence, and evidence has housekeeping. Every observation in Findings needs a source a reader could check — a log, a dataset, a published study, a dated interview. Numbers need units, periods and scope: not "sales improved" but "sales rose [the percentage from the sales record] between [start month] and [end month]". And wherever the numbers came from, the citation style follows the brief — the APA paper format and MLA paper format guides cover the mechanics, and the citation generators turn a source into a formatted entry in seconds.
The appendix is the evidence’s back room, and it has two strict rules. First: the appendix holds what a motivated reader might want to verify — raw tables, the full questionnaire, calculation walk-throughs, the interview schedule. It does not hold everything you collected; it holds what the body refers to. Second: every appendix item is named in the body at least once ("the full tally sheets are in Appendix A"). An appendix nobody references is dead weight; a body claim nobody can check is a liability. Sourcing discipline is also what keeps analysis defensible: respond to each source instead of only quoting it — a habit the term paper guide builds across a whole semester of graded sections.
- Every figure has a unit, a period and a source
- Every appendix item is referenced from the body at least once
- Citations follow the assigned style with no orphans in either direction
If the brief counts pages instead of words, the words-to-pages converter translates between the two, and the free writing tools hub collects the counters and checkers that keep each section inside its budget.
Six report sins, and their fixes
Everything above compresses into six recurring failures. Tap each card — the fix is on the back.
The summary summarizes the summary
Tap for the fix
The fix: write the summary last, from the finished sections — context clause, headline finding, recommendation. One paragraph, no forward references, no "the report will discuss".
Headings named Overview and Discussion
Tap for the fix
The fix: a heading is a map, not a label. Give each one the section’s point — subject, verb, result — so a skimmer who reads only the headings still absorbs the argument.
Findings that secretly argue
Tap for the fix
The fix: findings record what was observed. The moment a sentence says "should" or "because", it has drifted — move it to Analysis or Recommendations and leave the observation where the camera saw it.
The wall-of-text paragraph
Tap for the fix
The fix: reports get skimmed, so paragraphs break at four to six sentences, lead with the point, and hand anything comparative to a table or list the eye can scan.
The appendix dumping ground
Tap for the fix
The fix: the appendix holds evidence a motivated reader might check — raw tables, questionnaires, calculations — and every item in it is referenced from the body. If you never cite it in, it does not belong.
Recommendations with no owner or date
Tap for the fix
The fix: "it is recommended that X be considered" changes nothing. Every recommendation names who acts, what they do and by when — even when the answer to "who" is you, next week.
The pre-submission checklist
Eight checks, in the order a skeptical reader tends to apply them. Tap each as you clear it.
0 of 8 checks
- The executive summary stands alone: context, headline finding, recommendation — and no forward references
- Every heading carries the section’s point, not just its label
- Findings report only what was observed, each observation with its source or measure
- Analysis explains causes without introducing observations that never appeared in Findings
- Every recommendation names an owner, an action and a date
- Every appendix item is referenced from the body, and nothing unreferenced hides in the appendix
- Citations follow the assigned style; every in-text citation appears in the reference list and back
- The rubric was re-checked section by section — every required section exists under the name the rubric uses
Report due, structure still shifting?
When the deadline is close and the sections refuse to settle, a quoted, deadline-bound writer can build the report around your brief, your rubric and your evidence — summary first, proof behind it. Get a free price quote and judge the terms before you commit to anything.
Five-question check
A fast pass on report craft. Wrong answers reveal the right one.
1. What most separates a report from an essay?
2. An executive summary that stands alone contains…
3. "Monday sales dipped because the cart’s location loses foot traffic after 10 a.m." This sentence belongs in…
4. Which heading serves a skimming reader best?
5. The appendix is the right home for…
Frequently asked questions
How do you start writing a report?
Start with the brief, not the page: list the sections the rubric requires, the citation style, the deadline and the word or page budget. Then build the skeleton — six empty sections with their headings — and draft the middle first: Findings, then Analysis, then Recommendations. The introduction is easier once the middle exists, and the executive summary comes dead last, compressed from finished sections. Trying to write a report front to back is why so many introductions promise things the findings never deliver.
What are the main parts of a report?
The six-part spine: executive summary, introduction, findings, analysis, recommendations and conclusion — usually with a title page, a reference list, and appendices where raw evidence lives. Some reports merge Analysis into Findings or split Recommendations into options and a chosen option; your brief and its rubric decide the exact shape. The planner at the top of this page returns this skeleton tailored to six report kinds and three reader types.
How is a report different from an essay?
An essay is one flowing argument built to be read front to back; a report is a structure built to be entered anywhere. Essays persuade through connected prose, so the thesis arrives early and paragraphs hand off to each other. Reports persuade through architecture: a summary that states the bottom line, headings that carry meaning, findings kept separate from analysis, and recommendations an impatient reader can action without reading anything else. The reader of an essay travels; the reader of a report jumps.
How long should an executive summary be?
About a tenth of the report is the common convention — a convention, not a rule. For a class-sized report that means one paragraph: context clause, headline finding, recommendation. Two tests beat any word count: a reader who stops after the summary can still make the right decision, and every sentence carries something concrete — a figure, a date, a name — rather than an adjective promising that details exist somewhere below.
Do reports need references and an appendix?
References, yes whenever you used sources — reports cite like any other academic work, in the style the brief names, and a report paper without citations is a memo. An appendix, only when there is raw evidence worth keeping: full tables, questionnaires, calculations a motivated reader might check. Two rules keep an appendix honest — every item in it is referenced at least once from the body, and nothing that belongs in the argument hides inside it. If the brief is silent on either, ask; both shape the whole build.
What makes a report look professional?
Not vocabulary and not fonts. A professional report is one where the structure does the work: a summary that stands alone, headings that state points, findings that never argue, recommendations with owners and dates, numbers that carry units and sources, and an appendix that gets referenced. Consistent formatting of those numbers matters more than decoration — the same figure should not appear as a percentage in one section and a fraction in another. Skim your own report the way a busy reader will: summary, headings, recommendations. If that three-sweep pass communicates the decision, the report reads professional.
Was this guide useful?