Changing an approved study at Walden: the change-in-procedures request and what must wait

Why does a small change need the board at all?

Because the board's approval is not a blessing on your intentions — it is a determination that a particular set of procedures satisfies the criteria in 45 CFR 46.111: risks minimised, selection equitable, consent adequate, privacy protected. Change the procedures and the determination no longer covers what you are doing. The regulation is explicit about the machinery: 45 CFR 46.108 requires procedures for "prompt reporting to the IRB of proposed changes," and requires investigators to keep running the study exactly as approved until the board has approved the difference — the only carve-out being action needed at once to remove an apparent, immediate hazard to a participant.

Notice what the rule does not contain: a size threshold. No change is small enough to skip the board — the board decides what is minor, not the researcher. What "minor" changes is the review path, not the requirement: under 45 CFR 46.110, minor changes to previously approved research during the approval period may be reviewed on the expedited path rather than by the convened board. Walden has long published a request form for exactly this purpose — a change-in-procedures request — with its current name, format, and route in Walden's handbook and IRB portal. The principle beneath the form has not moved: describe the difference, attach the documents, wait for the letter.

What counts as a change the board must see first?

A useful test: if a participant, a site administrator, or a future reader compared what you did against the approved file, would anything differ? If yes, it is a change. The table covers the changes Walden capstone and doctoral studies most often need.

Two rows deserve a flag. Instrument and sample changes are rarely the board's alone, because they alter the proposal your committee approved and the University Research Reviewer concurred with; bring the change to your chair before, or alongside, the request to the board. And a site added mid-study needs what the original site needed: written permission on letterhead, signed at a level with real authority, naming what you will do there. Our application checklist lists those enclosures in their original roles.

What goes into the change request itself?

Whatever shape Walden's current form takes, a request the board can approve without a follow-up answers five questions in order:

1. What is changing? The old procedure and the new one, side by side, in concrete terms. "Interviews will be conducted by video call rather than in the site's conference room" — not "minor logistical adjustments."
2. Why? One or two honest sentences. Sites close, response drops, schedules collapse; boards read reasons every week and are not scandalised by reality.
3. Does risk change? Walk the change through risk, privacy, and voluntariness explicitly. A video call moves the conversation into the participant's home and onto a platform — say what that does to privacy and how the plan absorbs it. If risk honestly increases, say so; pretending otherwise costs a review cycle.
4. Which documents change? Attach every revised enclosure — consent, recruitment, instrument, data plan, site letter — version-stamped, old versions withdrawn. The file must agree with itself after the change as it did before; a change described in the request but absent from the documents is the most common reason these requests bounce.
5. What about people already enrolled? If the change touches anything participants were told — procedures, recording, time asked, confidentiality — say whether they will be re-consented or notified. 45 CFR 46.116 expects significant new findings bearing on willingness to continue to reach the participant; a changed procedure can be exactly that.

What may you keep doing while the request is pending?

The approved study, exactly as approved — and only that. The pending request changes nothing until the board's written approval arrives. Three disciplines follow. Do not run the new procedure "just this once" because a participant prefers it; an accommodating exception is still an unapproved change. Do not pause-and-improvise — if the approved procedure has become impossible, the study pauses there until the change is approved. And do not treat the request as retroactive paperwork. If a deviation has already happened — a question the instrument did not contain, a record opened outside the approved set — report it promptly, through the route Walden's handbook prescribes, alongside the problem-reporting your approval letter describes. Boards distinguish sharply between a researcher who reports a deviation and one whose deviation surfaces later; only the first keeps the board's trust.

The one true exception is the hazard clause above: to protect a participant from immediate harm you act first — end the session, secure the data — and tell the board promptly afterwards. The exception protects participants, never timelines.

How does the board review a change?

Proportionately. A minor change during the approval period is eligible for expedited review under 45 CFR 46.110 — experienced reviewers rather than the convened board — and most Walden change requests travel that path. A change that raises risk, adds a vulnerable population, or reshapes the study reads more like a new file; one large enough to make the study a different study may go back through the committee sequence first. The reply comes in writing and may approve, ask questions, or require modifications — the same spectrum described in what a returned Walden application means, applied to a smaller file. Answer it the same way: item by item, document by document, once.

File the approval you receive with the original letter. The change letters accumulate into the authoritative description of your study, 45 CFR 46.115 keeps the whole correspondence in the board's records, and your final study document must describe what was actually done under the versions actually approved. A tidy change file writes that final chapter itself; a loose one sends discrepancies to your committee's desk at the worst moment. The rest of the after-approval period — review and closure — is covered in continuing review and closing your study at Walden.

A short checklist before you file the request

1. The change is stated old-versus-new, in concrete terms a stranger could act on.
2. The reason is honest and brief.
3. Risk, privacy, and voluntariness are each addressed, not waved at.
4. Every touched document is revised, version-stamped, and attached; the file agrees with itself.
5. Changes that reach the proposal have gone to your committee chair.
6. Already-enrolled participants are addressed: re-consent, notification, or a stated reason neither is needed.
7. Nothing new has been done yet — and any accidental deviation is reported, not laundered into the request.

What to do next

If a change is coming — a site wobbling, a recruitment channel running dry — start the request before the study forces it, and start with whichever enclosure needs another signature. If you would rather hand it over, amendments are part of what the desk carries under a full engagement: we draft the request, rewrite every touched document so the file stays consistent, route the committee where the proposal is implicated, file it, and answer the board's reply — as we do the original application and every letter after it. How it works describes that arrangement, and the FAQ covers the questions candidates ask alongside it. Unsure whether your plan even counts as a change? Send the approved file and a paragraph on the difference through the free application review — the desk will tell you plainly, including when the honest answer is that no request is needed. The study stays yours; the decision stays the board's.