Answering the board's revisions so the next pass is the last
Most files that go round three times were sent round the second time by their own first response. A revision response is not an essay and not an apology; it is a closing instrument. It answers every item the board raised, in the board's order, and it leaves no new question behind it. At Grand Canyon University the portal shapes how that is done, and the mechanics are unforgiving in ways that are easy to miss.
The short answer
Answer inside the same submission packet, never a new one. Address each item where the reviewer raised it, re-version every affected document rather than uploading a replacement, change each altered sentence everywhere it appears, add nothing unrequested, and sign off once.
Where does a GCU revision response actually get written?
Inside the file that was returned. When an analyst asks for revisions, GCU's portal places a Submission Response folder on your home page, and that folder stays there until the corrected form has been sent back. Opening it produces the Revision Request Form, and the reviewer's questions appear inside it, at the points in the application where they were raised. You write your answers into those fields. That is the whole architecture: the board asks in place, and you answer in place.
Two portal behaviours surprise almost everyone. Once a packet has been routed to the IRB, documents can no longer be deleted — only checked out, with a new version checked back in. And you cannot add a document the reviewer did not ask for; the upload route opens when a request opens it. Both rules point the same way: the board keeps a versioned record of one file, not a fresh pile of attachments each round.
There is also a housekeeping message worth reading carefully rather than clicking past. If a comment reads that no revision was entered, GCU's own guidance says that indicates the request was not entered correctly on the analyst's side, and the fix is to contact the IRB office rather than to guess at what was meant. Guessing at an unstated request is how a response answers the wrong question with great confidence.
How do I work through the response form without breaking it?
The sequence GCU documents is short, and each step has a trap attached.
- Open the Submission Response folder and reach the revision request form through the edit icon beside the study.
- Read every comment before writing anything. The items interact: one change to the sample answers three questions at once, and answering them separately produces three slightly different sentences.
- Enter revisions where the questions sit, then save and continue to the next section. The form expects to be walked end to end; untouched sections can leave the packet reading as incomplete.
- Use the revise-existing control for further changes. The first use creates a new form version, after which a comparison view shows the two side by side. That version cannot be deleted, but it can be revised as often as needed.
- Accept a new form version if prompted. Where the IRB has published an updated application form since your submission, GCU's guidance is explicit that you must convert to it — and then click through the whole application again, because the conversion can introduce questions that did not exist when you filed.
- Sign off and submit once. Everything you meant to change has to be in the form by then.
A small detail with outsized consequences: marking an action complete in the document revision area is described by GCU as a tracking convenience, not a confirmation that anything succeeded. Verify the version actually attached before signing off. The board reads what is attached.
How are the documents themselves revised?
Through a check-out and check-in cycle rather than a replacement upload, which is the part most people get wrong under pressure. You select the document, create a revision — the version number increments on its own — check the document out, complete the checkout, edit the downloaded file offline, then check it back in by choosing the edited file and saving it. The old version does not disappear; it is superseded, and the board can see both.
That versioning also answers a question people ask nervously: what if the board can see my earlier consent form? It can, and that is fine. What it must not see is two live versions of the same promise, or a consent rewritten in ways the response never mentions.
Where the convened board is reading the study, GCU's procedure is more specific still. A response to a proposal requiring substantive revisions is expected to arrive with the revised protocol in tracked-changes form, or a document saying where each change was applied, and with revised consent or authorization forms in both tracked-changes and clean form. The board wants the change and the finished text separately. One further rule keeps a long file honest: significant amendments are folded into the current protocol so only one complete protocol exists, with revision dates marked.
What does the response itself have to say?
Every item, in the board's order, with a plain statement of where the change now lives. The structure below is what lets a reviewer close each point without hunting.
| What the board asked | What actually closes it | What else has to move |
|---|---|---|
| Attach a missing exhibit | The document, in the field the form provides, in its current dated form | The application answer that refers to it, so the file names what it now contains |
| Reconcile two documents that disagree | A decision about which is true, applied to the application field first | Consent, assent, recruitment material and any instrument description carrying the same fact |
| Close a protection gap | A changed procedure, described in the application in the board's own terms | The consent promise and the recruitment language, which must not outrun the procedure |
| Answer a question of fact | A direct answer in the field where it was asked | Nothing — resist the urge to improve neighbouring answers |
| Something that changes the method | Your chair and committee, before a word is written into the form | The proposal itself, so the application never gets ahead of the approved text |
Write each answer so it can be read alone. A reviewer working through a queue should be able to take item four, see what was asked, see what was changed, and see where the change now appears, without reconstructing the argument from three other items. Where you have declined to make a change, say so and say why, in one sentence — GCU's convened-review procedure anticipates exactly that, allowing an approval to be affirmed where the investigator has satisfied the requested modifications or provided a justification the board finds acceptable for not implementing one.
Why do second returns happen?
Almost always for one of five reasons, and all five are avoidable.
- A partial fix. The consent was corrected; the recruitment letter that repeats the same promise was not.
- An answer given only in prose. The response memo explains the new procedure, but the application field still describes the old one. The application is the document of record.
- New drift. An unrequested improvement appears in the revised text, and the reviewer now has a difference to ask about that nobody raised.
- An expired exhibit. A site authorization or an instrument permission that has gone stale while the file was in review. GCU's doctoral package checklist asks about exactly this, and expects a clear date stamp to be visible.
- A method change smuggled in as an edit. The one that costs the most, because it reopens the question of whether the file still matches what the committee approved.
The test worth applying before signoff is mechanical rather than literary: lay any two documents side by side and check that they say the same thing about population, inclusion and exclusion, what participants are asked to do, what is recorded, who can see it, and when it is destroyed. GCU's checklist demands that inclusion, exclusion and activities match exactly across application, consent and recruitment material. That is not a style preference. It is the test the reviewer runs.
What happens after the response goes back?
The status moves to show revisions complete, and the file re-enters review. Where the deferral named specific minor revisions, GCU's procedure lets the chair or the Office of Academic Research confirm them without another convened meeting. Where it named substantive revisions, the same convened board re-reads the file at a scheduled meeting, and may allow the investigator to present in person. Either way nothing begins until an approval notice exists — and where an approval arrives with a condition attached, data collection waits until that stipulation has been met and accepted.
If the letter has not yet been diagnosed — which desk sent it, which items are drift rather than genuine questions — start with how to read a returned GCU application. Where the response touches consent language, what the consent is required to say covers the promises that have to stay aligned, while the process step by step places this stage inside the wider route.
What to do next
Send us the board's letter and the packet as it stands. The free application review returns a written reading: each item classified, each document that has to change identified, and a plain statement of anything needing your chair before it can go into the form. From there the response, the re-versioning and every subsequent reply can move to this desk — how it works sets out the division of labour. Your research and your conclusions never move; nor does the ruling, which belongs to the board alone. What can be changed is the quality of the file it reads.
Sources
- GCU — How to Revise Your Application After IRB Review in iRIS
- GCU — How to Revise Uploaded Documents in iRIS
- GCU — How to Track the Status of Your iRIS Application
- GCU — iRIS IRB FAQ
- GCU IRB — Procedure for Review by Convened IRB
- GCU IRB — Doctoral IRB Package Checklist
- 45 CFR 46.109 — how a board reviews research
- 45 CFR 46.111 — findings required before an approval
Where this article and GCU's own materials differ, GCU's current doctoral handbook or IRB portal governs. gcuirb is an independent practice and is not affiliated with, endorsed by or connected to Grand Canyon University.