Under the newer regulations, internships and training carry real credits (and credits are credits) — evaluated substantially through your report and a short viva. Most students write it in one guilty night from fading memory; the students who collect full credit follow a simple system. Here it is, plus the answer to the universal worry: “my internship work felt too small to fill a report.”
The structure evaluators expect
- Front matter: title page, the company’s internship certificate (the load-bearing document — collect it before you leave, on letterhead, with dates), college bonafide as your template requires, abstract, contents.
- Company profile: one or two pages — what the organisation does, its domain, where your team sat in it. Write it like an engineer, not a brochure: what the company builds, for whom, with what technology.
- Training/work description — the core: your role, the tools and technologies you touched, and the tasks week by week. Structure beats prose: a week-wise table (week → work assigned → what you did → what you learned) plus detailed write-ups of your 2-3 most substantial tasks.
- Learning outcomes: technical skills gained, tools learned, and the professional observations — standups, code reviews, deadlines, how real teams communicate. Evaluators weight this chapter heavily because it shows reflection, not just attendance.
- Conclusion + any appendices (screenshots of work where permitted, log sheets your college prescribes).
The habit that writes the report for you
Ten minutes of daily logging during the internship — what you did, what broke, what you learned, names of tools — converts report-writing from archaeology into assembly. Interns who keep the log finish the report in an afternoon; everyone else reconstructs three weeks of “I think we did testing?” This log doubles as ammunition for interview stories and your resume bullets later — one habit, three payoffs.
“My work felt too small” — the honest fix
Observation-heavy internships and IPTs still yield strong reports, because evaluators grade engagement, not job titles. The technique: go one level deeper than what you did, into what you understood. “Observed the production line” becomes a page when you document the process flow, the machines’ roles, the quality checks and why they exist. “Fixed small bugs” becomes substantial when you explain one bug end-to-end: symptom → cause → fix → what it taught you about the codebase. Depth of understanding fills pages honestly; padding fills them detectably.
Never do these
- Confidentiality violations: no internal code, client names, or data without permission — describe work at the level your mentor okays. One line asking your mentor “what can I include in my college report?” protects you completely.
- Copying a senior’s report: departments keep archives; similarity is obvious and the viva is merciless on it.
- Certificate mismatches: dates and company names must match across certificate, report and any college forms — verification checks exactly this.
The viva is short and predictable: what did you do, explain this task, what did you learn, how is industry different from college. Your log and the learning-outcomes chapter are the entire preparation. Fifteen honest minutes daily during the internship, one afternoon of assembly after — full credit, and a report that quietly upgrades your placement story.