PhD viva preparation guide

How to Defend Your Thesis Contribution

In a PhD viva, defending your thesis contribution means showing that your work is original, significant, bounded, and genuinely yours. Examiners are not looking for inflated claims. They are looking for a clear account of what your thesis adds, how it differs from previous work, why the contribution matters, and what evidence supports it.

The Quality Assurance Agency for Higher Education states that doctoral graduates demonstrate an original contribution to knowledge in their subject, field, or profession through original research or the original application of existing knowledge or understanding. This is the standard behind many viva questions about originality, contribution, ownership, and significance.

Core idea: A strong contribution answer identifies the gap, states the contribution, locates it in the literature, explains the evidence, defines the limits, and shows why the thesis deserves the doctoral award.

1. Understand what examiners mean by contribution

A thesis contribution is not simply the topic you studied. It is the new knowledge, explanation, evidence, method, framework, dataset, argument, design, interpretation, or application that your research adds to the field.

For example, a thesis on software testing does not contribute merely because it studies testing. It contributes if it provides a new empirical finding, a new benchmark, a new repair method, a new theory of developer behaviour, or a stronger evaluation of an existing technique.

Weak answer: My contribution is that I studied AI generated code.

Stronger answer: My contribution is a validated framework for classifying security failures in AI generated code, supported by an annotated dataset and an empirical evaluation of how different models produce and repair these failures.

2. Prepare a one sentence contribution claim

Before the viva, write a single sentence that states your main contribution. This sentence should be specific enough that an examiner can test it. Avoid broad phrases such as this thesis contributes to the literature or this work fills a gap.

Template: This thesis contributes [type of contribution] by showing [new claim or output] through [evidence or method], which matters because [field level significance].

Example: This thesis contributes an empirical and methodological framework for evaluating configuration compatibility bugs in Android apps by combining failure taxonomy, repair examples, and model based analysis, which matters because existing app maintenance research does not sufficiently explain how compatibility failures can be detected and repaired at scale.

3. Distinguish the type of contribution

Examiners may ask what is original about the thesis. A precise answer identifies the kind of originality. Contribution can be empirical, theoretical, methodological, conceptual, practical, critical, comparative, or synthetic.

For instance, an empirical contribution may be a new dataset or new evidence about an under studied setting. A methodological contribution may be a new evaluation protocol. A theoretical contribution may refine an existing model. A practical contribution may produce a tool or process that changes how work is done.

Question: What is original about your thesis?

Strong answer direction: The thesis makes three contributions. First, it provides empirical evidence from a setting that has not been systematically studied. Second, it develops a framework for classifying the observed failures. Third, it evaluates whether existing repair techniques can address those failures. The originality is therefore empirical, conceptual, and evaluative.

4. Show the gap without overstating it

A contribution needs a gap, but the gap must be credible. Do not say that no one has studied your area if previous work exists. Instead, identify what previous work has done and what it has not yet explained, measured, compared, or solved.

For example, previous work may have studied model accuracy but not deployment risk. It may have evaluated tools on benchmark data but not on real world cases. It may have explained a concept theoretically but not tested it empirically.

Weak answer: Nobody has looked at this problem before.

Stronger answer: Previous work has examined related model performance and software repair tasks. The gap is that it has not evaluated configuration level compatibility failures in a way that connects real app behaviour, repair actions, and model generated patches.

5. Link every contribution to evidence

In a viva, a contribution claim is only persuasive if you can point to evidence in the thesis. Evidence may include chapters, datasets, experiments, interviews, observations, proofs, artefacts, case studies, design decisions, validation results, or comparative analysis.

Prepare a contribution evidence map. For each contribution, write where it appears in the thesis, what evidence supports it, and what limitation constrains it.

Contribution evidence map:

  • Contribution one: taxonomy of failure types. Evidence: chapter three, coding procedure, inter rater agreement, examples.
  • Contribution two: repair method. Evidence: chapter four, algorithm design, baseline comparison, ablation study.
  • Contribution three: field implication. Evidence: chapter six, synthesis of results, comparison with prior studies.

6. Explain contribution at the right level of scale

Not every PhD contribution changes an entire discipline. That is normal. The contribution may be field changing, subfield changing, method improving, evidence adding, or problem clarifying. A credible candidate states the contribution at the correct scale.

For instance, a thesis may not transform all AI safety research, but it may clarify one specific category of software risk and provide a reproducible way to evaluate it. That is still a legitimate doctoral contribution if it is original, rigorous, and significant within the field.

Question: How important is your contribution?

Strong answer: I would not claim that the thesis resolves the entire problem of AI generated software safety. Its contribution is more specific. It identifies a class of configuration related failures, shows why standard functional evaluation misses them, and provides a reproducible evaluation framework for future work.

7. Position your contribution against key literature

Examiners often test contribution by asking how the thesis relates to the field. You should be able to name the most relevant bodies of work and explain whether your thesis extends, challenges, refines, applies, or synthesises them.

For example, if your thesis builds on three research streams, prepare one sentence for each stream. State what that literature established, what it left open, and how your thesis responds.

Question: How does your thesis relate to existing work?

Answer pattern: The first body of work establishes X, but it does not address Y. The second body of work provides method A, but it has rarely been tested in context B. The third body of work motivates the problem. My thesis connects these streams by showing Z.

8. Defend contribution when examiners challenge novelty

An examiner may suggest that your idea is similar to earlier work. Do not become defensive. First identify the overlap, then state the difference. Similarity is not fatal if you can explain what your thesis adds.

Question: Is this not very similar to Smith’s earlier framework?

Strong answer: There is overlap in the broad problem area. Smith’s framework classifies failure symptoms, while my thesis focuses on the repairability of those failures and validates the classification against real app cases. The contribution is therefore not a replacement for Smith’s work, but an extension from classification to evaluation and repair.

9. Show your independent role

The viva also tests ownership. If your thesis includes co authored papers, collaborative datasets, shared infrastructure, or supervisor led projects, you should be ready to explain your specific contribution. This is especially important for paper based theses and interdisciplinary projects.

For example, state which research questions you designed, which data you collected, which analysis you performed, which code you wrote, which experiments you ran, and which interpretation was yours.

Question: Which parts of this work are specifically yours?

Strong answer direction: I led the research design, built the classification scheme, implemented the evaluation scripts, conducted the main analysis, and wrote the interpretation in chapters four and five. The collaborative element was access to the dataset, but the analytical framework and evaluation were my own contribution.

10. Handle limitations without weakening contribution

Limitations do not cancel contribution. They define the boundary of the claim. A strong answer explains what the thesis can claim, what it cannot claim, and why the contribution remains valid within that boundary.

For example, a benchmark may use a limited set of tasks. The contribution may still stand if the benchmark is well justified, the selection criteria are transparent, and the thesis does not overgeneralise beyond the task scope.

Question: Does this limitation undermine your contribution?

Strong answer: It limits the scope of the claim, but it does not remove the contribution. The thesis does not claim that the framework covers every possible failure mode. It claims that the selected failure class is important, under evaluated, and measurable through the proposed protocol. Future work can extend the protocol to other failure classes.

11. Connect contribution to publication potential

Examiners may ask what can be published from the thesis. This question tests whether the contribution can be communicated as scholarly work. Prepare a publication plan that separates the main thesis contribution into publishable units.

For instance, one paper may report the dataset and taxonomy. A second paper may present the method. A third paper may discuss the wider implications for practice or theory. The plan should show that your contribution has a coherent scholarly audience.

Question: What would you publish from this thesis?

Strong answer: I would publish three outputs. The first would be an empirical paper on the failure taxonomy. The second would be a methods paper on the evaluation protocol. The third would be a synthesis paper explaining how the findings change current assumptions about AI assisted software maintenance.

12. Prepare a concise spoken answer

Your contribution answer should be clear enough to say aloud under pressure. A useful structure is: gap, contribution, evidence, significance, limit.

One minute answer: My thesis addresses a gap in how AI generated software is evaluated. Existing work often measures whether code passes tests, but it gives less attention to configuration related failures that appear in real deployment contexts. The contribution is a framework for identifying, classifying, and evaluating those failures. The evidence comes from the dataset, the taxonomy, the repair experiments, and the comparison with existing techniques. The significance is that it gives researchers and developers a more precise way to study reliability risks. The main limitation is that the thesis focuses on one class of failures, so future work should extend the protocol to other settings.

13. Prepare common contribution questions

You should prepare answers to the questions below. Do not memorise scripts. Prepare claims, evidence, examples, and boundaries so that you can adapt naturally during the viva.

14. Final preparation checklist

Before the viva, check whether you can clearly answer these points:

Practise thesis contribution questions with MockBase

Reading a guide is useful, but the viva tests whether you can defend contribution aloud under pressure. Use MockBase to practise originality questions, contribution challenges, literature positioning, limitation handling, and examiner follow ups.

Open PhD Viva Practice App View more MockBase guides

Preparation sources

This guide was informed by official doctoral standards and viva preparation guidance from QAA, the University of Edinburgh, Cambridge, UKCGE, and the Scottish Graduate School of Social Science.