A waiver of the requirement for documentation of informed consent may be granted when the research presents no more than minimal risk, the waiver will not adversely affect participants' rights or welfare, and the research could not practically be carried out with signed forms. This is the documentation waiver under 45 CFR 46.117(c), distinct from waiving consent itself under 46.116(f). The two are separate regulatory actions with separate criteria, and confusing them is the most common error in IRB submissions.
The two waivers people conflate
Federal human-subjects rules split consent into two layers. Consent itself is the process of informing a person and obtaining agreement. Documentation is the physical or electronic record of that agreement, usually a signed form. A documentation waiver removes only the signature record. The researcher still must obtain and document consent through some other means, such as a verbal script or an information sheet.
The distinction matters because the criteria differ. Waiving documentation under 45 CFR 46.117(c) requires only that the research involve no more than minimal risk and that the signature either be the only record linking the participant to the study or threaten confidentiality. Waiving consent entirely under 46.116(f) requires four findings, including impracticability and, where relevant, debriefing. A study can qualify for one and not the other.
Some studies need to waive both. A survey of stigmatized behavior may need consent waived and documentation waived. Others, such as a benign usability test, need only the documentation waiver because participants can still be told what is happening.
Why the signature is treated as a separate risk
The signature is not neutral data. It creates a link between a named person and their participation, and that link persists. For research on illegal conduct, mental health, immigration status, or genetic risk, a signed form becomes a discoverable record that can expose the participant to legal, employment, or social harm.
Regulators reasoned that the act of signing can be the dominant risk in an otherwise low-risk study. A survey about workplace harassment carries little physical risk. A signed acknowledgment that a specific employee answered questions about their supervisor can trigger retaliation. The signature, not the questions, is the hazard.
This is why the "only record linking" criterion exists. If the signed form is the sole artifact connecting a person to the study, that form is a confidentiality liability. Removing it eliminates the link. If other data already identify the participant, the signature adds less marginal risk, and the criterion is harder to satisfy.
Plain language: the rule protects people when their name on a form is more dangerous than the study itself.
Quantified context and where the thresholds sit
The regulatory floor is minimal risk, defined in 45 CFR 46.102 as risk where the probability and magnitude of harm are no greater than those ordinarily encountered in daily life or during routine examinations. That is a qualitative boundary, not a number, and IRBs vary in how strictly they read it.
Review categories help translate risk into process. Expedited review under 45 CFR 46.110 covers categories published by the Secretary, including research on individual or group characteristics and recordings made for research purposes. A documentation waiver request often rides alongside an expedited determination. Full-board review is required when risk exceeds the expedited categories.
Institutional practice adds thresholds that are not in the regulation. Many IRBs require a written justification for each of the applicable 46.117(c) criteria, typically one to three paragraphs per criterion. Some institutions cap documentation-waiver approvals at studies using verbal scripts under a defined reading level. None of these institutional rules are federal law, but they govern whether a submission advances.
There are no reliable national statistics on how often documentation waivers are granted. Claims about approval rates should be treated cautiously; the data are held by individual IRBs and are not systematically published.
Time course of a waiver request
| Stage | What happens | Typical duration |
|---|---|---|
| Pre-submission | Researcher drafts protocol, consent script, and waiver justification | 1 to 3 weeks |
| IRB intake | Submission logged and screened for completeness | 1 to 10 business days |
| Reviewer assignment | Determined as expedited or full board | 1 to 15 business days |
| Review and stipulations | Reviewer requests clarifications or revisions | 1 to 4 weeks |
| Approval and expiration | Waiver granted with approval period, often 12 months | 12 months typical |
The durations are institutional norms, not regulatory guarantees. Full-board review adds a scheduled meeting cycle, which can add two to six weeks. Renewals repeat the review, and a waiver granted for one approval period does not automatically continue.
Edge cases that change the analysis
Verbal consent still requires a script. A documentation waiver does not permit an undocumented, informal conversation. The IRB usually approves a script or information sheet that the researcher reads and delivers.
Electronic signatures are documentation. Clicking "I agree" on a web form can constitute a signed record under many institutional policies and under the e-signature framework in 21 CFR Part 11 for applicable studies. If the click is retained and linked to the participant, it is documentation, and a waiver analysis must address it.
Children add a layer. Parental permission and child assent are separate from documentation. A waiver of documentation for the parent does not waive assent, and pediatric studies face stricter minimal-risk interpretation.
Deception studies often need both waivers. If participants are misled about the study's purpose, consent may be waived or altered, and documentation is often waived to avoid a signed record of the cover story. Debriefing then becomes a condition of approval.
The counterintuitive detail: a study can be minimal risk and still fail the documentation-waiver test. If the signature is not the only link and confidentiality is not threatened, the criteria may not be met even though risk is low. Risk level alone is not sufficient.
Common misconceptions
The first misconception is that a documentation waiver waives consent. It does not. Participants must still be informed unless consent itself is separately waived.
The second is that verbal consent requires no record at all. Researchers typically must document that consent was obtained, for example by recording the date and a script identifier in study logs.
The third is that low risk guarantees approval. The regulatory criteria are conjunctive, and the confidentiality analysis is independent of the risk finding.
The fourth is that a waiver covers the entire study. It covers a defined procedure and a defined approval period. Adding a new data collection may require a new determination.
The fifth is that state law is irrelevant. Some states impose additional requirements for research involving certain populations or records, and federal rules set a floor, not a ceiling.
Practical actions for a defensible request
State which waiver you seek: documentation only under 46.117(c), consent under 46.116(f), or both. Write a separate justification for each regulatory criterion, not a combined paragraph. Describe exactly how consent will be obtained and recorded without a signature. Identify every data source that could link a participant to the study and explain why the signature is or is not the only link. Attach the verbal script or information sheet and confirm its reading level. Red-flag warnings: do not describe a signature as "just a formality"; do not claim minimal risk without addressing the confidentiality analysis; do not submit a combined waiver request without separate criterion-by-criterion justification.
A practical test before submitting: can a reviewer point to a sentence in your protocol for every criterion? If not, the request is incomplete. Building that sentence-level mapping takes an afternoon and prevents a revision cycle.
Limitations and what the rules cannot settle
The criteria are qualitative, and IRB interpretation varies by institution and by reviewer. A determination at one site does not bind another. Researchers working across sites should expect separate reviews and possibly different outcomes.
The regulatory text is stable, but institutional policies, state law, and electronic-signature practices change. This article describes the federal framework and general practice; it does not predict any specific IRB decision.
Finally, the rules govern process, not ethics. A study can meet every criterion and still be ethically questionable, or fail a criterion and be ethically sound under a different design. The waiver is a tool, not a verdict.
This article is general educational information about research regulation, not a legal opinion or an IRB determination. It does not promise approval outcomes. Consult your institutional review board and, where state or international law is involved, a qualified local professional before relying on any waiver determination.