Find your branch before you write a word.
The IRB step of a WGU capstone is not one queue. It is a fork, then another, then another, and the four places the branches end ask for very different files. Most WGU capstones are quality-improvement projects at a single site, and the most common honest landing is a determination that the project is not human-subjects research at all. The costly error runs in either direction: walking the review branch when a determination would do, or claiming the light branch while your own paperwork describes the heavy one.
We are independent consultants who walk the entire WGU IRB process for you, end to end, every week — settling the determination, building each document, filing the submission, and answering each reply the board sends until approval arrives. Your project, your data and your findings stay yours; the board's decision stays the board's. The tree below will tell you where you likely stand, including when you can reasonably file without us.
The tree
Answer each fork for the project as you actually plan to run it, not as you hope it reads. Your path lights as you go; every landing below is a real, legitimate place for a WGU capstone to end. On a small screen the tree scrolls sideways; your answers keep.
Likely a determination: not human-subjects research.
Either no living people feed the project, or the aim is honestly to improve practice at your one site with nothing recorded that points back at a person. Under the common federal reading, that is not human-subjects research, and the right move is a determination request: a short, precise description of intent, data and site, filed through WGU's current portal so the office says so in writing. With a clean file you can reasonably submit this yourself. This landing is real, it is common for WGU capstones, and it is not a loophole; it is the category working as designed.
If you want a second pair of eyes on the intent language before you file, the review is free. If your draft is clean we will say exactly that: file it yourself.
Likely an exempt category.
People are involved and the knowledge is meant to travel, but nothing you keep identifies anyone. That usually reads as an exempt category, and "exempt" is a verdict the reviewer issues, not one you declare. You still file a complete application; the reviewer confirms the category. What decides it is the file: instruments that match the stated aim, recruitment wording that promises nothing, and a data plan that keeps the no-identifiers claim true from first collection to final page.
Expedited territory.
Identifiable information, minimal risk: this is the branch where the file does the heavy lifting. Expect the consent file, the data-security plan and the site permission letter to be read closely, because identifiability is exactly what those documents exist to protect. Start the site letter now; it is routinely the slowest document in the folder.
Talk-first territory.
A vulnerable population, or risk beyond the everyday: children, prisoners, cognitively impaired adults, your own patients or supervisees, or data whose exposure could genuinely hurt someone. This branch can reach a convened board, and the honest move is to plan before drafting. Sometimes a small, truthful redesign — different recruitment, different data, a different comparison — walks the same question down a lighter branch. Sometimes it should not, and the project deserves the full review. Either way, decide that before a single document is written.
The identifiers fork decides more than any other
hangs off fork 2Look at the tree again: fork 2 is the one that splits it in half. Everything to its left ends in a determination or an exempt reading; everything to its right ends at expedited review or a conversation you should have before drafting. Topic does not do that. Method does not do that. What you record does.
The fork asks about recording, not encountering. Of course you will see names on a unit; of course the charge nurse knows who answered the survey. The question the board's office cares about is what exists in your dataset, your notes and your appendices after collection. A spreadsheet with a name column is identifiable. So is one with a medical record number, a date of service tied to a small unit, a voice recording, or a free-text quote distinctive enough that a colleague could say who said it.
The subtlest version: a key you keep is an identifier. Coding responses as P01, P02 and holding a linkage file "just in case" moves you to the right-hand side of the tree, because re-identification stays possible. De-identified means the pointer back to the person does not exist anywhere you control, not that it is stored in a different folder.
The fork is not "will I be careful with identifiers". It is "will they exist".
Quality improvement is a claim you have to mean
hangs off fork 3Under WGU's current handbook, the capstone is framed as an applied, practice-improvement project: MSN candidates and their peers are typically fixing a process at the site in front of them, not testing a hypothesis for the field. That is why the determination leaf sits at the end of two branches on this tree. It is where a large share of WGU capstones genuinely belong.
But fork 3 is answered by intent at design time, and intent is a claim the rest of your file has to keep. A useful private test: would the project still be worth doing if nobody outside your site ever read a page of it? If yes — you are fixing the fall-rate on one unit, the handoff on one ward — that is improvement of practice. If the design only makes sense as evidence for other sites, with comparison arms and instruments built to generalize, it is research, whatever the cover page says.
Misclassification costs in both directions. Dress research as QI and you have collected data under a claim the office never reviewed; the branch you actually walked was never approved, and the section below on timing explains how badly that ends. Dress QI as research and you volunteer a project into review it never needed, buying yourself a heavier file and a board's calendar for nothing. Neither error is safer than the other.
And no, honest QI does not forbid publishing later. Sharing what one site learned is not the same as designing for generalizable knowledge; intent at design time governs, which is why the office asks you to state it plainly and why the statement deserves careful drafting.
What a clean consent file carries
hangs off the exempt and expedited leavesOn any branch where living people answer questions, consent is not a form; it is a small file, and reviewers read it as one. The information sheet, the recruitment wording and the data-handling plan have to tell the same story, because the fastest way to stall a minimal-risk application is a flyer that promises what the sheet retracts.
The sheet itself has known load-bearing parts: what the project is and who is running it; that taking part is voluntary and declining changes nothing about anyone's care, grade-free coursework standing or employment; what is collected, where it lives, who can see it and when it is destroyed; the honest risks, even when the honest answer is "inconvenience and little else"; how to withdraw; and a real person to contact. None of this is boilerplate. A sheet that says "no risks" over identifiable workplace opinions is the kind of line a reviewer circles.
Recruitment materials are part of the same review: the email you will send, the flyer for the break room, the script for the huddle. Write them before filing, submit them with everything else, and let them promise nothing but the sheet's own terms. On the expedited branch, add the data-security plan and make it specific: which encrypted drive, whose access, destroyed on what trigger.
The slowest document is not yours
hangs off the whole right sideEvery document in your folder is under your control except one. The site permission letter is written on someone else's letterhead, signed by someone with actual authority over the facility, and it moves at the speed of someone else's inbox. Candidates polish their own pages for weeks and then discover the letter is the document holding the file open.
It also has teeth. A usable letter names the project, names what you may access — people, charts, rooms, data — and comes from a role that can grant it: a director or administrator, not a friendly colleague on your unit. Many facilities route the request through their own machinery first, a nursing research council or an education office, and that internal loop is the long pole nobody budgeted for. Some sites, on the identifiable branch, will even want their own review before they sign anything.
On our files we draft the letter itself for the signer's letterhead and carry the request, so the only thing left to move is the signature — the same way we carry every other document in the folder, the submission, and each reply after it.
Start the longest limb first, before you polish anything you already control.
Nothing counts before the letter arrives
hangs off every leafThe one rule that spans the whole tree: collection starts when approval — or the written determination — exists, not when you feel confident about which leaf you will land on. Data gathered early generally cannot be blessed after the fact; there is no retroactive approval, and a project built on early data can be unusable from the root, however good the work.
"Collection" is broader than candidates expect. Pulling charts to "see what is there" is collection. Running the survey with three colleagues to "pilot the wording" is collection. Keeping notes on identifiable conversations you plan to quote is collection. Even on the determination branch, when your plan sits anywhere near the research line, the clean sequence is: written determination first, data second — the letter is fast precisely because the category is light.
This is the cheapest mistake to avoid on the entire page. It costs a date on a calendar and nothing else.
The grove keepers
three consultants, one fileEvery WGU file that comes through the practice is walked by the same three people, each holding one part of the branch. You will know who has your folder at every step.
Lydia reads the aim statement first and decides, with you, which leaf the project honestly sits on. She has drafted more determination requests for WGU capstones than any other document in the practice.
Emma builds the consent file, aligns every instrument to the stated aim, and writes the data-security plan so the identifiers answer stays true from first collection to last page. Her files rarely come back with a consent note.
Ruth drafts the site permission letter for the signer's letterhead, files the submission through WGU's current portal, and answers every revision request, amendment and continuing-review notice until approval. She keeps the longest limb moving.
From the leaves
what candidates said after the letter came4.8 / 5 average across the professionals we have served. Four of them, in their own words.
The tree put me on the determination leaf and I did not believe it. Lydia tightened two sentences in my aim statement and told me to file it myself. The office issued the determination and I never needed the heavier file.Hailey B., MSN capstone
I had a linkage key in a separate folder and thought that made my data de-identified. Emma walked me back through the identifiers fork, we dropped the key, and the whole project moved to the exempt side. One submission, one approval.Marcus T., MSN, RN, practicum project
My site letter was the thing holding everything open. Ruth drafted it for the director's letterhead, chased it, and had the submission in the portal the day it was signed. The board's one revision note was answered before I had read it.Dana K., MSN-Ed capstone
I had filed once already and been returned for describing a QI project in research language. The practice rewrote the intent section honestly, refiled, and the determination came back clean. I wish I had walked the tree before the first attempt.Renee L., MSN capstone, returned and refiled
What it costs
three packages, each quotedWe quote each package after the free review, so the price fits the branch you are on, not a menu.
Determination & Plan
the reading, your branch on the tree, the document plan- your fork answers read against the project as you plan to run it
- your branch on the tree, settled with you and named in writing
- the document plan for that branch, so nothing is drafted twice
Ask for the quote
The Complete File
Determination & Plan, plus every document built and version-matched, ready to file- the application, the consent file and recruitment materials
- instruments aligned to the aim; the data-security plan
- the site permission letter drafted for the signer's letterhead; every page version-matched
Ask for the quote
Full Handover
most chosenThe Complete File, plus the submission, every reply to the board, amendments and continuing review until approval: the whole branch off your desk- everything in The Complete File
- the submission itself, filed through WGU's current portal
- every revision response, amendment and continuing-review reply until approval arrives
Ask for the Full Handover quote
Questions, answered first
nine, short answer firstEach answer opens with the short version, so it can be lifted on its own; the longer reading follows. Fifteen questions with the same shape are on the questions page, and the how-it-works page walks the whole process.
Does a WGU MSN capstone need IRB review?
Usually it needs a determination rather than a full review. Most WGU MSN capstones are single-site quality-improvement projects, and the most common honest outcome is a written determination from WGU's IRB office that the project is not human-subjects research. You still file to get that determination; it is not something you declare yourself. Misclassifying in either direction is costly.
Research dressed as quality improvement collects data under a claim the office never reviewed, and the branch you actually walked was never approved. Quality improvement dressed as research volunteers a project into a review it never needed and buys a heavier file for nothing. The exact form and route for the determination request are set by WGU's current handbook or IRB portal; the tree above reads which branch your project honestly sits on.
What decides which review path my capstone is on?
Four questions decide it: whether the project draws information from or about living people; whether anything you record identifies them; whether the aim is to improve practice at one site or to produce generalizable knowledge; and whether a vulnerable population or more than minimal risk is involved. Topic and method matter far less than those four answers.
The identifiers question splits the tree in half. Everything where nothing recorded points back at a person ends in a determination or an exempt reading; everything identifiable ends at expedited review or a conversation to have before drafting. A linkage key you keep is an identifier, wherever it is stored.
Can I start collecting data before approval?
No. Collection begins when the approval or the written determination exists, not before, and there is no retroactive approval. Chart pulls to see what is there, pilot runs of a survey and notes on conversations you plan to quote all count as collection.
A project built on early data can be unusable from the root, however good the work. This is the cheapest mistake on the whole tree to avoid: it costs a date on a calendar and nothing else. On the determination branch the clean sequence is still written determination first, data second.
Do I need CITI training for a WGU capstone?
Plan on it. WGU's current handbook or IRB portal names the human-subjects training it expects and which modules; CITI is the usual vehicle, and the completion record goes into the file. Finish it before filing, because a missing training record is one of the simplest reasons a file stalls.
The training is about the person filing, not the project's risk level, so it applies on the light branches too. Keep the completion record current through the life of the project, and check WGU's current portal for whether anyone else named on the application needs a record as well.
Do I need a site permission letter?
If the project touches a facility's people, records, rooms or data, plan on a letter on the facility's letterhead signed by someone with authority to grant that access. It is routinely the slowest document in the folder because it moves at the speed of someone else's inbox, so request it first.
A usable letter names the project and the specific access granted, and comes from a role that can grant it: a director or administrator, not a friendly colleague. Many facilities route the request through their own research council or education office first; that internal loop is the long pole. On our files we draft the letter for the signer's letterhead and carry the request, so the only thing left to move is the signature.
What is the difference between exempt, expedited and full board review?
Exempt means the project fits a named low-risk category, confirmed by the reviewer rather than declared by you. Expedited means identifiable information at minimal risk, read closely by a designated reviewer instead of the convened board. Full board means the convened committee meets on it, usually because of a vulnerable population or more than minimal risk. A fourth outcome sits before all three: a determination that the project is not human-subjects research at all.
Most WGU capstones land at the determination or the exempt reading. On every branch the file decides: instruments that match the stated aim, recruitment wording that promises nothing, and a data plan that keeps the identifiers answer true from first collection to final page.
Can I survey my own coworkers or patients?
Often yes, but the relationship changes the file. Your own patients, supervisees or direct reports can feel they cannot decline, so the board reads recruitment wording, voluntariness language and anonymity claims closely. Surveying your own patients can also move the project toward the talk-first branch, so plan that before drafting.
Small, truthful design choices help: an anonymous instrument, distribution by someone outside the reporting line, a clear line that declining changes nothing about care or employment, and no cell small enough that "the one night-shift educator on 4 West" is identifiable.
What happens when the IRB returns my application?
A return is a set of notes, not a rejection. You answer each note specifically, revise every document the answer touches so the file still tells one story, and resubmit. Most returns trace to a mismatch: recruitment that promises what the consent sheet retracts, an intent statement in research language over a QI design, or a data plan that quietly keeps an identifier.
On our files the reply is ours to write: each note answered in the board's own order, every affected page version-matched, and the resubmission filed through WGU's current portal. Amendments after approval and continuing-review notices are answered the same way, until the project closes.
Do you conduct my research, and what does it cost?
No. We handle the entire IRB process, which means the determination and plan, every document, the submission and every reply until approval, while the research itself stays yours: your project, your data, your findings. Pricing is quoted in writing after the free application review as a fixed fee, in three packages: Determination & Plan, The Complete File, and Full Handover, the premium package that takes the whole branch off your desk.
The quote fits the branch you are on, not a menu, and there is no hourly billing. If the tree has put you on the determination leaf with a clean draft, the free review will say so, and you file it yourself. The pricing page details each package; the board's decision, on every package, stays the board's own.
Land on a leaf, then hand us the branch. We walk the rest.
From the leaf onward we handle the entire IRB process for you, end to end: the determination request or the review plan, every document — the application, the consent file, recruitment materials, instruments aligned to the stated aim, the data-security plan, site permission letters drafted for the signer's letterhead — the filing itself, and each reply the board sends until approval arrives: revision responses, amendments, continuing review. Your project, your data and your findings stay yours. The board's decision stays the board's.
It starts with the free application review: send where the tree left you and whatever exists — a determination draft, a half-built consent file, a blank page and a worry. If you landed on the determination leaf with a clean draft, we will say so, and you file it yourself.
Book the free application review- the determination or review plan, from your landing leaf
- every document, drafted and aligned
- the submission through WGU's current portal
- every reply to the board until approval