








Study with the several resources on Docsity
Earn points by helping other students or get them with a premium plan
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
ABSTRACT. This document specifies the recommended format to be used when submitting a formal technical report in a variety of disciplines and purposes.
Typology: Study notes
1 / 14
This page cannot be seen from the preview
Don't miss anything!









The pages of the report are to be assembled in the following order. This is the recommended order, however, certain reports may lend themselves to either reordering sections and/or excluding sections.
The format for this page may vary, however, the following information is always included: report title, who the report was prepared for, who the report was prepared by, and the date of submission. This is not a numbered page of the report.
An abstract is a concise description of the report including its purpose and most important results. An abstract must not be longer than half a page and must not contain figures or make reference to them. The results may be summarized in the abstract but qualitatively, not quantitatively. No specific technical jargon, abbreviations, or acronyms should be used. This is not a numbered page of the report.
Include all the report sections, subsections, and appendices. This is not a numbered page of the report.
Give the objective of the work, a brief description of the problem, and how it is to be attacked. This section should provide the reader with an overview of why the work was performed, how the work was performed, and the most interesting results. This can usually be accomplished with ease if the work has clearly stated objectives. After introducing the problem, indicate how those objectives are met. The length of this section depends on the purpose but the author should strive for brevity, clarity, and interest. Be careful not to use specific technical jargon or abbreviations such as using the term “oscope” instead of “oscilloscope”. Also, make sure to define any acronyms or abbreviations prior to using them. For example, in a surveying lab report a student might want to refer to the electronic distance measuring (EDM) device. The first time the device is referred to, the student must spell out what the acronym stands for before using the acronym as demonstrated in the previous sentence. This practice should be applied throughout the report when the author wants to use an acronym that has not yet been defined within the report. Do not assume that the reader is familiar with all the acronyms that are familiar to the author.
Include, if necessary, a discussion of relevant background theory. For example, if the phase shift of an RC circuit is to be measured, give the derivation of the theoretical phase shift. Include any preparation specified in the lab manual. In deciding what should or not should be included as background theory, consider presenting any material specific to the lab that you had to learn prior to performing the lab. This section may be divided into subsections if appropriate. Keep the discussion brief and refer the reader to outside sources of information where appropriate. The proper method of providing references and making citations within the report is provided in Appendix A.
Give the details of your design procedure. Be sure to introduce and describe your design work using sentences, equations alone are not sufficient. Use citations if you wish to refer the reader to reference material. Divide this section into subsections where appropriate. For example, a lab design may consist of designing several circuits that are subsequently interconnected; you may choose to treat each circuit design in its own subsection. Keep this section as general as possible, only applying specific numbers after the design is explained. If there is no design but strictly analysis, then provide the important details of all the analysis performed. Be brief. It is not necessary to show every step; sentences can be used to describe the intermediate steps. Furthermore, if there are many steps to the analysis, the reader should be directed to the appendix for complete details.
This section varies depending on requirements of the one who assigned the work and the audience. At a minimum, the author discusses the procedure by describing the method used to test a theory, verify a design or conduct a process. Presentation of the procedure may vary significantly for different fields and different audiences, however, for all fields, the author should BE BRIEF and get to the point. Like with any written work, if it is unnecessarily wordy, the reader becomes bored and the author no longer has an audience. Also, the procedure section should never include specific measurements/results, discussion of results, or explanation of possible error sources. Make sure all diagrams provided are numbered, titled, and clearly labeled. Depending on the situation, there are two likely types of procedure sections. In one case, a detailed procedure may have already been supplied or perhaps it is not desirable to provide a detailed description due to proprietary work. In another case, it might be the author’s job to provide all the detail so the work can be duplicated. The latter is more common in academic lab settings. The writing guidelines for each of these possible procedure sections are provided below.
Use this procedure type if you have been supplied with a detailed procedure describing the steps required to complete the work.
Present the results of the work performed using neatly organized and completely labeled tables and/or graphs whenever possible. When comparative data is available, present the data in a way that facilitates the comparison. For example, if theoretical and experimental values are available, present the values alongside one another accompanied by percent error. If it would help the reader understand the results, include a few sample calculations but put lengthy calculations in an appendix. ALWAYS accompany results with a meaningful discussion. The discussion explains what the results mean and points out trends. In some cases, the results speak mostly for themselves and the discussion may be brief, i.e., “Table 2 shows that the designed variable modulus counter works as expected”. In other cases, the meaning of the results may not be as clear requiring more detailed discussion. ALWAYS discuss the possible sources of error and how accurate the results need to be in order to be meaningful. Do not include a discussion of possible sources of error that would not add significantly to the observed error. What counts as significant depends on the situation. For example, if the components used have a tolerance of 5% and the accuracy of the equipment is within 0.1% of the measured value, then the equipment does not add any significant error. In general, it is impossible to obtain error‐free results, however, attention to detail when conducting procedures should minimize the error. Errors are different from mistakes. It is unacceptable to report mistakes. If a mistake was made in the work, the work must be repeated until acceptable tolerances are achieved before submitting a report. When working in the industry, it is imperative to know how accurate the results need to be. It is worth your time and effort (and in the best interest of your boss or client) to provide the appropriate level of accuracy. If that means repetitive measurements to check for accuracy within tolerance, then do it. If it means performing a detailed analysis prior to making measurements, then do it. In the academic setting, the result of laziness or lack of effort may only be a bad grade. In the workplace, you may get fired! Other information pertaining to writing the Results and Discussion section can be found in Appendix B. This information includes
In this final section of the body of the report, the author should briefly bring everything together. It is similar to the abstract except that now the results are concluded upon in a quantitative way. Therefore, the conclusion should be a concise description of the report including its purpose and most important results providing specific quantitative information. The conclusion should not contain figures or make reference to them. As with the abstract, the reader should be able to read this section on its own which means that there should be no specific technical jargon, abbreviations, or acronyms used.
List all works cited in the report, include all the important bibliographical information. The Works Cited should begin on a new page, not on the same page with the conclusion. Refer to Appendix A for information on preparing the Works Cited section.
This section may not always be present. Materials included in an appendix may include lab sheets, parts list, diagrams, extensive calculations, error analyses, and lengthy computer programs. Introduce numbered appendices rather than putting different items in one appendix.
For obvious reasons, the reader will first read the title page and abstract. Therefore, it is imperative that the abstract be clear and well written. It should tease the reader into looking further into the paper. The conclusion is often the next section to be read. All valuable readers, politically speaking, will jump directly to the conclusion making it important to provide a table of contents to ease document navigation. If the conclusion, relative to the title page, sounds interesting and conclusive they will read the other sections to learn more. The introduction is read next. It should provide the reader with enough information about how the report progresses so that the reader can pick and choose which sections are most applicable to their interests. Based on this, some or all of the subsequent sections may be read. In light of understanding how a technical report is read, there are several general guidelines to consider:
Technical Report Writing Guidelines provides a recipe for writing technical reports for a variety of disciplines and applications. If all of the information contained herein is studied and applied, the result will be a report worth reading. Considering that most technical jobs require accurate communication through written material, developing good technical writing skills can only improve your career status. Be aware that most jobs in a technical field require a significant amount of technical writing, from informal memos to formal proposals for presentation to customers. It is worth your time to read this material carefully and practice your writing skills.
A tremendous amount of information on proper citing of references in reports as well as how to cite the reference within the body of a report is provided by the College’s Library (see website at http://libraryreference.sunydutchess.edu/citations.htm). For technical reports, the American Psychological Association (APA) method or a modified version as explained below is most often used. For your convenience, this information is provided here, however, it is worth reviewing the website because other valuable resources are provided that facilitate bibliography creation. For technical reports, a modified APA method is often used. Using the APA method, a reference is cited in the body of the report using a “parenthetical citation”. Within the parenthesis, a lot of information is supplied including the author, the publication date, and the page number. If no author is provided, then the title of the referenced work is included. With this technique, a parenthetical citation referencing the information cited here would be ( Creating Parenthetical Citations and Reference List Pages Using APA Format , 2008). In technical reports, an abbreviated method is often used where the reference is identified by the numbered list in the Works Cited section. Using this abbreviated notation, the reference would be just [3]. Square brackets must be used. After the conclusion of a report, if outside sources of information were used a numbered list of the references is provided in the order cited within the paper. Examples of bibliographic information for periodicals and books can be found in [1] and for full text electronic databases and web sites in [2]. The details of how a citation should be written are copied from [1] and [2] here for your convenience. Also provided here is the classic method of providing a parenthetical citation using the APA method [3] in case you opt for that technique rather than the modified method described above.
When citing an article in a periodical, you must include:
When citing a book, you must include:
When citing an article from a full text database, you must include:
When citing information that was retrieved from a website, you must include:
Parenthetical citations are used to identify the sources you used in writing your paper. These citations appear in an abbreviated form within the text of your paper and lead a reader to the full citations in your Works Cited Page. The standard rule for parenthetical text citations is to include:
Always refer to graphs and tables when discussing results. Construct graphs using the following guidelines:
The list provided below supplies guidelines for answering technical questions as opposed to writing a formal technical report.