A technical report is a particular type of document used by scientists and engineers to perform a very specific job. It communicates to the reader information about the work that has been done; presenting the findings and helping the reader to understand the implications of the results in context.
A technical engineering report should be written as an independent record that can be read and understood by the reader, without any further explanation from the author. It stands as a comprehensive record of exactly how the work was done and what results were obtained.
A report should include every important piece of information associated with the work conducted. This will include things such as:
Almost all technical engineering reports follow this ‘storytelling’ format; the narrative being a logical and linear delivery of information about the work that was conducted, which has a beginning, middle and end.
The scene is set at the start, followed by the story of what happened. The ending provides the author with the opportunity to consider the impact and significance of what has happened and to consider, “what’s next?”. There are also a number of sections that appear after the report to provide extra information for the reader.
Over time, standard sections and conventions have become established to present and organise information contained within these documents.
Readers of technical engineering reports have come to expect certain information in these sections, so for the sake of clearly communicating the work, it is important to use these sections correctly.
On the next step, we’ll define what these sections are and look at the content, style and presentation that each requires.