Engineering Project Guide (2026) — Documentation, Reports & Evaluation
Most students treat project documentation as the last thing they do. Examiners treat it as the first thing they judge. The report, abstract, and literature review are read before the viva begins — and the impression they create shapes every question that follows.
This page guides you through the full documentation process in the correct sequence — from selecting your topic to building a report that holds up under direct questioning. Read in order if you are at the beginning. Jump to the section you need if you are mid-project.
Topic Selection — Before Documentation Begins
Documentation quality is directly constrained by topic quality. A poorly scoped topic produces a poorly structured report — no matter how well it is written. Topic selection is not a five-minute decision. It determines what you can document, what data you can collect, and what examiners will ask.
Synopsis — The First Document Examiners See
A synopsis is not a shortened version of the report. It is a proposal — a document that must convince the examiner or guide that the project is worth approving before a single test is run. Most synopses are rejected not because the project is weak, but because the argument for it is unclear.
Aim, Objectives & Scope — The Frame of the Entire Project
The aim, objectives, and scope are the three statements that frame everything an examiner evaluates. If these are vague, the methodology becomes unjustifiable. If the scope is undefined, results cannot be interpreted. Most students write these last. That is the wrong order — they should be written first and treated as fixed reference points throughout execution.
Abstract — 200 Words That Decide the First Impression
An abstract is not a summary. It is a four-part argument: what the problem is, what was done, what was found, and why it matters. Examiners read the abstract before anything else. A weak abstract signals a weak report — before a single page of the report has been read.
Literature Review — Critical Analysis, Not a Reference List
The difference between a literature list and a literature review is critical reasoning. A list says: these papers exist. A review says: this is what they found, where they disagreed, and what gap this project addresses. Examiners at every level — from university vivas to journal reviews — use the literature review to assess whether the student understands the field or simply searched for references.
Project Report — A Structured Argument, Not a Diary
A project report is not a record of what was done. It is a structured argument for why the work is valid, what it found, and what it means. Examiners read reports looking for gaps in reasoning — not just gaps in formatting. The methodology and results sections are where most reports lose credibility before the viva even begins.
Evaluation Framework — Define Success Before You Begin
Most students define whether their project succeeded after they have finished it. Examiners define it before they evaluate it. A project without a pre-defined measurement standard gives examiners the freedom to set the benchmark during the viva — which rarely works in the student's favour. This framework closes that gap.
Documentation is not the last stage of a project — it is the record of every decision made during it. A well-documented project defends itself. A poorly documented one forces the student to reconstruct the reasoning under pressure, in a viva room, in front of an examiner who has already formed an impression from the report.
Once documentation is complete, the next stage is viva preparation — understanding how examiners read what you have written, and how to answer the questions it will generate. That guidance is in the Viva Preparation section of this site.
Eight years. One standard.