A technical report presents the method, results and conclusions of a piece of technical work so that a busy reader can act on it. It is organized for scanning: numbered sections, a summary at the front and figures that carry the evidence.
This page covers the standard structure, how to write each part, how to present data, and the difference between conclusions and recommendations. It ends with an example summary and a pre-submission checklist.
The Standard Sections of a Technical Report
A typical technical report has a title page, a summary, a contents list, an introduction, the method or theory, results, discussion, conclusions, recommendations, references and appendices. Sections are numbered (1, 1.1, 1.2) so readers can jump straight to what they need.
Always check your brief or company template first, as section names and order vary.
Purpose and Audience First
Before writing, decide who will read the report and what they must do with it. A manager deciding whether to fund a redesign needs the summary and recommendations; an engineer checking your work needs the method and data.
Write so both can find what they need quickly. That means a front-loaded summary, informative headings and appendices for detail that only specialists will read.
Standard Structure
| Section | What it contains |
|---|---|
| Title page | Title, author, date, course or client, report number |
| Summary | Purpose, method, key results with numbers, main conclusion and recommendation |
| Contents | Numbered sections, plus lists of figures and tables |
| Introduction | Background, problem, aims and scope |
| Theory or method | Equations, equipment, procedure or model, enough to repeat the work |
| Results | Data in figures and tables, with brief description |
| Discussion | Interpretation, comparison with theory or targets, sources of error |
| Conclusions | What the results show, matched to the aims |
| Recommendations | Specific actions that follow from the conclusions |
| References and appendices | Cited sources, raw data, calculations, code |
Writing the Summary
The summary (often called an executive summary or abstract) is the most-read part of the report. Write it last, keep it to about 150 to 300 words for coursework, and make it stand alone.
- One sentence on the purpose or problem.
- One or two sentences on what you did.
- The key results, with numbers and units.
- The main conclusion.
- The main recommendation.
Example summary. This report assesses whether the existing cooling fan can keep the control enclosure below its 45 °C limit at the planned higher load. The enclosure was tested at three heat loads (50, 100 and 150 W) with ambient air at 25 °C, and internal temperatures were logged until steady state. At 150 W the internal temperature reached 52 °C, exceeding the limit by 7 °C, while 100 W gave 41 °C. The current fan is therefore adequate only up to about 110 W. It is recommended that the fan be replaced with one rated for at least twice the present airflow and that the test be repeated at 150 W before the upgrade is approved.
Values are illustrative.
Presenting Data
Figures and tables carry the evidence in a technical report. The text should point the reader to them and say what to notice, not repeat every number.
- Number figures and tables separately and refer to each one in the text before it appears.
- Put figure captions below figures and table titles above tables, unless your style guide says otherwise.
- Label every axis with the quantity and unit, such as "Temperature (°C)".
- Show uncertainty with error bars or stated tolerances where it matters.
- Use SI units throughout, with a space between number and unit (25 °C, 150 W).
Move long tables of raw data to an appendix and keep a summary table in the results.
Conclusions Versus Recommendations
These two sections are often confused, and markers notice. Conclusions state what you found; recommendations state what should be done about it.
| Conclusions | Recommendations |
|---|---|
| Follow directly from the results | Follow from the conclusions |
| Written in the past or present tense | Written as actions, often with "should" |
| Introduce no new data | Are specific and feasible |
| Example: the fan is adequate up to about 110 W | Example: replace the fan before the load rises above 110 W |
Number both lists so each recommendation can be traced back to the conclusion that supports it.
Style for Technical Writing
- Be precise: "the shaft deflected 2.4 mm" rather than "the shaft deflected significantly".
- Be concise: one idea per sentence where possible, short paragraphs and lists for steps.
- Be consistent: the same term, symbol and unit for the same thing throughout.
- Use the right voice: passive voice is common in methods ("the sample was heated"), but active voice is clearer elsewhere. Follow your department's preference.
- Define symbols: explain every symbol the first time it appears, or use a nomenclature list.
Pre-Submission Checklist
- The summary stands alone and includes numbers, a conclusion and a recommendation.
- Sections are numbered and match the contents list.
- Every figure and table is numbered, captioned and referred to in the text.
- Units are SI and consistent, with symbols defined.
- Conclusions match the aims and introduce no new data.
- Recommendations are specific and supported by conclusions.
- References follow one style, such as IEEE or Harvard.
- Appendices are labeled and referred to in the main text.
How STEM Donkey Helps with Technical Reports
Send your brief, data, any template, the citation style and the rubric. Deadlines run from 3 hours to 20 days.
An engineering or science writer prepares a custom technical report written from scratch, with a clear summary, labeled figures, correct units and evidence-based conclusions. It is plagiarism-checked and meant for study and reference. We never invent or alter data.
Choose a Standard, Master or Elite writer, see the price before you pay, and get free revisions within the scope of your original request. Your identity is never shared with the writer.
Want a Report That Reads Like a Professional's?
Send your brief, data and template. You get a custom technical report with a clear summary, labeled figures and evidence-based conclusions.
Order Your Technical ReportFree revisions · Full refund if late · Written from scratch for your order
Frequently Asked Questions
A lab report records an experiment for assessment, usually following a fixed academic format. A technical report is written for a reader who needs to make a decision, so it puts the summary and recommendations up front.
Follow your brief. Coursework reports often run 2,000 to 5,000 words plus appendices.
Many departments prefer impersonal language, but some accept "we" in the method. Check your brief or template.
IEEE is common in engineering and computing; Harvard and APA are common elsewhere. Use the style your course specifies.
Raw data, long derivations, sample calculations, code and supporting drawings. Anything the main argument does not need but a checker might.
Most technical reports have both. If your brief asks only for conclusions, put any suggested actions there clearly labeled as next steps.