What a board is actually looking for
It helps to know who reads this. A review board is a committee of people who volunteered on top of full jobs, working through a stack of submissions in an evening. They are not evaluating whether your study is interesting. They are checking that risk to participants is identified and minimised, that consent is genuinely informed, that data is protected, and that nothing in your procedure contradicts anything else in your packet.
Almost every delay comes from the last of those. A recruitment script that promises anonymity while the demographic form asks for a work email. A protocol saying interviews are thirty minutes and a consent form saying an hour. Boards catch contradictions because contradictions are the easiest thing in the world to catch, and each one costs you a revision cycle.
- Protocol written in your board's own template, in its own section order
- Consent and assent forms at the reading level your population actually has
- Flyers, emails and scripts that say precisely what the protocol says
- Instruments, with permission letters where the tool is somebody else's
- Data handling: where it lives, who opens it, when it gets destroyed
- Site permission letters chased before you submit, not after
Exempt, expedited or full board
Which category you fall into changes the timeline more than anything else you control, and students routinely aim at the wrong one. A minimal-risk survey of adults is a different animal from anything touching patients, minors, prisoners or protected records, and submitting the wrong category means starting again rather than being redirected.
So that gets settled before a word of the protocol is written, by somebody in the study group who has read submissions from the other side of the table. If a small change to your design keeps you in the faster lane without weakening the study, you'll hear about it while it's still cheap to make. Sometimes it's as small as who hands out the recruitment flyer.
The revision letter
Very few packets clear on the first pass, and yours coming back is not a failure. It's a numbered list, and answering it well is a specific skill. Each point gets its own response, in the board's numbering, saying exactly what changed and where, with the changed language quoted so nobody has to hunt for it.
What sinks people is arguing. A board member who asked for a clearer risk statement does not want a paragraph explaining why the original was fine. They want the clearer statement. Responses go back inside the week, because review cycles have a rhythm and missing one meeting can cost a month.
After approval, the study still has to work
Approval is a gate, not a finish line. The same people can stay with you through recruitment, the analysis and the chapters that come out of it, which matters because a method described one way in your protocol and another way in chapter three is a defense-day problem.
That covers survey design, statistical planning agreed before you collect anything, and the analysis itself in SPSS or R with output translated into language a committee reads comfortably. If the write-up is the part you're dreading, capstone coaching picks it up chapter by chapter, and the two run together rather than in sequence.
Send what you have
Your topic, your school's IRB template, and whatever draft exists. Read and priced within two hours, free.
Build the packet
Category settled first, then protocol, consent, instruments and letters, written to be read in one sitting.
Answer and close
Revisions handled point by point the same week, until the approval letter is in your hand.
Questions people actually ask
Realistically, how long until I'm approved?
It depends on your category and your board's meeting calendar far more than on your topic. Minimal-risk work in the exempt or expedited lanes often moves in a few weeks. Anything needing a full board sits until the next scheduled meeting, so missing a submission window is what actually costs you time. We build backwards from those dates rather than submitting whenever the draft happens to be ready.
My protocol came back with fifteen comments. Is that bad?
No, it's normal, and it's usually a good sign that the board engaged properly. Fifteen small clarifications is a far better outcome than three comments that question your whole design. Every point gets answered in the board's own numbering, with the revised wording quoted so nobody hunts for it, and the response goes back inside the week.
Do you do the analysis too?
Yes, and it's better when the same people plan it before you collect anything. That means agreeing your tests against your questions, checking your sample can actually support them, and then running the analysis in SPSS or R with the output written up in language a committee reads without effort. Tables get built to your style manual rather than pasted from the software.
Is any of this against the rules?
Consulting on research design and documentation is ordinary academic practice, and your committee chair will be doing some version of it too. What matters is that the study is genuinely yours, the data is genuinely collected, and you can answer for every choice in the room. We work to that standard because anything else falls apart at the defense.
Who actually writes my protocol?
A PhD-holding specialist with real board experience, matched to your discipline, and they stay with you from the first draft through to the approval letter. That continuity matters here more than almost anywhere else, because your protocol, your consent form and your recruitment script all have to keep saying the same thing.
