Walden IRB returned your application: what the letter means and exactly what to do next

What does "returned" actually mean at Walden?

The regulation behind the board, 45 CFR 46.109, gives it those moves — approval, required modifications, disapproval — and requires the decision in writing. Two details in it should reframe the letter in your inbox. First, a file reviewed on the expedited path cannot be disapproved by the reviewer at all: under 45 CFR 46.110, expedited reviewers may exercise every authority of the board except disapproval, which is reserved for the convened board. Second, even a formal disapproval must arrive with written reasons and a chance to answer. A letter listing revisions is therefore not a verdict; it is the board naming the modifications that would secure approval.

Walden's own handbook makes the cooperative reading explicit. Its board meets weekly, decides by majority vote among approve, approve with stipulations, and disapprove — and while its decisions are not appealed, the handbook states that the IRB chair works with the researcher to bring a proposal "into an approvable state." That sentence is the posture behind every returned file: the board is steering yours toward approval, not away from it. The letter arrives after a long runway — committee approval, the University Research Reviewer's concurrence, the board's reading against what they signed — and it is addressed to you, the researcher of record. Read it twice before touching a document: once to feel whatever you need to feel, and once to see it as a task list written in a formal register.

Which outcomes can the board's letter carry?

Walden's own labels live in its current handbook and portal, but every letter a review board sends falls somewhere on a short spectrum. Find yours first; the response differs by row.

Most letters that feel like rejection sit in the third row. The board has read your file and written you a map of the distance left. Treat the map as the asset it is.

How do you read the letter, line by line?

Every sentence in a revision letter asks for one of five things. Sorting the items by kind — before revising anything — tells you the true size of the job and who has to be involved.

• A missing document. "Please provide documentation of the site's agreement" means a letter of cooperation on letterhead, over the signature of a person who actually controls access. "Please provide the recruitment materials" means every flyer, email, script, and post, verbatim, each as its own enclosure. These items are gathering work, and the slowest of them — the site letter — should be started the day the board's letter arrives.
• A missing protection. Requests about voluntariness, withdrawal, confidentiality, or storage mean a required element is absent or vague. The fix is written into the document itself — a plain-language clause in the consent, a data plan that names the device, the access list, the retention period Walden's current handbook sets, and the destruction method — never merely asserted in your reply.
• An inconsistency. "Please clarify" often signals that two documents disagree — the application says interviews are recorded, the consent never mentions recording. The fix is to make every document state the fact the same way, not to explain the discrepancy.
• A question about you. "Please describe your professional relationship to the site" is the conflict-of-interest question. The board suspects a dual role and is waiting for the plan: who recruits, who consents, who sees identifiable data, and how a refusal stays invisible to you. Researching your own workplace at Walden walks through what holds up.
• A question about the design. Occasionally an item reaches into the study itself — the sample, an instrument, an incentive. That is not yours to settle alone in an IRB reply; the design belongs to your committee and the University Research Reviewer. Take it to the chair first; answer the board with the committee's position attached.

What must stop while the file is returned?

Everything. Nothing in a returned file is approved, including the parts the board did not question. No recruitment in any form — no flyer, no email, no colleague sounded out over coffee. No consent conversations, no survey link, no chart or roster opened for research purposes, even records your job already lets you see. The line Walden draws is the approval letter with its number; data gathered on the wrong side of it is not a head start but a liability that can put the whole study in question. If some activity has already happened — a pilot conversation, an early survey — do not bury it. Disclose it plainly in your response; boards deal far more gently with candour than with discovery.

One more thing must not stop: your CITI human-research training. If the completion lapses while the exchange is open, renew it before you resubmit, under the same name the application carries — an expired certificate is an avoidable next letter.

What should the first sitting produce?

1. Preserve the letter. Save it whole, with its date and reference. Your response will quote it item by item, and 45 CFR 46.115 puts all board-investigator correspondence in the permanent record — write as if the file will be read again, because it can be.
2. Build the item list. Number every request in the board's order and wording; if the letter was prose, number the sentences yourself.
3. Sort each item into the five kinds above — it tells you which items are an afternoon and which involve other people.
4. Start the slow items now. The site's signature and any committee consultation take longest; everything else proceeds while you wait.
5. Map each item to its documents, including the ripple: a consent change touches the application, a recruitment change touches the site letter. The file must agree with itself when it goes back.
6. Draft the response as a ledger — item, change, location — and hold it until every item is closed. One complete resubmission; a partial reply reopens the exchange. The ledger's mechanics are the subject of answering Walden IRB revision requests.

Why do Walden files come back at all?

The same reasons, year after year — and Walden has published its own list. Its Quick Answers page on ethics-approval delays names, among others: application forms filled out before the University Research Reviewer phase settled the design, leaving "stray references" to superseded elements; errors in participant-facing documents, which must be clean; a professional role that puts pressure on the people being recruited, as when a manager recruits subordinates; and letter-of-cooperation confusion — the board itself tells you whether written site permission is needed after it reads the application's data-source answers. To that list this desk would add the perennials: recruitment materials paraphrased instead of enclosed, a consent element missing in plain language, "securely stored" where a named device, access list, retention period, and destruction method should be, and a dual role described nowhere in an own-workplace study. None of this is exotic — a returned Walden file is almost always repairable in one coordinated pass. The enclosures a complete file carries are catalogued in the Walden IRB application checklist, and the whole sequence in the step-by-step guide.

What to do next

Read the letter twice, build the item list, and start the site letter today — that much is yours to do this week regardless of who carries the rest. If you would rather hand the exchange over, this is the desk's daily work: we read the board's letter the way the board meant it, sort the items, write the ledger, revise every enclosure so the file agrees with itself, involve the committee where the proposal is touched, and carry the correspondence until the approval letter arrives. How it works lays out the engagement end to end. Send the board's letter and your current file through the free application review and we will tell you honestly how far from approval the file stands — including, when it is true, that you are one clean resubmission away. The study stays yours; the decision stays the board's.