13 July 2026 · 6 min read
Whether it's a dissertation viva or a final-year project defence, the examiners' goal is the same: to confirm the work is yours and that you understand the decisions inside it. That's good news, because it makes most questions predictable — they come from your own document.
Write out answers to these five, then practise saying them aloud — spoken answers come out differently than written ones, and the difference is what rehearsal fixes.
A week before, re-read your dissertation or report with a pen, marking every decision point: why this sample size, why this framework, why this database. Each mark is a potential question. If you find a weakness, prepare an honest response — examiners almost always respect "that's a limitation, and here's how I'd address it" over a defensive answer.
You will get at least one. The wrong move is bluffing — panels detect it instantly and dig deeper. The right move: pause, think aloud about how you'd approach it, and connect it to what you do know. "I didn't examine that directly, but based on my findings I'd expect..." turns a gap into evidence you can reason in your field.
Run everything locally with prepared demo data — never depend on venue wifi or a live server. Rehearse a fixed demo path that shows each major feature, and keep a screen recording as backup. Test on the machine you'll actually present from.
Bring an annotated copy of your work. Listen to the full question before answering, and it's fine to ask for a rephrase. Remember that criticism of the work isn't criticism of you — engaging thoughtfully with a challenge earns more respect than agreeing with everything. Panels pass students who understand their own work, and by definition, nobody knows yours better.
Want a mock viva? Assignment Byte's academics can read your submission and grill you on it before the real panel does — message us on WhatsApp.