How to write a clear technical report (with structure and example)

A technical report exists so that someone who wasn't there (a client, a residents' association, a facilities manager) understands what was checked, what was found and what needs to happen next. If they have to read it twice to work that out, the report has failed, however thorough it is.

The good news is that almost every technical report, whether it covers a site visit, an inspection, an incident or an audit, follows the same structure.

The structure of a technical report

1. Header. Who issues it (company and logo), a unique reference and the date.
2. Title. Say what it is about: "Site visit report", "Incident report, production line 2". Avoid generic titles such as "Report".
3. Recipient. Who it is addressed to.
4. Key details. A box with the essentials: location, equipment or installation, date of the visit and the result. Someone who reads only this should get the point.
5. Purpose. Why the report was written, in one or two sentences.
6. Work carried out or findings. What was checked, how, and what was found. This is the longest part.
7. Conclusions and recommendations. What the findings mean and what needs to be done, with deadlines where they apply.
8. Signature. Name, job title and company of the person who signs it.

Appendices (photos, measurements, certificates) go at the end and are referred to in the text: "see photo 3".

An example

Section	Example
Title	Site visit report
Key details	1 High Street, London · Lift and booster pump · Satisfactory, with remarks
Purpose	Annual inspection of the shared equipment, requested by the residents' association.
Findings	The lift and the booster pump work correctly. Two emergency lights on the ground floor do not switch on.
Conclusions	Replace the two emergency lights within a month. No action needed on the rest.

In five lines, the reader knows what happened and what they need to do.

How to write it so it is understood

• Lead with the conclusion. Put the result in the key details and in the first paragraph of the conclusions. Busy readers won't go further.
• Separate facts from opinions. "The light does not switch on" is a fact; "the battery is probably flat" is a hypothesis, and should read like one.
• Be specific. "Pressure 2.1 bar, below the recommended 3 bar" informs; "low pressure" doesn't.
• Short sentences and numbered sections. They make it easy to refer to ("see section 3") and to reply point by point.
• One recommendation per point, with who should act and by when.
• Always use the same structure. If you write reports often, keep the same sections in the same order: your clients will know where to look.

Common mistakes

• Telling it in chronological order ("we arrived at 9, then…") instead of by topic. The reader cares about the outcome, not the timeline.
• Burying the problem in the fourth paragraph of the findings without mentioning it in the conclusions.
• Recommendations without a deadline or an owner: "it is recommended to review" says neither who nor when.
• Unexplained jargon when the reader is not technical.
• Forgetting the reference and the date: without them it is hard to cite the report or know which version is the latest.

Checklist before you send it

• Does the title say what it is about?
• Can the result be seen in the key details without reading anything else?
• Does every important finding have a conclusion or recommendation?
• Do the recommendations have an owner and a deadline?
• Does it have a reference, a date and a signature?

Make it for free as a PDF

With the free report generator you fill in the header, the key details and the sections (numbered, and you can reorder them), see the report as you type and save it as a PDF, even if it runs to several pages. No sign-up, and nothing leaves your browser.

And if you write the same kind of report again and again, Documentemplate turns it into a template: the fixed text stays, you fill in only what changes, sections about faults appear only when there are faults, and you can generate a whole batch of reports from a spreadsheet.