A SIWES defence is an oral review of the training documented in your report and logbook, where your institution requires one. Whether you have a defence at all depends on your institution, so start by finding out, then prepare from your own logbook rather than from a list of memorised answers.
Prepare from a report you can trace back to real work. UniDraft helps organise your confirmed activities and guidelines into an editable SIWES report, giving you a written account to review against your logbook. Start your SIWES document with UniDraft. You still prepare the talk, explain your role and verify every claim; it does not create slides or defend for you.
The short answer
- A defence is not universal. Some institutions assess SIWES from the logbook, report and employer's assessment alone; others add an oral presentation in the department. Confirm which applies to you.
- Confirm the actual format. Ask for the duration, required materials and assessment criteria; this guide supplies no universal length or weight.
- Questions come from your own documents. Expect "what did you do in week 9?" more than textbook theory.
- Preparation starts on placement. A logbook written honestly and regularly is the best revision material you will ever have.
- Honesty beats polish. An accurate account of a difficulty is worth more than a claim that everything went perfectly.
Does SIWES actually have a defence?
This varies, and no single national rule settles it. SIWES was instituted by the Industrial Training Fund (ITF) in 1973 and is a tripartite programme involving students, institutions and industry, described by that university in its scheme history (see the University of Ilorin's SIWES history page). What happens after you return is decided largely by your institution and department.
In practice you will meet one of three set-ups:
| Set-up | What it looks like | What you should do |
|---|---|---|
| Written only | Coordinator reviews logbook, report and employer's assessment; no oral component | Make the documents accurate and complete |
| Informal review | A short conversation with your coordinator about the placement | Be able to describe your work in plain language |
| Formal defence | Presentation and questions before a departmental panel, sometimes on a set date | Prepare a short talk and rehearse answers from your logbook |
Where a review or defence exists, it is normally one component alongside the logbook, the report and the industry supervisor's assessment. Some programmes score it and some treat SIWES as pass or fail, so read how SIWES is graded and then ask your coordinator for your own school's breakdown. Do not trust a percentage split from a blog or WhatsApp group.
To find out what applies to you, check in this order: your SIWES handbook or unit page, the departmental notice board, then your departmental SIWES coordinator. Ask three direct questions: Is there an oral review? What is its format and length? Am I expected to bring slides, or only the logbook and report?
What the SIWES unit already checks before you reach the panel
Before any defence, documents are usually checked. Rivers State University's SIWES unit page, for example, says the industry-based supervisor is required to endorse the logbook every week and that departmental coordinators supervise students at their locations at least twice before the attachment ends. It also states that allowance payments go only to students who submit completely filled logbooks, Forms 8 and technical reports within the stipulated time (Rivers State University SIWES Unit). These are that university page’s instructions; confirm the current schedule and documents for your own programme.
That matters for your defence because a panel that has seen your visit notes and your signed logbook already has a picture of you. Your job is to make your spoken account match it.
What a SIWES review or defence typically covers
Use these original preparation areas to review your evidence; they are not a prediction of a panel’s questions:
- What you actually did. Specific duties, tools, machines, software or procedures, not general categories like "assisted the engineers".
- What you learned, and how it connects to your programme and the courses you have taken.
- Challenges you faced and how you handled them.
- The organisation itself. What it does, how your unit fits in, who supervised you. This confirms you engaged with the workplace.
- Your documents. Why a particular entry says what it says, or how a diagram in your report was produced.
- Professional conduct and safety, especially for engineering, laboratory, health and agriculture placements.
A useful trick: open your table of contents and turn each heading into a question. "Organisation Overview" becomes "Tell us about the company." "Description of Work Done" becomes "Walk us through your main tasks." "Problems Encountered" becomes "What went wrong?" You now have a practice list tied to your actual report.
How to prepare, step by step
1. Reread your logbook the way a panel would
You should be able to describe any week without opening the book. Read it in order, mark the five entries where you learned the most, and mark any entry you cannot explain today. Those are your revision priorities. A logbook filled during the placement is far easier to speak from than one reconstructed at the end, so if yours is thin, see how to fill your SIWES logbook before the defence date, not after.
2. Reread your report against your logbook
Check that every claim in the report has a matching logbook trail. If the report says you configured a network switch, the logbook should show when. The report is normally built from the logbook, and how to write a SIWES report explains that route in detail. Fix mismatches in the documents where your institution allows, and know them well enough to explain honestly where they exist.
3. Build a one-page cheat sheet, not a script
Write one page with:
- the organisation's name, location, and what it does in two sentences;
- your department or unit, and your supervisor's name and role;
- your five main tasks, each in a line;
- two difficulties and what you did about them;
- three things you would tell the next student.
Memorising a script produces the blank stare when the panel interrupts. Knowing a page of facts lets you answer in your own words.
4. Prepare five tasks using a four-part answer
For each major task, be ready to give: the task, your action, the result, and the link to your course. Practise a concise answer, then add detail where the actual question requires it.
5. Prepare your talk if slides are expected
If your department asks for a presentation, the structure is usually simple: who you are and where you trained, what the organisation does, what you did, what you learned, challenges, recommendations, and questions. How to start a seminar or defence presentation covers the opening, and the slide-by-slide seminar structure guide shows one way to lay out a deck. Be clear about one thing: UniDraft does not create slides or presentation content, so you would build the deck yourself. If your department only wants the logbook and report, do not spend the week designing slides nobody asked for.
6. Rehearse aloud, once with a friend
Reading silently feels like preparation but is not. Explain your placement to a course mate outside your department and ask them what was unclear. If a classmate cannot follow it, a panel probably cannot either.
A one-week preparation plan
| Days before | What to do |
|---|---|
| 7 | Confirm the format, venue and time; collect your logbook, report and any coordinator's letters |
| 6-5 | Reread the logbook; mark the entries you cannot yet explain |
| 4 | Reread the report against the logbook; write the one-page cheat sheet |
| 3 | Draft answers to the ten most likely questions (below); prepare slides only if asked |
| 2 | Rehearse aloud with a friend, timed |
| 1 | Print spare copies; lay out clothes; sleep |
| Day | Arrive early, carry originals, listen fully before answering |
Ten questions to prepare for (and what each one is really testing)
- "Tell us about your placement." Tests whether you can organise your experience. Give organisation, unit, duration, and main focus in under a minute.
- "What was your typical day?" Tests whether the logbook is real. Describe a specific day, not an idealised one.
- "What was the most important thing you learned?" Pick one concrete skill and one link to a course.
- "Which task are you proudest of?" Use the four-part answer.
- "What challenges did you face?" Name a real one: a shortage of equipment, an unclear instruction, a mistake you made and corrected.
- "How does this relate to your course?" Name a course, a topic, and where the gap between the classroom and the workplace showed.
- "Explain how [tool, process or machine you used] works." Tests depth. If you only observed it, say so and explain what you understood.
- "What would you do differently?" Tests reflection. Something practical works best, such as asking for a wider rotation of tasks or keeping fuller daily notes.
- "What recommendations do you have for the organisation, or for the scheme?" Keep them constructive and specific.
- "Why did you write this in your report?" Tests authorship. If it is yours, you can explain it.
For more general oral-exam preparation, project defence questions and how to answer them covers the pattern of follow-up questions, although a SIWES review is usually shorter and more practical than a final year project defence.
Answering well under pressure
Listen to the whole question. Nervous students often start answering the first half. Pause for a second, then answer.
Answer the question asked. If asked "what did you do?", do not deliver a five-minute description of the company.
Use "I" for what you did and "we" or "the team" for what was shared. Panels get suspicious when everything is "we", and equally when a ten-person project sounds like your solo effort.
Be honest about observation versus doing. Many SIWES placements involve watching before doing, and that is normal. "I observed the technician calibrate it and then assisted with the second unit" is a strong, truthful answer.
Admit what you do not know. A short "I did not handle that, but here is what I understand" is far better than an invention. Never claim tasks, certifications or supervisor approvals you do not have. If a panel member catches one false claim, they will doubt everything else.
Deal with hostile or vague questions calmly. If you do not understand a question, ask the panel to rephrase it. That is normal.
Common mistakes and how coordinators spot them
| Mistake | How it shows up | Fix |
|---|---|---|
| Vague duties ("assisted staff") | Panel asks "assisted with what?" and you have no example | Prepare five specific tasks with details |
| Logbook filled at the end | Entries sound identical; dates do not fit what you describe | Be honest about it; describe the real work in your own words |
| Report copied from another student's | You cannot explain sections or diagrams | Use only what you actually did; rewrite in your own words |
| Memorised speech | You freeze when interrupted | Use a cheat sheet, not a script |
| No knowledge of the organisation | You cannot say what the company sells, does or regulates | Read the company profile, ask a colleague, or use their public materials |
| Overclaiming | Claiming to have designed what you only assisted with | Say exactly what your role was |
| Formatting problems | Format does not match the confirmed instructions | Run the .docx through the formatting checker early |
Formatting is worth a note. Confirm any submission prerequisites with your coordinator and use the free formatting checker or your university's format guide. For a wider view of what departmental reviewers look for, see submitting an IT report that passes departmental review.
What to do when things go wrong
- Your logbook has gaps. Do not fabricate entries. Tell your coordinator early, and reconstruct only what you genuinely remember, following your institution's rule on late or corrected entries.
- Your supervisor never signed off some weeks. Raise it with your coordinator before submission, not at the defence. Coordinators have usually dealt with it before.
- Your Form 8 is incomplete. The SIWES unit and your coordinator need to know now; see what SIWES Form 8 is and who fills it.
- Your placement ended early or changed. Report it as soon as it happens and be ready to explain the gap plainly.
- You freeze in the room. Ask for a moment, take a breath, and restart with your one-line answer to the question. Panels have seen nervous students before.
- You did not get relevant work. Say what you were given, what you learned anyway, and what you did to seek more responsibility.
SIWES vs IT: same thing?
In everyday use, yes. SIWES is the formal scheme name, and "IT" (Industrial Training) is the shorthand students commonly use for the same requirement. Some departments use "IT" for the course code or report, so use whichever term your handbook uses when you email your coordinator.
How this differs from a final year project defence
A final year project defence tests your research: your problem statement, method, results and conclusions. A SIWES review tests your experience: what you did, what you learned, and how it connects to your training. Expect less theory and more "show us you were there." If your institution's SIWES review leans formal, project defence preparation is worth skimming for tone and etiquette, but do not prepare for it as if it were a research viva.
Practise one task with the evidence closed
Choose an activity you actually did and explain its purpose, your role, the steps, the outcome and one thing you would handle better next time. Then reopen your report and logbook. Did your spoken account match them? Correct a mistaken statement rather than memorising a more impressive version.
Ask a friend to interrupt with "Why that step?" and "What did you personally do?" If you cannot answer, return to the task notes or ask your supervisor for clarification. Use the SIWES-specific slide plan to select evidence for the talk and the abstract guide to check your short overview. Neither should introduce activities missing from your records.
Where UniDraft fits in
UniDraft cannot defend for you, and it does not create slides, fill Form 8, or sign logbook entries. What it does is build your written SIWES report as an editable Word document from your own logbook and placement details, in your university's format, with the department's and supervisor's instructions applied. Review that account against your records before rehearsing. Check the current SIWES price and included correction rounds before checkout. If your coordinator asks for changes before the review, you supply the instructions, confirm what was extracted, and a new version is produced while earlier versions are kept.
Sources
- University of Ilorin SIWES: History -- SIWES instituted by the ITF in 1973; tripartite structure; joint ITF and NUC coordination.
- University of Ilorin SIWES: Guidelines -- SIWES described as a skills training programme preparing students for the industrial work situation.
- Rivers State University: SIWES Unit -- weekly logbook endorsement, coordinator visits, and required submissions of logbook, Form 8 and technical report.
- National Open University of Nigeria: SIWES -- an example of a university unit that processes students' logbooks and reports at completion.
