How to Write a Dissertation Proposal

What a dissertation proposal has to prove

Graduate students often arrive expecting the proposal to be a shorter, easier dissertation. It is not that. The proposal is the gatekeeping document: your supervisor, and for a PhD your committee, read it to decide whether to let you spend the next several years — or one very tight semester — on the design inside it. That decision runs on two questions, and every section of the proposal exists to answer one of them.

The first question is feasibility. Can this be done with the access, the time and the methods you actually have? A proposal that promises to interview ministers or to "analyze all of Twitter" reads as naive, not ambitious. The second question is contribution: what will be known after your dissertation exists that is not known now? For a PhD this is the contribution to knowledge the degree is built on; for a Masters it is usually smaller — a competent, evidence-based answer to a real question in a real setting — but it still has to be stated, not implied.

Everything else is scaffolding for those two claims. The introduction locates the gap, the literature chapter shows the gap is real, the methods show you can close it, the ethics line shows the closing is allowed, and the timeline shows it closes in time. If you are still earlier than that — still choosing between degree formats — the capstone vs thesis comparison sorts out the final-project formats first, and the proposal mechanics here shrink harmlessly onto an applied project. (Terms like research gap, sampling or ethics board are each defined in a line in the glossary.) And if your program routes the final project through a capstone instead, the proposal stage shrinks but does not disappear — the capstone project guide covers that route end to end.

The proposal section planner

The planner below assembles a sectioned skeleton for your level and field. Pick the degree, pick the field flavor, press Build my skeleton, and you get a working-title placeholder, an introduction prompt, three research-question slots with guiding questions, field-appropriate method hints, an ethics line, a timeline shape and the contribution prompt — ready to copy or download and fill in. Every prompt is a question for you to answer; none of it is a draft you can submit as-is.

Use the skeleton in the order it prints: title first, because it forces the variables into one line; questions second, because they decide the methods; literature third, because the chapter must end where the questions point. When the skeleton is approved and the chapters need a page budget, the research paper outline guide shows the same move at paper scale. The proposals students actually defend are the ones where every bracket has been replaced with something checkable — a number, a name, a date, a shelf mark.

Research questions: run the pattern check

Research questions are where proposals live or die. A strong question names the outcome or mechanism, the setting, and sometimes the comparison — in one sentence a reader can hold. A weak one either asks for a yes or a no, or hides three questions inside one very long sentence. Paste one of yours below and the checker runs a quick pattern check: question mark, length zone, answerable shape, vague placeholder words, and — for oversized questions — whether any feasibility anchor like a data source or a setting is named. It is pattern-matching, not supervision; a supervisor will still rewrite your questions, and should.

Aims and objectives: sort them

Aims and objectives get mixed up in almost every first draft, and committees notice. An aim is the destination in knowledge terms — what you want to understand, establish or assess, with no method and no sample size attached. An objective is the measurable step that gets you there — a verb, a data source, a scope. A one-aim, three-objective shape is the most common proposal layout: the aim feeds the title and the contribution section; the objectives become your research questions and your chapter plan. Sort the six statements below — all invented for practice — and the why-line explains every answer.

The literature review chapter in the proposal

In a dissertation proposal, the literature review chapter has one job: prove the gap is real. That is a different brief from the dissertation chapter itself, which maps the whole conversation in depth. For the proposal, organize by theme — the two or three debates your questions touch — and end each theme at the exact point where the answers stop. A proposal review that reads as a list of summaries ("Smith found X. Jones found Y.") hides the gap it is supposed to prove; a review organized by debate makes the gap fall out of the structure.

Two housekeeping moves make the chapter easier to write and easier to trust. First, annotate as you read: the annotated bibliography guide shows how a summarize-assess-reflect note per source becomes raw material for a themed review. Second, keep the proposal review honest about its own size — it is a trailer for the dissertation chapter, not the film, and most supervisors would rather see three debates handled sharply than ten gestured at. When the dissertation version is due, the literature review guide takes over with the full chapter method.

Ethics, then the timeline

Ethics belongs in the proposal in one honest line or one short block: what your participants, materials or data are, what consent and storage arrangements you will use, and which board or committee approves the work. It sits before the timeline for a reason — most committees will not let data collection start before the ethics application is approved, and the timeline has to show that sequence rather than hide it.

The builder below plots the five standard phases on a 24-month strip. Set each phase's start month and length, and it draws the plan with a total readout — plus a warning if data collection tries to start before the ethics application ends. It is a rough planning aid, not a Gantt chart; its job is to make the sequence arguable in a meeting with your supervisor, not to predict the future.

Two honesty notes the strip will not show. Overlaps are normal — literature review never really stops, and analysis usually starts while collection runs. Gaps are the red flags: a stretch with nothing scheduled before writing up is where dissertations go quiet. Bring the copied plan to your supervision meeting and let your supervisor break it; that is what the meeting is for.

The dissertation abstract, explained

The abstract and the proposal are different documents that students keep conflating. A dissertation proposal is written before the research, in the future tense, and argues that the work should happen. The dissertation abstract is written after the dissertation exists — usually last, though it sits at the front — and compresses the finished work into one paragraph: the problem, the method, the main findings, and the conclusion or contribution. It describes what happened, not what will happen.

What goes in the finished abstract, in order: one or two sentences on the problem and why it matters; one or two on the method — design, data, analysis; two or three on the findings, with the specifics rather than "results are discussed"; and one on what it all means for the field or the practice. Many departments cap the abstract at a few hundred words or a single page — your handbook wins if it names a number, and the word counter keeps you inside it. One more trap: some departments also ask the proposal to carry a short summary paragraph. That proposal abstract describes the plan; it is not the dissertation abstract, and it gets rewritten once the findings exist.

How long should a proposal be?

Honest answer first: there is no universal number, and any figure you read — including here — is orientation, not regulation. As general guidance, most departments expect a Masters proposal to run somewhere from a handful of pages up to a dozen, and a PhD proposal to run longer, often with a full literature chapter attached. Some programs hand you a template with a page limit; others say only "concise". The binding number is the one in your department's handbook or your supervisor's last email, and the word counter turns either into a target you can watch.

Length matters less than coverage. A four-page proposal that names the gap, the questions, the sample, the ethics line and the timeline beats a twenty-pager that circles the topic. If your draft is running long, the usual culprit is the literature section — cut it back to the debates your questions actually touch.

The proposal checklist

Eight checks before the proposal leaves your laptop. Tap as you fix.

0 of 8 checks

• The proposal answers the two gatekeeper questions: is it feasible, and what does it add
• The working title carries the variables, the setting and the period in one line
• The introduction names a specific research gap, not the general topic area
• Each research question fits in one sentence and builds on the one before it
• The literature section is organized by debate and ends at the gap the questions fill
• The methods section names the design, the sample or materials, and the analysis approach
• The ethics line names consent, storage and the approving body before any data work
• The timeline shows ethics approval before data collection, and survives being read aloud

Five-question check

A fast pass on the rules. Wrong answers reveal the right one.

Frequently asked questions

Was this guide useful? 👍 Yes 👎 Not really