After the 5th-semester internship, almost every BEU-affiliated department asks for the same thing at the start of the 6th semester: a bound file with your title page, certificate, week-wise logbook, project report, and viva. Students lose marks not because their work was weak, but because the file is incomplete, the hours do not add up, or the certificate cannot be verified in the room. This post gives you the full format that Training and Placement cells actually accept, in order, with the honest caveat up front: credit is decided entirely by your college through its T&P cell and Head of Department, so confirm this format with them before you print. No training provider, CannyIntern included, can grant credit or promise acceptance.
1. The title page
Put, in order: project title exactly as on your certificate, your name and university roll number, branch, semester and section, training period with start and end dates, provider and track name, internal faculty guide with designation, and department, college, and Bihar Engineering University with the academic session. Below that, one line stating the report is submitted in partial fulfilment of the industrial training requirement. Get three things exactly right: the spelling of your name must match your certificate and verification record letter for letter, the dates must match the certificate and the verification page at cannyintern.in/verify, and the project title must be identical everywhere. A mismatch as small as a spelling variant or a wrong month is enough for a strict department to send the file back. If your department issues its own cover template, use theirs instead of anything here.
2. The certificate page
The second page is a copy of your training-completion certificate, and behind it many departments expect the verification printout. The rule that matters: the certificate comes only after every module passes review, and progress counts only reviewed passes, never attendance alone. If you trained with CannyIntern, your examiner can check your record in under two minutes at cannyintern.in/verify with your verification code, matching name, program, training period, reviewer sign-off, and Verified status with no login and no fee. Print that verification result and file it directly behind the certificate copy so the examiner never has to ask for a link during the viva. Keep the work individual: group certificates where several names share one project report are the single most common reason departments reject a submission. The full kit your TPO needs, including the printable logbook template and viva bank, is at /tpo-kit.
3. The week-wise logbook: 6 weeks x 20 hours
The logbook is the heart of your file. The widely followed BEU norm is around 120 hours over four to six weeks, most defensibly documented for the 5th-semester round as six weeks of roughly twenty focused hours each. Use one row per week with four columns: week number and dates, focus and hours, deliverable submitted, and reviewer status, exactly as in the printable template at /tpo-kit. Under focus write the topic and honest hour count; under deliverable write what you submitted that week with a date; under reviewer status write Approved with date or Revise with what changed. A complete arc: Week 1 orientation and tooling, Week 2 foundations with two small exercises, Week 3 core build part one with one revision cycle, Week 4 core build part two with test evidence, Week 5 integration and capstone draft, Week 6 final evaluation and report, totalling 120 hours across six dated, reviewed deliverables. Examiners forgive a week marked Revise and resubmitted; they do not forgive six identical weeks with no evidence.
4. The project report chapters
After the logbook comes the engineering report itself, typically fifteen to thirty pages: abstract stating what you built and the measurable outcome; introduction with problem statement and objectives; tools and technologies with versions; system design with one architecture diagram; implementation describing module by module what you personally built; testing and results with at least one failure honestly documented and fixed; conclusion with the limitation you accept and the single improvement you would make with two more weeks; and references plus annexures holding your repository URL, screenshots, and submission receipts. Write it in your own voice and keep it consistent with your logbook: for every claim in the implementation chapter, point to the week it was submitted and the reviewer comment it received.
5. Viva prep and filing checklist
The viva is usually five to ten minutes and follows six questions, also published for your TPO at /tpo-kit: walk us through your build and what you personally implemented; hardest technical decision and rejected alternatives; one failure and how you resolved it; one evaluation criterion in your own words and where your submission meets it; the single improvement with two more weeks and how you would measure it; and where we can check your work right now. Rehearse with your own file open and be able to open your repository and verification record on a phone. Assemble the physical file in this order: title page; certificate copy plus verification printout; offer letter; week-by-week syllabus; six logbook sheets totalling 120 hours; project chapters; declaration of originality; guide certificate and HoD forwarding signature where required. Check name spelling, date consistency, honest hour totals, live links, and signatures the night before.