What is Report Writing? Types, Structure, and Examples

What is Report Writing?

Report writing is the practice of presenting information, findings, and recommendations in a structured, factual document written for a specific reader and a specific decision. A report is not an essay. An essay argues a position; a report presents evidence and, usually, tells the reader what to do about it.

The distinguishing features are structure and purpose. A report is organized into labeled sections so a reader can go straight to the part they need, and it exists because someone has to make a decision, approve something, or understand what happened.

What separates a report from other writing

The difference is easiest to see by comparison.

ReportEssayEmail

PurposeInform a decisionArgue a positionCommunicate quicklyStructureLabeled sections, numberedContinuous proseLooseReading patternNavigated and skimmedRead start to finishRead onceToneObjective, factualAnalytical, persuasiveConversationalContains recommendationsUsuallyRarelySometimesFindings and interpretationKept separateInterwovenNot distinguished

That last row is the one most people get wrong. In a report, what you found and what you think it means belong in different places. Mixing them makes it impossible for a reader to disagree with your interpretation while still trusting your evidence — and that is precisely what a decision-maker needs to be able to do.

Why report writing matters at work

Reports are how organizations make decisions they can defend later. A budget gets approved, a supplier gets chosen, an incident gets addressed, a project gets stopped — and in each case there is usually a document behind it that someone will look at again if the decision is questioned.

This has a practical consequence for how you write. Your report may be read by someone who was not in the room, months after the fact, looking for the reasoning. If it only makes sense to people already familiar with the situation, it has failed at the job it will be judged on.

The other reason it matters: reports are read by senior people, and they are frequently the only sustained piece of your thinking that those people ever see. Whether that is fair is beside the point.

Types of reports

Informational reports present facts without interpretation — progress updates, monthly figures, attendance records. The reader wants to know the state of things.

Analytical reports present findings and interpret them. Most business reports are analytical: here is what we found, here is what it means, here is what we suggest.

Research reports document an investigation — methodology, data, results, conclusions. Standard in academic and scientific settings, and in market research.

Technical reports document how something works, was built, or failed. Written for a reader with specialist knowledge, and unusually dependent on precision.

Feasibility reports assess whether a proposed course of action is viable, usually across cost, time, capability, and risk.

Incident reports record what happened, when, who was involved, and what was done. Often used in a formal or legal process afterward, which makes factual accuracy and separation of fact from opinion critical.

Progress and status reports track a project against its plan. Routine, easy to write badly, and most useful when they are honest about problems rather than reassuring.

Annual reports summarize a year’s performance for external readers — shareholders, regulators, funders, the public.

Audit and compliance reports assess whether something meets a required standard, and state findings against defined criteria.

Recommendation reports compare options and argue for one. Closely related to feasibility reports, but with a decision attached.

Most real reports blend types. A feasibility report contains informational and analytical sections. The point of knowing the categories is that each implies a different emphasis — an incident report needs precision about facts, a recommendation report needs a defensible comparison of options.

The standard report structure

Not every report needs every section. Short internal reports may need only four or five. Use this as a checklist rather than a template.

Title page. Title, author, date, and who it is for. The title should say what the report is about, not be clever — “Q3 Warehouse Staffing Review” beats “Meeting the Challenge.”

Executive summary. The most important section, and the one most often written badly. It should state the purpose, the key findings, and the recommendations — in full, not as a teaser. Many readers will read only this, and that is a legitimate use of a report, not laziness on their part.

Write it last, even though it appears first. And do not treat it as an introduction: an introduction sets up what is coming, a summary delivers the conclusions.

Table of contents. For anything over about ten pages. Generate it automatically from heading styles rather than typing it, so it survives revision.

Introduction. Why the report exists, what it covers, what it deliberately does not cover, and who commissioned it. That third item saves more arguments than any other sentence in a report.

Methodology. How you gathered your information — what data, over what period, from where, and with what limitations. Include this whenever your findings could reasonably be challenged. A reader who cannot see how you know something has no reason to accept it.

Findings. What you found, presented without interpretation. Use tables and charts where they carry the information better than prose. Organize by theme rather than by the order in which you discovered things.

Analysis or discussion. What the findings mean. Patterns, causes, implications. This is where interpretation belongs.

Conclusions. What follows from the analysis. Conclusions are not recommendations — a conclusion says “demand is growing faster than capacity,” a recommendation says “add a second shift by March.”

Recommendations. What should happen, specifically. Vague recommendations are the most common failure in workplace reports. “Improve communication” is not actionable. “Introduce a weekly written handover between shift leads, from 1 November” is.

Where possible, say who should do each thing, by when, and what it costs.

References. Sources, in a consistent citation style.

Appendices. Detail that supports the report but would interrupt it — raw data, full survey instruments, technical specifications, correspondence. If a reader does not need it to follow your argument, it belongs here.

How to write a report: a working process

1. Establish the brief before writing anything. Who is the reader? What decision does this inform? What is in and out of scope? How long should it be, and when is it needed? Is there a required format? Getting this wrong is the single biggest cause of wasted effort — a report aimed at the wrong reader cannot be fixed by editing.

2. Gather your material. Collect more than you will use, and keep a record of where each piece came from as you go. Reconstructing sources afterward is miserable.

3. Decide the recommendation before you write. This sounds backwards but it is not. If you do not know what you are going to recommend, you do not yet know what your report is for, and you will write a tour of your research rather than a case for a decision. The recommendation may change as you draft — that is fine. Starting without a view is not.

4. Outline the structure. Set out the sections and note what goes in each. Check the sequence makes sense to someone who knows nothing about the subject.

5. Draft the middle first. Findings and analysis. Leave the executive summary until the end, because you cannot summarize an argument you have not yet made.

6. Write the executive summary and recommendations last. By this point you know what you are actually saying.

7. Edit for the reader, not for yourself. Cut anything that does not serve the decision. Reports get longer with each revision unless someone actively resists it, and length is not a sign of thoroughness.

8. Check the numbers. Every figure, total, percentage, and date. A single wrong number undermines the credibility of everything around it, and a reader who catches one will start checking the rest.

What makes a report good

It is written for its actual reader. A report for a finance director and a report for a technical team are different documents even with the same findings. Adjust the vocabulary, the level of detail, and what you can assume is already known.

Fact and opinion are visibly separate. The reader should always be able to tell which is which.

It is navigable. Clear headings, numbered sections, a contents page when long enough. Assume the reader is skimming, because they are.

It is specific. Numbers rather than “significantly.” Dates rather than “soon.” Named owners rather than “the team.”

It acknowledges limitations. A report that admits what it does not know is more credible than one that appears certain about everything. Stating a limitation also protects you when someone later asks why a factor was not considered.

It is honest about bad news. Progress reports that conceal problems until they are unfixable are worse than useless. Reporting a problem early is the entire value of reporting.

It is proportionate. A two-page report that answers the question beats a thirty-page one that buries it.

Common mistakes

1. No executive summary, or one that teases rather than tells. If a busy reader has to read the whole document to find your conclusion, most will not.
2. Findings and opinion blended together, so the reader cannot separate evidence from interpretation.
3. Vague recommendations that nobody can act on or be held to.
4. Padding — background nobody asked for, methodology described at length for a routine exercise, restating the same point in three sections.
5. Undefined jargon and acronyms. Spell out every acronym at first use. Reports circulate beyond their original audience.
6. Charts that do not earn their space. A chart should make something clearer than the sentence it replaces.
7. Inconsistent formatting, which reads as carelessness and makes a reader wonder what else was careless.
8. No proofread. Errors in a document about rigor undermine the claim to rigor.

A pre-submission checklist

1. Does the executive summary state the conclusions, not just the topic?
2. Could someone read only the summary and act correctly?
3. Are all recommendations specific, with an owner and a timeframe?
4. Is every number checked?
5. Is every acronym defined at first use?
6. Is there anything here the reader does not need?
7. Are findings separated from interpretation?
8. Are limitations stated?
9. Is the formatting consistent throughout?
10. Has someone else read it?

That last one is worth more than the other nine. A reader unfamiliar with the work will find the gaps you cannot see.

Word’s structural features — heading styles, automatic tables of contents, cross-references, tracked changes — exist largely to support exactly this kind of document. Our guide to Microsoft Word covers them. Reports are also a form of workplace communication, and the broader skills carry across: see our guide to digital communication.

Frequently asked questions

What is report writing in simple words? Presenting information and findings in a structured document, organized into sections, written for a particular reader and usually to support a decision.

What are the main types of reports? Informational, analytical, research, technical, feasibility, incident, progress, annual, audit and compliance, and recommendation reports. Most real reports combine more than one.

What is the standard format of a report? Title page, executive summary, contents, introduction, methodology, findings, analysis, conclusions, recommendations, references, and appendices. Short reports may use only a handful of these.

What is the difference between a report and an essay? An essay argues a position in continuous prose and is read from beginning to end. A report presents findings in labeled sections, is navigated rather than read straight through, keeps evidence separate from interpretation, and usually ends with recommendations.

What is the difference between conclusions and recommendations? Conclusions state what follows from your findings. Recommendations state what should be done about it. “Demand is outgrowing capacity” is a conclusion; “add a second shift from March” is a recommendation.

How long should a report be? As long as the decision requires and no longer. A two-page report that answers the question is better than thirty pages that bury it. If a length has been specified, treat it as a constraint to work within.

What should an executive summary contain? The purpose, the key findings, and the recommendations — stated in full. Write it last. It should stand alone, because many readers will read nothing else.

Should I write a report in the first person? Conventionally reports avoid the first person in favor of neutral phrasing, and most organizations still expect this. Practice varies, so follow your organization’s house style if it has one.

How do I make my report recommendations stronger? Be specific. Name what should happen, who should do it, by when, and what it will cost. Tie each recommendation to a finding so the reader can see the reasoning.

What is the most common mistake in report writing? Writing for yourself rather than the reader. It shows up as no executive summary, unnecessary background, vague recommendations, and undefined jargon. Every one of those costs the reader effort that should have been yours.