Continuing review and closing your study at Walden: what the board expects after approval

Does your Walden approval expire?

The honest answer is: your letter says. Under the revised Common Rule, continuing review is no longer a universal requirement — 45 CFR 46.109 requires it, at intervals matched to the study's risk and not less than once per year, for research reviewed by the convened board, while research on the expedited path is generally excused unless the board decides otherwise and documents why. An institution's board may still choose oversight the regulation does not force, and 45 CFR 46.115 expressly contemplates that choice by requiring boards to record "the rationale for conducting continuing review of research that otherwise would not require continuing review."

So the governing document is the letter the Walden board sent you, read alongside Walden's current handbook and IRB portal. Look for three things: whether the approval states a term, what the board asks you to submit and when, and what conditions ride with it — reporting problems, seeking approval before changing anything, using only the approved versions of your documents. Most Walden doctoral studies are minimal-risk and travel the expedited path, but your letter, not an assumption, says which path your file took. Diary the dates it creates the day it arrives; the after-approval period runs on a calendar that is unforgiving in one specific way.

What does the board expect a continuing-review submission to say?

Where your letter or Walden's process calls for periodic review or a progress report, the board is asking a simple question in formal dress: is the study still the one we approved, and are participants still protected? Regulators have long described the shape of a good answer — the progress reports and problem summaries that 45 CFR 46.115 places in the board's records, and the elements federal guidance expects a reviewing board to weigh. A submission the board can act on without writing back covers:

• Where the study stands — recruiting, collecting, finished collecting, analysing.
• Enrolment against plan — how many people have taken part, against the number the approved file described.
• Withdrawals and complaints — anyone who stopped, and anything any participant or site raised, resolved or not.
• Unanticipated problems and deviations — anything that departed from the approved procedures, already reported when it happened and summarised again here.
• Changes — every approved change-in-procedures request, listed; and none that were not approved. If a change is pending or needed, say so — the request itself travels by the route in changing an approved study at Walden.
• The consent document in current use — which must be the approved version, and is commonly asked for so the board can confirm exactly that.
• The data's condition — where they live, who can reach them, and whether identifiers have been separated or destroyed on the schedule your data-security plan promised.

Write it in one sitting from your log, not from memory. Walden's handbook already requires a recruitment and data collection log, and it expects the raw dataset, final dataset, and analysis process to be available electronically to your committee — the log is not extra paperwork; it is the raw material of every after-approval letter you will owe the board.

What happens if approval lapses?

Everything stops. A lapse is not a grace period or a paperwork state — when approval expires unrenewed there is no approval, and research activity halts: no recruitment, no consent, no sessions, no new records opened. Federal oversight bodies describe the sole exception narrowly: only what is needed to protect participants already enrolled, routed through the board, not around it. Data gathered inside a lapse sit on the wrong side of the only line that matters, exactly like data gathered before approval: they can be ruled unusable and can put the study itself in question.

The operational moral is dull and absolute: whatever renewal or progress submission your letter requires, file it well before the date, complete on the first pass. A submission that arrives on the deadline with an item missing becomes an exchange, and the exchange can outlive the approval it was meant to extend. If a lapse has already happened, stop everything, write to the board plainly through the route Walden's handbook prescribes, report anything that occurred inside the gap, and wait for the board's instruction — candour is the only good move on that board.

When is a study finished — and why does closing it matter?

A study is not finished when the last interview ends; it is finished when the board closes the file, and it does that only when you report the conditions met. Open and closed are different postures: an open study carries every duty of the approval — reporting, change requests, any renewal the letter requires — while a closed one releases you and tells the board participants are no longer at risk.

The closure submission itself, in whatever form Walden's current portal gives it, is a short honest accounting: final numbers, confirmation that activity has ended, a summary of any problems across the study's life, and the data's final state — de-identified, stored as the plan promised, on the retention and destruction schedule the plan named. Then keep what must be kept: signed consents, approvals, correspondence, and the data, held confidentially for the period Walden's handbook counts beyond CAO approval — with 45 CFR 46.115 setting the board's own records floor after completion. Closure ends the study's activity, not its paper trail.

What does the board have to do with the final study document?

Two things, and both are checked late in the sequence, when surprises are most expensive. First, the approval number from your letter appears in the final doctoral study itself — published Walden studies on ScholarWorks print it in so many words — which is why the letter is filed, not merely celebrated. Second, the study you describe in that document must be the study the board approved, as amended by the change letters you actually obtained. Committees and reviewers read methods chapters against IRB files; a procedure that appears in the chapter but never in the file is a discrepancy you would much rather not explain at the end. The whole arc — from CITI training through the application to this final match — is drawn in the Walden IRB process, step by step, and the enclosures that make the original file whole are in the application checklist.

A short after-approval calendar

1. Day one: file the approval letter; diary every date it creates; open the study log.
2. Throughout: run only the approved file; report problems promptly; route every change through the board before it happens.
3. Well before any stated term: assemble the progress submission from the log; file it complete.
4. At the end of collection: execute the data plan's promises — separation of identifiers, storage, the schedule.
5. When analysis ends: submit the closure; keep the records for the required period.
6. In the final document: print the approval number; describe the study the file actually approved.

What to do next

If the letter is in hand, read it against this page today and diary what it creates — that hour is the cheapest defence the after-approval period offers. If the board's dates are already close, or a lapse has already happened, move now rather than perfectly. And if you would rather the whole correspondence be carried for you, that is the desk's standing arrangement: under a full engagement we track the letter's calendar, draft each progress and closure submission from your log, route every change, and answer the board until the file is closed — the same way we carry the application itself. How it works describes the arrangement end to end. Send your approval letter and where the study stands through the free application review, and we will map what the board expects from here to closure — including, when it is true, that nothing is owed but the closure itself. The study stays yours; the decision stays the board's.