Use your own report to prepare questions about: why you chose this topic, why this method, what this table means, what you would change. If you know your project well enough to explain each choice in a sentence or two, you have a useful basis for rehearsal without predicting the panel.
This guide gives you 28 realistic questions grouped by chapter, a structure for answering each, and a plan for the ones you cannot answer. Panel style differs between departments and between examiners, so treat these as patterns to prepare for, not a leaked list. If you are still working out what the day involves, start with what a project defence is and how to prepare for it.
The most useful practice answers come from a report that reflects your own choices. UniDraft helps organise confirmed methods, evidence and guidelines into an editable project document. Start your project document, then use the questions below to check your understanding. You prepare the answers and slides; the software cannot sit the defence or guarantee a grade.
The short answer
- Questions follow your chapters. Expect them in roughly the order of your report: problem, literature, method, results, conclusion.
- Most are "why" questions. The panel wants to see that each choice was deliberate, not that you picked the one "correct" option.
- Answer in four moves: the answer in one sentence, your reason, your evidence, the limit. Then stop.
- Numbers matter. Know your sample size, response rate, main result and headline finding without looking.
- Honest beats impressive. "I do not know, but here is how I would find out" is a respectable answer. A confident wrong one is not.
What the panel is really testing
An oral defence exists mainly to confirm that the work is yours and that you understand it. UK university guides for research students describe examiners as confirming that "the work contained in your thesis is your own" and probing why you chose your topic and methods (Imperial College London; Prospects). Those guides are written for PhD candidates, and they do not establish undergraduate difficulty or procedure. The useful general preparation principle is that the panel is checking ownership and understanding, not trying to catch you out.
In Nigeria this often has a practical edge. The panel may include your supervisor, another lecturer from the department, and sometimes an external examiner who has never seen your work. The second and third are reading it cold, so their questions tend to be about clarity: "Explain this in simple terms" or "What exactly did you measure?" Prepare for both the friendly question and the sceptical one.
How to structure any answer
Use four moves, in this order.
- The answer, in one sentence. "I used a survey because my objective was to measure opinions across many students."
- The reason. "An experiment was not possible, and interviews would have limited how many people I could reach."
- The evidence from your project. "I collected [number] responses, with a response rate of [percentage]."
- The limit. "The trade-off is that this questionnaire alone cannot establish a causal explanation for the responses."
Stop there. Panels often ask a follow-up if they want more, and a short, complete answer invites the follow-up you have prepared for instead of burying you in detail you did not need.
Every model answer below uses placeholders in square brackets. Replace them with what you actually did. Do not lift an answer that describes work you did not do: a follow-up question will expose it, and it is exactly the situation the defence exists to test.
Opening and overview questions
1. "Briefly tell us about your project." This is usually the first question, and it is a gift. Give a 60-to-90-second answer: the problem, what you did, the main finding, the conclusion. Practise it aloud until it is smooth. If you also have slides, how to open a seminar or defence presentation covers the first minute in more detail.
Model shape: "My project addresses [problem] among [population]. I [method] and found [main result]. This suggests [conclusion], and I recommend [main recommendation]."
2. "Why did you choose this topic?" Give a real reason: something you saw during SIWES, a local problem, a course that interested you. The panel is looking for ownership. If you picked the topic because your supervisor suggested it, say that too and then explain why you came to find it worthwhile.
3. "What is the main contribution of your work?" Say what your project adds in concrete terms: an evaluated function under stated conditions, evidence from a defined population, or a justified comparison. Avoid grand claims. A small, accurate contribution beats an inflated one.
Chapter 1 questions: problem, objectives, scope
4. "What problem are you solving, and who has it?" Name the problem, the people affected, and the evidence that it exists (a statistic, a report, your own observation). Your statement of the problem should already contain this; be ready to say it out loud in two sentences.
5. "How do your objectives relate to your research questions?" Each objective should map to a question, and each question to something you measured or built. If you can say "objective 2 was answered by Table 4.3", you are in good shape. If your objectives and questions do not line up, fix your wording of the link rather than pretending, and see how to write research questions and objectives for what a clean match looks like.
6. "Did you achieve your objectives?" Go through them one by one. If one was only partly met, say so and explain why. This is a common place to lose marks by claiming everything was achieved when Chapter 4 shows otherwise.
7. "Why did you limit the scope to [place/group/period]?" Give the practical and methodological reason: time, access, cost, or a deliberate choice to keep the study manageable. Then admit the consequence: your findings apply to that setting, and you cannot claim more.
8. "Why should anyone care about this?" A blunt but common question. Tie your answer to a real beneficiary: students, a clinic, a small business, a department. One concrete sentence works better than a paragraph on "national development".
Chapter 2 questions: literature and framework
9. "How does your work relate to [a specific study]?" The panel may name a study from your own list. Say what that study actually established, how yours differs (population, method, time, place), and whether your results agree. Knowing your five most important sources properly is better than half-knowing forty. The habits behind a strong review are in how to write the literature review.
10. "What gap does your study fill?" State the gap plainly: "Existing studies looked at [X] in [other setting]; I found none in [your setting]." Never claim "no one has ever studied this" unless you searched thoroughly. Say "I could not find" instead.
11. "Why did you choose this theoretical or conceptual framework?" Explain what the framework helped you do: choose variables, structure questions, interpret results. If you are unsure of the difference between the two, read conceptual vs theoretical framework before the defence, because examiners like to test it.
12. "Define [key term] in your own words." This is the terminology check. Give the definition you used in the project, then a short example. Do not skip preparing these because they look easy; they are the questions students most often stumble on because they never said the definition aloud.
13. "Where did you get this claim, and is the source reliable?" Be ready to open your reference list and show a real source: author, year, and what it said. If a citation looks doubtful, you can check it in the citation finder before the day rather than discovering a problem in the room.
Chapter 3 questions: methodology
Prepare to justify the method and its limits; this guide has no measured ranking of which chapter is questioned most.
14. "Why did you choose this method over [alternative]?" Use the four moves. Resource limits, fit with your question, and precedent in the literature are all legitimate reasons. The panel is checking that the choice was deliberate. See how to write the methodology chapter for the reasoning each design choice should carry.
Model shape: "I used [design] because my question asked [what/how many/what relationship]. [Alternative] would have [limitation for my situation]. The trade-off of my choice is [limit]."
15. "How did you determine your sample size?" Give the population, the formula or rule you used, and the result. If you used a formula, know its inputs. If you used a convenience sample because access was limited, say so honestly and state the effect on generalising. The logic is set out in how to calculate sample size.
16. "How did you select your respondents?" Explain the sampling method in plain words, for example random, stratified or purposive, and why it suited your study.
17. "How do you know your questionnaire measures what you say it measures?" This is validity and reliability. Say who reviewed the instrument (your supervisor, an expert), whether you piloted it, and what reliability figure you obtained if you calculated one. Never quote a Cronbach's alpha you did not compute. Questionnaire validity and reliability explains what to check.
18. "Why did you use this statistical test?" Match the test to the data type and the question: comparing groups, testing association, describing frequencies. If you cannot name the assumption behind your test, revisit which statistical test fits your project before the defence.
19. "What ethical steps did you take?" Consent, anonymity, permission from the institution or organisation, and secure handling of the data. If your study involved people, expect this question.
20. "Could someone repeat your study from what you wrote?" Say yes only if it is true. Point to the sections where your procedure, tools and analysis steps are described.
Chapter 4 questions: results
21. "Explain this table or figure to us." Panels often flip to a page and point. Practise reading your three or four key tables aloud: what the rows and columns are, what the highest and lowest values are, and what they mean for your question. Never just read the numbers. Say what they show.
Model shape: "This table shows [what is compared]. The main pattern is [highest/lowest/difference], which means [interpretation for objective X]."
22. "Why is this result surprising, or different from other studies?" Do not get defensive. Offer a real explanation, even a tentative one: a different population, a smaller sample, a change in the setting, a measurement limitation. Then say you cannot be sure, and what would test it. See how to write the results chapter for how to present findings that hold up under this kind of questioning.
23. "How do you know this result is not by chance?" If you ran a significance test, state the result and what it means in plain words. If you only reported descriptive statistics, say so and do not claim more than description supports.
24. "What happened to the responses you did not use?" Be ready with the number of questionnaires distributed, returned, and usable, and the reason any were discarded.
Chapter 5 questions: conclusion and reflection
25. "What are the limitations of your study?" Name two or three real ones: sample size, single location, self-reported data, time. Then say how each affects your conclusions. Owning your limitations shows you understand your own work. Chapter 5: discussion, conclusion and recommendations covers where limitations belong in the report.
26. "What would you do differently if you started again?" This is expected, not a trap. Give one or two specific changes: more time on data collection, a larger or more varied sample, a different tool. Vague answers such as "I would do everything better" read as unreflective.
27. "Are your recommendations realistic? Who would act on them?" Tie each recommendation to a specific finding and a specific actor, such as the department, a hospital unit or a school administrator. A recommendation with no owner is easy to challenge.
28. "What further research does your work suggest?" Offer one or two next steps that follow from your limitations: a larger sample, another location, a longer period.
When you do not know the answer
If a question goes beyond what you can answer, That is normal, and how you handle it shows more about you than a perfect answer would.
- Take a breath. A short pause reads as thoughtful. Panels are used to it.
- Ask for it to be repeated or rephrased. St Andrews' guidance for research students notes that you can ask for clarification and take time to think.
- Say plainly that you do not know. Imperial College London's guide puts it simply: be honest and say so.
- Reason from what you did. "I did not test that directly, but in my data [related finding], so I would expect..."
- Say how you would check. "I would look at [source or method] and confirm with my supervisor."
What not to do: invent a citation, claim a result you did not obtain, argue with the panel, or blame your supervisor. A student who bluffs and is caught loses credibility on every earlier answer too.
If a panel points to a real mistake, such as a wrong figure or a misplaced label, acknowledge it, explain the effect on your conclusions, and say how you would correct it. Errors noted at the defence usually come back to you as corrections to make, so it helps to know how to manage supervisor corrections without losing earlier work.
Common mistakes students make
| Mistake | What the panel hears | Better |
|---|---|---|
| Reading answers from a page | You do not own the work | Use a card of key numbers only |
| Answering a different question | You did not listen | Repeat the question back briefly |
| Long, unfocused answers | You are avoiding the point | One-sentence answer first |
| Claiming "no limitations" | You have not reflected | Name two real ones |
| Defensive tone at criticism | You cannot take feedback | "That is a fair point; here is my reasoning" |
| Not knowing your own numbers | Someone else did this | Memorise five key figures |
| Guessing when unsure | You may bluff elsewhere | Say so, then reason aloud |
A one-week preparation plan
- Seven to five days before: re-read your whole report as if you were the examiner. Highlight every choice you made and write one sentence of reasoning next to it.
- Four to three days before: go through the 28 questions above and answer each aloud, using your real numbers. Record yourself on your phone if you can.
- Two days before: do a mock defence with a friend or your coursemates. Ask them to interrupt with follow-ups. If your department offers a rehearsal, use it. How to prepare a defence presentation covers the slides and talking points.
- The day before: confirm the time, venue and what to bring (printed copy, laptop, any required forms). Sleep.
If you are a SIWES student rather than a final-year project student, the questions come from your logbook instead; how to defend your SIWES report covers that case. And if you are worried about the worst case, what happens if you fail your final year project explains the usual next steps.
Where UniDraft fits in
Good defence answers depend on a project you understand, built from choices you actually made. UniDraft builds your final-year project as an editable Word document around your confirmed topic and your own real results, applying project/supervisor instructions, student-confirmed guidelines, department patterns, university baselines and platform defaults, in that order. It never invents results, sources or approvals, and you must verify the final wording against the work you can explain. It does not write your presentation slides or guarantee grades. Correction rounds produce new versions while earlier versions are kept; check current included rounds before checkout, so you can see what changed before you walk in. You can also check a draft's font, spacing and margins with the free formatting checker before you submit.
Sources
- Prospects (Jisc): How to pass your PhD viva -- examiners confirm the work is yours and probe why you chose your topic and methods; acknowledge what you do not know rather than guess. Written for PhD candidates.
- Imperial College London: The viva -- examiners establish that the work is your own; if you do not know an answer, be honest and say so.
- University of St Andrews: The viva -- you can ask for clarification, take time to think, and say so if you do not know.
These are postgraduate-level guides, used here for the general logic of oral examinations. Your own department's defence format and panel may differ, so confirm with your supervisor or project coordinator.