How to answer Walden IRB revision requests so the second pass is the last one
A revision request from the Walden IRB is answered with a ledger, not a letter of explanation: each item the board raised, beside the exact change made and the enclosure where the reviewer will find it. Every document the change touches is revised in the same sitting, anything that alters the proposal your committee signed is flagged rather than slipped in, and the whole file goes back once. The board then has one job left — confirming — instead of a second reading.
Build a ledger: the board's item, your change, the document and page it lives in. Revise every enclosure the change ripples into. Flag anything that touches the signed proposal. Resubmit the whole file once, through the channel the board used, with nothing left open.
What is the reviewer actually doing with your response?
Under 45 CFR 46.109, an IRB may approve research, require modifications to secure approval, or disapprove it, and it must tell the investigator its decision in writing. A Walden revision letter is the middle outcome: the board has told you, in numbered or bulleted terms, what stands between this file and an approval. When your reply arrives, the reviewer is not starting over — they hold the letter they wrote in one hand and your file in the other, moving down the list: is this item closed, and did closing it break anything else?
That framing settles how a response should look. The reviewer needs to find each change without hunting, see it carried into every document it affects, and be confident nothing else moved. A reply that is terse but precise — item, change, location — lets the board confirm mechanically, which is the fastest route to the letter that carries the approval number. Which portal fields or email threads the exchange runs through is set by Walden's current handbook and IRB portal; the discipline of the reply is the same on every route.
How should the response be laid out?
One row per item, in the board's order and wording. If the letter numbered its requests, keep those numbers; if it was written in paragraphs, number the sentences yourself and note that in a brief preface. Four columns carry everything the reviewer needs.
| The board asked | What changed | Which enclosure, which page | Touches the signed proposal? |
|---|---|---|---|
| How prospective participants will learn of the study | Added the recruitment email and the unit-board flyer, verbatim, as separate enclosures; the application now names both channels | Recruitment email v2, Flyer v2; application, recruitment section | No — channels were described in the proposal |
| Voluntariness and the right to stop | Added a plain-language clause stating participation is voluntary, may be ended at any time, and has no effect on employment or care | Consent document v3, under "Voluntary nature of the study" | No |
| Where data are stored and who has access | Replaced "securely stored" with the named encrypted drive, the access list, the retention period Walden specifies, and the destruction method | Application, data-security section; consent document v3, confidentiality section | No |
| Reduce the interview count from twelve to eight | Not changed — explained below; committee notified and a response from the chair is attached | Response memo, item 5; chair's email | Yes — sample size is in the approved proposal |
The fourth column is the one most responses omit and the one that keeps files out of trouble. Walden fixes the order of review — committee, University Research Reviewer, then board — so a revision that changes what the committee approved is not yours to make alone in reply to the IRB. It goes to the committee first, and the ledger says so.
Which documents must change together?
Almost no revision lives in one place. The board reads your file as a single claim about how the study will run, and it reads for drift — a consent document promising anonymity while the application describes audio recording, a flyer offering a gift card the application never mentions. A reviewer who finds one inconsistency looks for more. Before sending anything, walk the ripple:
- A consent change ripples into the application's consent-process answers, any recruitment script that summarises participation, and the data-security description if confidentiality language moved.
- A recruitment change ripples into the application's recruitment section, the letter of cooperation if the site's role changed, and the consent document's account of how the person was approached.
- A data-handling change ripples into the consent document, the application, and any agreement or site letter naming what will be accessed.
- An instrument change ripples into the application's procedures and, because instruments sit in the approved proposal, back to the committee.
- Any change at all ripples into the version stamp: a new label and date on the revised enclosure, the superseded version removed rather than left beside it.
When the ripple is complete, the file says the same fact the same way everywhere it appears. That single property — internal agreement — is what a second-pass reviewer looks for, and what a hurried response most often lacks. Our application checklist lists the enclosures a Walden file carries so none is missed in the sweep.
What does a good answer sound like?
The board's requests arrive courteous and general; good answers are specific and short. Two contrasts show the register.
- Asked how confidentiality will be protected, a weak answer says the data will be kept confidential and secure. A strong answer names the encrypted device, says identifiers become codes with the key stored separately, states the retention period Walden's current handbook requires, names the destruction method — and points to the consent clause where the participant is told the same.
- Asked about the researcher's relationship to the site, a weak answer denies any conflict of interest. A strong answer describes the relationship plainly — employed on the unit, no supervisory authority over prospective participants — then describes the separation built into the design: who recruits, who holds the roster, how a colleague's refusal stays invisible. Where the board raises this, the dual-role plan is the answer.
In every case the reply points to a document rather than standing in for one. Where the board wants a clause, the clause is written into the consent; where it wants a letter, the letter is enclosed. The ledger is a map to those places, not a substitute for them.
What should you avoid in the reply?
- Arguing the point. Occasionally the board has misread something. Say so in one calm sentence, quote the passage that already answers the concern, and let the reviewer judge. A page of defence reads as an unrevised file.
- Partial replies. Sending the finished items while two are still with the site starts a fresh reading of an incomplete file. Wait for the letter of cooperation; send once.
- Unannounced changes. If you improved something the board did not ask about, list it in the ledger under its own heading. Silent edits discovered on comparison cost you the reviewer's trust.
- Mixed versions. An old consent document left beside the new one is the most common reason a second pass becomes a third.
- Starting anything. Nothing is approved while the exchange is open: no contact with prospective participants, no survey link, no chart opened — and no informal conversations that are really recruitment.
How do you resubmit at Walden?
Answer through the route the board used to reach you. Walden's current handbook and IRB portal set whether revised enclosures are uploaded to the application record, attached in reply to the board's message, or both. Whichever it is: keep the board's reference so the reply lands on the right file; attach every revised enclosure with its new version stamp, plus the ledger; and keep your committee chair informed where Walden's process expects it. Then stop — a follow-up asking whether the file arrived adds a second item to the reviewer's queue without moving the first.
If the next letter asks one more clarification, answer it the same way — ledger, document, version — without treating a single further question as failure; it is the board confirming. The exchange ends when the board's letter carries the approval number Walden expects printed in the final study; until then, the study is not open. What the first returning letter actually meant, and how to read it before revising, is covered in what a returned Walden application means.
A short checklist before you send
- Every item in the board's letter has a row in the ledger, in the board's order and wording.
- Every row names a document and a location, or states plainly that nothing changed and why.
- Every document the change ripples into is revised, re-stamped, and swapped for its old version.
- Anything touching the committee-approved proposal has been raised with the committee; the ledger says so.
- The file states each fact — recording, incentive, retention, who recruits — the same way everywhere.
- Your CITI completion is current, under the name the application carries.
- Nothing has been started. No participant, no record, no link.
What to do next
If a revision letter is sitting in your inbox, the first move is the ledger, not the documents — list what the board asked before deciding what to change. If you would rather not carry the exchange yourself, this is the part of the Walden process the desk handles most often: we write the ledger, revise every enclosure the board touched so the file agrees with itself, flag what belongs to the committee, file the resubmission, and answer every letter after it until the approval number arrives. How it works describes the engagement; the FAQ answers the questions that arrive most. Send the board's letter and the file as it stands for the free application review, and we will tell you which items close with a sentence and which reach into the proposal — before you commit to anything. The study stays yours; the decision stays the board's.
Sources
- 45 CFR 46.109 — IRB review of research: authority to approve, require modifications to secure approval, or disapprove; written notification of the decision: law.cornell.edu
- 45 CFR 46.110 — expedited review: reviewers may exercise the IRB's authorities except disapproval: law.cornell.edu
- 45 CFR 46.116 — informed consent: circumstances that minimise coercion or undue influence, understandable language, voluntariness and withdrawal: law.cornell.edu
- 45 CFR 46.115 — IRB records, including all board-investigator correspondence: law.cornell.edu
- Walden University Handbook, Doctoral Learning and Resources — weekly review; decisions are not appealed, the chair instead working proposals "into an approvable state": academics.waldenu.edu — doctoral research resources
- Walden Quick Answers — common reasons ethics approval is delayed: stray references to superseded design elements, errors in participant-facing documents: academicanswers.waldenu.edu/faq/343947