Find the problem inside a real organization first.
Practice doctorates are built on a problem somebody at a site actually wants solved, which means the site comes before the proposal rather than after it. Start where you already have standing: your own unit, a former employer, a clinic where a colleague can introduce you. Access is the scarce resource here, and existing relationships are the cheapest form of access there is.
Then narrow the problem until it fits inside the months you have. A project that improves one measurable outcome on one unit with one intervention can finish; a project that reforms a service line cannot. Write the problem as a single sentence naming the population, the setting, the change you propose and how you would know it worked, and take that sentence to the site rather than a document nobody has time to read.
Secure a champion before you secure anything else.
Every approval that follows moves faster with someone inside the organization who wants this to happen. A champion is usually a manager, a director of nursing, a quality lead or a physician with standing in the department, and their job is to open doors you cannot see from outside: who signs, whose data you would need, which committee meets when, and what has already been tried here.
Meet them in person if you can, bring the one-sentence problem and a page describing what you would need from the site, and ask directly what the internal route to approval looks like. Then write down what they tell you, because that route is frequently unwritten and differs between organizations that otherwise look identical.
The approval sequence, in the order it usually runs.
The exact steps vary by school and by site, so confirm yours with your chair early, but the shape below holds in most programs and each step depends on the one above it.
- A letter of support or site agreement from someone entitled to sign on the organization's behalf
- Your training certificates completed and current, commonly through the CITI program
- Committee or chair approval of the written proposal at your university
- A determination of whether the work counts as quality improvement or as research
- University review board submission, at whatever level that determination requires
- The site's own review board or research committee, where the organization operates one
- A data use or confidentiality agreement if you will touch identifiable information
The determination question, which decides everything after it.
Whether your work is classified as quality improvement or as research changes the review it needs, the consent it requires and how you may present it later. The distinction generally turns on intent and generalizability: improving care at one site using established practice tends toward quality improvement, while producing knowledge meant to apply beyond that setting tends toward research.
Do not make this call yourself, and do not let a site manager make it for you. Submit the determination request to your university's review board with an honest description of what you intend to do and how you intend to disseminate it, and get the answer in writing before you collect anything. Reclassifying a project after data collection has begun is the single most expensive mistake in this whole sequence.
Timing, and the two boards that do not coordinate.
Build your calendar around other people's meetings rather than your own availability. Review boards and site committees meet on fixed schedules, and a submission that misses a cycle waits for the next one regardless of how urgent your program deadline feels. Ask for those meeting dates at the start of the term and place your deadlines a fortnight ahead of them.
Expect a revision request too, since most protocols receive one and it is a normal part of review rather than a setback. Answer every point in a numbered response letter, mark the changes in the document, and resubmit quickly while the reviewers still remember the file. Where the protocol writing itself is the bottleneck, EDL 305 takes it from draft to approval letter with a free quote in two hours, and the hours side of the degree is counted in this companion guide.
Common questions.
Do I need review board approval for a quality improvement project?
You need a determination, which is not the same thing. Most universities ask you to submit a short description so the board can decide whether the work is research requiring full review or quality improvement that does not. Get that decision in writing before collecting anything, because obtaining it afterward is difficult and can prevent you from publishing or presenting the results later.
What should a site letter of support actually contain?
The organization's name and letterhead, your name and program, a short description of the project, an explicit statement that the site permits it, what access is being granted, and a signature from someone entitled to grant that access. Ask your chair for the school's template first, since many programs supply exact wording and a letter missing it comes straight back.
How early should I start looking for a project site?
Earlier than your program's schedule implies, and ideally a term or two before the project courses begin. Approvals depend on committee calendars you do not control, and a site that withdraws in month one is an inconvenience while one that withdraws in month six can cost a whole term. Line up a realistic second option before you need it.
Does my project need approval from the site's board as well as my school's?
Often yes, when the organization runs its own review body. The two do not coordinate with each other and each has its own forms, meeting schedule and requirements, so plan them sequentially rather than assuming one satisfies the other. Ask your site champion early whether an internal committee exists, since that answer can add weeks to your timeline.
