Somewhere in your bag there is a SIWES logbook with two weeks filled and eleven weeks empty, and your plan is to fill everything the weekend before submission. That plan fails every year, and it fails in a way your supervisor can see from across the room. One pen, one ink, one handwriting mood, thirteen weeks. Nobody writes thirteen weeks in one sitting without it showing.
So this guide is about how to fill your SIWES logbook properly with about ten minutes a day, and what to write on the days when nothing seemed to happen. And if you are already in the last month with a nearly empty book, there is a section down there for you too, no judgement. Some schools print it as a SIWES log book, two words on the cover. Same book, same rules.
What the logbook is actually for
The logbook is the evidence. Your report will make claims about what you did for months, and the logbook is the signed record those claims stand on. When a marker doubts a report, the first thing they open is the logbook, and a report that says one thing while the logbook says another loses the argument every time. SIWES itself is run by the Industrial Training Fund, but the logbook in your hand belongs to your school’s process, so whatever your SIWES unit says about filling it beats this guide and every other guide.
The two-book system, and why it works
Do not write into the logbook directly during the day. Buy a cheap jotter and carry that instead. During work, scribble what you did into the jotter the way it comes: rough, quick, with the names of machines, software, forms and people’s corrections while they are still fresh. Then once a week, sit down and copy the week neatly into the real logbook, in your best handwriting, before your supervisor signs it.
The jotter is doing three jobs at once. It keeps the real logbook neat, because nobody’s desk handwriting at 4pm is their best. It protects you from the ruined-page problem, because a mistake in the jotter costs nothing while a mess in the logbook stays there till submission. And it means the details survive. The name of the reagent, the error code, the account number format you were taught, those are gone by Saturday if they were never written down on Tuesday.
What a daily entry should look like
The entries that fail are the vague ones, and everybody writes the same vague ones. Look at the difference.
Weak: “Worked in the office.” Instead: “Sorted and filed payment vouchers for the week, checked each one carried an approval signature, and registered them serially in the voucher file.”
Weak: “Did practicals.” Instead: “Prepared culture media under the supervision of the laboratory scientist, sterilised it in the autoclave at the stated pressure, and poured plates for the next day’s samples.”
Weak: “Worked on the computer.” Instead: “Installed Windows and the office antivirus on two new systems, created staff user accounts, and connected both systems to the departmental printer.”
Same days. Same work. The difference is that one version names the task, the tools and the point of it, and the other names nothing. Write the specific version, one to three lines per day, and Chapter Three of your report will practically be sitting in the logbook waiting for you.
How to fill a SIWES logbook on the slow days
Every placement has days where you swept, waited, or watched. Students panic on those days and either leave the line blank or invent something, and both are worse than the truth. A slow day still gives you a real entry. You observed a procedure, so write that you observed it and what it involved. You read the organisation’s safety manual or standard operating procedure, write that, it is real training. You cleaned or arranged equipment, write it and name the equipment. “Observed the monthly bank reconciliation being performed by the accounts officer and noted the causes of the differences” is an honest entry that earns more respect than a fabricated one, because supervisors know what their own office looked like that day.
Pen, pencil and the correction fluid rule
The common practice across Nigerian institutions is blue or black pen for the entries and a sharp pencil for sketches and diagrams, and if your school’s own instruction says something different, your school wins. What gets students into trouble is the third item: correction fluid. Many schools treat correction fluid in a logbook as unacceptable, because a logbook is a record and a record you can paint over is not a record. This is exactly why the jotter comes first. Make your mistakes in the jotter, where they cost nothing, and let only the settled version enter the logbook in ink. For diagrams, draw the outline lightly in pencil, get it right, then neaten it. If you are unsure of an entry, you can pencil it faintly and ink over it once your supervisor has seen it, but ask your SIWES unit before making that a habit, because some schools want ink only.
Diagrams are cheap marks sitting on the table
Most logbooks have space for sketches, and most students leave it empty. Draw. The layout of the network cabinet, the flow of a voucher from request to payment, the parts of the machine you maintained, labelled in your own hand. One clear labelled sketch a week does two things: it fills the book with evidence nobody can fake in one night, and it shows the marker you understood the thing well enough to draw it. You do not need to be an artist. You need a ruler and honest labels.
Signatures: weekly, not once at the end
Take the logbook to your industry supervisor at the end of every week, or at whatever rhythm your school’s own instruction states, and let them sign while the week is still fresh in both your memories. Do not save fourteen weeks of signing for the final Friday, because you are betting your logbook on your supervisor being present, patient and willing that one afternoon, and people travel, offices get busy, and some supervisors will simply refuse to sign a stack of history they cannot remember. And never, ever sign for them. A forged signature turns a weak logbook into a misconduct case, and no logbook is worth that.
If your programme is eight weeks, or you started mid-week
Not everybody does six months. Some programmes run a few months, some run weeks, and the book is filled the same way regardless: real dates, real entries, however many weeks yours lasted. If you started on a Wednesday, your first week is Wednesday to Friday and you write exactly those days rather than inventing a Monday. If a public holiday or a strike ate a day, write the date and the fact plainly. Days you were absent stay honest too. A ruled line through a day you did not work reads far better than fiction, because the logbook’s whole value is that it is true. Where your school gives a specific instruction for short or broken weeks, that instruction wins, so ask your SIWES unit rather than guessing.
The common mistakes, and how to avoid each one
Mistake one: filling the whole book in one night and hoping nobody notices. Markers have seen thousands of logbooks. One ink, one pen pressure, one handwriting mood across three months, they notice in seconds. The fix is the ten minutes a day this guide is built on, and if it is already too late for that, the next section is for you.
Mistake two: copying a coursemate’s entries. The two of you will submit to the same department, the two books will sit on one desk, and identical entries sink both owners at once. Share ideas if you like, but write your own days from your own jotter.
Mistake three: claiming hands-on work on procedures you only observed. One question from the supervisor exposes it, and everything else in the book becomes suspect after that. Write observed when you observed, and the honest entry will carry you further.
Mistake four: leaving whole weeks blank to fix later. Later never comes, and blank weeks in a signed book raise questions no explanation settles. Write the week while it exists, even the thin ones.
Mistake five: correction fluid. Covered above, and worth repeating because it is the one mistake that cannot be undone: mistakes belong in the jotter, ink belongs in the book.
Mistake six: losing the book itself, which happens to somebody every single year. So photograph every filled page with your phone at the end of every week. If the logbook ever disappears on a bus, those photos are the difference between a bad day and a lost semester.
If the programme is almost over and the book is still empty
Let us be honest about how this usually goes: plenty of students meet this page in the last month, with a nearly empty logbook and a plan to fill everything in one seating. If that is you, here is how to come out of it with a book you can defend.
First, gather your evidence before you write anything. Your phone gallery knows what you did; so does your chat history with colleagues, the rough jotter you half kept, your email, and the memory of the people you worked beside. Sit with all of it and rebuild the programme week by week on rough paper, real tasks against real dates, and ask a colleague from the placement to check your sequence where you are not sure.
Second, spread the copying over several days, not one exhausted night. Write in the day, rest your hand, come back. You are not doing this to disguise anything; you are doing it because week nine deserves the same care week one got, and a tired hand at 2am gives it none.
Third, reconstruct, never invent. Write the tasks that happened, mark the days you genuinely cannot account for rather than decorating them, and do not manufacture procedures you never touched. Then take the book to your industry supervisor, tell them the truth, and let them sign what they can stand behind. A supervisor will forgive a student who fell behind and rebuilt honestly. What nobody forgives is fiction, and a marker only needs one invented entry to stop trusting all the rest.
The logbook becomes the report
Fill your SIWES logbook the way this guide describes and the report at the end stops being frightening, because every signed week becomes a paragraph of your experience chapter. When that time comes, our complete SIWES report format guide carries the whole structure, and if you want your own course’s angle, we have guides for accounting students, computer science students and laboratory placements.
And if the training is already over, the logbook is thin, and the report deadline is real, talk to us. Tell us what you actually did and what your department asked for, and we’ll help you put it on paper properly. Ten minutes a day, that’s all this book ever wanted.