01The board reads a document, not your intentions
Reviewers have your file and nothing else. They cannot ask what you meant, so anything ambiguous is resolved against you, and any question the form left unanswered becomes a comment. A study you could defend in five minutes of conversation still fails on paper if the paper leaves a reviewer guessing about who is recruited, how consent is obtained or where the data will live.
So the protocol is written into your board's own template rather than adapted into it afterwards. Each field is answered in the language the field uses. Where the template asks a question your design had not yet settled, that is settled before submission rather than after a reviewer notices it, which is the difference between a decision you make and a decision that is made about you.
- Protocol drafted directly into your institution's current template
- Consent documents written at a readable level for the people signing them
- Instruments, recruitment wording and permission letters prepared as one package
- Data handling described concretely: what is stored, where, for how long, who sees it
- CITI records checked as current before a single document goes in
02Submit the whole package or none of it
The commonest avoidable delay has nothing to do with ethics. A protocol arrives without the survey attached, or with a consent form that describes a different procedure, or with a recruitment email nobody wrote because it was not on the checklist. The file is returned, and the wait starts again from the back of the queue.
Everything is therefore assembled and cross-read before submission. The consent document has to describe the same procedure the protocol describes. The instrument has to collect the variables the analysis plan uses. Site permission has to exist if the setting belongs to somebody else. One inconsistency between two attachments is enough to produce a comment, and every comment costs a cycle.
03What a revision letter is actually telling you
Comments sort into a small number of families: the scope is wider than the design justifies, a risk is understated, the consent wording sits above what the people signing it can comfortably read, or the data plan does not say who can identify whom. Reading the letter as a list of edits misses this. Reading it as four questions answers it.
The response addresses every item explicitly, marks what changed and where, and never quietly declines one. Reviewers reread against their own letter, and an unanswered point returns as a second comment. Approval is the board's to give and nobody outside it can promise a decision; the aim is a submission with nothing left in it for a reviewer to raise. The chapters around the protocol run under capstone and dissertation support, and the analysis behind it can be handled alongside coursework where a course is running at the same time.
Send what exists
Your board's template, your proposal or method chapter, and any letter you have already received. Reading it and pricing it is free and takes about two hours.
The package is built
Protocol, consent, instruments and permissions are drafted together and cross-read so no two documents describe different studies.
Letters answered in full
Every reviewer comment gets an explicit response and a marked change, and the resubmission goes back quickly rather than eventually.
FAQQuestions to control
Can you guarantee my study is approved?
No, and any service saying otherwise is describing a decision it does not control. Approval belongs to your board alone. What is controllable is how many rounds it takes: a complete package, written on the board's own template, with the consent form and the instruments agreeing with the protocol, removes most of what reviewers actually write back about.
How many revision rounds should I expect?
Fewer than most students experience, though rarely zero, since boards frequently ask for at least one clarification as a matter of routine. The point of the work is to eliminate avoidable rounds, which are the ones caused by missing attachments, inconsistent documents and vague data descriptions rather than by anything genuine about your research design.
My protocol came back with a long letter. Is that bad?
Usually not. Length reflects thoroughness rather than judgement, and a detailed letter is more useful than a short one because it tells you exactly what the board needs. Send the letter with your submitted file. Every comment is sorted, answered explicitly, and the changed text is marked so a reviewer can verify the response without rereading the whole protocol.
Do you write the consent documents too?
Yes, and they are treated as their own problem rather than as an appendix. A consent form has to be understandable by the people signing it, which usually means shorter sentences and plainer words than the protocol uses, while still stating the procedures, the risks, the voluntary nature of participation and how confidentiality is actually maintained.
Who does this work?
Researchers who hold doctorates and have taken their own studies through review boards, which is not the same as having read about the process. The research and review lead on the crew carries a PhD. Where a study needs statistical expertise the protocol has to describe accurately, the analysis plan is written with the statistics lead rather than approximated.
