Your WGU IRB file came back: what the letter is asking, and what closes it
The file returned with notes. That is the ordinary shape of this branch, not a verdict on your capstone: the board has told you in writing, for the first time, exactly what it needs before it can say yes. The task now is to read the letter as separate requests, work out what each one is really about, and send back a folder in which every one of them has already been closed.
Nothing has been refused. Number the requests, answer each one in the place the board asked about, replace every document the answer touches, and file the same project again with nothing left open.
What does a returned WGU application actually mean?
WGU's published policy sets one gate and describes what sits behind it: research involving people must be approved by the university's board and must conform to that board's policies and procedures, and every proposal goes in so the board can settle what level of review the work needs. Nothing in that arrangement treats a first pass as the only pass. The file arrives, someone reads it against a fixed set of protections, and the reply either approves the work or names what is still missing from the picture.
Replies come in recognisable flavours. Some are administrative: a field left blank, an attachment that will not open, a training record nobody can locate. Some are substantive, meaning the protections you described do not yet cover the situation your own text describes. A few are structural, where the reviewer cannot tell which project is in front of them because the aim on page one and the procedure on page four are not the same piece of work. None of those is a judgement about whether your question is worth asking; each is a statement about a folder, and folders are fixable. You now know precisely what the approval is waiting on, and yesterday you did not.
One caution belongs here. WGU's policy notes that its detailed procedures and forms live on an information site reached through university sign-in, so wording, fields and routes can move between terms. Read your own letter against WGU's current handbook or IRB portal, never against a copy of someone else's file from an earlier term.
What are the notes actually asking for?
Copy the letter into a working document and number every request, including any that arrives quietly inside a longer sentence. Then label each numbered item with one of four kinds, because the kind decides the work. Most people lose a pass by treating a protection gap as though it were a missing attachment.
| Kind | How it sounds in the letter | What closes it |
|---|---|---|
| Missing item | "Attach the signed site authorisation." "We have no completion record for you." | The document itself, in the place the application provides for it. No explanation substitutes for the file. |
| Contradiction | "The application describes a survey; the consent text describes interviews." | Decide which is true, then change every page that states it. One truth, worded identically everywhere it appears. |
| Protection gap | "Explain how someone on your own unit can decline without you knowing." | A changed procedure, described in the application and mirrored in the consent text and the recruitment wording. A reassuring sentence alone will not do it. |
| Clarification | "State where recordings are held and when they are destroyed." | A specific answer in the field that asks the question: named storage, named access, named destruction trigger. |
Two items hide inside letters and deserve their own flag. The first is anything touching design rather than paperwork: a different population, a different instrument, a different comparison. WGU's own application asks that the project you describe line up with the proposal already approved earlier in the capstone sequence, and a WGU guidebook states the rule from the other side, expecting the methodology chapters to follow the approved proposal once board approval exists. A design item therefore means a conversation with your capstone instructor before it means an edit.
The second is anything mentioning your relationship to the people in the project. WGU's application asks outright for the relationship between participants and the person running the work, and its protected populations question names those you supervise or teach. Such a note wants a safeguard, not a sentence, and the dual-roles piece sets out what the board looks for.
Which sentence in the letter is doing the real work?
Nearly every letter has one line that governs the rest, and it is rarely the longest note. Look for the sentence describing your project back to you, because that sentence is the reviewer's understanding and every other note follows from it. If the description is right, the remaining items are repairs. If it is wrong — if the board believes you are producing knowledge for the field when you are improving one unit's practice, or the reverse — then repairs are pointless until the description is corrected, because six small fixes will land the seventh reading in exactly the same place.
Correcting a reading is not arguing with it. It means finding the wording in your own file that produced the misreading, because it is nearly always sitting there: an aim borrowed from a published paper, a purpose line promising transferable findings, an instrument copied from a study with different intent. Repair the sentence that misled the reviewer, say plainly in your response that you have done so, and the smaller notes tend to collapse into that one.
Why does one note usually touch three documents?
Because the board reads a single story told by several pages at once. WGU's application asks that the described project match both the proposal approved earlier and the description participants are given in the consent document. That is a three-way alignment, and a note changing one leg of it changes the other two.
Take the commonest example. A note asks you to drop the audio recording. Recording appears in the procedure answer, in the attached instruments, in the consent text that promised people they would be recorded, in the confidentiality answer, and often in the recruitment wording. Answer in the procedure field alone and you have handed the reviewer four fresh contradictions. That is how a file needing one repair returns needing five.
The discipline is unglamorous: for every change, list the pages asserting the thing you changed and edit all of them before looking at the next item. Writing the response itself is a separate craft, and it decides whether the next pass is the last one.
What is forbidden while the board holds the file?
Collection of any kind. A return is not a soft approval with conditions attached, and no blessing arrives retroactively for anything gathered while the board was reading. Under the federal framework WGU's policy points to, consent must be obtained before a person is involved in research at all.
- No pilot run of the survey "just to test the wording" with anyone whose answers you might later use.
- No chart pull to see how many cases exist, if the pull itself records anything about people.
- No recruitment messages, sign-up sheets or huddle announcements.
- No notes on a conversation you intend to quote.
- No second, cleaner application filed beside the first — one project, one file, answered where it sits.
That last item catches people who read a return as a rejection and start over. Starting over throws away the one advantage a return hands you: a reviewer who has read the project and named what they need.
How do you know the folder is ready to go back?
- Every numbered request has a written answer, and every answer names where the change now lives.
- Every document that asserted the old fact asserts the new one, in the same words.
- Superseded pages are gone, not sitting beside their replacements.
- Anything you changed that nobody asked about is flagged in the response, with its reason.
- Any point you dispute is answered once, with a reason and an alternative protection, rather than restated.
- Records the file depends on — the human-subjects training completion WGU's current handbook or IRB portal expects, and the facility signature where one is involved — are attached, not promised.
- Where a WGU population is asked for data, the institutional route the policy sets has been walked first, through your capstone instructor.
The application checklist covers the same ground before a first submission, and the process end to end shows where a return sits along the branch.
Where does this desk fit?
A return is when most people call us, because it is the first moment requirements stop being general and become specific to one folder. We read the letter, sort it into the four kinds above, rebuild every page the answers touch, and carry the resubmission and any further reply through to approval. This practice is independent and has no affiliation with Western Governors University. The capstone remains yours — your question, your data, your findings — and the decision remains the board's. The eight stations describe the engagement, and the questions page handles the rest.
What to do next
Send the letter and the folder it refers to, with the attachments the board named. The reading is free: you will hear which items are single-line repairs, which ones move the folder, and how the resubmission should be shaped — including an honest "you can file this yourself" when that is true. Request the free application review.
Sources
- WGU policy handbook, Institutional Review Board (IRB) — approval requirement, review levels, the institutional route for university data, and the sign-in-gated IRB information site: cm.wgu.edu (WGU Knowledge Center, IRB policy)
- WGU Institutional Review Board, Request for Approval to Conduct Research (published copy of the university's capstone application form) — alignment with the approved proposal and the consent document, the relationship and protected-populations questions, the facility signature reminder: request_for_approval_to_conduct_research (PDF)
- WGU Program Guidebook, MS Curriculum and Instruction — capstone competencies placing board approval ahead of the methodology chapters: wgu.edu program guidebook (PDF)
- 45 CFR 46.116 — consent obtained before a person is involved in research: Cornell LII, section 46.116
- 45 CFR 46.111 — what a reviewer must find satisfied before approving anything: Cornell LII, section 46.111
Send the letter. Get the list it really contains.
One free reading, no obligation: what each note asks for, which pages have to move, and how the folder should look when it goes back.
Request the free application review- each note sorted into its kind
- the pages every answer will touch
- whether you can reasonably answer it alone