How to write a revision response the Capella IRB accepts the first time

What does a reviewer actually do with your response?

A Capella reviewer reopening a deferred or returned file has one job: confirm that each item in the letter has been addressed and that the fix did not break anything else. Capella's SOPs say a deferred exempt or expedited file "will be reevaluated by the reviewer(s) once revisions are made," and a file deferred by the full committee "must be reevaluated during a convened meeting." Either way, the reader is checking a list against a file. Your response should make that check mechanical. If the reviewer has to search three attachments to find out whether you changed the recording language, you have made the decision harder than it needs to be.

Capella's revision FAQ tells you the mechanics — edit the existing application, "update all answers and upload new document versions while removing outdated files," and resubmit with the Submit button. The deferral FAQ tells you where free text goes: the Additional Information section at the end of the form for explanations with no matching field, and the Additional Documentation question for files with no designated slot. The memo described here lives in that Additional Information section, or as an attached response document, and it points at changes you have also made in the application fields themselves.

What does the point-by-point memo look like?

Four columns, one row per board comment, in the board's order. Keep the board's own numbering if it gave you one; if the letter was written in paragraphs, number the items yourself and say so in a one-line preface.

Three habits make this table work. The comment is quoted, not paraphrased, so the reviewer can see you read the same sentence they wrote. The response states what is now true, not what you intended; "we clarified" is weaker than "the sentence now reads…". And the location is specific enough to be checked at a glance — document, version, section or paragraph, and the matching application field.

Why tracked changes, clean copies, and version stamps?

A reviewer needs to see two things about every revised document: what changed, and what the participant will actually see. A tracked copy answers the first; a clean copy answers the second. Submit both for each revised participant-facing document — consent, recruitment text, interview guide, survey introduction — and say in the memo which is which. If the file type does not support tracked changes, a short "changes from previous version" note at the top of the clean copy serves the same purpose.

Version stamps do the rest. Put the version number and date in the filename and in the document footer: Consent_Form_v3_2026-08-23.docx, footer "Consent Form v3 — 2026-08-23". Every reference to the document in your memo and in the application then names the same stamp. The IRBManager instruction to delete outdated versions is the other half of this: one current version of each document should be attached, and it should be the one your memo names. Two consent forms in the file, neither stamped, is the single most common reason an otherwise complete response comes back.

Stamp the research plan too. Capella's SOPs warn that information contained in school documents "but not on the IRB application is considered not approved by the IRB," and that major changes to the research plan "may be subject to further scientific merit review." If a board comment forces a change to sampling, method, or instruments, the research plan or SMART form changes with it, your mentor sees it, and the stamped revision is attached.

What is the one-file-one-fact rule?

Every fact about the study appears in several documents: how many participants, how long an interview takes, whether it is recorded, what the incentive is, where data live and when they are destroyed, who sees identifiable responses, who sends the invitation. Each document that states a fact must state it the same way as every other document — including the IRB application fields, which are the board's document of record. Most deferral letters contain at least one "reconcile" item, and most second returns are caused by a fix in one place that created a new mismatch elsewhere.

Before you submit, build a small alignment grid: facts down the side, documents across the top, and tick each cell after reading the actual sentence. The facts that most often drift are sample size, recording, the incentive, the storage and destruction plan, and the description of who recruits. Capella IRB consent form requirements lists the consent elements that have to match the application word for word.

How do I answer a comment I disagree with?

Once, briefly, and with an alternative. State that you have considered the comment, give the reason the requested change would harm participants or the study, and propose a protection that meets the board's concern by a different route. Then stop. If the board repeats the request on the next pass, make the change. Capella's SOPs note that the IRB "may require changes to the study design if the potential benefits do not justify the potential risks"; the board's decision is its own, and relitigating a decided point costs a cycle. The study remains yours in every respect that matters — design, data, findings — and the response is the place to show the board that you have protected participants, not to win an argument.

What is the pre-submit checklist?

1. Every board comment has a numbered row in the memo, quoted verbatim.
2. Every row names a document version and section, and the matching application field.
3. Every application field the memo names has actually been edited — open the form and read the new text.
4. Every revised document is attached once, as tracked and clean where it is participant-facing, with a version stamp in the filename and footer.
5. Every superseded document has been deleted from the form.
6. The alignment grid is complete: sample size, recording, incentive, storage and destruction, who recruits, who consents — identical across application, consent, recruitment text, instruments, research plan, and site letters.
7. Any change the board did not request is listed in a final "Other changes" row with the reason.
8. Changes to the research plan have gone to your mentor, and the stamped revision is attached.
9. Your mentor has read the letter and the revisions — Capella's FAQ expects this before resubmission.
10. Sign and submit at the end of the form; confirm the xForm has left your "awaiting your attention" list.

What to do next

If a letter has just arrived, read what a returned Capella application means and what to do next for the outcome types and the cycle. If you would rather hand the whole thing over, this is what we do: we build the memo, rewrite every document the board touched so all of them agree, attach the stamped tracked and clean copies, update the application fields, and manage each reply until the approval letter. How it works describes the engagement and the packages describe what each one covers. Send us the deferral letter and the current file for a free review — we will tell you which items are one-line fixes and which ones change the study, before you commit to anything.