Internship log book format: weekly log, daily log and attendance sheet
An internship log book is a running record of what you did and how many hours you spent, signed by your supervisor. This page gives an internship log book format in weekly and daily versions, an internship attendance sheet format, and the mistakes that make internship offices doubt a log.
The log is a small part of your grade but a large part of your evidence. In HEC’s internship guidelines the student keeps a weekly activity log and hands it in every three weeks with a report, and completing the log counts for 5% of the final assessment. More importantly, it is what your evaluation form and final report are checked against.
Log book, weekly report and attendance sheet are not the same
| Document | What it records | Style | Who signs |
|---|---|---|---|
| Log book (activity log) | Tasks and hours, day by day or week by week | Short lines, numbers | You, checked by the site supervisor |
| Attendance sheet | Days present, time in and out | A grid of dates and times | Site supervisor or HR |
| Weekly report | What you did, learned and found hard that week | Paragraphs | You, reviewed by supervisors |
This page covers the first two. For the narrative report, use our internship weekly report format, and for the final document, the internship report format.
Internship log book format: weekly version
The HEC sample activity log asks for the intern’s name, the host organisation, the faculty supervisor and the reporting period, then one row per week with the tasks performed and the number of hours. A practical version adds dates and a signature column. Here is an example for a web development intern, with illustrative entries:
| Week | Dates | Main tasks performed | Hours | Supervisor initials |
|---|---|---|---|---|
| 1 | [DD/MM] to [DD/MM] | Set up the development environment; studied the project codebase; fixed two layout bugs on the contact page | [hours] | |
| 2 | [DD/MM] to [DD/MM] | Built the booking form with validation; wrote the API call to save bookings; code review with mentor | [hours] | |
| 3 | [DD/MM] to [DD/MM] | Added an admin list of bookings with search; deployed to the test server; fixed review comments | [hours] | |
| … | Continue one row per week until the last week |
Put the header details at the top: your name and registration number, programme, host organisation, site supervisor with an official email, faculty supervisor, and the internship start and end dates. End with a total of hours and signatures from you and the site supervisor.
Daily log format
Some departments want a daily log book instead. It takes five minutes a day and makes the weekly version easy to write.
| Date | Time | Task | Output or result | Hours |
|---|---|---|---|---|
| [DD/MM/YYYY] | [10:00 to 13:00] | Wrote unit tests for the login module | 12 tests, 2 bugs found and logged | 3 |
| [DD/MM/YYYY] | [14:00 to 17:00] | Fixed the two login bugs; mentor review | Fix merged after review | 3 |
Internship attendance sheet format
An attendance sheet is simpler. UMT’s BS Education manual, for example, asks the host to keep an attendance record alongside the weekly log. A clean format:
| Date | Day | Time in | Time out | Hours | Onsite or remote | Supervisor sign |
|---|---|---|---|---|---|---|
| [DD/MM/YYYY] | [Mon] | [09:30] | [16:30] | [7] | [Onsite] | |
| [DD/MM/YYYY] | [Tue] | [09:30] | [16:30] | [7] | [Remote] |
Hours expectations vary. CUST’s computing guidelines mention about 40 hours a week, and UMT’s education manual about 30 to 35. Check your own department before you agree a schedule with the host. If your department does not accept fully remote work, mark remote days honestly and agree a hybrid pattern in advance; see online internships.
Sample log entries for other fields
The same internship log book format works in any field. What changes is the kind of output you record. A few illustrative one-line entries:
| Field | Weak entry | Useful entry |
|---|---|---|
| Data science | Worked on data | Cleaned 3 months of sales data; removed duplicates; first chart of weekly sales |
| Mobile apps | App work | Built the login screen in Flutter; connected it to the test API |
| Graphic design | Designs | Three social post drafts for a client campaign; revised one after feedback |
| Business (BBA) | Office work | Prepared a supplier price comparison for 12 items; presented it to the manager |
One caution for computing students: some departments count only software work. CUST has reportedly excluded SEO, marketing, e-commerce and spreadsheet work for its CS internships, so make sure your log shows the kind of work your department accepts.
How to keep a log book your supervisor will sign
- Write it the same day. A log filled in one sitting at the end shows: same pen, same phrasing, round numbers.
- Use specific verbs and outputs. “Built the booking form” beats “worked on project”.
- Record real hours. They should match your attendance sheet and the dates on your offer letter and certificate.
- Get it initialled weekly. Waiting until the last day puts your supervisor in the position of signing weeks they cannot remember.
- Keep it consistent with your evaluation form, weekly reports and final report. Internship offices compare them.
- Do not buy one. Press reports describe students paying for attendance sheets and signatures. A log with no work behind it collapses the moment a faculty supervisor calls the host.
How Ezitech records tasks and hours
At Ezitech, a PSEB-registered software house in Rawalpindi, interns check in daily on our intern portal with the hours they worked, and every task has dates, a status and the mentor’s review. That makes the log book a by-product of the work rather than a separate chore.
Your university’s internship office can see the same record through our University Portal: tasks, check-ins with hours and evaluations, plus an Internship Progress Report it can download. If the department has its own log book or attendance form, the office uploads it there and we fill and sign it. See the internship programme for tracks and lengths (one, two or three months), and the fee and refund policy for programme details.
An internship where the log keeps itself
Daily check-ins with hours, weekly mentor reviews, and a record your internship office can open directly.
Questions
What is an internship log book?
It is a record of the tasks you did and the hours you spent during your internship, usually week by week, checked and signed by your site supervisor. Universities use it to confirm the internship really happened.
What is the difference between a log book and a weekly report?
A log book is short lines of tasks and hours. A weekly report is a few paragraphs on what you did, learned and found difficult. Many departments ask for both.
What should I write in an internship log book?
For each day or week: the dates, the specific tasks you performed, what came out of them, and the hours. Add your details, the host, supervisors and internship dates at the top, and a total of hours at the end.
Who signs the internship log book?
You fill it in and your site supervisor checks and signs it. In the HEC model the faculty supervisor also reviews it when you submit it every three weeks with your report.
What is the internship attendance sheet format?
A table with the date, day, time in, time out, hours, whether you were onsite or remote, and the supervisor’s signature. Some universities ask the host to keep it, others ask you to submit it.
Can a remote internship have a log book?
Yes, and it matters more, because no one saw you in the office. Record hours honestly and get it checked weekly. Confirm first that your department accepts remote work at all.