Every station on a WGU capstone's IRB branch, in the order it is actually walked
The IRB is not the first desk your capstone passes, and it is not a desk you can skip by deciding your project is light. WGU's own published form tells you the order in one line: the project you describe to the board has to be the project your course already approved. Everything downstream — the branch, the folder, the filing, the letter — is built on that match.
Course proposal approved first, then the branch settled, then the folder built to match that proposal, then the filing through WGU's current portal, then the board's reply answered, then the letter. Collection begins at the letter and never before it.
What has to be settled before the board reads anything?
The capstone proposal itself. WGU's published Request for Approval to Conduct Research carries a note before the first question: the description of the proposed project should line up with the proposal already approved in the earlier task, and with the description participants are given in the informed consent document. Three documents, one project, and the board is entitled to read all three.
That note is the whole sequence compressed. It means the aim statement is not something to invent while filling in an application form. By the time the board sees your file, the aim has already been through a course assessment, and any drift between the two is visible to a reader holding both.
In the nursing tracks the shape is even more explicit. WGU's published program guidebook for the MSN in nursing leadership and management runs a healthcare improvement project through a sequence of courses — the business case, the planning of the execution, the evidence-based measures chosen for evaluation, the field experience where the project is implemented, and finally the capstone, where results are analysed against the indicators chosen during planning. The project has a defined problem, a site, stakeholders and metrics long before anyone opens an application form.
Do you get to decide that no filing is needed?
No. This is the misreading we correct most often in the free review, and WGU's Policy Handbook leaves little room for it: proposals to conduct research using human subjects go to the IRB so that the IRB can decide whether full review and approval are required. The decision about how heavy your review is belongs to the office, not to the person filing.
What this changes in practice is the vocabulary. A capstone that is honestly a single-site improvement project does not need approval as research — but it usually still needs something in writing that says so, and that piece of paper is obtained by filing, not by concluding. We walk through the honest version of that argument in why most WGU capstones are improvement projects, and what you still have to file.
Is there a gate before the IRB gate?
For some projects, yes, and it catches people every term. WGU's handbook states that proposed research collecting data from WGU's own population — its learners, employees, graduates or the employers of graduates — or drawing on existing university data about those groups, must be approved by the Vice President of Institutional Research or a designee before it goes to the IRB, with the capstone instructor enabling that submission as part of the capstone process.
Read the population line carefully against your own design. A project that surveys nurses on your unit does not touch it. A project that surveys people enrolled at WGU, or asks the university for data about them, lands squarely inside it — and discovering that after the IRB file is built is an expensive way to learn the order of the queue.
What is the actual order, station by station?
Below is the walk as we run it. The numbering matters more than the names: each station produces something the next station consumes, which is why skipping one usually means redrafting two.
-
The aim, approved inside the course
The problem, the site, the change and the measures are settled and signed off in the capstone sequence. This is the document every later page has to agree with.
-
The branch read against four forks
Living people or not; anything recorded that points back at a person or not; one site's practice or knowledge meant to travel; vulnerable population or more than everyday risk. Those four answers, not the topic, set where the file ends up. Where each branch ends takes them one at a time.
-
The institutional-research check, where it applies
Only for projects touching WGU's own population or university-held data about it. Cleared through the capstone instructor before the board is approached at all.
-
The human-subjects training record
Published WGU capstone guidance has candidates attach a CITI completion certificate to the application. It is one of the few items nobody can prepare on your behalf, and it is worth confirming it is current rather than merely completed.
-
The site's signature, requested early
Any project reaching into an organisation needs authorisation from someone whose role can grant it. WGU's own form ends with that reminder, and puts the administrator or supervisor signature on the consent document before the application is submitted. This is the one limb whose length you do not control.
-
The folder, built to one story
Application pages, consent file, recruitment wording, instruments as participants will see them, and the data-handling plan — each version-matched to the others. Every document a WGU application carries lists them and shows where they contradict each other.
-
The submission
Filed through the route WGU's current handbook or IRB portal sets for your programme. Older published copies of the form name the assessment system in use at the time, which is exactly why the route is worth confirming rather than assuming.
-
The reply, answered specifically
Most files come back with notes at least once. Each note is answered in the board's own order, every page the answer touches is revised, and the file is resubmitted as one consistent object rather than a patch.
-
The letter — and only then, collection
The determination or the approval is the starting gun. Everything before it is preparation, whatever it feels like.
Where does a WGU file actually stall?
Rarely at the board. Almost always at a station upstream of it, and almost always at one of four.
| Station | What stalls there | Who can move it | What prevents it |
|---|---|---|---|
| The approved proposal | The application describes a different project than the course signed off | You, by rewriting one of them | Drafting the application from the approved proposal, not from memory |
| Institutional research | A project touching WGU's own population goes to the board first | The capstone instructor, who enables that submission | Reading the population line before the folder is built |
| Site authorisation | The signer is a colleague rather than someone who can grant access | Only the facility | Requesting it at station five, not station eight |
| The identifiers answer | The application says nothing identifiable; an appendix disagrees | You, before filing | One data story across every page of the folder |
What if data was already collected?
Say so, immediately, and stop. There is no mechanism that reaches backwards and blesses information gathered before a determination or an approval existed, and a capstone built on such data can be unusable from the root no matter how careful the work was. The pull of charts to see what is there, the pilot of a survey on three colleagues, the notes kept on conversations you intend to quote — all of it is collection.
The honest fix is nearly always a redesign of the data you will use going forward, filed properly, rather than an attempt to fold the early material in quietly. Boards read applications that do this, and it is a far worse conversation than the one you avoid.
What happens after the letter arrives?
The file stays live. WGU's Policy Handbook states that once a proposal is approved the IRB monitors the research and conducts continuing reviews, and that researchers are responsible for promptly notifying the board of unanticipated risks and of changes to an approved plan before those changes are implemented — unless a change is needed to remove an immediate hazard to participants.
The practical translation is short. If the design shifts — a second unit, a new question added to the instrument, a different way of storing responses — the amendment is filed and approved first. Continuing review notices arrive on the schedule the board sets, and closure is its own step, not something that happens because you stopped collecting.
What to do next
Set the approved proposal beside the application and read the pair the way a board reads them: same population, same site, same data, same intent. If they diverge anywhere, that gap is the first thing to fix, before a single consent page is drafted.
If you would rather have a second reader on it, send us what exists. How the walk runs sets out what we take off the desk and what stays yours, the questions page answers the fifteen that come up most, and and a free application review names the branch your capstone honestly sits on — including the times when the honest answer is that the draft is clean and you should file it without us.
Sources
- WGU Policy Handbook — Institutional Review Board (IRB), cm.wgu.edu
- Western Governors University Institutional Review Board — Request for Approval to Conduct Research (published copy of the WGU form, PDF)
- WGU Program Guidebook — RN to MSN, Nursing Leadership and Management (PDF), wgu.edu
- 45 CFR part 46 (the Common Rule), full regulatory text, govinfo.gov
- OHRP — Quality Improvement Activities FAQs, hhs.gov
Send us the proposal and whatever else exists.
One of the three consultants reads it against the four forks and replies with the branch your capstone honestly sits on. Free, no obligation, and if the draft is clean we will tell you to file it yourself.
Request the free application review- whether the application matches the approved proposal
- which landing the project honestly reaches
- which documents that landing needs, and in what order