What the file contains
A submission is not a document, it is a set of them, and the usual failure is assembling the parts on separate days without reading them against each other.
- The protocol itself, on your board's own form and in its own section order
- Consent and assent documents pitched at the reading level of your actual participants
- Recruitment material promising exactly what the data plan is able to deliver
- A decision on which review track your study belongs in before anything is drafted
- Site permission letters requested early, rather than promised inside the submission
- A CITI training walkthrough where yours is not finished yet
- Every revision request answered in the committee's own numbering, until cleared
The audit read
Before anything is submitted, somebody who did not write it reads the whole file end to end in one sitting, deliberately as a stranger would. They are not checking whether the research is good. They are checking whether the documents agree.
It catches the same handful of things almost every time: a duration that differs between the protocol and the consent form, an anonymity promise sitting beside a question that collects an identifier, a procedure described in two orders. None of these are dishonesty. They are what happens when four documents get edited on four different evenings, and they are also the commonest reason a packet comes back.
The parts people forget until they are asked
Site permission letters are the classic. Students promise them inside the submission and then discover that the organisation granting permission wants its own approval process first, which takes weeks nobody budgeted. Requesting them at the beginning removes an entire category of delay.
CITI training is the other one. It is not difficult, it simply takes an evening nobody has scheduled, and a submission cannot proceed without it. The desk walks you through the modules relevant to your study rather than leaving you to work out which certificate your board actually wants.
Plan the analysis before you collect anything
This is the advice that saves the most money and gets taken the least. Agreeing which tests answer which questions, and confirming your sample can support them, costs an afternoon at the design stage. Discovering afterwards that the data cannot answer the question costs a term and sometimes a rebuild.
The same specialists cover that planning and the analysis itself in SPSS, R or Excel, with output written as sentences a committee reads without effort rather than pasted from software. Where the chapters themselves are the difficulty, the mentoring side runs alongside rather than after, and this piece covers the revision letter in detail.
Send what exists
Your topic, your board's template and any draft. Read and priced within two hours, at no cost.
Build and audit
Route settled first, then the file written, then read end to end by somebody who did not write it.
Answer and clear
Revision points handled inside the week, planned around your committee's real meeting dates.
Questions people actually ask.
Realistically, how long until I am cleared?
What governs it is the track you file under and when your committee next convenes, far more than what you are studying. Low-risk submissions on the fast routes frequently clear inside a few weeks. Anything wanting a full sitting simply waits, which is why hitting a submission window beats writing quickly.
Do you write the protocol, or only check it?
Either, and the cheaper order is worth knowing. Sending a finished draft for an audit read costs less than commissioning the file, and if the draft turns out to be essentially sound you are told exactly that. Students who want the whole thing built from a topic and a blank template are equally common.
Can the desk handle statistics too?
Yes, and it works far better arranged before collection than rescued afterwards. That covers matching tests to your research questions, checking the sample can carry them, then running the analysis and writing the results in language a committee reads comfortably. Tables are built to your school's template rather than pasted out of the software.
Is getting help with research consulting allowed?
Advising on design and documentation is ordinary academic practice and your chair does a version of it. The conditions are that the study belongs to you, the data is really collected, and every choice is one you can defend aloud. The desk works to that standard because anything looser falls apart at the defense anyway.
My study involves a vulnerable population. Is that harder?
Slower rather than harder, and entirely workable with a realistic timeline. Expect a full committee review and a file that anticipates what those populations always raise: additional protections, assent alongside consent, and a genuinely careful account of what could go wrong and how each risk has been reduced.
