0% found this document useful (0 votes)
15 views4 pages

Format Guide For Technical Reports Ups

The document provides a guide for formatting technical reports with sections on the summary, abstract, introduction, theoretical background, experimental procedure, results, discussion, conclusions, references, and appendices. It details the content and organization that should be included in each section.

Uploaded by

fryki076
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
15 views4 pages

Format Guide For Technical Reports Ups

The document provides a guide for formatting technical reports with sections on the summary, abstract, introduction, theoretical background, experimental procedure, results, discussion, conclusions, references, and appendices. It details the content and organization that should be included in each section.

Uploaded by

fryki076
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

FORMAT GUIDE FOR TECHNICAL REPORTS

Ing. Daniel Valverde


FORMAT GUIDE FOR TECHNICAL REPORTS

This guide is intended to clarify the organization of technical reports, not to tell “how to
write” the report.

General Comments

1. Typed on A4 white paper.


2. Should be stapled in the upper left-hand corner or put into a folder that is bound along the
left edge.
3. Past tense, passive voice in the third person is most used.
4. Be complete, concise, and accurate.
5. Use a title page. Include the title of the experiment, class number, group number, names of
students in the group, and your name.
6. Structure of report:
(Executive) Summary
Abstract
Introduction
Theoretical
Experimental Procedure
Result
Discussion
Conclusions
References
Appendices
I. (EXECUTIVE) SUMMARY
A. Should tell in 1-2 pages what was done, how it was done, what was found,
the major conclusion, and any recommendations.
B. Think of the Summary as an extended abstract.
C. The Summary might be the only part of a part that a boss will read. Think
of it as the 1- or 2-page summary you give to your boss to explain the project
that you have been assigned.
D. Usually, an Executive Summary is placed at the beginning of the report.

1
FORMAT GUIDE FOR TECHNICAL REPORTS
Ing. Daniel Valverde
II. ABSTRACT
A. “What was done”…….in one or two sentences. It is best not to start with “In this
experiment…” or “The purpose of this experiment was to….”
B. “What method was used” in a few words.
C. “What results obtained”. Give any significant numbers. Were results good or bad? How
do they compare with other results of similar experiments?
D. 150 – 200 words. Usually one paragraph.
E. It is suggested that the abstract be written after the main text is completed.
III. TABLE OF CONTENTS
IV. INTRODUCTION
A. Purpose of investigation
V. THEORETICAL
A. Theory of phenomenon investigated.
B. Literature survey (optional) – Brief history of past attempts to study the phenomenon
(if any) and other related work.
*This section can be combined with the Introduction.
VI. EXPERIMENTAL PROCEDURE
A. Give equipment and procedure used. Explain with figures.
B. Cover the procedure in sufficient detail to demonstrate your understanding. The
procedure from the handout can be used if it is tailored to your specific conditions.
VII. RESULTS
A. Relevant, reduced data are to be presented in the form of tables, graphs, or
photomicrographs.
B. The purpose of the text in this section is to explain the data as presented.
C. Do not include a figure or table without referring to it.
D. Any data given in the appendices must be referred to.
E. Include sample calculations or explain here and include the calculation in an
appendix.
F. Mechanics
1. Number figures in Arabic numbers and tables in Roman numbers. Number
consecutively.

2
FORMAT GUIDE FOR TECHNICAL REPORTS
Ing. Daniel Valverde
2. Photographic prints included in the report should be affixed with mounting
tissue or mounting cement or placed into plastic mounting sheets.
3. Draw all diagrams, charts, and graphs neatly – use graphics software when
possible. Remember that colors do not always Xerox well.
4. In graphs, mark experimental points with circles or other large symbols;
provide a key for the symbols.
5. Remember – a figure, graph, or table, together with its caption, must be able
to stand alone and be completely understood.
VIII. DISCUSSION (OF RESULTS)
A. Elaborate on the data.
B. Compare results with respect to changes in the relevant variables.
C. If questions are asked in the Lab outline, build the discussion around the questions.
D. Recommendations to improve the Lab.
*VII and VIII can be combined.
IX. CONCLUSIONS
A. List the most important conclusions from the discussion.
B. Give conclusions in the format:
1. __________________________________________________________________
2. __________________________________________________________________
C. These conclusions should not tell anything new. The information should appear
somewhere in the Discussion.
X. REFERENCES
A. Reference all work you mention specifically.
Journal: Author(s), ‘Title”, Journal Name, year, Vol. No., page(s).
Book: Author(s), Title, edition, publisher, address of publisher, year, page(s).
page = p., pages = pp.
B. In the body of the report:
Student1 or Student (1)
XI. APPENDICES
A. Long compilation of data or extensive calculations.

3
FORMAT GUIDE FOR TECHNICAL REPORTS
Ing. Daniel Valverde
B. In general, anything that should be included but which would interfere with the
coherency (train of thought) of the report.
C. Supplementary material.
D. Number Appendices: 1, 2, 3, etc., or A, B, D, etc.
E. Each appendix covers a distinct topic.

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy