Guide to Writing a Project Report

1.Why a report?

The production of a good piece of technical writing for a project report is as

much a part of the project as doing the experimental work. However excellent

and original a piece of work the project may be, unless the results can be

communicated to other people it may as well not have been done!

2.How much detail to include?

It is not necessary, or even desirable; to describe every minute detail of what

was done. One of the most important aspects of good technical writing is to be

concise, yet remain informative.

5. Format of reports.

Whilst not mandatory, there are good reasons for the usual format of a report.

Sections that you need to include are,

• Title

• Abstract

• Table of contents

• Introduction

• Experimental techniques and methods

• Results and discussion

• Summary/conclusions

• References

• Appendices (if used)

5.1. First Page.

This should contain the title, the author(s) and the date.

Title.

This should convey the area and scope of the project.

5.2. Second Page.

The Abstract.- a brief summary of the report

5.3. Third page.

This should comprise a table of contents, indicating the page numbers of the

different sections.

5.4. Fourth page and onwards.

Introduction.

This is where you need to outline the underlying concepts (and if required a

brief version of a any theory) needed to discuss the project.

Results and discussion.

Present your results in a logical sequence, highlighting what is important and

how the data you obtained have been analysed to provide the results you

discuss. You should discuss what you infer from the data. You need to adopt

a critical approach

Summary and conclusion.

This is the section in which you need to put it all together

References.

Assessment criteria.