A technical report must enlighten readers on the subject matter being reported's reasons, methods, findings, and conclusions. A report split into sections that occur in a logical sequence allows the reader to rapidly gain an overview of the contents as well as identify particular information. This, in turn, helps them decide what further information is needed and where to find it. Following a technical structure ensures that your reader will not only understand the material but will also be able to repeat or reference back to specific points within the text. This is particularly important when submitting your work for peer review or presenting it at conferences or meetings. Technical reports are often read by people other than the writer so it is essential that you make sure that they can easily locate any particular point within the text. The most common technical structures are: title page (including abstract), introduction, body paragraphs (including figures and tables), conclusion. There are many more ways to divide up a report into relevant sections; however, these are some of the most effective. It is important to note that the technical structure described here is merely a guideline and does not necessarily have to be followed in its entirety. For example, you may choose to start each new section with a heading if this seems like the best way to organize your thoughts. However, it is recommended that you first try writing without section headings to get a feel for how the piece is progressing before making any changes.