The document provides guidance on writing a technical report, including defining its objectives, format, and content. It explains that a technical report describes the process, progress, or results of a research project. An effective technical report has clear objectives, is written for the intended reader, and follows a standard format including a title page, summary, table of contents, introduction, body, conclusions, and references. The key content sections are explained in detail.

2. If the objectives of the report have been
clarified, the writer will know the appropriate level
of technical language and the correct tone for the
readership. The style will be formal because reports
are formal documents. The report is now taking
shape, although little or no formal writing has been
produced. The format has been chosen, the material
organized, the logical progression clarified and the
sections prepared; then the writing of the report can
now begin.

3. All praise to almighty Allah who is most
beneficent and merciful. Who enabled me to read and
write, then to holy prophet Muhammad (PBUH), who
gave the light of Islam to mankind.
First of all I pay my deepest thank to Almighty
Allah, Who enabled me to complete this presentation. I
pray deepest thanks to my teacher Prof. Dr. Mirza
Shahid Baig. Also special thanks to my fellow Sami
Ullah Khan bahi and Umair Malik who helps me a lot.

4. 1. Introduction.
2.Technical Report.
2.1 Introduction.
2.2 Objective.
3. Format.
3.1 Title page.
3.2 Summary.
3.3 Table of Content.
3.4 Introduction.
3.5 Text body.
3.6 Conclusions.
3.7 References.
3.8 Appendixes.
4. References.

5. A technical report (Scientific
Report) is a document that describes
the process, progress, or results of
technical or scientific research or the
state of a technical or scientific
research problem. It might also
include recommendations and
conclusions of the research.

6. • Technical reports are often prepared for sponsors of
research projects.
• Technical reports are today a major source of
scientific and technical information. They are
prepared for internal or wider distribution by many
organizations.
• There are no absolute rules about the details of
report production, because every report must be
totally adapted to the needs of its reader.
• Flexibility and adaptation may be useful, but only to
make the report more accessible to the reader.

7. The objectives of a report identify exactly what
information it covers, for whom it is written and why
it should be produced; these objectives should be clear
to the writer long before the process of writing starts.
It is helpful to put down in note form the
precise details of the objectives and to check these
details regularly until the last stages of production.

8. • The reader is the most important person.
• Keep the report as short as possible.
• All references should be correct in all details.
• The writing should be accurate.
• The right diagram with the right labels should be in
the right place for the reader.
• Reports should be checked for technical errors,
typing errors.
• The report should look as good as it is.

9. As material arrives, it should be put into one of
three categories:
 Obviously important information which must go into
the report because it is completely relevant to the
objectives.
 Borderline information which might be useful to some
readers, or which might amplify or substantiate other
more important material.
 Information which is interesting (or not) to the writer,
but which is not relevant to the objectives of the report.

10. The full format of a report can be as
follows:
 „ „ Title page.
 Summary.
 „ „ Table of Contents.
 „ „ Introduction/Scope.
 „ „ Procedure/ Body Text.
 „ „ Conclusions.
 „ „ Recommendations.
 „ „ References.
 „ „ Appendices.

11. The title page is the first page of the report proper
which the reader will see. It should contain :
• The title and author’s name.
• The report reference number and date, if available.
• The company’s name and logo if desired.
• A statement of copyright if needed, and no more.

12. The summary (sometimes referred to as the
executive summary) provides a brief overview of the
substance of the report; usually no more than half a page.
It is not an introduction to the topic. The summary should
outline all the key features of your report, including the
topic, what you did and how you did it. The summary
gives the most important findings of your research or
investigation.

13. The contents page sets out the sections and
subsections of the report and their corresponding page
numbers. It should clearly show the structural relationship
between the sections and subsections. A reader looking for
specific information should be able to locate the
appropriate section easily from the table of contents.
Number the sections by the decimal point
numbering system.

14. The introduction provides the background
information needed for the rest of your report to be
understood. It is usually half to three-quarters of a page
in length. The introduction includes:
• The background to the topic.
• A clear statement of the purpose of the report.
• A clear statement of the aims of the project.

15. This is main part of the report, where you present
your work. The introduction and conclusions act as a
frame for the body only; therefore all the details of your
work must be included here.
The presentation of information should flow
logically so that the reader can follow the development of
your project.

16. The conclusions section provides an effective
ending to your report. They must give some overall
insight into the value of your work in general and
inform the reader of what the major impact of your
work is.

17. A reference shows that information comes
from another source and also gives the details of
these sources.

18. Appendixes contain material that is too detailed
to include in the main report, such as raw data or
detailed drawings. Usually each appendix must be
given a number and title.

19. • www.wikipedia.org/wiki/Technical_report
• www.monash.edu.au/lls/llonine/writing/engi
neering/technical_report
• www.monitor2manager.com/p/example_techn
ical_report.doc
• www.theiet.org/student/resources/technicalre
port.cfm
• www.media.uclam.ac.uk/report_writing_guide
.pdf