How to Write a Report: Structure, Steps and a Sample Outline

A report is a structured document that answers a specific question with evidence and, usually, recommendations. To write one, define its purpose and audience, gather and analyze your information, organize it under standard headings (summary, introduction, method, findings, discussion, recommendations), and write the summary last. Good reports are easy to scan: a busy reader should get the main answer from the first page.

Reports show up everywhere, from lab and book reports in school to incident reports, project updates and market analyses at work. The details differ, but the logic is the same.

Start with the brief

Before you collect a single fact, get clear on four things:

1. The question. What exactly is the report supposed to answer? "Why did customer complaints rise in Q3?" is a report question. "Customer complaints" is just a topic.
2. The audience. A manager who'll make a decision needs a different level of detail than a technical team that will implement it.
3. The scope. What's in and what's out? Time period, departments, locations, budget.
4. The format. Required headings, word count, citation style, file type and deadline.

If you're a student, these come from your assignment brief. At work, ask whoever requested the report. Five minutes of clarifying questions can save hours of writing the wrong thing.

Common report types

Each has its own conventions, but most borrow from the structure below.

The standard report structure

1. Title page – title, author, date, and who it's for.
2. Executive summary or abstract – the whole report in a few short paragraphs: question, method, key findings, recommendations.
3. Table of contents – for anything longer than a few pages.
4. Introduction – background, purpose, scope and the question you're answering.
5. Method – how you gathered information: surveys, interviews, experiments, sources consulted.
6. Findings or results – what you found, presented clearly, often with tables or charts.
7. Discussion or analysis – what the findings mean and how confident you can be.
8. Conclusions – the direct answer to your question.
9. Recommendations – specific actions, ideally prioritized.
10. References and appendices – sources, raw data, survey questions, extra detail.

Short reports can combine sections. A two-page status report might be just summary, progress, issues and next steps.

How to write a report, step by step

1. Gather your information

Collect what you need to answer the question: data, documents, interviews, observations or published research. Keep track of where each piece came from as you go. Rebuilding a source list at the end is miserable, and it's how citations get lost.

2. Analyze before you write

Look for patterns, differences and surprises. Ask what the evidence actually shows, not what you expected it to show. Note where the evidence is thin, conflicting or limited. Those limitations belong in the report too.

3. Outline with headings

Turn your structure into an outline with headings and two or three bullet points under each. This is where you decide what goes in the main body and what moves to an appendix.

4. Write the findings first

Findings are the core of the report, so draft them before the introduction. Present each one plainly: what you found, the supporting evidence, and a figure or table if it helps. Keep interpretation for the discussion section so readers can see the facts separately from your reading of them.

Weak: "There were a lot of complaints about delivery, which was bad."

Clear: "Late delivery was the most common complaint category in Q3, appearing in 212 of 540 logged complaints. Most of those involved orders shipped from the Eastfield warehouse after it changed carriers in July."

Note: the clear version gives a number, a comparison and a likely link, without yet claiming the carrier change caused the problem. (Figures here are invented for illustration.)

5. Write the discussion and conclusions

Explain what the findings mean for the original question. If there are several possible explanations, say so and weigh them. Your conclusions should answer the question in the brief directly.

6. Make recommendations specific

"Improve delivery" isn't a recommendation. "Review the Eastfield carrier contract and run a 30-day trial with a second carrier for orders in the northern region" is. Where possible, say who should act, by when, and roughly what it would cost or require.

7. Write the introduction and summary last

Now that you know what the report says, write the introduction to set it up and the summary to condense it. The summary should make sense to someone who reads nothing else.

8. Revise, check and format

Read through for clarity and flow, then check every number, label and citation. Make sure tables and charts have titles, units and sources. Apply consistent heading styles so the table of contents works.

Writing style for reports

• Plain and precise. Use the simplest word that's accurate. Define technical terms the first time you use them.
• Short paragraphs. One idea each, with a clear topic sentence.
• Headings that inform. "Delivery delays concentrated in one warehouse" is more useful than "Findings 2."
• Visuals that earn their place. A table or chart should show something faster than a sentence could.
• Honest about limits. If your survey had a small sample or your data covered one month, say so.

Example outline: a short business report

Title: Reducing Late Deliveries in the Northern Region

Executive summary: Late deliveries rose in Q3, mainly from one warehouse after a carrier change. Recommend a carrier trial and weekly tracking.

1. Introduction – complaint trend, purpose, scope (Q3, northern region)
2. Method – complaint log review, carrier data, interviews with three warehouse leads
3. Findings – complaint categories; timing of delays; warehouse comparison
4. Discussion – likely causes; other factors such as staffing; limits of the data
5. Conclusions – carrier change is the most likely main factor
6. Recommendations – carrier trial; weekly late-delivery dashboard; review in 60 days
Appendix – complaint category definitions, interview questions

Using AI and research tools honestly

Tools can genuinely save time on reports. A summarizer helps you digest long source documents, a report generator can propose an outline from your notes, and a grammar checker catches errors in a long draft. What tools can't do is supply your data or verify your conclusions. Every number, quote and source in the report must be something you checked. If you're writing for school, follow your instructor's policy on AI use and disclose it where required.

AI Report GeneratorTurn notes into a clear report

Key takeaways

• Pin down the question, audience, scope and format before you start.
• Use a standard structure and informative headings so readers can scan.
• Draft findings first, separate facts from interpretation, and write the summary last.
• Make recommendations specific: who, what, by when.
• State your limitations and double-check every figure and source.

If you're working on a school assignment about a book rather than a business question, the shape is different; see our guide on how to write a book report.