In this guide · 10 sections
Summary in plain words
- A proposal defense is a checkpoint halfway through: the committee decides whether the research can move on to the final defense.
- Read your program's rules first: deadlines, format and committee vary from one program to the next.
- Plan backwards from the date of the meeting, with at least 8 weeks.
- After the meeting, turn each suggestion into a task and update the timeline to the final defense.
What a thesis proposal defense is
Many master's and PhD programs have a checkpoint halfway through. Depending on the country and the program, it is called a proposal defense, a qualifying exam or a progress review. A committee, usually your supervisor and two other faculty members, reads a partial version of your thesis and decides whether the research is on track for the final defense.
It is not the final defense. Nobody expects a finished thesis. The point is to correct course while there is still time, so the committee's criticism is help, not a failing grade.
When it happens
In a two-year master's, it often happens after the first year. In a PhD, it usually comes later, in the second or third year. Some programs also require coursework or a language requirement before you can schedule it.
Two dates usually appear in the handbook and belong in your timeline right away:
- Scheduling the committee: the form you or your supervisor sends to the graduate office, with the date and the committee members.
- Sending the document: the committee needs time to read. Programs often ask for it a few weeks before the meeting.
What to send the committee
The content varies by program and field, but a proposal document usually includes:
- An introduction with the research problem, rationale and aims.
- A literature review or theoretical framework.
- A detailed method: what you will do, with whom or with what, and how you will analyze the data.
- Preliminary results, if you have any.
- A provisional table of contents for the thesis.
- A timeline for what is left until the final defense.
What the committee looks for
More than the writing, the committee looks at how well the research holds together:
- A clear problem and clear aims. Can you say in two sentences what the research wants to answer?
- Fit between question, method and data. Does the chosen method answer the question asked?
- Feasibility. Does what is left fit in the time remaining?
- Engagement with the literature. Do the key authors in the field appear, and does the research position itself among them?
- Contribution. What does the work add to what is already known?
An 8-week plan to the proposal defense
Start from the date of the meeting and walk back through the calendar. The plan below assumes that most of the review and the method already exist as drafts. If your program wants the document earlier, move the rows forward by the same amount.
| When | What to do | Deliverable |
|---|---|---|
| 8 weeks before | Read the handbook and agree on the date and committee with your supervisor | Date and committee set |
| 7 weeks before | Schedule the committee, if your program requires it | Form sent to the graduate office |
| 7 to 5 weeks before | Complete the introduction, review and method | First full draft |
| 4 weeks before | Send it to your supervisor and work in the comments | Revised draft |
| 3 weeks before | Check the formatting and send the document to the committee | Document sent by the program's deadline |
| 2 weeks before | Build the presentation | Slides ready |
| 1 week before | Rehearse with a timer and list likely questions | Rehearsed talk |
In the week you send the document, do not start new chapters. Use the time to make what you have clear and coherent.
How to build the presentation
Many programs set aside 20 to 30 minutes for the talk, followed by questions. An outline that works in most fields:
- Problem and rationale: why this research matters.
- Research question and aims.
- Theoretical framework in a few slides, only the essentials.
- Method: what you have done and what you will do.
- Preliminary results, if any.
- What is left and the timeline to the final defense.
End with the timeline. It shows the committee you know what comes next and opens the conversation about feasibility. Rehearse at least once with a timer, ideally in front of people from your research group.
Common committee questions
- Why this method and not another?
- What does the work contribute to the field?
- Does what is left fit in the time until the final defense?
- How will you handle the limitations of your data or sample?
- Why these authors? Did you consider this other line of work?
After the meeting: turn suggestions into tasks
Right after the meeting, sit down with your supervisor and decide which suggestions go into the work. You do not have to accept them all, but you should be able to explain the ones you leave out.
Each accepted suggestion becomes a task with a stage and a due date. That way they do not get lost in your notes, and the timeline to the final defense starts out up to date:
Common proposal defense mistakes
- Finding out the program's deadline too late. Read the handbook at the start of the program, not in the month of the meeting.
- Treating it like the final defense. Delaying to hand in a finished thesis usually costs more than sending a partial one.
- A talk that runs too long. Going over time takes minutes away from the questions, the most useful part.
- Answering criticism defensively. The committee is helping the research. Thank them, take notes and decide later, calmly.
- Forgetting the suggestions afterwards. If they do not become tasks, they come back at the final defense, when it is too late.
Create a project with this guide's columns and invite your supervisor.
Create free account