How the Doctoral Process Actually Works

Your handbook tells you what to submit and when.

It rarely tells you how the process actually works — who decides what, what each stage is looking for, and where the real gates are.

And if your institution has no handbook at all, this page is where to start.

This page does not claim to be definitive — it is a guide. Where things vary by institution — and much of it does — we say so, and tell you what to ask.

What actually happens, and in what order

Most doctoral programs run through the same stages under different names.

  1. Coursework, where there is any — then a comprehensive or qualifying examination
  2. Topic and proposal — you establish what you will study and how
  3. Proposal approval — by your committee, and frequently by a review body beyond it
  4. Ethics or IRB approval — before you may collect anything
  5. Data collection
  6. Writing the remaining chapters
  7. Institutional review of the completed dissertation, under various names
  8. Defense
  9. Final revisions, formatting approval, and deposit

The names differ. The sequence rarely does, and knowing it is more useful than knowing your own handbook's vocabulary for it.


Who decides whether I pass?

This is the part candidates most often have wrong, and getting it wrong wastes months.

What does my Chair actually decide?

Your primary supervisor and your route to everything else. They guide the work, approve it for committee review, and are your advocate in the process.

What they are not: the final decision-maker. A Chair's approval does not guarantee anything downstream, and candidates who assume it does are the ones most shocked by a later rejection.

What does my committee decide?

Usually three to five members including your Chair. They approve your proposal and your final dissertation, and they examine you at defense.

They are readers with their own expertise and their own views. Committee members disagreeing with each other is normal and is not a sign that something has gone wrong.

What is School Review actually checking?

This is the stage candidates know least about and fear most, with reason — and those two facts are related. Dread scales with the size of the information gap, not the size of the risk, which means most of it can be dealt with by finding out what actually happens.

Names vary, and the real ones are worth knowing. Walden uses a University Research Reviewer (URR), who sits alongside your committee as an independent evaluator. Capella and others use School Review. Your institution will have its own term.

They are not looking for the same things your committee looked for. Your committee assessed whether the scholarship is sound. Review is checking whether the document meets institutional requirements.

It is not a second opinion on the scholarship. It is a different test.

The function is consistent: a check by people who do not know you, applying institutional standards, after your Chair and committee have already approved the work.

Review checks:

  • Internal consistency across chapters. Research questions in chapter 1 that do not match the ones actually answered in chapter 4. Purpose statements that drifted between drafts. A Chair or committee often reads chapters as they arrive, months apart; review reads them together, in one sitting.
  • Alignment. Whether the problem, the questions, the framework, the method, and the findings actually form a chain. Each link can look sound in isolation while the chain does not hold.
  • Whether the conclusions actually follow from the findings. A chapter 5 problem, not a chapter 4 problem.
  • Claims outrunning evidence. Conclusions the data does not support, usually in the discussion or conclusion, often written last and too often fastest.
  • Methodology properly evidenced.
  • Citation integrity. References that do not exist, do not say what they are cited for, or appear in the text but not the list.
  • Template and format compliance. Tedious, mechanical, and a common cause of rejection on its own.

Which is why work can clear a Chair and a committee and still be returned. See our rejected and bounced dissertations page.

And there may be more gates than you think

There often is, and almost nobody is told in advance. A separate editorial check — style, citations, tables, formatting — conducted by university editors after your committee has approved the document. It is not about your scholarship, and work does come back from it. Ask your program what stages come after the defense, and ask now.

Walden's process is a useful example because it is published in detail. To complete a dissertation there, a candidate must:

  • Pass the prospectus and then the proposal
  • Obtain approval from the committee, the University Research Reviewer, and the Institutional Review Board
  • Pass a Form and Style Review — a separate editorial check by university editors, conducted after the committee has approved the final document
  • Gain approval at the oral defense
  • Obtain final approval of the abstract from the Chief Academic Officer
  • And publish on ProQuest before the degree is conferred

Seven stages of approval, several of which most candidates do not know exist until they arrive at one.

The Form and Style Review is the one that surprises people. It is not about your scholarship — it is APA style, citations, references, tables, figures, scholarly tone, and formatting. Walden's editors line-edit the first chapter and review ten to fifteen pages of each remaining one. Work can come back from it after the committee has said yes.

Find out your own institution's list. It will not be identical and it will not be shorter than you hope.

What does the IRB do, and why is it taking so long?

That is one of the questions IRB offices report hearing most, which tells you how common the wait is. One university publishes its own averages: 42 days to an exempt determination, 83 days for expedited review. Expedited. The IRB has one question — are participants protected — and it will not be hurried.

Separate from all of the above, and it answers one question: are your participants adequately protected?

It has no view on whether your study is any good. It can and does delay studies for months, and it will not be hurried.

And the graduate school — the gate people forget

Format, deadlines, deposit, and the administrative gates. Frequently the most rigid of all of them, and the least amenable to argument.


What is each stage actually looking for?

Knowing this changes how you prepare for each one.

GateThe question it is asking
Proposal approvalIs this worth doing, can it be done, and has this candidate shown they can do it?
IRBAre participants protected? Nothing else
Institutional reviewDoes this document meet our standards and hold together?
DefenseDoes this candidate understand their own work well enough to defend it?
Format reviewDoes it comply?

Note what is not on that list. No gate asks whether your findings were what you hoped, and no gate asks whether the work was easy. A null result properly reported passes every one of them.


How long does a doctorate actually take?

Wildly variable, and here are honest ranges rather than a schedule.

StageRealistic range
Proposal developmentMonths, frequently more than a year
Proposal reviewWeeks to months, depending on how many bodies see it
IRB or ethicsLonger than almost anybody expects. See below
Data collectionVaries enormously. An online survey can close in weeks; interviews, site access, or a hard-to-reach population can take a year
Writing chapters 4 and 5Months
Institutional reviewWeeks to months — and a return sends you back to the start of that queue
Defense schedulingCommittee diaries, not your readiness. Weeks at best
Final revisions and depositWeeks

Three things that table does not show, and they matter.

Proposal development is where most time is lost — and where most of it should be spent. Time spent there is not delay; it is the highest-value work in the whole process.

And here is where it goes wrong. A great many candidates essentially wing it — a guess at a theoretical framework, and a methodology that follows from the guess — because the proposal deadline arrives at the point of least knowledge and something has to be submitted.

The proposal gets approved. The trouble arrives later, and by then it is expensive:

  • An instrument that measures something adjacent to your research questions rather than the questions themselves
  • A sample you cannot actually recruit, discovered months after approval
  • A framework you cannot defend, because you chose it from a summary rather than from the studies that used it
  • A statistical method that no longer fits. This one catches people badly. The analysis was chosen at proposal stage to suit the study as it was then described — and by the time data collection begins, the study has changed. The sample is smaller, or the variables have shifted, or the design was amended to get past ethics. The approved test is now the wrong test, and nobody has noticed
  • And a Chapter 4 you cannot interpret, because the findings answer a question you did not really ask

Every one of those is a downstream feasibility problem that took very little effort to solve at proposal stage, and takes a great deal now.

And the statistical one deserves a habit rather than a warning. Before you collect a single data point, read your approved methodology again and ask whether it still describes the study you are actually about to run. If anything has changed — sample, variables, design, timeline — the analysis probably needs revisiting, and that is a conversation with your Chair rather than a problem to discover in Chapter 4. See our Methodology at Proposal Stage page — particularly on making the research questions, the framework, and the instrument fit each other, and you.

IRB is the stage candidates most consistently underestimate, and there are published numbers.

The University of Georgia publishes its own averages. For 2021: 42 calendar days from submission to an exempt determination, and 83 days for research eligible for expedited review.

Read that second figure again. Expedited averaged nearly three months.

The University of Tennessee tells its researchers plainly to "plan for at least two months between initial submission and final approval" — and notes that its stated turnaround goals cover the initial response, not approval.

And the delays are a known institutional problem, not a candidate's impatience. Indiana University's faculty passed a formal resolution when approval times exceeded seventy days, noting that the delays were "prohibitive to student achievement."

Those are three institutions and yours will differ. But the direction is consistent, and the number to plan against is months rather than weeks.

It takes longer still for anything involving vulnerable populations, sensitive data, or an unusual design. Build that in rather than discovering it.

Data collection is the stage that varies most, and it is worth being specific about why.

An online survey through a platform like SurveyMonkey or Qualtrics can close quickly — sometimes in weeks, occasionally in days, if the population is reachable and the incentive is right. The good news on this? Many online-program candidates finish this stage faster than they expected.

Interview studies, site-based research, and hard-to-reach populations are a different matter entirely, and those are where the year-long overruns happen.

Recruitment is the usual reason it overruns when it does. See our Methodology at Proposal Stage page on what to do when it stalls.

And the total is rarely what the program advertises. The advertised figure describes a candidate with no setbacks, full-time, with fast reviewers. Without outside aid? Plan against your own maximum registration period rather than against the brochure.

Those limits are often longer than candidates assume. Walden, to take one published example, allows up to eight years, with an extension available by petition. That is Walden's limit, not a general rule — yours may be shorter or longer, which is exactly why it is worth getting in writing rather than guessing.

And if the question is what help costs against what the extra terms cost, we have a page on exactly that.


What should I ask my program, and when?

This is the practical section, and it is the one nobody else provides.

Print these questions. Get written answers. Keep them.

Ask about the gates
  • What review bodies see my work, in what order, after my committee?
  • What is the typical turnaround at each, and what happens if it is returned?
  • How many times may work be returned before there are consequences?
Ask about time — including what happens if you run out
  • What is my maximum registration period, and when does it expire?
  • Under what circumstances can it be extended, and who decides?
  • What happens to my status if I take a leave of absence?
Ask about your committee — including what happens if your Chair leaves
  • Who appoints my committee, and can I request changes?
  • What happens if my Chair leaves the institution?
  • What happens if committee members disagree about my work?
Ask about requirements
  • Am I required to publish before I defend? Published, accepted, under review, or merely submitted? These are four different requirements and the difference between "accepted" and "submitted" can be a year of your life. Get the answer in writing — candidates routinely assume the stricter version when the looser one applies.
  • Am I required to use an existing validated instrument?
  • What is the institutional AI policy, and where is it written down?
And the one candidates never ask

What have been the most common reasons for a dissertation being returned at review here?

Somebody in your program knows the answer. It is the single most useful piece of information available to you, and it is nearly never volunteered.


Why has nobody told me any of this?

Not conspiracy. Distribution.

Your Chair knows the process but has done it from the other side, and much of it is so familiar to them that it does not occur to them to explain it. Your program administrator knows the deadlines but not the scholarship. Your handbook documents requirements without explaining function.

Every piece of it is known by somebody. None of them holds all of it, and none of them is responsible for giving it to you.

Which is why you are assembling it yourself, several years in, one surprise at a time.

One of seven pages on getting started. Browse all 62.

Fast Help & More Resources