Talking to people looks like the least procedural way to gather anything, and in a file it is the most. Your questions become an instrument read line by line. Your recorder creates a data trail to be followed from the moment it starts to the moment the audio is gone. And the room belongs to the practicum site, which has views about who may be in it, when, and who might overhear.
File the guide verbatim as an instrument, including probes. Account for every recording from capture through transcription to destruction, and name anyone else who hears it. Promise only what you can keep: a focus group cannot guarantee confidentiality, and the site controls the room.
The guide. Not a topic list, not a paragraph describing areas you intend to explore — the questions themselves, in order, with the probes written out. A board cannot assess what it cannot read, and “questions will be developed following initial interviews” returns a file, because it asks approval for something that does not yet exist.
Semi-structured work is entirely acceptable; it simply has to be described honestly. Say which questions are put to everyone, which probes are conditional and on what, and where you may follow an unanticipated line. What no board accepts is a guide submitted as finished and then used as a starting point.
Three things travel with the guide and are frequently forgotten: the opening script you say aloud, including how you introduce your own role at the facility; the words you use to obtain agreement to record; and the closing, particularly if you offer anything for taking part. All three are part of what a participant experiences, so all three belong in the file.
Chamberlain publishes named templates for some of this — a consent form template and a recruitment template appear among the materials listed on its IRB pages — while stating that the board itself does not advise on study design or create such documents. Read that as the division of labour it is: the format may be given to you, the substance is yours to build. The sequence above it is fixed by Chamberlain’s current DNP Project & Practicum Handbook, which routes projects through a Prescreening Review Form and bars recruiting until both decisions are received.
This is what separates a hospital interview from an interview anywhere else, and it is the site’s to answer. A conversation on the practicum site happens inside a facility responsible for the space, the people in it, and anyone who might walk past. So its board or nursing-research council asks things Chamberlain never will:
Answer these in the site’s own vocabulary, and carry the same answers into the Chamberlain file so the two documents do not describe two different rooms.
One board reads the instrument and the promise. The other reads an occupation of its premises by someone asking its people about its work.
The recording is where the two tracks meet most sharply. Chamberlain asks how it is protected; the site asks whether it may exist at all, and who besides you will ever play it.
A recording is identifiable by nature. A voice is a voice, and a transcript of a nurse describing her own unit often identifies her whether or not her name is spoken. Once recording enters the plan, the file needs an account running from capture to disposal without gaps:
Say the same thing in both files: the data-security plan Chamberlain reads and the handling description in the site’s packet should be one document.
Less than in an interview, and the sheet must say so. One to one, you can undertake to protect what you were told, and that undertaking is within your power to keep. In a focus group, five colleagues hear each other, and no board can make them silent afterwards. The honest phrasing is direct: what you say here will be heard by everyone present, we ask everyone to keep it in the room, and we cannot guarantee they will.
Ground rules help and belong in the file: no names of patients or colleagues, nothing discussed outside the room, and a statement that anyone may stay and stay quiet. So does composition. A focus group mixing charge nurses with the staff they assign is a different room, and both boards notice the mix before the questions.
Every promise has limits, and the sheet should name them before anyone speaks. On a hospital site the recurring three are: a disclosure suggesting harm to a patient or the participant; anything the facility’s policies oblige an employee to escalate, which may include the interviewer where the interviewer is also staff; and anything a legal process later compels. Saying less is not kinder. Someone who learns the limit afterwards has been misled, and a board spotting an unlimited promise sends the sheet back.
The regulation supports plain speech rather than reassurance: what participants are told must be in language they can follow, must not sign away any legal right, and must be put to them where pressure is kept out (45 CFR 46.116). Boards must separately find adequate arrangements for privacy and for keeping data confidential (45 CFR 46.111(a)(7)).
| Document | What it must carry | What returns it |
|---|---|---|
| The guide | Every question and probe, in order, plus the opening and closing scripts | A topic list instead of questions; probes missing from the attachment |
| The information sheet | Purpose, what taking part involves, voluntariness, recording, storage, limits, contact | An unlimited confidentiality promise; a focus-group sheet copied from an interview one |
| The handling plan | Device, transfer, transcription arrangement, de-identification step, destruction point | Transcription by an unnamed third party; audio with no stated end |
| Site permission | A signature from someone with authority over the space and the staff | A liaison’s goodwill instead of an authorised signature; a room nobody cleared |
A fifth item hides between them: recruitment wording. How people learn the conversation exists is part of the file — and if a manager tells them, that is a design decision, not logistics. See the unit manager problem.
Interview procedures appear directly among the exempt categories, but with conditions recordings often fail. The category reaches interviews where identity cannot readily be worked out; or where disclosure beyond the project would not reasonably expose people to legal liability or to damage to their employability, finances or reputation; or where identity is reachable and the board carries out a limited review (45 CFR 46.104(d)(2)). Read the middle limb against your project: nurses describing what happens on their unit are discussing their employment. Retained audio tends to defeat the first limb outright.
That does not make a heavier path inevitable. The path is a board’s call on a described file, made separately on each track, and the two calls need not agree. Exempt, expedited and full review sets out how each category behaves; classification covers what decides the path in the first place.
We build the guide as an instrument, write what participants are told so it promises only what your procedures can hold, put one handling plan into both files, secure the room and the signature for it, and carry every reply until both approvals are in writing. We are independent consultants, not affiliated with Chamberlain University. How it works shows the route; the FAQ answers the first questions.
Send your draft guide and tell us where the conversations happen and who is in the room. We will tell you free of charge what each board will ask, what your recording plan is missing, and whether your consent language promises more than the design can keep. Request the free application review. For the surrounding sequence, the process step by step puts both tracks in order.
35% off the whole process when you start this season, and the application review is free.
Fixed fee, quoted in writing after the free review. No hourly billing, no add-ons. The review is free either way.