The purpose of a technical report is to completely and clearly describe technical work, why it was done, results obtained and implications of those results. The technical report serves as a means of communicating the work to others and possibly providing useful information about that work at some later date. A well‐written report allows the reader to quickly understand what has been accomplished. The report also provides sufficient detail to allow the reader to recreate the results although the level of detail provided depends heavily on the report’s audience and any proprietary nature of the work. Clear presentation of results is at least as important as the results themselves; therefore, writing a report is an exercise in effective communication of technical information. Results, such as numerical values, designed systems or graphs by themselves are not very useful. To be meaningful to others, results must be supported by a written explanation describing how results were obtained and what significance they hold, or how a designed system actually functions. Although the person reading the report may have a technical background, the author should assume unfamiliarity with related theory and procedures. The author must therefore supply details that may appear obvious or unnecessary. With practice, the technical report writer learns which details to include. The key to a well‐written report is organization. A report that is divided into several sections, occurring in a logical sequence, makes it easy for the reader to quickly obtain an overview of the contents as well as locate specific information. This document provides guidelines for producing a well‐written technical report.