The results section of a business report is where writers most commonly mix up two jobs: reporting what happened and explaining what it means. Those are different tasks. The results section handles the first one only. If you let interpretation creep in here, you undermine the section that follows, the discussion section, which is where analysis belongs.
Get the results section right and the rest of the report flows from it. Get it wrong and every downstream section inherits the problem.
What the results section is actually for
The results section presents your findings without commentary. It answers the question: what did you find? Not what does it mean, not what should the organisation do about it. Those answers live elsewhere.
This distinction matters because readers at different levels of seniority stop reading at different points. A finance director may read the executive summary and skim the results. A project lead may read results closely and skip the appendix. The results section carries the data for every reader, so it needs to be self-contained and trustworthy on its own terms.
Three things belong in a results section: the data, any directly observable patterns in that data, and the conditions under which the data was collected. Three things do not belong: causes, judgements, and recommendations.
How to organise the content
Structure your results to match the order in which you posed your research questions or objectives. If your problem statement asked three questions, your results section should answer them in the same sequence. Readers follow along more easily when the shape of the results mirrors the shape of the question.
Within each finding, present the most significant result first. Business readers scan. Putting the headline number at the end of a paragraph is a habit left over from academic writing, where the convention is different. Flip it: state the finding, then support it with detail.
Use subheadings. A results section covering multiple data streams is hard to navigate without them. Each subheading should state what that block of results is about, not how you feel about it.
- Good: "Customer satisfaction scores by region, Q1–Q3 2026"
- Weak: "Concerning trends in customer satisfaction"
The second version has already editorialised. Save that for the discussion.
Presenting numbers accurately
Numbers in a results section need three things: precision, consistency, and context. Precision means reporting the number you actually have, not rounding aggressively to make it look cleaner. Consistency means using the same unit throughout, so you don't mix percentages with absolute counts in the same paragraph. Context means giving the reader enough information to understand what the number is relative to.
"47 respondents agreed" means nothing without knowing the total sample size. "47 of 212 respondents (22%) agreed" is a result. Write the second form every time.
Tables and charts belong in the results section when the data is too dense to read in prose. A single figure or percentage fits in a sentence. Five figures across three variables need a table. The rule: if reading the numbers out loud in a sentence forces the reader to hold more than three values in memory at once, put them in a table instead. If you're writing a data visualisation element, the guidance at how to write a business report data visualisation section covers how to match chart type to data type.
Common mistakes that undermine results sections
The most frequent error is editorialising. Phrases like "worryingly, the data showed" or "encouragingly, sales increased" belong in the discussion. The results section reports. It does not react.
The second most common mistake is omitting negative or inconclusive findings. If the data showed no significant difference, that is a result. Report it. Leaving it out creates a misleading picture and, in many professional contexts, an integrity problem. Readers with access to the raw data will notice.
A third mistake is confusing results with methods. "We surveyed 150 employees using an online questionnaire" is a methods statement. "63% of employees rated internal communication as poor" is a result. If you find yourself writing about how you gathered the data while trying to report what it showed, stop and move the procedural content back to the methods section.
Finally, watch the verb tense. Results sections are conventionally written in the past tense because the data collection is finished. "Sales declined 14% in Q2" is correct. "Sales decline 14% in Q2" is not.
Keeping results distinct from conclusions
The clearest test for whether a sentence belongs in the results section is to ask: does this sentence require any judgement on my part? If you had to interpret, infer, or evaluate to write it, it belongs in the discussion or conclusions sections instead. If you simply read it off the data, it belongs here.
"Turnover in the sales team was 34% over twelve months" is a result. It requires no interpretation. "High turnover in the sales team reflects weak management" requires interpretation. That's a discussion or conclusions statement.
Some writers find it helpful to draft the results section immediately after completing data collection, before they've had time to form strong opinions about what it means. That distance reduces the temptation to collapse findings and analysis into one muddled section.
A well-written results section doesn't feel like a conclusion. It feels like evidence. The reader should finish it knowing exactly what the data says and not yet knowing what you think about it. That gap is what makes the rest of the report worth reading.