Complete before good: the reading that happens before the board reads your project.

What does Herzing check before it reads anything?

Look at where the checklist sits. On both of Herzing's IRB applications it is not an appendix, not a footnote, and not a summary at the end — it is the first thing on the first page, above every substantive question the form asks. Typography is telling you the order of operations. Somebody establishes that the parts are all there, and only then does anybody form a view about what the parts say.

The forms then close the loop in their own words. Each explains that after submission you will hear back in writing: either the review is complete and the project may go ahead, or further information is required before the human-subjects question can be settled. Herzing has written both branches onto the document you are filling in. The first branch is a reading. The second branch is a receipt.

What does a complete Herzing folder actually carry?

Two different manifests, depending on which application your programme is routed to. Set them side by side and the shared spine is obvious, as is the part that changes.

Why is completeness settled before quality?

Because of what a review pass physically is at Herzing. A file does not float in a queue until somebody has a spare hour; it is placed on a dated agenda. The university publishes its meeting dates in pairs, each one beside the date its materials are due, and its Statement of Principles says what happens to a non-exempt application that arrives late: it goes to the meeting after. The Bylaws place the board's stated meetings in the second week of every eight-week term, with the IRB Administrator announcing dates and deadlines to the university community.

So a pass is a slot, and a slot gets used whatever is in it. Send a file with an unsigned line, a missing certificate or an absent letter, and that slot is spent producing a document telling you what page one could have told you for nothing. Send the same project complete, and the identical slot yields a reading of the design — questions about your sample, your consent language, your security plan. Both outcomes consume one pass. Only one of them moves the project forward.

This is why the desk keeps insisting on an unglamorous sequence: fill every pocket, then file. What a pass takes in calendar terms belongs to the board, and nobody outside it should be forecasting that to you. How many passes your file demands, though, is entirely within your gift — and a complete folder demands one.

Which items most often leave a folder incomplete?

Predictably, the ones that depend on somebody who does not work for you.

1. The signatures. The improvement application wants three, and one of them belongs to a program chair. A form that is otherwise flawless and short one signature is not a filing at all — it is a draft with attachments.
2. The letter from an affiliated institution's chair. Marked "if applicable", which is exactly why it gets read as optional. If it applies to you, it is not optional; it is a document another person has to produce on their own calendar.
3. The external board's paperwork. Where a site or health system runs its own review, Herzing wants both that application and its approval letter. People routinely send the letter alone, having thrown away the thing it approves.
4. The training certificate itself. The checklist asks for a copy of the certification. A completion number typed into a field is not a copy, and this is the fastest item on the entire list to verify — which means it is also among the fastest to be caught.
5. The instruments. Every questionnaire and survey, where any are used. "The survey is drafted" does not satisfy a line that asks for a copy of it.

Notice how many of these have nothing to do with the merit of your project. That is the point. They are the reasons a good project gets a receipt instead of a reading.

Does "complete" only mean "all present"?

No, and this is where careful people still come unstuck. A folder can hold every listed item and remain unreadable as a single document, because the items disagree: a consent form describing a sample the application does not, a security answer naming a retention period the plan contradicts, an instrument carrying a question the abstract never mentions. Each item is present. The file is still not coherent.

A reviewer reads across documents as a matter of habit, and every mismatch is something they must stop and reconcile — which converts a strength of your project into a finding against your paperwork. What agreement means, document by document, is worked through in the checklist the board reads as one file. Which of the four review levels will do the reading is settled separately, in what actually sorts a Herzing file.

Does a complete folder buy an approval?

No, and anyone telling you otherwise is selling something we do not. Completeness buys exactly one thing: a reading of your project rather than of your paperwork. What happens in that reading is governed by the board's own approval criteria — whether risk has been minimised and is reasonable against anticipated benefit, whether selection is equitable, whether consent is properly sought or lawfully waived, whether privacy and confidentiality are genuinely provided for.

Those are judgements about the design, made by a board applying federal criteria, and they belong to the board alone. What we can promise is the thing that gets judged first. The study, the data and the conclusions stay yours from first draft to final presentation; we build and carry the file that surrounds them.

What to do next

Open your application to page one and read the checklist as a manifest rather than a suggestion. For each line, answer with a document you could attach in the next minute — not a plan, not a draft, not a number you could look up. Any line that fails that test is the reason your next pass would produce a receipt.

If more than one line fails, hand the folder over in whatever state it is in. Our free application review comes back in writing: the pockets that would hold up under a reviewer's eye today, the ones that would not and the reason, and the item to chase first — usually whichever depends on somebody else's signature. There is no charge and no obligation afterwards. How it works describes what we do next, and where you are welcome to stop.

Sources

• Herzing University IRB, Application for Improvement or Innovation Project Approval (PDF, November 2025) — the page-one checklist and signature lines. Healthcare_Improvement_InnovationProject_Application.pdf
• Herzing University IRB, Application for Research Protocol Approval (PDF, October 2025) — the page-one checklist and the faculty sponsor undertaking. IRB_Research_Protocol_Application_1025.pdf
• Herzing University IRB, Statement of Principles (PDF, September 2025) — the meeting schedule and submission cut-off. IRB_Statement_of_Principles.pdf
• Herzing University, Institutional Review Board Bylaws (PDF, September 2025) — stated meetings, quorum and the Chair's triage. IRB_Bylaws.pdf
• Herzing University, Institutional Review Board (IRB) — the dated IRB calendar. herzing.edu/institutional-review-board-irb
• 45 CFR 46.111 — the seven findings that have to be made before any approval issues. ecfr.gov — title 45, part 46

Checklist wording, form names and calendar dates change between editions; check each against Herzing's current IRB handbook or portal. The order — complete first, good second — does not change.