Most dissertation timelines fail not because students work too slowly, but because the plan never accounted for things outside their direct control. Committee turnaround, IRB review, and recruitment delays. A realistic timeline builds those in from the start.
It's tempting to treat a dissertation timeline as a rough formality. Something you sketch once to satisfy a program requirement and then quietly ignore. In practice, the initial plan does real work well beyond that first submission. It's what you compare actual progress against later, it's what tells your committee whether a proposed extension is reasonable, and it's often the document that determines whether a stalled semester feels like a minor deviation or a full-blown crisis. A timeline built carelessly at the start, say, one that simply divides "time until graduation" by "number of chapters", gives you no real basis for noticing early that a particular phase is taking twice as long as planned, because there was never a phase-specific target to measure against in the first place. This guide focuses specifically on constructing that initial plan well; once it exists and life inevitably interferes with it, our companion guide on staying on a dissertation timeline covers how to replan around real slippage, balance the work against a job or family commitments, and keep scope creep from quietly extending every phase.
| Stage | Common Underestimate |
|---|---|
| Committee feedback turnaround | 2–4 weeks per round is typical, not days |
| IRB review | Even expedited review can take several weeks; full board review longer |
| Participant recruitment | Often the single biggest source of timeline slippage |
| Transcription (qualitative) | Hours per interview, easy to underbudget across a full sample |
| Final formatting/library submission | Institutions often have their own format check process with its own queue |
Before you can work backward from a defense date, you need a realistic sense of how much calendar time each phase genuinely consumes, not how long the writing itself takes, but how long the phase takes once committee turnaround, institutional queues, and real-world scheduling are folded in. These ranges assume a full-time or near-full-time pace; part-time candidates should generally expect the higher end or beyond.
| Phase | Typical Duration |
|---|---|
| Topic refinement and literature review | 2–4 months |
| Proposal drafting and committee approval | 2–3 months, including at least one revision round |
| IRB submission and approval | 3–8 weeks depending on review level |
| Data collection | 1–4 months, highly dependent on recruitment difficulty |
| Analysis and results write-up | 1–3 months |
| Discussion/conclusion chapter and full-draft revisions | 2–3 months |
| Defense scheduling and preparation | 3–6 weeks once the full draft is committee-approved |
| Final formatting and library deposit | 2–4 weeks, often on the institution's own separate queue |
Add these up and you'll typically land somewhere between twelve and twenty-four months for a full-time candidate with a reasonably smooth path, which is exactly why building the plan phase-by-phase, rather than picking a single overall guess like "eighteen months," produces a far more defensible schedule. When any individual phase runs long, you can see precisely which one moved and by how much, instead of just watching an undifferentiated end date slip.
A phase-by-phase list is useful, but mapping it onto actual academic semesters (or, for programs without semesters, calendar quarters) makes the plan concrete enough to act on. A typical full-time candidate targeting a defense roughly eighteen months out might lay out something like this: Semester 1: finalize research questions, complete the bulk of the literature review, and produce a full proposal draft. Semester 2: defend the proposal, submit and clear IRB review, and begin data collection. Semester 3: complete data collection, run the analysis, and draft the results chapter. Semester 4 (a shorter final push). Finish the discussion and conclusion chapters, complete full-committee revisions, and schedule the defense. Laid out this way, each semester has one or two clear, checkable deliverables rather than a vague sense that "things are progressing," which makes it far easier to tell early whether you're actually on pace.
Consider a candidate, we'll call him Jamal, aiming to defend in April of his third year. Working backward, he first blocked out the final formatting and deposit stage (about three weeks), then defense scheduling and preparation (about a month, since his program required the full draft to be committee-approved at least three weeks before the defense date itself). That set his "complete, approved full draft" deadline at roughly early February. Working backward again through discussion/conclusion writing and a full revision round (two and a half months), his results chapter needed to be drafted by mid-November, which meant analysis needed to start once data collection wrapped in October. Data collection, given his recruitment difficulty with a fairly narrow professional population, he budgeted at three months rather than the one-month best case, meaning it needed to start in July. Right after an IRB approval he budgeted six weeks for, meaning his proposal needed committee approval by late May. Laid out this way, Jamal could see that his original hope of starting data collection "sometime in the fall" was actually incompatible with an April defense, and he moved his proposal defense up by two months to make the rest of the chain feasible. A correction made possible only because he built the plan backward from the true end date rather than forward from an optimistic guess.
Treat your chair's feedback turnaround as the actual bottleneck, not your own writing speed. Many students plan around how fast they can write a chapter, when the real constraint is how fast their committee responds. Submitting chapters in smaller chunks can sometimes shorten the overall feedback cycle.
Whatever stage your timeline says is next, we can help you make progress on it now.
This varies enormously by program, field, and individual circumstances. Anywhere from one to several years is common. A realistic personal timeline matters more than any general average.
Build buffer time in from the start rather than treating it as an afterthought. A plan with zero slack anywhere is really a best-case scenario wearing the name of a realistic one. That said, actually adjusting the plan once real delays happen is its own skill; see our timeline management guide for how to replan once you're mid-program.
Mostly just at different speeds. The phases and their dependencies stay the same, but part-time candidates should generally plan on 1.5 to 2 times the full-time duration for phases that depend heavily on sustained personal work time, like writing and analysis, while externally-paced phases like IRB review take roughly the same calendar time regardless of your own availability.
Yes. Tell us where you're stalled (a chapter, the proposal, data analysis) and we can take that specific piece off your plate so the rest of your timeline can move forward.
Yes. A plan built purely in "months" without reference to your actual calendar will systematically overestimate available working time, since winter breaks, conference season, and committee members' own teaching schedules all create predictable dead zones worth blocking out from the start rather than discovering later.