Theory
Your week-by-week record
The logbook is your ongoing, weekly record of the internship, a simple table you fill in as you go. It is one of your deliverables, it feeds your final report, and it is the honest evidence of what you did each week.
This lesson gives its format. The logbook is deliberately simple: a few columns capturing, each week, what you were asked to do, what you actually did, and the tools you used. This lesson shows the columns and how to keep it. The key habit is filling it in weekly, as you go, not reconstructing it from memory at the end. Kept well, the logbook makes your report easy and your record trustworthy.
At a glance
| Column | What you record |
|---|---|
| Week No | The week number of the internship (1, 2, 3, ...) |
| Date | The date(s) of that week's work |
| Tasks assigned | What you were given to do that week |
| Tasks completed | What you actually did/finished |
| Tools / technologies used | The tools, languages, or technologies you used |
Theory
Keeping the logbook well
Each week, add a row (or rows) recording: the week number, the date(s), the tasks assigned to you, the tasks completed, and the tools and technologies used.
Two habits make it valuable. Fill it in weekly, while the details are fresh, not from memory at the end (which is inaccurate and stressful). Be specific and honest: 'built the registration form and connected it to the database using React and Firebase' is far more useful than 'did some coding'.
The logbook then serves you well: it is an accurate, contemporaneous record of your engagement; it feeds the weekly summary in your final report (so writing that becomes easy); and it is verified by signatures (the next topic). A well-kept logbook is a small weekly effort that pays off greatly at the end. Confirm the exact required format with your faculty mentor.
Quiz
What does the internship logbook typically record each week?
- Only your personal opinions about the company
- The week number, date, tasks assigned, tasks completed, and tools/technologies used
- Nothing; it is left blank until the end
- Just the final grade you expect
Show the answer
The week number, date, tasks assigned, tasks completed, and tools/technologies used
The logbook records, each week, the week number, the date(s), the tasks assigned to you, the tasks you actually completed, and the tools/technologies you used, a simple, structured, factual record of your work. Option A is wrong: the logbook records your actual work, not just opinions about the company. Option C defeats its purpose: the logbook is maintained WEEKLY as you go, not left blank until the end (reconstructing it later is inaccurate). Option D is irrelevant: it records work done, not expected grades. Fill it in weekly, specifically and honestly, and it accurately documents your engagement and feeds your final report.
Think first
Why fill in the logbook weekly rather than all at once at the end?
It is less hassle to write the logbook in one go at the end. Why keep it weekly? Then tap.
Show the answer
Because filling the logbook in WEEKLY, as the work happens, produces an ACCURATE, HONEST, and DETAILED record, whereas writing it all at the end forces you to reconstruct weeks of work from fading memory, giving a vague, inaccurate, and less credible account, and often a stressful scramble. Memory is unreliable over time: by the end of the internship, the specifics of week two, exactly which tasks you were given, what you completed, which tools you used, have blurred or been forgotten, so an end-of-internship reconstruction ends up generic ('did some development work') rather than specific and true. A logbook filled in each week captures those details while they are FRESH and exact, so it faithfully reflects what actually happened, which is the whole point of a record. This accuracy matters for several reasons. It makes the logbook a TRUSTWORTHY evidence of your genuine, ongoing engagement over the full 120 hours, something a hastily back-filled version cannot credibly be, especially since it is signed by your supervisor week by week (the next topic) to verify it in real time; you cannot honestly get weekly sign-offs on entries you have not yet written. It makes your final REPORT easy, because the weekly summary and the description of work done draw directly on a rich, accurate logbook, rather than you straining to remember the whole internship at report-writing time. It reduces STRESS: a small weekly habit spreads the effort, versus a painful, error-prone cram at the end. And it reflects good professional practice, keeping records as you work is exactly what professionals do (progress logs, timesheets, notes), and it builds the discipline of documentation. There is also an INTEGRITY dimension: a weekly, signed logbook is an honest, verifiable account, whereas a fabricated-from-memory one risks being inaccurate or, worse, invented, which the signing process is designed to prevent. So keeping the logbook weekly is not extra hassle for its own sake; it is what makes the record accurate, credible, and useful, and it saves you effort and stress overall. Record it as it happens, and the log is true, verifiable, and effortless to draw on later.
Summary
Key takeaways
- The logbook is your weekly record of the internship, kept in a simple table filled in as you go.
- Typical columns: Week No, Date, Tasks Assigned, Tasks Completed, and Tools/Technologies Used.
- Each week, add a row recording what you were asked to do, what you actually did, and the tools/tech used.
- Fill it in weekly, while details are fresh, not reconstructed from memory at the end.
- Be specific and honest ('built the registration form using React and Firebase' beats 'did some coding').
- The logbook is accurate evidence of your engagement, feeds your report's weekly summary, and is verified by signatures.
- Memory hook: a simple weekly table, week/date/tasks-assigned/tasks-completed/tools, kept up to date as you go.