A supervisor trusts a daily log when every entry has a time, a specific task, a checkable output and one real learning point, and when the entries match the files and messages the supervisor has actually seen. Keep each entry to four short lines, attach or name a piece of evidence, and sign off weekly. This guide gives a ready log format, two filled sample weeks for a 14-day project management internship, and a method for making entries verifiable without making them long.
Why supervisors distrust most internship logs
Supervisors read many logs that look alike: “Worked on project documentation”, “Attended meeting”, “Learned about teamwork”. Such lines cannot be checked, so they get ignored. A log earns trust when a supervisor can pick any line, ask “show me”, and the student can produce something in under a minute.
Project management work suits this well, because it produces natural artefacts: task lists, schedules, risk registers, meeting minutes, status updates. Each of these has a date and an author, which makes verification easy.
The four-column daily log format
Use one row per work block, not one essay per day. The four columns are time, task, output and learning. Add a fifth “evidence” note inside the output column rather than a new column, so the table stays narrow.
| Column | What to write | Good example | Weak example |
|---|---|---|---|
| Time | Start and end time, plus total hours | 10:00-12:30 (2.5 h) | Morning |
| Task | One verb plus one object, with the project name | Built a task breakdown for the hostel-app project | Worked on project |
| Output | What now exists, with file name or message reference | WBS_v1.xlsx, 24 tasks, shared in team chat 12:40 | Completed the work |
| Learning | One specific thing you now understand or can do | Tasks over 8 hours should be split so progress is measurable | Learned a lot |
Rules for each column
- Time: log real hours. If a block ran over, write the true figure. Round to the nearest quarter hour.
- Task: start with a verb such as drafted, updated, reviewed, compared, scheduled or presented.
- Output: name a file, a version, a count or a recipient. If nothing was produced, write “no output; reading only” and explain in the learning cell.
- Learning: one sentence, written as something you could now explain to a classmate.
Free 2-Week CareerSwami Internship
Online, 14 days, with a free offer letter and a free completion certificate once you finish the work. Check with your college that it fits your requirement before you enrol.
Making entries verifiable without making them long
Verification does not need more words. It needs anchors that a second person can see. Use the following in every entry where possible.
- File names with versions. “Risk_Register_v2.xlsx” is checkable; “risk document” is not.
- Counts. “12 risks listed, 3 rated high” lets a supervisor open the file and confirm in seconds.
- Message or meeting references. Note the channel and time: “sent to supervisor by email, 4:10 pm”.
- Same-day writing. Fill the log before you close your laptop. Entries written a week later read as reconstructed.
- Weekly sign-off. At the end of each week, ask your supervisor to initial or reply “seen” to a message containing your week’s log.
- Honest gaps. A log with a day marked “waiting for access, 1 h reading” is more credible than a perfect one.
An evidence habit that takes two minutes a day
Keep one folder named with your internship dates. Save each output into it with a dated file name, such as 2026-11-16_WBS_v1.xlsx. At day’s end, copy the file names into the log. This single habit does most of the verification work.
Worked illustration: two filled sample weeks for a 14-day project management internship
The entries below are illustrative only. They show format and level of detail for a fictional student on a small app-development project; they are not records of a real internship. Fourteen days are shown as two working weeks of seven days each, so adjust to your own schedule.
Sample week 1 (days 1 to 7): learning the project and building the base documents
| Day | Time | Task | Output | Learning |
|---|---|---|---|---|
| 1 | 10:00-11:00 (1 h) | Attended onboarding call and read project brief | Notes in Day1_Notes.docx, 1 page; 5 questions listed | Scope and goal must be agreed before any planning |
| 1 | 11:30-13:00 (1.5 h) | Listed stakeholders from the brief | Stakeholder_List_v1.xlsx, 8 names with roles | Stakeholders differ in interest and influence |
| 2 | 10:00-12:30 (2.5 h) | Drafted a work breakdown structure | WBS_v1.xlsx, 24 tasks, sent to supervisor 12:40 | Tasks above 8 hours should be split |
| 3 | 10:00-12:00 (2 h) | Revised WBS after supervisor comments | WBS_v2.xlsx, 6 tasks split, 2 added | Feedback is easiest to apply when tracked by version |
| 4 | 14:00-16:30 (2.5 h) | Estimated durations for each WBS task | Estimates column filled for 26 tasks; 4 flagged as uncertain | Uncertain estimates need a range, not one number |
| 5 | 10:00-12:00 (2 h) | Built a simple schedule in a spreadsheet Gantt view | Schedule_v1.xlsx, 3 milestones | Dependencies decide the order, not preference |
| 6 | 11:00-12:30 (1.5 h) | Took minutes in the weekly team meeting | Minutes_W1.docx, 6 action items with owners | Each action item needs one owner and a date |
| 7 | 15:00-16:00 (1 h) | Compiled weekly summary and requested sign-off | Week1_Log.pdf emailed 16:05; supervisor replied “seen” | A weekly summary exposes what slipped |
Week 1 total in this illustration: 13 hours.
Sample week 2 (days 8 to 14): risks, tracking, reporting and handover
| Day | Time | Task | Output | Learning |
|---|---|---|---|---|
| 8 | 10:00-12:30 (2.5 h) | Created a risk register | Risk_Register_v1.xlsx, 12 risks, 3 rated high | A risk needs a cause, an effect and an owner |
| 9 | 10:00-11:30 (1.5 h) | Wrote mitigation steps for the 3 high risks | Risk_Register_v2.xlsx, 3 mitigations added | Mitigation is an action, not a hope |
| 10 | 14:00-16:00 (2 h) | Updated schedule with actual progress | Schedule_v2.xlsx; 2 tasks marked late | Comparing plan with actual shows slippage early |
| 11 | 10:00-11:30 (1.5 h) | Drafted a one-page status report | Status_Report_D11.docx, RAG status: amber | A status report should state decisions needed |
| 12 | 11:00-12:30 (1.5 h) | Ran a change-request log for two new requests | Change_Log_v1.xlsx, 2 entries, 1 approved | Scope changes should be logged before work begins |
| 13 | 10:00-12:00 (2 h) | Prepared a 6-slide summary of my work | Summary_Deck_v1.pptx, 6 slides | Present results first, method second |
| 14 | 15:00-16:30 (1.5 h) | Presented to supervisor and handed over files | Folder shared 16:35; final log emailed and acknowledged | Handover notes save the next person time |
Week 2 total in this illustration: 12.5 hours. Combined, about 25.5 hours across 14 days.
What a supervisor can check in this sample
- Open WBS_v1 and WBS_v2 and compare the 24 and 28 task counts.
- Check the email timestamps for Day 2, Day 7 and Day 14.
- Count the risks marked high in the register.
- Read the minutes and match action items to the next week’s updates.
Kannur University private-registration students: how a log fits the 2-credit internship
This section applies to students on the university’s private-registration route. According to the 2024 FYUGP regulations for the Private Registration scheme of the School of Lifelong Learning, every candidate completes a 2-credit internship, with credit awarded in semester IV. The same document says the internship must be associated with the candidate’s Major discipline, and suggests hosts such as local industries, business organisations, health bodies, local governments and media organisations.
On workload, the regulations state that sixty hours of engagement are needed for two credits. That matters for your log: hours are the unit being counted, so the time column is not decoration. The sample weeks above total roughly 25 hours, so a short online internship would cover only part of that figure and would need to be combined with other engagement if your department accepts it.
The document says the internship follows guidelines prescribed for the purpose, but those guidelines are not in the regulations. It also gives a general assessment scheme: a 2-credit course is marked out of 50, split 15 for continuous comprehensive assessment and 35 for end-semester evaluation, and no separate internship scheme is given. So the format of the report, who signs your hours and how marks are allotted must come from the university. These regulations apply to the Centre for Private Registration; they do not cover regular affiliated-college students, who should ask their own college. The 2024 document may have been updated, so check the current version.
Also note that the internship credits sit within the intermediate-level courses of semesters 3 and 4, and end-semester exams are ordinarily in March/April for even semesters, so plan your log submission well before then.
Five verification steps for Kannur University students
- Ask the School of Lifelong Learning or the Centre for Private Registration, in writing, for the current internship guidelines referred to in the regulations.
- Ask whether a prescribed log, report or certificate format exists, and who must sign it.
- Ask whether an online internship is accepted for the sixty hours, and whether hours from separate short internships can be added together.
- Confirm how the 15 CCA and 35 ESE marks apply to the internship and what must be submitted to earn them.
- Confirm the submission deadline for semester IV and whether your Major discipline needs approval of the host organisation beforehand.
Starting a log on a short online internship
A free two-week online internship such as the 14-day CareerSwami internship comes with a free offer letter and a free completion certificate after successful completion, and it offers 26 tracks. It does not by itself promise academic credit, so use it as supplementary practice and keep a log from the first day. Save the offer letter with your log, since it records your start date.
Weekly review checklist before you send the log
- Every row has a start time, end time and total hours.
- Every task begins with a verb and names the project.
- Every output names a file, count or recipient.
- No learning cell says only “learned a lot”.
- Hours add up to the figure you will report.
- Evidence folder file names match the log.
- Supervisor has been sent the week’s log and asked to confirm receipt.
Writing style that reads as honest
- Use plain past tense: “Drafted”, not “Was involved in drafting”.
- Report problems: “Access to the tracker delayed work by 1 h.”
- Credit others: “Used supervisor’s template for the status report.”
- Avoid inflated numbers. A small true number beats a large vague one.
Frequently Asked Questions
How many lines should one day of an internship log have?
One row per work block is enough, usually one to three rows a day. Each row has a time, task, output and learning point. Longer entries rarely add trust; checkable detail does.
What counts as evidence for a project management log entry?
Dated files such as a work breakdown, schedule, risk register, meeting minutes or status report, plus emails or chat messages showing when you shared them. Name them in the output cell.
Should I log hours I spent reading or waiting?
Yes, if you label them honestly, for example “1 h reading; no output”. Do not log idle time as productive work, because a supervisor who spots padding will doubt the rest.
Can a supervisor sign each day, or is weekly enough?
Weekly confirmation is usually practical. Send the week’s log by email and ask for a reply saying it is seen. If your university or host demands a different signing pattern, follow that.
How do Kannur University private-registration students know how many hours to log?
The 2024 regulations mention sixty hours of engagement for two credits. Confirm the current figure and how hours are verified with the School of Lifelong Learning in writing.
Is a spreadsheet or a handwritten log better?
Either works if it is dated and consistent. A spreadsheet is easier to total and send as a PDF; a handwritten log needs legible scans. Whichever you choose, keep the same four columns throughout.
What if I forgot to log a day?
Fill it in as soon as you notice, using your saved files and messages to reconstruct it, and mark it “written later”. Honest late entries are acceptable; invented ones are not.
Can the log from a short online internship be used for university internship credit?
Do not assume so. Ask your department in writing whether an online, two-week internship and its log are accepted, and in what format, before relying on it.
Related Project Management guides
- Sathyabama Students: Estimating Task Durations Without Guessing in an Internship
- C.T. University: Presenting Your Project Management Internship in a Final Viva
- Jannayak Chandrashekhar University: A Project Management Internship for Arts and Science Students
- All Project Management internship guides
Ready to put this into practice?
Join the free two-week CareerSwami online internship in Project Management. The internship, the offer letter and the completion certificate are free.




















