Dissertation Timeline Generator: milestones from start date to defense

Build your dissertation timeline

Set the four inputs and the twelve milestones lay themselves out in order, each starting the next working day after the previous one ends. Durations are working days — Saturdays and Sundays are skipped, nothing else is. Edit any duration and the whole plan recalculates forward from the start date; if a milestone now lands past your deadline, the row turns red and the summary counts the overrun. If you want to see the tool before trusting it with your own dates, load the demo plan: an invented, illustrative ten-month Masters timeline starting October 12, 2026.

A plan is only worth what its durations are worth, so the sections below give you the reference numbers: what each milestone holds, how long each should take by program and pace, where the buffers hide, and what to do the day the plan breaks. If you are still at the stage before a plan exists — the proposal itself — the dissertation proposal guide covers that document, and the numbers here slot straight into it.

The twelve milestones every dissertation plan needs

The order is fixed because dependencies force it: you cannot collect data the methodology has not justified, and you cannot draft chapters around analysis that does not exist yet. What varies is how long each one takes. Here is what each milestone actually holds:

Two of the twelve are not work at all: the advisor review round is mostly waiting, and the submission buffer is deliberately nothing. Both exist because plans that schedule only production break at the first queue they meet.

How long each milestone should take

The defaults below are the tool's starting points, in working days, before pace adjustments. They are calibrated to be honest rather than optimistic — a plan you cannot keep is worse than no plan — and every number is editable because your program's rules outrank this table:

Research pace then bends the relevant rows. Library-based work stretches the literature review by about a fifth, because desk research lives and dies on the reading, and trims data collection, because there are no participants to chase. Lab-based work does the opposite: it adds roughly forty percent to the ethics application, thirty percent to data collection, and a little to methodology and analysis, because equipment queues and participant recruitment are calendar events you do not control. Mixed methods leave the defaults alone — which is itself a warning, since mixed projects inherit both sets of delays.

If you are unsure which track you are on, the distinction between the two document families matters more than the label: capstone versus dissertation separates the applied, course-bound project from the research-degree one, and the durations differ accordingly. A capstone drafting season looks like the capstone paper structure — shorter chapters, a practice problem instead of a theoretical gap — and pretending otherwise inflates the plan for no benefit.

One reading rule for the table: these are durations, not promises. If your supervisor says the proposal draft is due in three weeks, enter fifteen working days and move on. The generator's job is to keep the arithmetic coherent when you change one number, not to overrule the people who mark the work.

Two buffers that decide whether the deadline holds

Most timelines do not die from missing work. They die from missing waiting time — and there are two queues in every research degree.

Why advisor review needs two to four weeks

Your advisor is not sitting idle waiting for your chapter. It joins a stack: other students' chapters, journal reviews, grant panels, teaching. Two to four weeks is the realistic turnaround for a full chapter read with care, and the spread is the point — a plan that assumes five days treats the best case as the expected case, and the first slow read knocks every later milestone sideways. Schedule the review round as its own milestone with real length, keep drafting the next chapter while you wait, and never book your revisions to start the day after you send the draft.

Ethics lead times start before data collection

Ethics boards meet on fixed calendars, and an application that misses one cycle waits for the next. That is the mechanism behind the lead time: submission, a pre-review pass that often asks for changes, resubmission, then the meeting itself. On lab-based projects the application routinely earns its place as a milestone longer than the methodology chapter, because approval gates everything downstream — no approval, no participants, no data. The practical move is to draft the application while the methodology is being finalized rather than after it, and to treat board feedback as a scheduled stage, not an interruption. Library-based projects trade this queue for a smaller one: archive access requests and permissions, which are worth their own row precisely because librarians and registries also work in queues.

While you wait on either queue, the work that moves is the writing group. Chapters reviewed by peers before the advisor sees them come back cleaner, which shortens the advisor round itself. If your program expects collaborative work, put the expectations in writing with a group project contract — who reviews what, by when — so the peer queue has the same discipline the advisor queue already has.

When the plan slips: how to re-baseline

A slip is not a failure of planning; it is information arriving late. The re-baseline is the discipline of feeding it back in before the deadline finds out. The sequence that works:

1. Name the slip in the simulator. Pick the milestone that actually moved and the honest number of weeks. The preview shows the new finish date, which milestones shift, and whether the deadline still holds.
2. Apply it once. The delay lands in the milestone's duration — the plan stays one plan, not a fantasy plus a spreadsheet of excuses.
3. Read where the damage lands. If the finish date still beats the deadline, the slack between the plan and the deadline absorbed it, and you are done.
4. Compress where there is slack, not where there is not. Fit to deadline shrinks durations proportionally with a two-day floor and reports each cut. Milestones with padding take the hit; the submission buffer does not.
5. Tell the person who marks the work. A re-baselined plan taken to supervision is a plan. A silently optimistic one is a resignation letter with dates on it.

The verdict line in the planner runs the same logic in reverse every day: it compares what you have marked done against what the plan expected you to have done by today, weighted by milestone length. Run ahead of that line for a fortnight and you have room; fall behind it and the simulator shows exactly which buffer will pay. Neither state is a mood — they are arithmetic, which is why they are checkable weekly instead of felt nightly.

How the working-days math works

Durations count working days: Saturdays and Sundays are skipped; every other calendar day — including public holidays — counts. That is the whole rule, kept simple on purpose, because a planner that also models regional holidays needs a holiday calendar this page does not have. The honest consequence: when your institution closes for two weeks between Christmas and New Year, shorten those affected durations yourself, or accept that the plan will finish late by exactly that much.

A worked example: data collection set to ten working days starting Monday, October 12, 2026 runs to Friday, October 23 — two weekends sit inside the stretch, so ten working days span sixteen calendar days. Each milestone starts on the next working day after its predecessor ends, which is why the plan has no gaps and no overlaps: compress one row and everything downstream moves that same day.

The deadline comparison is plain calendar arithmetic — plan finish date against deadline date — and the slip simulator speaks the same units, so a "three weeks" delay becomes fifteen working days and the preview shows the calendar-day difference at the finish line. If any of this feels too coarse, that is the trade: simple enough to check by hand, which is what a plan you actually trust requires.

Take the plan into your calendar with .ics

The export button builds a standard iCalendar file — the same format every calendar app has imported for twenty years — with one all-day event per milestone. Each event carries a title like "Masters thesis: Literature review", its start and end dates, and a description with the duration and status at export time. Press Export .ics and the file dissertation-timeline.ics downloads; import it through your calendar app's import menu, or drag it onto the calendar list. The events land as all-day blocks, so your classes, shifts and meetings sit right next to the plan they have to survive.

Two details worth knowing. First, calendar apps store an all-day event's end date as the morning after the last day — that is the file format working correctly, not an off-by-one bug. Second, re-export after every re-baseline: the events keep stable identifiers, and most calendar apps offer a merge so the fresh plan replaces the stale one instead of doubling the clutter. A calendar that says two things at once is worse than a calendar that says nothing.

The export is also the cheapest backup there is. The plan itself lives in this browser and nowhere else, so if you clear site data, the .ics file — or the copy button on any row's dates — is your record of what you agreed to.

What a timeline generator cannot do

The honest limits, stated plainly because a planner you over-trust is worse than one you understand:

• It does not know your program's rules. Mandatory milestone dates — proposal defense, ethics cycle, submission windows — override any default here. Enter them as durations that land where your handbook says.
• It cannot see people's calendars. Advisor queues, committee availability and lab scheduling all live outside the page. The review buffer models them crudely; only your advisor can model them accurately.
• The defaults are a starting point, not research. They are chosen to be defensible and editable. If your supervisor's expectations differ, the supervisor wins.
• It does not write anything. There is no drafting help here — for the writing itself, the free writing tools hub and the study guides hub cover the parts a calendar cannot.
• It stores nothing you can lose. The plan lives in this browser's storage under one key, saves only when you interact, and the Reset button removes it entirely. Export the .ics if the dates matter.

Used within those limits, the planner earns its keep: it converts a vague dread — "the deadline is far away, but is it far enough?" — into twelve rows you can argue with, and it makes the cost of every slip visible before the slip happens, which is the only time it is cheap.

Quiz: five questions on planning a dissertation

Five questions on milestones, buffers and the working-days math. Every wrong answer shows the right one, and four options keep the guessing honest.

Frequently asked questions

Did the planner hand you a plan you can actually start on? Yes Not really