The findings section is the engine of a business report. Everything before it sets up the question; everything after it draws conclusions. Yet it's the section most writers rush through, dumping raw data in the order it arrived rather than in the order a reader can absorb it. The result is a wall of numbers and observations that forces the reader to do the analytical work themselves.
This guide covers how to structure a findings section, how to present data without distorting it, and how to keep readers moving through material that could easily lose them.
What the findings section actually does
A findings section reports what you discovered. It doesn't interpret, recommend, or argue. That work belongs in the analysis and conclusions sections. The findings section answers one question: what did the data show?
This distinction matters because mixing findings with interpretation muddies both. A reader who can't tell where the evidence ends and the opinion begins will trust neither. Keep the sections clean.
The findings section works alongside the methods section. If your methods section is clear about how you gathered information, readers arrive at the findings already oriented. They know what kind of evidence to expect. A weak methods section forces you to over-explain your findings, which slows the whole document down.
How to organise your findings
Don't present findings in the order you collected them. Present them in the order that builds the clearest picture. Three organisational approaches work well in business reports:
- Thematic: group findings by subject area or category. Works well when data comes from multiple sources or when you're covering several distinct topics in one report.
- Chronological: arrange findings along a timeline. Works when the sequence of events is itself part of the story.
- Order of significance: lead with the most important finding, then move to supporting or secondary data. Works when decision-makers need the headline fast.
For most business reports, a thematic structure is the clearest. It lets you group related data points, which reduces repetition and helps readers build an accurate mental model of what's going on.
Writing about data without losing the reader
Numbers alone don't communicate. A finding isn't "response rate: 62%." A finding is "62% of survey respondents reported delays of more than five working days." The number needs a subject, a verb, and a unit of measurement that means something to a non-specialist reader.
Write one finding per paragraph. State it in the first sentence. Follow with the supporting data, then stop. Don't pivot to interpretation. Don't add a moral. Just state the finding and move on.
Exact figures beat vague quantifiers in every case. "Fourteen of the 20 site managers flagged equipment availability as a constraint" is a finding. "Many managers raised concerns about equipment" is not. Precision is the minimum standard for a findings section.
If you're working with a large dataset, use tables or charts for the numbers and reserve the prose for what the numbers show at a high level. A paragraph that recites eight figures in sequence is hard to read and even harder to remember. Put the figures in a table, then write a sentence that gives the reader the single most important thing to notice about them. That's the finding.
Headings, labels, and visual structure
Every subsection of your findings needs a heading that describes what it contains. "Survey results" is a label. "Staff satisfaction scores by department, April 2026" is a heading. Readers scan before they read, and headings that tell them what to expect earn their attention faster.
Label every figure, table, and chart. Include a caption that explains what it shows, not just what it is. "Figure 2. Customer complaint volumes by category, Q1–Q2 2026" is better than "Figure 2. Customer complaints." The more information a label carries, the less work the surrounding prose has to do.
When you're proofreading, check every number twice. The findings section is where numerical errors cause the most damage. A wrong figure in an executive summary is embarrassing. A wrong figure in the findings section can change the entire meaning of a report. Our guide to proofreading numbers and data in business documents walks through a systematic method for catching errors before they reach the reader.
Common mistakes in findings sections
The most common error is editorialising. Phrases like "worryingly, only 30% of clients renewed" or "encouragingly, output increased" belong in the analysis section, not in findings. The findings section is where you report; let readers form their own initial reaction to the data.
The second most common mistake is omitting inconvenient findings. If your data produced a result that complicates your argument, it still goes in the findings section. A report that selectively reports is not a report. It's advocacy dressed up as analysis, and experienced readers will notice the gaps.
A third mistake is burying the most important finding at the end. Whatever you discovered that matters most to the reader's decision goes first or near the top. Don't make a senior reader work through 14 paragraphs to reach the point.
Connecting findings to the rest of the report
The findings section doesn't stand alone. It feeds the analysis section, which feeds the conclusions, which feed the recommendations. Every finding you include should connect to at least one conclusion or recommendation later in the document. If a finding doesn't connect to anything downstream, ask whether it belongs in the report at all.
A well-written report introduction sets up this chain clearly. If you've already told readers what question the report is answering, the findings section slots naturally into that frame. A strong report introduction makes the findings section easier to write and easier to read.
Before submitting any findings section, read it back as though you're the decision-maker who commissioned the report. Ask three things: do you understand what was found, do you trust the way it's presented, and do you know what comes next? If the answer to all three is yes, the section is doing its job.