Which board first? Why the practicum site's IRB opens before Chamberlain's file closes

Why does the practicum site get a board of its own?

Because it may be legally engaged in the work. Federal guidance sets out when an organisation becomes engaged in human subjects research: when its own employees or agents, for research purposes, intervene or interact with participants, obtain identifiable private information about them, or obtain their informed consent. An engaged organisation is expected to hold a Federalwide Assurance and secure IRB review, or to be covered by a formal reliance arrangement.

The same guidance draws the other half of the line, and it is the half worth understanding. An organisation that merely permits its facilities to be used — letting an investigator from elsewhere distribute a survey on the premises — is often not engaged. Nor is one that simply releases identifiable information to investigators at another institution, or tells people a study exists and passes along approved materials.

So whether your site needs its own review is a genuine question with a real answer, and it turns on who is doing what. If you are its employee pulling its charts, the picture looks different from an outside investigator handing out a questionnaire in its lobby. Working that out early is worth more than any other single step, because a site that concludes it is not engaged can often say so quickly, and a site that concludes it is engaged has just become your critical path.

Whose job is it to find the site's board?

Yours. Chamberlain's DNP Project & Practicum Handbook lists among your responsibilities the identification of whether an IRB is required at the practicum site in order to implement your project. It is not the practicum coordinator's task, and it is not something the experiential learning team discovers on your behalf while arranging contracts.

That distinction matters because a different piece of site paperwork is handled for you, and the two are easily confused. The Clinical Affiliation Agreement — required for every practicum site and signed by a duly authorised officer of the facility — is secured by Chamberlain's experiential learning services team, and the handbook warns that completing site contracts can be lengthy. An affiliation agreement is a contract between two institutions about your presence. It is not ethical review, it does not mention your project, and it will not satisfy a nursing research council. Neither will a Letter of Support, which the handbook separately requires from the site's primary decision maker. Three different pieces of paper, three different purposes; only one of them is a board's decision. That confusion is common enough to deserve its own article on permission versus site IRB review.

What does the site's board ask that Chamberlain doesn't?

Different questions, from a different vantage point. Chamberlain is asking whether the project is sound, ethical and correctly classified. The site is asking what happens on its premises, to its people, with its data, under its name.

Why can't both files simply go in together?

They can, and often the drafting does happen in parallel. What cannot happen is closing the Chamberlain file before the site has answered — because Chamberlain asks for the site's answer.

Chamberlain's IRB Handbook lists, among the materials to be submitted when germane to the study, copies of approvals from other or collaborating IRBs, along with letters of support. The same handbook states that incomplete packets are not reviewed until all necessary items are provided. Where a site board is genuinely in play, its approval is not a document you add afterwards for tidiness; it is one of the items that makes the school's packet complete.

There is a converse trap. If you tell Chamberlain that no site board is involved and one later materialises, you have changed a material fact in a file that has already been assessed. That is an amendment, and amendments spend time you did not budget.

What makes the site's calendar the binding constraint?

Two things that compound. The first is that councils meet on their own schedule and accept submissions against their own deadlines. You cannot escalate into an agenda. Each return waits for another pass of it.

The second is that your implementation window is fixed by the curriculum, not by you. Chamberlain's handbook requires that all prescreening and site IRB approvals be complete before implementation begins in NR-707, that the project begin at the very start of that course, and that the intervention run for a stated minimum length inside a bounded implementation window. That is a genuine floor. An approval that lands late does not simply compress a comfortable schedule — it can leave insufficient room for the intervention the course requires. This is the mechanism behind the phrase we repeat: the slower board sets your start date, and the start date has a deadline behind it.

The practical consequence is an inversion of the intuitive order. Do not perfect the Chamberlain file and then go looking for the site's board. Find the board, get its submission calendar in writing, plan backwards from it, and assemble the Chamberlain file in the time the council is already using.

Could one board review for both?

Sometimes, and it is worth asking. The regulations on cooperative research allow institutions to arrange joint review, to rely on another qualified IRB, or to make similar arrangements to avoid duplicated effort. Where a single-IRB arrangement is used, one board becomes the reviewing IRB and the other cedes primary responsibility as a relying IRB, formalised in a reliance agreement that both institutions sign and keep.

Chamberlain publishes reliance agreement forms for both directions and notes that information about single-IRB arrangements is available on its IRB pages. But read one limit before building a plan on it: Chamberlain's IRB Handbook states its IRB will not act as a relying IRB where Chamberlain faculty, staff or people enrolled at Chamberlain are the proposed subjects, or where Chamberlain data is used. And each institution remains responsible for safeguarding participants regardless of which board reviewed. Reliance removes duplicated review; it does not remove either institution's interest.

What should you actually do first?

1. Ask the site, in writing, whether it requires IRB or research council review for a project like yours, and who chairs it. Email your preceptor and the site's research or nursing education office the same week.
2. Ask for the submission calendar and the packet in the same message. You want deadlines and forms, not a general assurance.
3. Record the answer even when it is no. A written "no board required" is a document for your file and for Chamberlain's.
4. Identify the person who signs. The Letter of Support comes from the site's primary decision maker, and site applications usually need a name with standing at the organisation.
5. Ask what the site calls it. Some organisations route improvement work through a nursing research council or an operational committee rather than an IRB. The label differs; the gate is the same.
6. Only then build the Chamberlain file, with the site's vocabulary and timing already known. The whole route is laid out in the step-by-step walk through both tracks.

What to do next

Send one email today, to your preceptor and to the site's research office, asking whether your project requires review by an IRB or research council and when that body next accepts submissions. Nothing else on either track is as time-sensitive, and the answer reorganises everything that follows.

If you would rather not guess at the wording, or you do not yet know who at the site to ask, request the free application review. We identify the board of record, get its calendar in writing, and tell you plainly which door to open first — including when the answer is that only one board is involved and you can proceed without us. The boards' decisions are their own; the sequencing is where the practice earns its place.

Sources

• Chamberlain's current DNP handbook (©2026) — your duty to establish whether the site reviews, the affiliation contract and Letter of Support, and the rule that NR-707 waits on both answers — DNP Project & Practicum Handbook (PDF)
• Chamberlain's board handbook — the expectation of other boards' letters inside its own packet, packets left unread when items are absent, and its relying-board limits — Chamberlain IRB Handbook (PDF)
• OHRP on when an organisation counts as engaged, and when hosting alone does not, 73 FR 63067 — Federal Register, via govinfo
• Shared projects, and the arrangements that let one board cover another — 45 CFR 46.114 (Cornell LII)
• Chamberlain's board pages, where its reliance forms sit — Institutional Review Board, Chamberlain University

Site requirements vary by organisation. Chamberlain's current handbook or IRB portal is the authority here; where it departs from anything on this page, follow Chamberlain. This is an independent practice, unaffiliated with Chamberlain University.