TL;DR
When an IRB reviews your dissertation proposal, they are checking:
- Whether risks to participants are minimized and reasonable relative to potential benefits
- Whether you have clear, appropriate informed consent and recruitment procedures
- Whether you protect privacy and confidentiality, and address vulnerable populations correctly
- Whether your protocol and materials match each other and meet regulatory requirements
They are not required to judge whether your research question is interesting, original, or impactful in your field.
A clean IRB approval letter feels like validation: someone "official" signed off on your study, so it must be good, right? Not quite. IRB approval is proof that your dissertation is ethically and procedurally acceptable — not that your research question is brilliant, important, or well-designed.
If your application gets bounced back with revisions, or even a "reject," that says something about risk, consent, or paperwork. It says nothing about your worth as a researcher, and nothing about whether your topic deserves to exist.
How is IRB different from your dissertation committee?
Think of IRB and your committee as two different "review lanes" for the same project. They intersect, but they aren't judging the same things.
IRB evaluation focuses on risk level (exempt, expedited, or full board), consent language, data handling, and regulatory elements like the Common Rule requirements in 45 CFR 46. Your dissertation committee focuses on theoretical grounding, research design quality, methodological fit, contribution to the literature, and whether the project is feasible for you as a student. These scholarly merit criteria are not part of IRB's legal mandate.
| Lens | IRB review | Committee review |
|---|---|---|
| Primary focus | Risk to participants, compliance | Research merit & rigor |
| Approves/rejects based on | Ethics, consent, privacy, regulatory compliance (45 CFR 46) | Theoretical grounding, methodology, contribution to field, feasibility |
| Cares about your topic's importance? | No — not part of their mandate | Yes — central to their evaluation |
You can have an IRB-approved study with a weak research question, and you can have a strong, exciting dissertation idea that temporarily stalls at IRB because of a consent paragraph or a missing checkbox. Both outcomes are normal.
What do exempt, expedited, and full board review actually mean?
The type of review your dissertation gets is about risk, not "importance."
Exempt review is used for specific categories of low-risk human subjects research — certain educational tests, benign surveys, secondary use of existing data — that fit narrow criteria in 45 CFR 46.104(d).
Expedited review covers studies with no more than minimal risk that fit one of the federally defined expedited categories, typically reviewed by the IRB chair or a designated member instead of the full board.
Full board review is required for anything above minimal risk, or that doesn't qualify for exempt or expedited. It goes to a convened meeting, with a quorum and a majority vote. Read more on how review levels are determined.
A low-risk, survey-based dissertation on a sensitive topic might be exempt. A modest clinical or intervention study might go full board. Neither review level says "this research matters more" in academic terms — it only signals different oversight needs.
Why does IRB commonly ask for revisions?
Most revision requests are about mechanics and compliance, not your topic. Here's what you're actually being asked to fix:
| Revision issue | What this means | What to fix |
|---|---|---|
| Consent form missing required elements | Federal rules specify exactly what you must include — purpose, procedures, risks, benefits, confidentiality, voluntary participation. | Check 45 CFR 46.116 and add missing sections. |
| Consent written at too high a reading level | If participants are undergraduates or community members, a highly technical consent is a common barrier. | Rewrite at an 8th-grade level; remove jargon or define every term. |
| Protocol and consent don't match | Protocol describes one set of procedures; consent talks about different ones or omits a risk. | Cross-check all documents — procedures, risks, time commitment, and compensation must align exactly. |
| Recruitment materials overpromise or downplay risk | Ads sounding like guaranteed benefit, or compensation phrased in a way that looks coercive, trigger concerns. | Reframe recruitment language as neutral; describe compensation factually. |
| Missing protections for vulnerable populations | Studies with children, prisoners, or people with impaired decision-making need extra safeguards. | Add required procedures: assent + parental permission, prisoner representative, etc. |
| Incomplete training or documentation | Key personnel lack current human-subjects training; data security plan is vague. | Ensure all researchers have certificates. Detail where and how data is stored, who has access, and retention timelines. |
Notice what's not on this list: "Your question isn't important," "Your topic is boring," or "Your design is theoretically weak." Those are committee concerns, not IRB criteria.
How long does IRB review actually take?
Timelines vary by institution and risk level, but there are rough patterns worth knowing so you can plan around them instead of refreshing your email every hour.
Exempt determinations are usually the fastest — often one to three weeks, since they don't require a full committee meeting. Expedited reviews typically run two to four weeks, since they only need sign-off from the chair or a designated reviewer rather than a quorum. Full board reviews are the slowest, often four to eight weeks, because they depend on when the committee physically (or virtually) convenes — some boards meet monthly, not weekly.
Revisions add another round on top of whichever timeline you started with. A minor revision (fixing a consent readability issue, say) might only need the chair's sign-off and add a week. A substantive revision that changes your risk profile or procedures may need to go back through the same review level it started at, adding the full cycle again.
The practical upshot: build IRB review into your proposal timeline the way you'd build in any other dependency, not as an afterthought after your proposal defense. If your study is likely to need full board review, that alone is a reason to submit early rather than treating the application as a formality to knock out after everything else is finished.
Two real examples
A graduate student studying burnout among hospital nurses submitted an online survey to her IRB. It came back with three requests: simpler consent language, since the original was written at a graduate reading level while participants had varied backgrounds; a clearer explanation of how email and IP addresses would be stored and separated from responses; and a tweak to recruitment emails so they didn't imply that participating would help the nurses' employment prospects.
To the student, this felt personal — like the board didn't like her topic, or thought she was exploiting nurses. In reality, the board was making sure the study stayed low-risk and non-coercive. The topic itself — burnout — was never being judged for importance.
Compare that to a different case: a candidate studying disclosure patterns among survivors of intimate partner violence. Because the population was considered vulnerable and the topic sensitive, the study went to full board rather than expedited review — a slower process, with more scrutiny on the consent language, the debrief procedure, and what would happen if a participant became distressed during an interview. That's not the board signaling the topic was risky to study in an academic sense. It's the board doing exactly what full board review exists for: making sure a higher-risk population is protected more carefully. The topic was, if anything, more clearly important — it just needed a higher level of procedural care to match.
Can I start data collection before IRB approval?
Short answer: no. Beginning data collection without IRB approval — even if you expect exemption — violates federal regulations and could invalidate your entire study.
Here's why this matters. Starting before approval breaches 45 CFR 46, regardless of risk level — that's a regulatory violation, not a technicality. It also invalidates your data: even excellent data may not be usable in your dissertation if you didn't have prior approval, meaning months of work could become unusable. And it can affect your future, since graduate schools and employers verify IRB compliance, and violations can follow you into your credentials.
Always wait for written approval before participant contact, consent administration, or data collection. If you're waiting on a decision, use that time to pilot your instruments or refine your analysis plan — work that doesn't require participant data.
Why do advisors say "IRB is just paperwork"?
When advisors say "IRB is just paperwork," they don't mean it's unimportant. They mean three specific things: it's solvable and procedural, not a referendum on your research merit; your job right now is compliance and clarity, not brilliance; and delays or revisions are normal, and don't say anything about your worth as a researcher.
In this sense, "paperwork" is actually good news. Paperwork can be edited, resubmitted, and approved. Your research idea stays intact the entire time.
Does this mean my topic is bad?
No. An IRB rejection or revision request means your current plan for protecting people isn't acceptable yet — not that your idea is worthless.
"IRB feedback is about how I'm doing the study, not whether the study deserves to exist." The IRB is required to disapprove studies that don't meet risk, consent, or privacy standards, regardless of how brilliant the underlying question might be.
Many impactful studies on HIV, mental health, and other sensitive topics have gone through multiple IRB rounds before approval — in some published HIV human-subjects research, more than 30% of articles never mention IRB approval at all, even though the topics are clearly important. So: IRB approval is a safety check, not a quality badge. Lack of approval is a signal to revise your procedures, not your worth as a scholar.
What should you do next?
If your IRB application was rejected or sent back for revisions, treat it like a technical revision, not a verdict on your topic — the IRB Revision Checklist below walks through each category.
Map each comment to a specific requirement. Identify whether the issue is consent elements, reading level, recruitment language, data security, or vulnerable-population protections — naming the category makes it solvable instead of overwhelming.
Fix inconsistencies. Make sure your protocol narrative, consent form, and recruitment materials describe procedures, risks, and compensation exactly the same way, line for line.
Simplify and clarify consent. Aim for a reading level suited to your actual participants, include all required basic elements, and avoid jargon unless you define it plainly.
Strengthen privacy and data-security plans. Specify where data will be stored, who has access, how identifiers will be separated from responses, and how long you'll retain the data.
Address vulnerable groups explicitly. If you include children, prisoners, or other protected populations, add the specific safeguards your institution requires.
Confirm training and signatures. Ensure all study personnel have current human-subjects training and that all required institutional sign-offs are present.
Check review level expectations. Confirm whether your study is likely exempt, expedited, or full board based on risk — mismatches between how you describe risk and the actual design cause delays.
FAQ
Does IRB approval mean my research question is good?
No. IRB approval only confirms that risks to participants are minimized, consent is appropriate, and privacy is protected. It is not a judgment on whether your research question is interesting, original, or important — that's your committee's job, not the IRB's.
What is the difference between IRB and a dissertation committee?
IRB evaluates risk level, consent language, and regulatory compliance under rules like the Common Rule (45 CFR 46). Your committee evaluates theoretical grounding, research design, methodological fit, and contribution to the literature. These are two different review lanes for the same project.
What is the difference between exempt, expedited, and full board IRB review?
Exempt review covers narrow categories of low-risk research, like certain surveys or secondary data use. Expedited review covers no-more-than-minimal-risk studies, reviewed by the IRB chair or a designated member. Full board review is required for anything above minimal risk, and goes to a convened meeting with a quorum vote. The review level reflects risk, not importance.
Why did my IRB application get sent back for revisions?
Most revisions are about mechanics, not your topic: missing consent elements, consent written at too high a reading level, mismatches between your protocol and consent form, recruitment materials that overpromise benefit, missing protections for vulnerable populations, or incomplete training documentation.
Final thoughts
Working through this list turns IRB feedback into a structured, solvable problem rather than a judgment on your idea. (If the feedback itself feels vague or hard to parse, the same approach for reading unclear advisor feedback applies here too.)
A stamped ethics protocol is a license to proceed safely, not a medal that says "this dissertation matters." Your committee, your field, and ultimately your readers decide whether your research question is insightful and impactful — not the IRB.
IRB approval means you've convinced a board that your participants will be treated fairly, risks are reasonable, and rules are followed. That's it. It was never a verdict on whether your topic — once you've actually narrowed it down to a real question — was worth asking in the first place.
