Every stage ends in something you can hold
Progress on a long project is notoriously hard to measure, which is how people end up eighteen months in with a feeling rather than a document. So each stage here is defined by what exists at the end of it.
- Topic: a problem statement narrow enough to answer with your access and your months
- Proposal: the document a committee signs off, and the gate everything after it waits behind
- Literature: a matrix covering every source, and the chapter written out of it
- Methodology: a design that agrees with your review packet and your data plan
- Results: tables in your school's template, with the findings stated plainly
- Discussion and defense: the closing chapter, the slides, and a rehearsal
Your chair's turnaround is the real schedule
Students plan around how fast they can write, which is the wrong variable. A chapter takes a fortnight to draft and then sits with a supervisor for three weeks, or six, or however long their term is. Across five chapters that waiting is most of the calendar.
Which changes what good planning looks like. Something should always be with your chair, so their reading time overlaps your writing time rather than following it. Send a partial chapter with a specific question rather than a perfect one with none, because a two-page question is answered in days and a complete draft can sit for a month. Being permanently in somebody's queue is the objective.
The proposal is the gate that matters
Everything before it is preparation and everything after it is execution. It is also the only document a committee formally approves, which makes it the point where their expectations and yours are forced to match. Ambiguity that survives the proposal reappears as a rewrite in chapter four.
So it is worth spending disproportionate effort there, and worth pushing for specificity while it is still cheap. If two committee members read your problem statement differently, that is a conversation to have now, in writing, rather than after the data is collected. Where board approval is required, the packet gets built alongside through the research desk rather than after the proposal clears.
Where the spending should stop
You will defend this aloud, in a room, to people whose job is asking why you chose what you chose. A document you cannot account for fails there rather than quietly, so the argument has to remain yours at every stage.
What is worth paying for is structure, drafting help where you are stuck, somebody who has done this before, and honest reactions ahead of your chair's. What is not worth paying for, at any price, is a finished dissertation with your name on it. The ongoing week-to-week version of this relationship is mentoring.
Send the stage
Your program, what exists, and your chair's most recent comments. Quoted within two hours.
Buy only that stage
Priced from what is actually in front of somebody rather than from a guess about chapter five.
Keep the queue full
Something always with your chair, so their reading happens while you are writing the next piece.
Questions people actually ask.
Why not quote the whole project?
Because chapter four's shape depends on how chapter three landed, and committees redirect. A single upfront figure is either padded heavily against that uncertainty or destined to grow later. Quoting each stage from what genuinely exists is more honest and usually cheaper, and it lets you stop at any point without a negotiation.
My chair takes a month to reply. Can anything be done?
Change what you send. A complete chapter invites a complete read, which waits for a free weekend they may not have. A partial section with one specific question attached can be answered between meetings, and it keeps you visible. The aim is being permanently in the queue rather than periodically joining it.
Can I start at methodology?
Yes, and many people do. Send whatever exists together with your chair's latest comments and the stage is quoted from where it truly stands. Occasionally the honest answer is that the problem statement needs revisiting first, since a methodology resting on a vague question becomes very difficult to defend later on.
How much should the proposal get?
More than feels proportionate. It is the only document your committee formally approves, which makes it where their expectations and yours are forced to align. Ambiguity that survives it does not disappear; it returns as a rewrite once data has been collected, at the point when rewriting is most expensive.
Will you write the dissertation?
No. A committee will make you justify every decision out loud, and nothing rescues a document its author cannot explain. What you are buying is structure, help at the stuck points, somebody who has crossed this ground, and candid reactions before your chair delivers theirs. The rest has to stay yours.