In this guide
Submission day has a quiet way of exposing everything you postponed. Students who built excellent projects have lost marks over a missing logbook entry or a report bound in the wrong order. The documents are part of the deliverable — treat them with the same seriousness as the hardware.
The five documents you need
MSBTE project submission typically requires these five items. Confirm the exact list with your guide early, because formats and requirements vary by institute and scheme year — the MSBTE official website publishes scheme documents, but your institute's project coordinator has the final word on what your batch must submit.
| # | Document | What it is | Why it matters |
|---|---|---|---|
| 1 | Project logbook | A dated, handwritten record of weekly work: what you did, problems faced, decisions taken | Evidence of your process — examiners check that the project grew over the semester, not the last fortnight |
| 2 | Project report | The bound written document describing the full project | The permanent record of your work; the external examiner reads this before your viva |
| 3 | Bound certificate pages | Signed certificate, declaration, and approval pages bound into the report | Formal proof the work is yours and was supervised and approved |
| 4 | Soft copy | Report PDF, source code, and supporting files on pen drive or as specified | Lets examiners verify code and keeps an archivable copy with the department |
| 5 | Micro-project proposal | The approved proposal document from your earlier micro-project work | Shows continuity and that earlier approvals were obtained properly |
Warning: Do not assume last year's format still applies. Scheme revisions change report formats, certificate wordings, and page requirements. One confirmation meeting with your guide in the first month saves a rebinding scramble in the last week.
The logbook: evidence of your process
The logbook is the document students neglect most and examiners value most. It should be handwritten, dated, and maintained weekly — not reconstructed the night before submission. Each entry needs only a few lines: what was attempted that week, what worked, what failed, and what was decided. Failed attempts belong in the logbook; they prove you tested and iterated rather than copying a finished design. A logbook with honest failure entries and course corrections reads as genuine. A pristine logbook with no problems reads as fiction.
Report page order
Examiners expect a standard sequence. Keep this order unless your institute specifies otherwise:
- Title page
- Certificate (signed by guide, HOD, and principal as required)
- Declaration by the students
- Acknowledgement
- Abstract
- Table of contents, list of figures, list of tables
- Chapters: introduction, literature review, system design, implementation, testing and results, conclusion and future scope
- References
- Appendices (datasheets, lengthy code listings)
Get the certificate and declaration pages signed early — chasing signatures in submission week is a classic, avoidable crisis. Print one draft copy for your guide's review before you send anything for binding.
Hardbound copies and the soft copy
Plan for 2–3 hardbound copies plus the soft copy: typically one for the department library, one for your guide, and one for yourselves. Binding takes a few working days at a print shop, longer in submission season when every batch in the city is queueing — book your slot at least a week ahead. For the soft copy, include the final report PDF, all source code with a short readme explaining how to build and run it, and key datasheets. Label the drive clearly with your project title, names, and year.
A submission timeline that works
- 8 weeks out: Confirm the exact document list and formats with your guide.
- 6 weeks out: Start the logbook properly if you haven't — and begin the report draft alongside the build, not after it.
- 3 weeks out: Full report draft to your guide for review.
- 2 weeks out: Corrections done; certificate pages signed.
- 1 week out: Binding booked and submitted; soft copy assembled and checked on a different computer.
Documentation takes the back third of any project — if you haven't started writing by the halfway mark of your build window, your project timeline needs adjusting now, not later.