Six checks to run before you submit
Print the whole packet and read it end to end in one sitting, as somebody encountering it for the first time. You are not evaluating the research, you are hunting for disagreement between documents. These six catch most of what would otherwise come back.
- Does every document state the same duration for the same activity?
- Does the consent form promise a level of privacy the data plan can actually deliver?
- Is anything identifying collected that the recruitment material implies is not?
- Could a participant work out what happens to them, in order, from the procedure section alone?
- Was the consent form pitched at whoever signs it, or at the person who wrote it?
- If you hold authority over your participants, does the packet say what you have done about that?
Read it aloud to somebody outside your field
The most effective free check available, and almost nobody does it. Find a person who does not work in your discipline and read them the consent form and the procedure section. Not the protocol, just those two.
What you are listening for is the moment they stop following. Every place they interrupt is a place a reviewer will pause too, and a reviewer cannot ask you what you meant. They write a clarification request instead, and that costs a meeting cycle. Ten minutes of somebody looking politely confused will save you a month.
The four things a committee is checking
It helps enormously to know the actual scope, because students arrive braced for a critique of their research and receive something much narrower.
Whether risk to participants is identified and reduced. Whether consent is genuinely informed rather than merely signed. Whether data is handled the way the packet claims. And whether every document tells the same story. Scientific merit belongs to your chair and your committee, not here, which is why a defensive submission reads oddly to the people assessing it.
Where we come in
You can do all of the above yourself, and this page exists partly so that you can. Paying for it puts the audit in the hands of somebody who has assessed these from the committee's chair, which surfaces a different category of fault: the phrasing certain to trigger a query, or the gap that looks like inattention instead of economy.
The full build, from protocol on your board's own form through consent documents and site letters to the revision responses, is the research desk. And when a letter does come back, this explains how to answer it so that the next sitting clears rather than the one after.
Run the six checks
One sitting, whole packet, hunting for documents that disagree. Free, and it catches most returns.
Send what you have
Your draft, your board's template and its meeting dates. Read by a specialist and quoted within two hours.
File into a window
Audited, reconciled, and submitted against a specific meeting rather than whenever it happens to be ready.
Questions people actually ask.
What causes most returns?
Documents that disagree with each other. A protocol stating one duration beside a consent form stating another, or a recruitment message promising more privacy than the data plan can deliver. Nobody is being deceptive. This is simply what four files edited across four different nights look like, and one attentive read catches nearly all of it.
Who should I get to read it before submission?
Somebody outside your discipline, and read the consent form and procedure section to them aloud. Wherever they stop following is precisely where a reviewer will pause, except a reviewer cannot ask what you meant and issues a clarification request instead. Ten minutes of that saves a meeting cycle more often than any amount of polishing.
Can you audit a packet I have already written?
Yes, and it is the cheapest thing on this page. Send the whole file and it gets read end to end by somebody who has sat on the committee side, looking for contradictions, ambiguity and the omissions that reliably generate clarification requests. If it is already sound, you are told that rather than sold a rebuild.
What is actually being assessed?
The list is short. Has the risk been named and lowered. Will the person signing actually understand what they are agreeing to. Does the data get treated the way you say it does. And do your own documents tell one consistent story. Scientific merit belongs to your chair rather than to a review committee, which is why arriving braced for a critique of the research reads strangely to them.
Is getting help with a protocol acceptable?
Taking advice on how a study is designed and written up is unremarkable in academia, and your supervisor supplies a version of it already. Three things have to hold: the research belongs to you, the data was really gathered, and you can stand behind every decision when asked. Looser than that and the defense exposes it whatever the paperwork looked like.
