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

What does it mean when a Purdue Global IRB application comes back?

It means a reader could not close a question with the file as filed. Under 45 CFR 46.109(a), a board reviews the work and may approve it, may require modifications as the price of approval, or may refuse it outright; 46.109(d) obliges the board to notify the investigator in writing of that decision, and where a study is disapproved, to state the reasons and give the investigator a chance to respond. The letter you are holding is almost always the middle instrument — modifications required — and the word most candidates hear, rejected, appears nowhere in it.

Purdue Global's own initial-review procedure is explicit about the returning move. Its published SOP 302 states that where a reviewer determines that additional information is needed, the proposal goes back to the researcher with an explanation and the researcher has the opportunity to make edits. That is a loop the process is built to run, not an exception it tolerates. Treat the letter as the first reading you have received from someone who did not write the study, because that is exactly what it is.

Who sent it back — the faculty reviewer or the board?

The distinction changes what you owe. Purdue Global routes a submitted protocol first to the faculty member working with the researcher, or to the supervisor where the researcher is an employee, for an administrative check that the paperwork is complete and every required element is present. SOP 302 says plainly that incomplete submissions are not routed onward for board review. If your file stopped there, nothing about the science has been judged; a document is absent, a field is blank, or a required upload never attached.

Past that gate the file reaches a board member, who determines whether it is exempt from further review. Where the proposal is judged to fit the expedited criteria, the SOP describes routing to two additional reviewers, with the IRB Chair making the determination if those two do not reach consensus. So a return can arrive from an administrative reader, from a single reviewer, or from a reviewer whose colleagues disagreed. Look at who signed it and at which stage it names before you write a word of reply.

How do you read a finding without under-reading it?

Take each finding and ask three questions of it in order. First: what is the reviewer's underlying worry — risk, privacy, voluntariness, equitable selection, the adequacy of consent? Purdue Global publishes the worksheet its reviewers use, IRB-314, and it is a checklist of the 46.111 criteria: risks minimised, risks reasonable against anticipated benefits, selection of participants equitable, adequate provisions for privacy and for confidentiality of data, additional safeguards wherever participants could be exposed to coercion or undue influence. A finding is nearly always one of those boxes refusing to be ticked.

Second: which documents carry the fact the finding touches? A single dimension — the sample figure, the instrument's name, the recruitment channel, the number of sites, who does the recruiting — usually appears in the protocol, the consent or information sheet, the recruitment material, the data-collection instrument and the site permission letter. List them before editing.

Third: what will make the answer checkable in one pass? A reviewer reopening your file is confirming that each item was addressed and that the fix broke nothing else. Make that confirmation mechanical rather than investigative, and you have removed the reason for a second return. The mechanics of that memo are the subject of a separate sheet: writing a revision response the board accepts on the next pass.

What should you not do with a returned file?

• Do not start collecting data. A return is not a conditional approval, and Purdue Global's guidance is unambiguous that documented approval precedes data collection. Nothing gathered on the wrong side of that line becomes usable later.
• Do not answer only in the cover note. A reply that explains a change the protocol still does not contain leaves the reviewer with two contradictory documents and one more reason to write back.
• Do not quietly change something the board did not ask about without flagging it. Unannounced edits found by a reviewer cost more trust than the edit was worth.
• Do not argue first and comply second. Where you genuinely disagree — and sometimes you should — the disagreement is stated calmly, with the design reason, in the same list position as every other item.
• Do not restart the file as a new submission because the return felt total. Unless the design itself has changed, the existing file is the one that carries your history with the board.

Does a return put the study at risk?

No. It puts the schedule at risk, which is a different thing, and it is worth being honest that a second and third return cost more than the first. What a return does not do is prejudice the board against the work. Purdue Global's board describes its mission as protecting the rights, welfare and privacy of participants while supporting investigators through the process; the letter is the supporting half of that sentence doing its job in writing.

The one case that deserves care is a letter that reads less like a list and more like a challenge to the premise — a reviewer asking whether the activity is research at all, or whether the design can answer the question it poses. Purdue Global's initial-review criteria include a determination of scientific or scholarly validity, established through the experience of an investigator, a funding agency review, a separate peer review or a faculty committee. A letter probing that ground is asking for a different answer than a missing-upload letter, and it is worth reading twice before replying once.