EE3636-EE3646-EE3099-EE3600 December
2025
Writing your Final Report
As the nature of projects varies greatly, it is not really possible to lay down exact rules
for the content and structure of all project reports. This is why it is important to consult
your supervisor, who will advise you on the appropriate structure and content for your
particular project.
It is recommended that you submit a plan or outline of your project report to your
supervisor for comments and feedback in January or as soon as possible after
January.
You are also encouraged to submit a first draft to your supervisor several weeks before
the report submission deadline. Please remember to allow your supervisor sufficient
time to read your work, and be aware that your supervisor may have other pressures
of work at that time.
For the final report:
• You are required to upload an electronic copy of your report on Wiseflow. For
projects with industrial support you should additionally provide copies as
required by your company.
• You must obtain a standard front-page template from Brightspace.
• On a separate page, before your Table of Contents, you are required to provide
the following declaration:
The author of this report declares that the report complies with the
University's rules on plagiarism.
• Your report should be printed on A4 size paper with single column, 1.5 line
spacing. Character sizes should be 12 points. The font colour should be black.
Only Tahoma, Ariel or very similar (so called “sans serif” family) are allowed.
EE3636-EE3646-EE3099-EE3600 December
2025
Structure and content of the Final Report
Your final report should include chapters, sections, and subsections, broadly
organised as follows:
Chapter: Introduction
This chapter should briefly overview the project topic. In addition, the chapter
should include sections covering the following:
Aim and Objectives
A clear statement of the Aim and Objectives. Remember, aim is a
general statement of what is to be achieved, and objectives are the
procedures used to achieve the aim of the project
Deliverables or specific outcomes
A clear statement of the expected outcome(s).
Project Plan (Gantt Chart)
Strongly related to the key activities identified above.
A statement on Risk Assessment and Ethical Approvals.
Societal impacts and engineering practice.
Chapter: Literature Review
This chapter should provide a more detailed review of the technical field, largely
based upon survey material. This review is a quick preliminary survey, to
discover something of the 'shape' of the relevant field of information; in doing
this you will identify key abstracts, journals, books, series of reports, and so on.
Key technical issues will be summarised.
Chapter: Experimental/investigative methods to be adopted
An outline of the key activities necessary to complete the project, itemising the
experimental methods to be used (for example, a design-based project), or the
investigative techniques to be adopted (in the case of, say, a critical survey).
Design efforts should be presented in detail, along with associated critical
considerations, parameters, and adaptations. Essentially, this chapter should
EE3636-EE3646-EE3099-EE3600 December
2025
present the design, development, and implementation work undertaken during
the project.
Chapter: Experimental/investigative results and analysis
The results from experiments/investigations and their analysis, and
observations. Figures, plots, tables, artefacts, prototypes should be
shown with brief captions, while more detailed explanations should be
provided in the body of the chapter.
Chapter: Conclusions / Future Work
Further specific instructions
• The final report should be both comprehensive and concise. It is not a log-book
or a diary of the project. A good report represents and explains your work such
that a professional engineer, on reading it, would be able to understand your
work fully without your assistance.
• Your final report should include specific discussion about the societal impacts
of your project work and the engineering practice you followed. Please look
at the respective assessment plan in the appendix of the project handbook.
Please make sure you read the assessment plan that applied to your module
code (e.g., MEng students have a different module code).
• Your report main body should not be longer than 40 pages counting from page
1, chapter 1 “Introduction” and ending at the last page of your last chapter
“Conclusions”. i.e. including all diagrams and results but excluding the title
page, tables of contents, list of figures, references, bibliography and
appendices. Industry does not like long reports and it is a good discipline to be
succinct in what you say. When a report is submitted with its main body
longer than 40 pages, it would be capped at a “B” grade.
• Data sheets should not be included in your report main body unless you are
advised to do so by your supervisor.
• Use appendices only to provide a source of information for reference, e.g. your
monthly reports, perhaps a detailed mathematical proof, snippets of source
EE3636-EE3646-EE3099-EE3600 December
2025
code etc. We do not mark material in appendices as such, although we will
doubtless look at them in support of marking the main body of your report.
• Computer program listings should not be included. You can include short snip-
pets of code to illustrate how you solved specific coding problems but these
should be limited to the absolute minimum necessary. Use pseudo-code, UML
and/or describe what you've done using Design Patterns.
• Monthly Report Forms must be included as an appendix to your report.
• For MEng students only, and in addition to the Monthly Reports, your final
report must contain your Project Planning Document as an appendix. This does
not need to be the original, week 3 version! Project plans, aims, objectives,
even titles evolve with time. It should therefore be a full and representative
version.
• Your final submission of the report should not include your name or that of
supervisor’s to make “anonymous marking” realisable.