Why this happens
Examiners read many reports and look for a clear problem statement, a justified method, honest results and conclusions tied to evidence. Reports often lose marks for long copied theory chapters, unlabelled graphs and claims without data, all of which are easy to fix with a disciplined structure.
What you need
Tools
- Word processor or LaTeX editor
- Reference manager
- Spreadsheet or plotting software
Materials
- Your college's report format guidelines
- Project data, photos and diagrams
- Logbook or Git history
Before you start
- Never invent or adjust data to fit expectations; it is academic misconduct and examiners often spot it.
- Describe any hardware testing accurately, including safety measures; do not suggest readers repeat unsafe tests.
Step by step
- 1
Write the problem statement first
Before anything else, write three or four sentences: the problem, why it matters for EVs, what you set out to do and how you measured success. Keep this paragraph visible while writing; every chapter should support it. If a section does not help answer the problem, cut it or move it to an appendix.
- 2
Follow a clear structure
Use a structure such as: abstract, introduction, literature review, system design, implementation, testing and results, discussion, conclusion and future work, references and appendices. Check your college's required format and margins early. Number figures, tables and equations consistently, and refer to each one in the text before it appears.
- 3
Make the literature review critical, not copied
Summarise what earlier work did, compare approaches in a table and state the gap your project addresses. Write in your own words and cite every source. Long, copied theory on how lithium cells or motors work adds pages but not marks, and may trigger plagiarism checks. Keep background theory to what your design actually uses.
- 4
Justify every design choice
In the design chapter, explain why you chose each major component or method, with the calculation or comparison that led to it. A sizing table, a trade-off matrix or a simulation result is far more convincing than 'this motor was selected'. Include block diagrams and clean wiring diagrams with labels.
- 5
Present results honestly with good graphs
Every graph needs labelled axes with units, a legend, readable fonts and a caption that says what the reader should notice. State test conditions, number of trials and uncertainty. Report results that did not match expectations and explain why; a thoughtful analysis of a shortfall is worth more than unexplained perfect numbers.
Tip: Read each graph caption alone and check it still makes sense.
- 6
Tie conclusions to evidence
Each conclusion should point to a specific result in your report. Avoid claims such as 'range increased greatly' unless you measured it, and give the figure with conditions. In future work, list concrete next steps that follow from your limitations, not generic statements.
- 7
Include safety and ethics
Add a short section on how you handled risks: current-limited supplies, fuses, fire-safe bench, supervision, insulated tools and how you avoided working on high-voltage systems. Mention data sources and permissions for any survey or industry data. Examiners and recruiters notice when students treat safety as part of engineering.
- 8
Edit, check and proofread
Leave a few days between finishing a draft and editing it. Check spelling, units, figure numbering, references and consistency of terms. Ask a classmate to read the abstract and conclusion only and explain your project back to you; if they cannot, rewrite those sections. Run your college's similarity check before submission.
How to tell it worked
A reader can state your problem, method, key results and conclusions after reading the abstract, every graph is labelled and captioned, and every claim points to evidence in the report.
Stop and call a technician if
- Your planned test needs working on a vehicle battery pack or high-voltage system without supervision; change the test or arrange it through your lab and guide.
- You are unsure whether you may include company or partner data; ask your guide before submission.
Questions
How long should the literature review be?
Long enough to show what has been done and where your gap is, usually a modest share of the report. Your college guidelines may give a guide length.
Can I include failed experiments?
Yes. Explaining what went wrong and what you learned shows engineering judgement and is often valued by examiners.
