The question bank: 42 defense questions by committee role
Quick answer: almost every defense draws its questions from three seats. The chair probes the claim — what the thesis says, why it matters, what is new. The methods examiner probes the evidence — design, sample, measurement, validity. The outside reader probes the translation — plain language, practical stakes, scope. Prepare one honest answer skeleton per question below, rehearse them with the three-part pattern from the next section, and the follow-ups take care of themselves.
Where do defense questions actually come from? From the document, mostly. A committee reads your thesis with a pencil looking for the sentence that carries the most weight, then asks you to defend it. The rest come from roles: whoever chairs the session guards the argument's shape, the methods specialist guards the evidence, and the outside reader — the one from a neighboring field — guards the claim's reach. A question you have already written an answer for stops being a threat and becomes a scoring opportunity.
Two sibling pages touch this ground, and this page takes over from both. The thesis proposal guide carries six question flip cards that preview the proposal-stage defense, and the college thesis guide packs an eight-item pre-defense checklist plus a short paragraph on the ten-to-twenty-minute undergraduate format. What neither has room for — the full bank, the answer frameworks, the scoring rubric — lives here. If the defense ahead of you is the short undergraduate kind, start with that sibling's format notes and come back to this bank for the questions; if you are defending a built deliverable rather than an argued claim, the capstone paper guide maps how a project write-up turns into defense talk, because artifact questions follow different physics.
How to use the bank: the skeletons below are starting frames, not scripts. Examiners hear a memorized paragraph in the first ten words. Write your own version of each skeleton in your own voice, then run it through the answer builder in the next section. And note — every defense follows its department's own rules, so the handbook and your supervisor's advice outrank anything on this page.
Showing 42 of 42 questions.
The chair and supervisor: claim, contribution, consequence
The chair keeps returning to the argument's chain — what each chapter contributes and where the claim sits. That chain is planned, not found, and the thesis introduction guide shows how the opening chapter states it so these questions have obvious answers.
- In one sentence, what is this thesis's answer? — Say the claim verbatim from your conclusion. No history, no hedging, one sentence.
- Why is this question worth a thesis? — Name who needs the answer and what changes once it exists. "Interesting" is not a stake.
- What is genuinely new here? — One sentence on the combination, case or time window that was not available before. New does not have to mean world-changing.
- How does chapter three move the argument forward? — State the chapter's one job in the argument chain, then the finding it banks.
- Which finding does the whole thesis stand on? — Name the load-bearing result and where it lives: the table, the page, the section.
- If you had one more month, what would you add? — Pick the item you cut during scoping, say why it lost, and what it would settle.
- What did you change your mind about during the work? — One honest reversal plus the evidence that flipped it. Certainty that never moved reads as unrevised.
- Where does your literature stop covering the ground? — Point at the exact seam your two reading clusters leave open. That seam is your question.
- Who will disagree with this thesis most? — Name the school or reader, state their strongest objection fairly, then give your one-line response.
- What would falsify your answer? — Name the evidence that would break the claim. An answer that cannot be wrong cannot be right.
- Explain the thesis to someone outside your field. — Thirty seconds, one everyday example, zero jargon. Rehearse it; this opener arrives almost every time.
- What are you most proud of here, and what embarrassed you? — One of each, with the reason. The embarrassed half is where the credit gets earned.
The methods examiner: design, data, and the validity audit
The methods examiner has read your chapter four with a red pen and asks about rules, not results. Every good answer here is a rule stated plainly plus its cost admitted — the pattern is always "here is the rule, here is what it excludes, here is why the answer holds anyway."
- Why this method and not the obvious alternative? — Name the alternative, then the one concrete mismatch — access, scale or question shape — that ruled it out.
- How did you choose your sample or corpus? — State the frame, the size, the window and the selection rule, then the cost of that rule.
- What are the limits of your sample? — Two limits, each paired with the reason the answer still holds inside it.
- How did you handle missing or messy data? — Give the rule you applied consistently and the number of cases it touched.
- Are your categories your own? — Say which codes came from the literature and which emerged from the data, one example of each.
- How reliable is your measurement or coding? — Name the check you ran — second coder, retest, triangulation — and what it showed.
- Is your case representative of anything? — Do not claim representativeness. Claim what the case is an instance of.
- Could your result be coincidence? — Point at the size of the effect or the repeated pattern, never just at a threshold.
- What did you measure, and what did you interpret? — Separate the measured variables from the interpreted ones, and own the interpretation.
- Why did you stop collecting data where you did? — Give the stopping rule — saturation, window, budget — as a rule, not a feeling.
- How would a different design change the answer? — One sentence on what the alternative would see that yours cannot.
- Which result surprised you, and how did you check it? — The surprise first, then the verification step that made it survivable.
- Is the evidence strong enough for the claim? — Match them, or soften the claim. Softening earns more credit than defending.
- Did ethics constraints shape the findings? — State what clearance allowed, what it excluded, and where the exclusions show up in the answer.
- What is the biggest threat to validity here? — Name it before the examiner does, then the design feature that contains it.
The outside reader: translation, scope, and the referee's eye
The outside reader is the referee from the neighboring field who checks whether your claim travels. Their questions look softer and cut deeper: translate this, justify the reach, show me a real example. Jargon dies in this seat.
- Why should anyone outside your subfield care? — Translate the finding into the neighboring field's problem, in that field's own words.
- Explain your key term without the jargon. — A plain-words definition plus one example. The term you skip over is the one you get asked about.
- What is the practical implication of this work? — One concrete reader — a teacher, a planner, an engineer — and the thing they would do differently.
- How does this connect to what my field knows? — Find the bridge concept and name the shared ground before you claim the difference.
- Which chapter is the weakest, and why? — Name it yourself, with the reason and the fix you would budget for.
- What would a referee in my area flag first? — The two-line version of your limitations section, delivered without flinching.
- Does your title still describe the thesis? — Read the title against the final answer. If it drifted, offer the better title on the spot.
- Where else could this question be asked? — One other setting, population or corpus where your method would travel intact.
- What does the thesis not explain yet? — The loose end, honestly held, plus the reason it sat outside the scope.
- Whose framework are you standing on? — The lineage in two or three names, and what you took from each.
- What would you do differently if you started today? — One specific design change and its reason. Not a list of regrets.
- Is the conclusion bigger than the evidence? — Either defend the reach or trim the sentence. Scope auditors win this exchange every time.
- Can you give a real example of the phenomenon? — One worked example from your own data, with actual numbers if you have them.
- What should the next student on this topic read first? — Two sources, in reading order, each with a one-sentence reason.
- Why did this question keep you up at night? — One honest sentence about the stakes. The committee is listening for the scholar, not the machine.
One warning travels with the whole bank: the dangerous question is rarely the first one — it is the follow-up. Every skeleton above is built to survive a second "why?", which is why each one names a location, a rule or a reason instead of an adjective. If a skeleton of yours cannot survive being asked twice, it is not an answer yet; it is a hope with confidence.
The three-part answer: say it, ground it, bound it
Every strong defense answer runs the same three moves in the same order. Say it: the direct answer in one sentence, first, with no warm-up. Ground it: the evidence location that carries the answer — the chapter, the table, the number of cases. Bound it: the honest limit, stated by you, plus the reason the answer holds inside it. The order is the whole trick. Candidates who bury the claim under two paragraphs of context get interrupted; candidates who state the claim first get to finish.
Why does the third move belong in the answer itself? Because the limitation question is coming whether you volunteer it or not, and volunteering it changes what kind of conversation you are having. An examiner who hears you name your own boundary moves on to the next question. An examiner who finds the boundary themselves now has a discovery to press. Ninety seconds is the target for the full pattern: roughly twenty for the claim, forty for the evidence, thirty for the limit.
One boundary note of its own: if the defense on your calendar is the proposal defense — a smaller committee questioning a plan rather than a finished argument — the thesis proposal guide owns that stage, and its six preview cards cover the feasibility family that dominates there. This page is for the final one, where the work is done and every question lands on finished evidence. The pattern below works for both, but the bank above is final-defense material.
Question from the chair: did the rain gardens actually work?
Why it fails: it opens by praising the question, never states a claim, hides behind "complicated", and ends on "I think" — eighty words that answered nothing. The committee now knows one thing for certain: you do not know your own headline result. Every sentence here is a hedge wearing a sentence's clothes.
Why it works: the claim lands in the first six words, the evidence names its exact home in the document, and the limit is volunteered with the reason the claim survives it. Same topic, same data as the weak version — the entire difference is the three-move order.
The Priya example above is invented for illustration — a master's thesis on campus rain-garden retrofits and storm flooding, with placeholder numbers. No such student, campus or dataset is real. Use the shape, swap in your own claim, evidence location and limit.
The Defense Answer Builder
Pick the question you fear most and build its answer here. The three fields map one-to-one onto the pattern: the direct sentence, the evidence it rests on, and the limit you volunteer. Live counters keep each part inside its spoken range, the preview assembles the full script the way you would say it aloud, and the copy button hands you plain text for your rehearsal notes. Everything stays in your browser, and your work saves on this page for next visit.
Answer Builder — one question, three moves, ninety seconds
Question in → say it / ground it / bound it out → a spoken answer you can rehearse
Assembled script
Spoken length: 0 words, about 0 seconds at a calm pace.
A rehearsal aid, not a script to recite — examiners hear memorization instantly, so keep the bones and use your own words on the day.
Build three or four of these — one chair question, two methods questions, one outside-reader question — and you have rehearsed the pattern enough that unplanned questions start landing in it too. That is the real goal: not a script for every question in the bank, but a reflex strong enough that any question gets the same three moves.
The Mock-Defense Grader
Before you book a practice session with housemates, grade yourself honestly against the ten checks below — four families: the claim, the evidence, the delivery, the limits. Tick only what you could do right now, without notes, standing up. The meter and verdict update as you tick, and your score saves in this browser so you can grade again the night before and watch the number move.
Mock-Defense Grader — ten checks, four families
Tick what you can honestly do today → the verdict tells you what to rehearse
The claim (chair territory)
The evidence (methods-examiner territory)
The delivery (everyone's territory)
The limits (outside-reader territory)
0 of 10 checks banked.
Grade twice: once two weeks out, once the night before. The first pass writes your rehearsal agenda — every unticked box is a session with the answer builder or a read of the relevant chapter. The second pass is a confidence check, and the number matters less than its direction. A score that moved from four to eight means the preparation worked; a score stuck at five means the problem is not knowledge but rehearsal, and the fix is speaking aloud, not reading again.
The day-of checklist
The night before, stop revising by early evening — the last four hours of cramming buy nothing and cost sleep, and sleep is what the panel is actually grading at nine in the morning. Pack once, check the list, and go to bed on the plan. On the day itself, the checklist below is deliberately small: eight items, all logistics, because by now the content lives in you.
- Printed thesis in hand, with sticky tabs on the five pages you will most likely be sent to
- One-page cheat sheet: the question verbatim, three headline numbers, the two limits you will volunteer
- Water, tissues, charger — and the thesis PDF on two devices in case one refuses to cooperate
- Phone silenced, watch alarms off, first two sentences rehearsed aloud once on the walk over
- Arrived fifteen minutes early: room walked, seat chosen, slides loaded if slides exist at all
- One slow exhale before the first answer of every round — pace beats brilliance in defense rooms
- Every answer runs say it, ground it, bound it — direct sentence first, evidence second, limit third
- Closing line ready: thanks to the panel, the one-sentence takeaway, and nothing new introduced
0 of 8 steps.
Two last habits on the day. Take a breath before every answer — a beat of silence reads as thought, while an instant reply reads as rehearsed. And when the panel closes and the room empties, write down every question you were asked before you eat anything: the list is gold for the final corrections, and for anyone you supervise someday. Undergraduates running the short format will find the same rhythm in the college thesis guide, scaled to its ten-to-twenty-minute version.
A five-question defense-prep drill
One correct answer each; a wrong pick reveals the right one. Five for five means the pattern on this page stuck.
1. The chair opens with: "In one sentence, what is the answer of this thesis?" The three-part pattern says your first sentence should be:
2. The "ground it" move points at the exact evidence because:
3. The methods examiner asks why you did not use the obvious alternative design. The strongest reply:
4. The outside reader asks you to explain your key term "without the jargon." You should:
5. "What would you do differently if you started today?" is best answered with:
Rehearsal window shrinking?
A defense rewards preparation and punishes improvisation: questions you never wrote a skeleton for, a claim that wobbles the moment it is spoken, a limit you hoped nobody would find. When the date is fixed and the practice hours refuse to appear, a quoted, deadline-bound writer can take your manuscript, your department's format and the grader on this page, and return feedback built to survive the room.
Questions students ask about defense questions
How many questions are asked in a thesis defense?
There is no fixed number, and any page that promises one is guessing. Short master's defenses often settle into five to ten questions after the presentation; longer doctoral defenses can run through twenty or more, because the committee works through the document chapter by chapter. The number matters less than the coverage: nearly every defense touches why this question, why this method, what the evidence supports, and where the limits sit. The three role groups in the bank above exist so that coverage never surprises you.
What are the most common thesis defense questions?
Three families repeat at almost every defense. The openers: the answer in one sentence, why the question is worth asking, and what is new. The methods set: why this design, how the sample was chosen, where the limits sit, and the biggest threat to validity. The outside-reader set: explain the key term in plain words, the practical implication, and the weakest chapter. Then there is the most common question of all — the follow-up, the one that arrives thirty seconds after whatever you just said, which is why every skeleton on this page is written to survive a second why.
What should I do if I do not know the answer to a defense question?
Use the honest three moves. First, say what you can answer — name the part of the question inside your evidence. Second, answer that part properly, with the same say it, ground it, bound it pattern as anywhere else. Third, park the rest out loud: name what would be needed to answer the remainder and offer it as future work. Never invent a number or a source on the spot; examiners recognize the texture of their own field instantly. Committees grade the recovery, not the gap.
How long should an answer to a defense question be?
One to two minutes for most questions — roughly 130 to 260 spoken words — and shorter for the openers, which deserve tight, confident sentences. The three-part pattern keeps you inside that window naturally: state the answer, point at the evidence, name the limit, stop. The hardest habit is the stop. If you have made your point and no follow-up arrives, silence is fine; examiners use pauses on purpose, and filling them with a second, weaker answer is the most common way a good answer turns into a shaky one.
Do I defend my thesis proposal separately from the final thesis?
Many graduate programs run both as separate meetings: a proposal defense, where a smaller committee questions the plan, and a final defense, where the full committee questions the finished work. Some programs combine them or skip the first. The question sets differ in kind — proposal defenses ask feasibility and design questions, the stage the thesis proposal guide covers with its preview cards, while final defenses ask what the completed evidence shows and what it means. If your program runs both, write down every question you were asked the first time; several of them return at the final defense, sharpened.
Which seat at the table worries you most?