| name | prepare-a-thesis-defense |
| category | school |
| description | Prepare a thesis defense by mapping claims to evidence, rehearsing methods and limitations, anticipating questions, and verifying presentation logistics. Use when a candidate must defend completed research before examiners. |
prepare-a-thesis-defense
Defend the actual contribution and its limits, not an idealized project.
When to use
- Use for thesis, dissertation, capstone, viva, proposal defense, or public examination.
- Do not invent analyses, overstate independence, or conceal corrections and limitations.
Preconditions
- Gather the submitted version, regulations, format, examiner information allowed by policy, data, code, approvals, and accommodations.
Procedure
- Create a claim-evidence map for question, contribution, methods, results, limits, and implications.
- Build a concise narrative explaining the problem, choices, findings, and what remains unknown.
- Verify every figure, number, quotation, citation, and version against the submitted thesis.
- Prepare method, alternative explanation, ethics, validity, literature, and contribution questions.
- Rehearse concise answers that distinguish evidence, interpretation, uncertainty, and future work.
- Run full and compressed presentations with neutral reviewers.
- Test room or call, files, fonts, media, backups, timing, accessibility, and recovery.
- Record issues requiring correction and follow the formal post-defense process.
Failure plan
- If a material error is found, disclose it through the authorized process before presenting it as reliable.
- If technology fails, use the tested offline or verbal route.
Worked example
A candidate demonstrates the main result, explains why causal inference is limited, answers an alternative-model question, and records a mislabeled appendix figure for correction.
Done
- A defense package contains claim-evidence map, verified deck, question bank, rehearsal report, logistics plan, and correction list
- Submitted-version, timing, figure, citation, limitation, accessibility, backup, and mock-question checks verify readiness