Changing an approved Chamberlain project: which board must approve the change, and what waits
Your approvals cover the project as you described it, not the project as it turns out to be. When something has to change — a recruitment route that yields nobody, a unit that reorganised, an instrument that will not survive the workflow — the change goes back for a decision before it is put into effect. Chamberlain publishes a Study Amendment Application Form for exactly this, and names what triggers it. Then the question arrives a second time, because a DNP project also answers to the practicum site’s board, and that board sees nothing you do not show it.
Chamberlain states that proposed changes must be approved before they are implemented, and publishes a Study Amendment Application Form to request them. Ask which approval the change stopped describing — often both boards’ — and file with each separately. The only carve-out is immediate harm.
Does an approved project really have to go back?
Yes, and here the federal framework and Chamberlain’s own material say the same thing. Written procedures for a review body must ensure that proposed changes in approved activity are reviewed before those changes take effect (45 CFR 46.108(a)(3)(iii)). Chamberlain’s IRB page states it in its own words: proposed changes must be approved before they may be implemented. Propose, get the decision, then act — never act and report afterwards.
The reason is structural. An approval is a finding that one described activity satisfies a defined set of criteria. Alter the description and the finding no longer maps onto what is happening on the floor, leaving you running something nothing has approved. Chamberlain closes the retrospective escape route explicitly: its IRB Handbook states the board will not approve work already completed.
One line in the Handbook makes changes more consequential than people expect. Studies cleared through the lighter pathways are not subject to further review unless changes to the study occur. In other words, a change is precisely the event that reopens a file which had otherwise finished with the board.
What does Chamberlain say triggers an amendment?
Chamberlain’s IRB page publishes a Study Amendment Application Form and names four triggers: a change to the study title, a change to the lead investigator’s contact details, a change to the previously approved protocol, and a change to previously approved recruitment or consent materials. That last pair is the one most often overlooked — editing the wording on an information sheet or a recruitment flyer is a change to an approved document, not housekeeping.
A wrinkle specific to DNP work. Chamberlain’s DNP Project & Practicum Handbook routes these projects through a Prescreening Review Form rather than the full application package, and states that most such projects are expected to meet the prescreening criteria for a finding that the work does not constitute human subjects research. Whether a change to a prescreened project is handled by a fresh prescreening submission or by the amendment form is set by Chamberlain’s current handbook or IRB portal, and it is a question worth asking your project faculty in writing rather than guessing at.
Which board does this change belong to?
The useful question is not “is this big enough to report” but “whose approval has this change stopped describing”. Read each row against both columns; a great many changes answer yes twice.
| The change | What the Chamberlain side turns on | What the site’s board turns on |
|---|---|---|
| Altered recruitment route or materials | Named as an amendment trigger where the materials were previously approved. | Who is approached on their premises, by whom, and whether their people were consulted. |
| Adding a unit, a floor or a second facility | Whether the project described is still the project being run. | Almost always substantive — a new setting may fall outside the approval, or outside that board’s authority. |
| A different instrument, or new items on one | A change to the previously approved protocol. | What is now being asked of their people, and whether it reaches clinical information it did not before. |
| Where data lives, or who may see identifiers | Consistency with the data-security description already on file. | Usually the row they care about most: their network, their records, their exposure. |
| Edits to a consent or information sheet | A named trigger — previously approved consent materials. | That the sheet still says what their board approved, in the version their file holds. |
| A change of investigator contact details, or of the site liaison | A named trigger on the Chamberlain side. | Frequently a fresh signature: the support letter named a person, and that person has changed. |
| Changing the practicum site itself | Engages the project and practicum requirements, not only the review file. | A different board entirely — the previous site’s approval does not travel. |
Where a row is ambiguous, ask the board rather than deciding for it. An enquiry costs a message; an unapproved change is a different order of problem.
What is the carve-out, and how narrow is it?
There is one. A change may be put into effect without prior review where it is needed, in the regulation’s words, “to eliminate apparent immediate hazards” for the person taking part (45 CFR 46.108(a)(3)(iii)). Chamberlain’s own page carries the equivalent: a temporary change where there is a possibility of immediate harm, pending approval. Every word is load-bearing — the hazard must be apparent, immediate, and to the participant — and acting first is followed by reporting to the board, never instead of it.
What it never covers is the situation that generates most unapproved changes: a session ending, a recruitment route producing nobody, a manager proposing a different unit, a chair asking for one more measure. None endangers a participant. Those are reasons to file promptly, not reasons to proceed.
What has to wait while the change is under review?
The changed part waits; the approved part does not automatically stop. If you are seeking permission to add a second unit, work continues as approved on the first and nothing begins on the new one. If you are seeking approval for a revised information sheet, nobody may be enrolled on the revised sheet until it is approved — and where the revision exists because the old sheet was wrong, that is usually a reason to pause enrolment rather than keep using a page you no longer stand behind.
Two board-specific traps live here. First, one board’s approval licenses nothing on the other’s side. Chamberlain accepting an amended protocol does nothing for the site’s file, and site sign-off does nothing for Chamberlain’s; Chamberlain’s DNP handbook is explicit that both its own prescreening and the site’s IRB approval must be in hand before implementation begins. Second, if the change needs a fresh signature from your site liaison, that signature belongs to somebody with clinical duties — ask early, not once the form is otherwise finished.
How do you file it so it lands as one change?
- Write the change as a sentence before opening any form: what is changing, from what, to what, and why. If it will not compress to a sentence, it is several changes and should be described as several.
- List every document that sentence touches. A recruitment change usually reaches the protocol, the recruitment text and the information sheet at once. Revise them together and version them together.
- Decide the boards. Use the table above; where both are engaged, prepare both filings in one sitting so the two files never hold different versions of the same fact.
- State what is not changing. Reviewers read a change request against what they approved, so saying plainly that the population, the setting and the data path are untouched answers the largest question before it is asked.
- File on each board’s own route — Chamberlain’s through the channel its IRB page currently names, the site’s through the office that issued its approval — and keep both reference numbers on one page.
- Hold until each decision is in writing before the changed activity begins on that board’s side.
What do people most often misjudge?
- Treating a change as too small to mention. A filing a board can close administratively is far cheaper than a divergence it discovers later.
- Filing with Chamberlain and assuming the site inherits it. Nothing connects the two files except you.
- Bundling an unrelated tidy-up in, which turns a narrow question into a broad one.
- Editing a participant-facing page while the protocol still describes the old one, leaving two accounts on the record.
- Reading the immediate-harm carve-out as general permission to act first.
- Missing that a change can put continuing review back in play — what each board expects after approval covers that side.
Who carries this when the change is complicated?
Amendments are quiet work with loud consequences, and they land at the worst moment — mid-implementation, with a liaison to chase and two files to keep identical. It is also worth knowing that Chamberlain’s IRB states plainly that it does not provide advisement or mentoring on study design, so the work of shaping the change is yours to arrange. We establish which boards it belongs to, revise every document it reaches, prepare both filings so the files stay in step, and handle each board’s reply until the change is approved in writing on both sides. Your project, your data and your findings remain yours; each board’s decision remains its own. How it works shows the full route; the FAQ answers the common first questions.
What to do next
Describe the change in a paragraph and tell us which approvals you already hold. We come back at no cost with which board or boards it belongs to, which documents it reaches, and what may continue meanwhile. Request the free application review. If a board has already written to you about it, answering revision requests point by point is the format that closes it, and reading a returned application explains which desk the letter came from.
Sources
- Chamberlain University, Institutional Review Board — Study Amendment Application Form, its named triggers, and the rule that changes are approved before implementation: chamberlain.edu — Institutional Review Board
- Chamberlain University IRB Handbook — no approval of completed work; lighter-pathway studies reopened by a change: chamberlain.edu — IRB Handbook (PDF)
- Chamberlain University, DNP Project & Practicum Handbook — the Prescreening Review Form route, and both approvals required before implementation: chamberlain.edu — DNP Project & Practicum Handbook (PDF)
- 45 CFR 46.108 — written procedures, prior review of proposed changes, and the immediate-hazard exception: ecfr.gov — section 46.108
- Office for Human Research Protections, regulations and policy guidance: hhs.gov/ohrp