Last updated: July 30, 2026
The first time I held my SIWES logbook, I thought it would be the easiest part of industrial training.
I was wrong.
I still remember sitting in a small office near closing time during my SIWES. Everybody was already mentally halfway home. My supervisor asked for my logbook, flipped through a few pages, paused, and looked at me.
He tapped one page and said, “You wrote ‘worked in the office today’ three times this week. What exactly did you do?”
I didn’t know what to say.
Because the truth was, I had done plenty. I just didn’t know how to write it properly.
Nobody explained it.
And that’s how many students get into trouble.
You secure placement. You resume. You survive transport, attendance register, office stress, maybe even awkward colleagues. Then one day your school supervisor visits and asks for your SIWES logbook.
Suddenly that small booklet becomes very important.
If you’re on SIWES right now and confused about how to fill your SIWES logbook, this will help.
Why your SIWES logbook matters
Your SIWES logbook is not just attendance evidence.
It’s your record of training.
Your school wants to see:
- where you worked
- what you did
- what you learned
- whether the training relates to your course
- whether you actually participated
Most school supervisors check the logbook before asking anything else.
I’ve seen students panic because they left three weeks blank.
I’ve also seen students rush to borrow another person’s logbook to copy.
Bad idea.
Your SIWES logbook should reflect your own experience.
That’s what schools under the Industrial Training Fund SIWES programme are trying to measure.
How to fill your SIWES logbook correctly
Think of your SIWES logbook like a weekly work diary.
You’re not writing an essay.
But you’re also not writing one-word updates.
Each day should answer:
- What did I do?
- Where did I do it?
- What did I learn?
Keep it simple.
But be specific.
Weak example
Monday: Worked in office.
Too vague.
Better example
Monday: Assisted with sorting student files according to registration number and entered biodata into the department database. Learned how student records are stored and retrieved when requested.
That’s better.
It feels real because it is.
Your supervisor can understand exactly what happened.
Sample SIWES Logbook Entry (What a Real Week Can Look Like)
Here’s what a properly filled SIWES logbook can look like.
You don’t need to copy this exactly. Use it as a guide.
| Day | Description / Work Done |
|---|---|
| Monday | Resumed at the office by 8:00 am. Assisted with sorting incoming student files and arranging them according to registration number. Learned how records are stored for easy retrieval. |
| Tuesday | Entered student biodata into the office database using the desktop computer. Cross-checked names, registration numbers, and departments before saving entries. |
| Wednesday | Assisted in preparing files for internal documentation and observed how official memos were recorded and archived for future reference. |
| Thursday | Helped scan student records and upload them into the digital archive. Learned how documents are renamed and organized in folders. |
| Friday | Participated in weekly staff briefing. Assisted with compiling attendance records and arranging files needed for the following week. Supervisor reviewed completed tasks. |
If you’re in another field, yours may look different
A computer science student’s SIWES logbook could look like this:
| Day | Description / Work Done |
|---|---|
| Monday | Installed Windows operating system on two desktop systems in the ICT unit and configured basic settings. |
| Tuesday | Assisted with troubleshooting internet connection issues in staff offices and replaced faulty network cable connectors. |
| Wednesday | Installed antivirus software on office computers and updated expired security definitions. |
| Thursday | Backed up office files to external storage and learned the file recovery process used by the ICT team. |
| Friday | Assisted with formatting laptops for new staff use and installing required software applications. |
That’s why copying another student’s logbook rarely works well.
Your entries should match your department and actual workplace.
What supervisors actually look for
Most supervisors are not expecting perfect grammar.
They’re looking for evidence.
1. Consistency
Did you fill it regularly?
Or does it look like everything was written the night before inspection?
They can usually tell.
2. Relevance to your course
If you study accounting, they expect accounting-related exposure.
If you study microbiology, they expect lab work.
If you study computer science, they expect technical tasks.
Even if your office gives you random admin duties, document anything related to your field where possible.
3. Learning progress
Your entries should show growth.
Maybe in Week 1 you observed.
By Week 4 you assisted.
By Week 10 you were handling small tasks yourself.
That progression matters.
4. Signatures
This one causes problems every year.
Don’t wait till the end.
Get signatures regularly.
I’ve seen students spend two weeks chasing a supervisor who travelled for a workshop because they forgot to sign the logbook earlier.
Don’t let that be you.
What Nobody Tells You
A lot of students fill the SIWES logbook late.
Usually at the end.
I understand why.
You’re tired after work.
Maybe transport back home took two buses.
Maybe NEPA took light and you’re charging your phone at the neighbour’s shop.
Maybe you just want to sleep.
But writing it later becomes harder.
You forget details.
Days begin to merge together.
Everything starts sounding like:
“Assisted with office work.”
Then repeated for five pages.
That’s where the problem starts.
The easiest thing I’ve seen students do well is this:
Before leaving work each day, open your phone notes app.
Write 2 or 3 quick bullet points.
Then transfer it into the SIWES logbook later.
That way you don’t forget.
And when your school supervisor visits unexpectedly, you’re not hiding behind the receptionist asking them to say you stepped out.
Common SIWES logbook mistakes that affect your grade
These mistakes happen every semester.
Writing only one sentence for the whole week
Too short.
Repeating the same thing every day
Even if your duties are repetitive, explain them differently and mention details.
Leaving blank pages
This immediately raises questions.
Forgetting dates
Always check dates before writing.
Missing signatures
Very common.
Very avoidable.
Writing tasks you can’t explain
Don’t write “configured server infrastructure” if all you did was watch somebody restart the router.
Because if your supervisor asks, you’ll need to explain it.
Write what actually happened.
A practical action plan for your SIWES logbook
If you’re currently on SIWES, here’s what I recommend.
1. Update it every week
Same day is even better.
Don’t pile it up.
2. Write specific tasks
Mention:
- what you did
- tools used
- software used
- skills learned
3. Keep it brief but detailed
3 to 5 lines per day is usually enough.
4. Get signatures often
Weekly if possible.
Don’t postpone it.
5. Review before visitation
Before your school supervisor arrives, check:
- dates
- signatures
- company name
- missing pages
- your student details
6. Ask final-year students in your department
They usually know what your department pays attention to during SIWES assessment.
That advice can save you stress.
Final thoughts on your SIWES logbook
Your SIWES logbook feels like small paperwork until somebody asks for it.
Then suddenly it becomes the most important thing in your bag.
Treat it seriously from the beginning.
A clean, detailed SIWES logbook makes your assessment easier.
It shows effort.
It shows consistency.
It shows that you learned something.
And if nobody has properly explained how to fill your SIWES logbook before now, at least you won’t be standing awkwardly beside your desk while your supervisor flips through empty pages.
That moment comes faster than you expect.
Leave a Reply