Notes on Report Writing
1. Who is the intended recipient?
What is their interest / expertise?
2. What are the Objectives / Aims you wish to achieve with your report?
- Get good marks?
- Have your project proposals accepted?
3. Decide Layout - Typically:
- Summary (normally about 1 side A4. This may be the last bit you write).
- Contents List
- Nomenclature (even 'simple' reports will usually need some nomenclature).
- Introduction, including aims, objectives and background (this may be separated if there is a lot of background reviewed).
- Theory
- Experimental
- Results (do not include tables of results - use graphs, including experimental points. Avoid colour
and do not put more than 4 curves on 1 graph).
- Discussion of Results (this will often include comparisons between theoretical and experimental results where
you will be expected to describe reasons for the differences. Validity of assumptions should also be considered).
- Conclusions (about 1 side of A4)
- Future Work (it is normally impossible to tackle all aspects of an assignment fully. By listing and prioritising
suggested further investigations, you are demonstrating that you understand the potential limitations of this work).
- Appendices (the detailed evidence - such as tables of results - goes in here)
- References (diagrams and tables etc, can be copied from other authors work and used in the report, but they must
be acknowledged and fully referenced).
4. Avoiding loss of marks:
- Submit work on time (zero marks are given for late work unless you have valid extenuating circumstances).
- Writing up almost always takes longer than you think it will.
- Write good English.
- Explain calculations, labelled sketches are normally essential, include units.
- Calculations in design reports need an introduction, full explanation and a conclusion.
- Use a word processor, at least for the text (save back up copies on two or more floppy discs, CD or USB devices).
- Get a friend (not necessarily a fellow student) to carefully read through the report.
David Grieve, 12th October 2000, revised 17th August 2005.
Return to Index of Online Documentation