The FDA allows verbal consent prior to participation only when the research meets the narrow criteria for an exception from informed consent (EFIC) under 21 CFR 50.24, and even then, verbal consent is not the default: the regulation requires documented community consultation, public disclosure, and—when feasible—an attempt to contact a legally authorized representative before enrollment. In practice, verbal consent precedes participation in a small subset of emergency, life-threatening research where written consent is impossible and time is critical.
This question sits at the intersection of research ethics, federal regulation, and clinical urgency. Most thin explainers collapse the answer into "emergency research," which is incomplete. The FDA's framework actually contains several distinct pathways—some allow verbal or short-form consent, some waive consent entirely, and some apply only to minimal-risk studies. Understanding which pathway applies, and why, requires going one level deeper into the regulatory mechanics.
The regulatory mechanism behind verbal consent
Informed consent in FDA-regulated research defaults to a written, signed, and dated document under 21 CFR 50.27. That default exists because the signature serves two functions: it documents that a conversation occurred, and it creates a durable record the subject can revisit. Verbal consent removes the signature, so the regulation must substitute something else to preserve those functions—usually an independent witness, an audit trail, or both.
Three separate mechanisms can produce verbal consent, and they are frequently confused. First, 21 CFR 50.24 permits an exception from informed consent for planned emergency research when subjects cannot consent and no legally authorized representative (LAR) is available. Second, 21 CFR 56.109(c) allows the institutional review board (IRB) to waive documentation of consent—meaning the consent conversation still happens, but the signature is not required. Third, 21 CFR 50.25 and the short-form consent process allow a verbal script plus a short written summary, witnessed and signed by a third party.
The key distinction is between waiving consent itself and waiving documentation of consent. Only the first removes the conversation; the second keeps the conversation but drops the signature. Verbal consent prior to participation most often refers to the second and third mechanisms, with 50.24 governing the most dramatic cases. Under 50.24, the IRB must find that the research involves a life-threatening condition, that available treatments are unproven or unsatisfactory, that consent is not feasible, and that the potential benefit justifies the risk.
Quantified context: how often and how tightly bounded
The exception pathway is deliberately rare. The FDA's 1996 final rule creating 21 CFR 50.24 was designed in response to trials like the earlier public-access defibrillation studies, where waiting for written consent would have made enrollment impossible. Since then, EFIC studies have remained a small fraction of federally regulated trials—typically concentrated in cardiac arrest, severe trauma, and acute stroke research.
The timeline below shows how a 50.24 study unfolds, which clarifies why verbal consent is time-bound rather than open-ended.
| Stage | Timing | What happens |
|---|---|---|
| Pre-study IRB review | Months before enrollment | IRB reviews community consultation plan and public disclosure |
| Community consultation | Before enrollment | Meetings with affected communities; results reported to IRB |
| Public disclosure | Before and after study | Notice in communities where research will occur |
| Enrollment without consent | Seconds to hours | Subject enrolled; verbal explanation when feasible |
| LAR contact attempt | Within the enrollment window | Attempt to reach family or representative |
| Consent to continue | As soon as feasible | Written consent obtained from subject or LAR |
| Post-study disclosure | After completion | Results and community updates published |
The critical threshold is the "therapeutic window"—the period during which intervention can still help. In cardiac arrest, that window is measured in minutes; in trauma, in the first hour. If written consent cannot be obtained within that window, the study either uses 50.24 or cannot proceed. That is the circumstance the regulation was built for.
Edge cases where verbal consent is permissible
Several edge cases produce verbal consent without a full 50.24 exception. The first is the short-form consent process under 21 CFR 50.27(b)(2), where a subject who cannot read or write, or who speaks a language without a translated form, receives a verbal explanation from an interpreter and a short written summary. The witness signs both the summary and the consent document.
The second is the IRB waiver of documentation under 56.109(c). This applies when the only record linking the subject to the research would be the consent document, and the principal risk would be breach of confidentiality—for example, certain survey or interview studies on sensitive behavior.
The third is the emergency-use provision under 21 CFR 56.104(c), which allows a one-time emergency use of an investigational article without IRB approval, though this is not a research enrollment pathway and does not produce generalizable data.
A counterintuitive professional caveat: many researchers assume that a verbal "yes" on the phone from a family member counts as consent. It does not. An LAR providing consent by phone still requires documentation—either a signed form or a witnessed verbal process—unless the IRB has separately waived documentation. The conversation alone is not the legal instrument.
Misconceptions that derail compliance
The most common misconception is that 50.24 lets researchers skip consent entirely. It does not. The regulation requires an attempt to contact the LAR within the enrollment window, and if the LAR is reached, that person's objection stops enrollment. Consent is deferred, not eliminated.
A second misconception is that verbal consent is always acceptable when a subject is "too sick" to sign. Sickness alone is not the trigger; the trigger is the combination of a life-threatening condition, infeasibility of consent, and IRB approval of the exception.
A third misconception is that community consultation is a formality. IRBs have rejected 50.24 applications when consultation was perfunctory, and the FDA has emphasized that consultation must meaningfully inform the community.
Red-flag warnings for research teams:
Enrolling a subject under 50.24 without a documented LAR contact attempt is a protocol violation. Using verbal consent for a non-emergency study because "it's faster" is not permitted; documentation waivers require specific IRB findings. Skipping public disclosure after study completion is a common audit finding. Assuming a phone call from a family member satisfies documentation requirements without a witness or signed form is a frequent error. Treating the short-form process as a substitute for translation without an interpreter present undermines validity.
Practical actions for researchers and IRBs
If you are designing a study that may require verbal consent, the sequence matters more than any single document. First, determine which mechanism applies: full 50.24 exception, IRB waiver of documentation, or short-form process. Each has different evidentiary requirements.
Second, for 50.24, draft the community consultation plan before the IRB submission and budget for at least one public meeting in the affected community. Third, build the LAR contact attempt into the protocol with a defined time window and a documented script. Fourth, prepare the post-enrollment consent-to-continue process, including who obtains it and when. Fifth, plan the public disclosure of results separately from the informed consent document.
For IRBs reviewing these applications, the threshold questions are: Is the condition genuinely life-threatening? Is consent genuinely infeasible? Does the risk-benefit ratio favor the exception? Has the community been meaningfully consulted? A "no" to any of these means the study cannot use 50.24.
The comparison table below clarifies how the pathways differ.
| Pathway | Consent conversation | Signature | IRB role | Typical use |
|---|---|---|---|---|
| Standard written consent | Yes | Yes | Reviews form | Most trials |
| Short-form consent | Yes, interpreted | Witness signature | Reviews process | Language or literacy barriers |
| Documentation waiver | Yes | No | Approves waiver findings | Minimal-risk, confidentiality-sensitive |
| 50.24 EFIC | Deferred; LAR attempt | Eventually, when feasible | Reviews consultation and disclosure | Cardiac arrest, trauma, stroke |
| Emergency use (56.104(c)) | Not research consent | None | Notified after | Single-patient emergency |
Limitations and what the regulation cannot do
The 50.24 pathway does not resolve the ethical tension it manages—it only structures it. Subjects enrolled without prior consent cannot be asked afterward whether they would have wanted to participate, because the enrollment already occurred. The regulation compensates with community consultation and public disclosure, but these are proxies, not substitutes for individual autonomy.
A further limitation is that 50.24 applies to FDA-regulated research; studies funded by other agencies or conducted outside FDA jurisdiction may follow different rules, such as the Common Rule's separate emergency provisions. Researchers working across funding sources must reconcile both frameworks, and where they diverge, the stricter requirement governs.
Finally, the regulation does not define "life-threatening" with a numerical threshold. That judgment rests with the IRB and the clinical context. A condition that is life-threatening in one setting may not be in another, which is why IRB review is case-specific rather than categorical. The best a research team can do is document the clinical rationale thoroughly and let the IRB's findings carry the weight.
This article is general educational information about FDA research regulations, not legal advice or a compliance opinion for any specific protocol. Consent requirements depend on your study design, funding source, and IRB determinations; consult a qualified research compliance professional or the FDA's Office of Clinical Policy before relying on any pathway described here.