Engineering Writing: Technical Reports and IEEE Referencing

Engineering writing aims for one thing above all: a reader should be able to understand, check and act on your work without asking you a question. Technical reports, lab reports and design documents all follow from that goal.

This guide covers the standard report structure, the style conventions engineering markers expect, how to present units, equations, figures and tables, and how IEEE referencing fits in.

Common Engineering Writing Tasks

Technical Report Structure

Most engineering reports use a variation of this structure. Your module guide or company template may rename or merge sections.

1. Title page: title, author, student number or role, module or client, date.
2. Summary or abstract: purpose, method, key results and main recommendation on one page or less.
3. Contents, and lists of figures and tables for longer reports.
4. Introduction: background, the problem, aims and objectives, scope.
5. Theory or background: the principles and previous work your approach builds on.
6. Method or design: equipment, procedure, models or design process.
7. Results: data, presented in tables and figures with brief commentary.
8. Discussion: interpretation, comparison with theory, sources of error, limitations.
9. Conclusions: what the work found, tied to the objectives.
10. Recommendations: what should be done next, if the brief asks for it.
11. References: IEEE or your department's style.
12. Appendices: raw data, code, calculations and drawings.

The Executive Summary

Many readers read only the summary. Write it last, make it stand alone, and include actual numbers and the main recommendation rather than promising them.

The figures are illustrative.

Technical Style Conventions

• Precision: "the voltage fell by 0.4 V" rather than "the voltage dropped slightly".
• Concision: short sentences, one idea each; cut phrases like "it can be seen that".
• Voice: passive voice remains common in methods, but active voice is clearer elsewhere; follow your department's preference.
• Tense: past tense for what you did and found; present tense for facts and for what your figures show.
• Uncertainty: state measurement uncertainty and tolerances rather than implying perfect accuracy.
• Defined terms: define abbreviations at first use and keep terminology consistent.

Numbers and Units

Units are where engineering reports most often lose easy marks. Follow SI conventions unless your module states otherwise.

Equations, Figures and Tables

Equations

Treat equations as part of the sentence, with punctuation, and number displayed equations in round brackets at the right margin. Define every symbol immediately after the equation where it first appears.

Figures and Tables

• Number figures and tables separately, in the order they are mentioned.
• In IEEE-style documents, figure captions go below the figure and table titles above the table.
• Label axes with the quantity and unit, such as "Temperature (°C)".
• Refer to every figure and table in the text and say what the reader should notice.
• Cite the source in the caption for any figure you reproduce or adapt.

Appendices and Code

Move detail that interrupts the main argument into appendices: raw data tables, full calculations, long code listings and detailed drawings.

Label each appendix with a letter and title, list it in the contents and refer to it in the text, such as "the full calibration data are in Appendix B". Keep short, essential code fragments in the body only when the reader needs them to follow your method. An assessor should never need an appendix to understand your conclusions.

Writing a Strong Discussion

The discussion is where engineering judgement shows. Markers want to see that you understand what your results mean, not just that you produced them.

• Compare results with theory, simulation or specifications, and quantify the difference.
• Explain discrepancies with specific causes, such as instrument tolerance or simplifying assumptions.
• Distinguish random error from systematic error.
• State the limitations of your method and how they affect your conclusions.
• Link findings to the objectives set in the introduction.

IEEE Referencing in Engineering Reports

Most engineering departments use IEEE style: numbered citations in square brackets, listed in order of first citation.

• Cite with [1], placed inside the sentence before punctuation.
• Reuse a source's number each time you cite it.
• List references numerically, with initials before surnames and abbreviated journal titles.

The examples are illustrative. Datasheets, standards and software documentation are common engineering sources; cite each by type. The free Bibloq citation generator formats IEEE references from a DOI or URL.

Engineering Report Checklist

• Summary stands alone and includes real numbers.
• Aims and objectives stated in the introduction and answered in the conclusions.
• Method detailed enough to repeat.
• Every number has a unit and sensible precision.
• Equations numbered and symbols defined.
• Figures and tables numbered, captioned and referred to in the text.
• Discussion explains discrepancies and limitations.
• References numbered in order of first citation.

Common Engineering Writing Mistakes

• Presenting results with no commentary, leaving the reader to interpret them.
• Missing or inconsistent units.
• Figures pasted from software without labelled axes.
• Conclusions that introduce new results.
• Reference list ordered alphabetically instead of by citation number.
• Copying procedure text from the lab sheet instead of describing what you actually did.

How Bibloq Helps with Engineering Writing

Send your brief, rubric and any data, calculations or design notes. A writer with an engineering background prepares a custom technical report, lab report or design report for study and reference, with clear structure, correct units and IEEE referencing.

We never invent data or test results; reports are built only on what you provide. Editors can also review your own draft for clarity, figures and references. Free revisions within the scope of your original request are included.