Skip to content
Free student toolkit

The student project guide — from topic to viva.

Written by our mentors for Engineering, Polytechnic, Arts & Science, Management and School students. Your college or university format always comes first — use this guide alongside it.

01

Choosing the right topic

The best project is one you can finish on time, explain completely and demonstrate confidently. Before you commit, check your topic against these six questions:

  1. Relevant — does it belong to your department and use what you studied?
  2. Feasible — can it be built in the time and budget you have, with components, software or data you can actually get?
  3. Improved — does it add something over the existing system: better accuracy, lower cost, a new feature, a new application or a fresh dataset?
  4. Demonstrable — can you show it working in a few minutes in front of examiners?
  5. Explainable — can every team member explain every block, formula and line of logic?
  6. Interesting to you — you will live with it for a semester; pick something you are curious about.

Mentor tip: an ordinary topic built and explained well scores better than an advanced topic you cannot explain. If in doubt, pick the simpler version and add one clear improvement.

02

Writing the abstract

An abstract is a 200–300 word summary that lets a reader understand your whole project in one minute. Write it last, after your design is clear, in five parts:

1. ContextThe area and why it matters (1–2 sentences).
2. ProblemWhat is wrong or missing in the existing system.
3. Proposed solutionWhat you built and the key method, algorithm or hardware.
4. ResultsWhat it achieved — accuracy, time saved, cost, findings.
5. SignificanceWho benefits and possible future use.

Fill-in template
“[Area] is important because [reason]. Existing systems [limitation]. This project proposes [your solution] using [method / tools]. The system [what it does]. Testing showed [result]. The work can help [users] and can be extended to [future scope].”

Keep it in the past or present tense, avoid references and abbreviations without expansion, and add 4–6 keywords below it if your format asks for them.

03

Report format & chapters

Most universities follow a structure close to this. Chapter names change by stream — technical projects describe a system, research projects describe a methodology.

PartTechnical project (Engg / Poly / CS / MCA)Research project (MBA / BCom / BBA / Science)
Front matterTitle page · Bonafide certificate · Declaration · Acknowledgement · Abstract · Contents · List of figures & tables · Abbreviations
Chapter 1Introduction — background, problem, objectives, scopeIntroduction — background, industry/company profile, need for the study
Chapter 2Literature survey — 10–15 related papers and their gapsReview of literature — earlier studies and the research gap
Chapter 3System analysis — existing system, proposed system, requirementsResearch methodology — objectives, hypotheses, sampling, tools
Chapter 4System design — block / architecture diagram, modules, flowcharts, UML/circuitData analysis & interpretation — tables, charts, statistical tests
Chapter 5Implementation, testing & results — screenshots, test cases, outputFindings, suggestions
Chapter 6Conclusion & future enhancementConclusion & scope for further research
End matterReferences · Appendix (code snippets, datasheets)Bibliography · Appendix (questionnaire)

Common formatting rules

  • A4 paper, Times New Roman 12 pt body, chapter titles 14–16 pt bold, 1.5 line spacing.
  • Margins usually 1.5″ on the binding (left) side and 1″ on the others.
  • Number figures and tables by chapter (Fig 4.2, Table 5.1) and refer to each one in the text.
  • Use one reference style throughout — IEEE for engineering, APA for management and science are most common.
  • Page numbers in Roman numerals for front matter, Arabic numbers from Chapter 1.

Always check: your department’s template overrides everything here — especially the certificate wording and font sizes.

04

PPT for every review

Reviews show steady progress. Keep 10–14 slides, one idea per slide, large diagrams and very little text.

Zeroth reviewTitle, abstract, objectives, literature survey, why this topic.
First reviewExisting vs proposed system, block diagram, modules, requirements, ~30% work done.
Second reviewDesign details, 60–70% implementation, early results and screenshots.
Final reviewComplete results, live demo, comparison, conclusion, future scope, references.

A slide order that works

Title & team → Problem → Objectives → Existing system & drawbacks → Proposed system → Block / architecture diagram → Modules → Tools & components → Results / analysis → Conclusion & future scope → References → Thank you.

05

Viva preparation

Examiners want to see that you understand the project. These questions come up in almost every viva:

  • Explain your project in two minutes.
  • What is new in your project compared to the existing system?
  • Walk us through the block / architecture diagram.
  • Why did you choose this component, algorithm, tool or statistical test?
  • What problems did you face and how did you solve them?
  • What are the limitations? How would you improve it?
  • What was your individual contribution?
  • What is the cost, and could it be used in real life?

Every project page on CP Projects lists the viva questions specific to that topic. Practise answering aloud, keep answers short, and say “I would need to check that” rather than guessing.

06

Plagiarism & AI originality

Colleges check reports with similarity tools such as Turnitin, Ouriginal or DrillBit. Many set a limit of around 10–15% similarity for project reports — confirm the limit your university uses.

  • Write in your own words. Read a source, close it, then explain the idea as you understand it.
  • Cite everything you use — papers, websites, datasets, images and code.
  • Use AI tools to understand, not to write. Many colleges now also check for AI-generated text, and examiners can tell when you cannot explain your own report.
  • Your results are your own. Screenshots, readings, survey data and analysis from your work are naturally original.
  • Quotations and references are usually excluded from the similarity score when formatted properly.

Our promise: every CP Projects build is customised with you, and we review your report in your college format so the work and the explanation are genuinely yours.

07

A 12-week plan

WeeksGoalOutput
1–2Choose topic, read 10–15 papers or studiesTitle, abstract, literature notes
3–4Design the system or research methodBlock diagram, modules / questionnaire, tool list
5–8Build, collect data, test module by moduleWorking prototype or completed data collection
9–10Results, analysis, improvementsGraphs, tables, screenshots, comparisons
11Write the report and prepare the PPTDraft report checked for similarity
12Rehearse demo and vivaFinal report, PPT, confident team
08

Notes for your stream

Need a mentor to guide you?

Talk to us about your department, topic and deadline. The first conversation is free.