The conclusions section of a business report is the section most writers get wrong in exactly the same way: they paste a summary of the findings and call it done. A summary tells the reader what happened. A conclusion tells the reader what it means. Those are different documents, and readers notice when you've written the wrong one.
What a conclusions section actually does
A conclusions section takes the evidence from your findings and draws reasoned, specific inferences from it. It answers the question the report was built to answer. If the report asked "should we consolidate our Sydney and Melbourne warehouses?" the conclusions section answers yes or no, and says why the data supports that answer.
It doesn't introduce new data. It doesn't repeat the methods. And it doesn't hedge every statement with language like "it may be possible that" or "the results could suggest." By the time a reader reaches the conclusions section, they've read the evidence. They want the call.
This is distinct from the recommendations section, which comes after. Conclusions say what the evidence means. Recommendations say what to do next. Keep them separate. A conclusion that slides into "therefore, the company should immediately reorganise its logistics team" has crossed the line. Save that sentence for the next section.
Common mistakes writers make here
Three patterns account for almost every weak conclusions section:
- The echo chamber. The writer restates each finding in slightly different words. This wastes a reader's time and signals that the analyst hasn't actually thought about what the data means.
- The hedge pile. Phrases like "the data suggests," "it appears likely," and "there may be some evidence" stack up until the section says nothing assertable at all. Draw the conclusion or don't write it.
- The scope creep. New information appears that wasn't in the findings section. Readers rightly distrust a conclusion built on evidence they haven't been shown. If a fact matters to the conclusion, it belongs in the findings first.
The findings section of a business report is where you present data. The conclusions section is where you interpret it. Each section has one job. Don't let them bleed into each other.
How to structure the section
Keep it short. A conclusions section for a 10-page report rarely needs more than a page. A 30-page report might justify two. Start with the main conclusion, the single most important inference the data supports. Then work through secondary conclusions in descending order of significance.
Use the same numbering or heading style as the rest of the report. If your findings were numbered 1 through 5, your conclusions can mirror that structure so readers can cross-reference easily. This isn't mandatory, but it helps reviewers who will flip back and forth between sections.
Each conclusion should state a specific claim, not a category. "Customer satisfaction fell in Q2" is a finding. "The Q2 drop in customer satisfaction correlates with the rollout of the self-service portal and not with pricing changes" is a conclusion. One interprets the other.
Sentence-level writing for conclusions
Write in the active voice. "The audit revealed three instances of duplicate billing" is far clearer than "three instances of duplicate billing were revealed by the audit." The subject acts; it doesn't receive action.
Be specific about scope. Don't write "results were mixed." Write "satisfaction scores improved in three of four regions; the Northern region declined by 11 percent." A number beats a qualifier every time. If you don't have a precise figure, use the closest real one you do have.
Short sentences help. After paragraphs of methods and data, a four-word sentence lands hard. Use that rhythm deliberately. State the conclusion. Explain the evidence behind it. Move on.
Avoid the phrase "in conclusion." Your heading already tells the reader where they are. Starting the section with "In conclusion, this report has shown that..." burns the reader's patience before you've said anything. Cut the preamble and start with the claim.
Connecting conclusions to the rest of the report
The conclusions section should feel like the logical endpoint of everything that came before it. A well-structured business report makes that feel inevitable: the introduction asked a question, the methods described how you investigated it, the findings presented the evidence, and the conclusions answer the question.
If the conclusions section surprises the reader, something earlier in the report has failed. Either the findings didn't fully present the relevant evidence, or the conclusions have strayed beyond what the evidence actually supports. Read the conclusions against the findings before you submit. Every claim in the conclusions section needs a clear anchor in the findings.
If your report includes an executive summary at the front, the conclusions you write here should be consistent with it. Decision-makers often read the executive summary and the conclusions section and skip the rest. Those two sections need to agree on what the report found. For guidance on writing that front-of-document summary, see how to write better executive summaries.
A practical checklist before you submit
Before you hand the report over, run through these four checks on the conclusions section:
- Does every conclusion trace directly to evidence in the findings section?
- Have you avoided introducing any new data or examples?
- Is every conclusion stated as a specific claim rather than a category or a hedge?
- Does the section answer the original question the report was commissioned to address?
If the answer to any of those is no, revise before you send. A weak conclusions section doesn't just disappoint at the end. It retroactively undermines the effort that went into everything before it. Get it right and the whole report holds together.