Answering the WGU board's revisions: the response that ends the loop

What is the response document, and why does the board need one?

A reviewer holding your resubmission has one job before any thinking begins: confirm that each thing they asked for has happened. Every minute spent finding your changes is a minute in which the file looks incomplete. The response document removes that search. It lays the board's own requests down the page in the board's own order, and beside each one puts two facts — what you changed, and where the change can now be seen.

That second fact is the one people leave out, and it is the one that does the work. "We have clarified the storage arrangements" tells a reviewer nothing they can verify. "Storage is now named in the confidentiality answer and in the third paragraph of the information sheet" lets them look, see it and tick. The same sentence also proves you found every page the change belonged on, which is the anxiety underneath most second returns.

Where the response physically goes depends on how WGU's current handbook or IRB portal routes revisions: some routes want the answers inside the application itself, some want an attached memo, some want both. Ask your capstone instructor which applies before you build the document.

What order should the work happen in?

Not the order of the letter. The letter's sequence reflects how a reviewer reads a folder; your sequence has to reflect how a folder is built, because some items make others obsolete.

1. Settle the design items first

   Anything asking for a different population, instrument, comparison or setting is not an editing task. WGU's application expects the project you describe to match the proposal endorsed earlier in the capstone sequence, so a design change is a conversation with your capstone instructor before it is a keystroke. Settle it, then let every other answer be written against the settled version.

2. Then the protection items

   Requests about voluntariness, privacy, identifiers or safeguards change procedures, and procedures are described in several places. Decide the new procedure completely — who does it, who cannot see the result, what is recorded — before drafting a word about it.

3. Then propagate

   For each settled change, list every page asserting the old version and edit them in one sitting: application answers, information sheet, recruitment wording, instruments, security plan, site letter. Half-propagated edits are the single most common cause of a second pass.

4. Then the missing items

   Records and signatures are gathered last only because they take nobody's judgement, and first only because they take somebody else's calendar. A facility signature or a training completion record should be in motion from the day the letter arrives, and attached before the file moves.

5. Then write the response

   Written last, against a folder that has already changed, so that every "where it now lives" line is a statement of fact you have just verified rather than an intention.

6. Then read the whole folder cold

   Front to back, as one story, ideally a day later. You are looking for the sentence that still describes the old project — there is usually exactly one, and it is usually in an appendix.

What about a note you think is wrong?

Answer it once. Disagreement is legitimate — reviewers work from what the file says, and sometimes the file said something you did not mean. What is not legitimate is repeating your original sentence more firmly, in the hope that a second reading lands better.

A response that works has three parts and stops. State what you understand the concern to be. Give the fact that bears on it, briefly, with a source if one exists. Then offer something: an alternative safeguard, a narrower claim, an extra piece of documentation. The board is charged with deciding whether protections are adequate against fixed criteria, and criteria are satisfied by arrangements rather than by conviction. Handing the reviewer an arrangement to approve is the difference between a discussion and a stall.

Where you accept a request you privately think unnecessary, accept it plainly, without editorial. A single line of grievance in an otherwise clean response invites the reviewer to reread everything.

What gets a file returned a second time?

• Answers with no address: the change happened, but the reviewer cannot find where.
• Half-propagated edits: the procedure answer moved, the information sheet did not.
• Old versions still attached beside the new ones.
• Silent extra changes the board did not request and you did not flag, which read as drift.
• A design change made in the application alone, without the approved proposal being brought into line.
• Documents promised in the response but not attached — a signature "to follow" is an open item.
• Anything collected in the meantime; the approval is the gate, and it has not opened yet.

Reading that list backwards gives you the pre-flight check. Reading the return letter itself is the step before this one, and the process end to end shows where both sit on the branch.

Where does this desk fit?

Revision responses for WGU capstone files are ordinary work here: sorting the letter, settling what has to change, rewriting every page the changes touch so the folder reads as one project again, then carrying the resubmission and each further reply until approval arrives. This practice is independent and has no affiliation with Western Governors University. The capstone stays yours, and what the board decides stays the board's. The eight stations describe the engagement; the questions page handles the rest.

What to do next

Send the board's letter and the current folder. The free reading names each request, what would close it, and which documents each answer has to move — including an honest word when the whole thing is one clear afternoon of your own work. Request the free application review.