Skip to content
Assyro AI
Assyro AI
Module 1
1.19
Guide

How to prepare a pre-EUA package or EUA request

Organize the emergency-use question, available evidence and operational conditions while keeping pre-EUA discussion separate from authorization.

By Assyro
Published
Article updated FDA · eCTD v4.0 placement
On this page

What should a pre-EUA package or formal EUA request establish?

Identify the proposed emergency use and the actual declaration and product context, then organize available evidence around the decision criteria: serious or life-threatening condition, potential effectiveness, benefit-risk and adequate approved available alternatives. Include relevant manufacturing, supply, use information and proposed conditions, with explicit gaps. Pre-EUA engagement supports preparation; it is neither authorization nor proof that a formal request meets the criteria.

Before you begin

FDA emergency-use authorization preparation under the applicable declaration and product-specific framework. EUA differs from marketing approval and emergency IND/expanded access; this general guide does not establish eligibility for a particular emergency.

What you will prepare: A structured evidence-and-gap package or formal request tied to the actual emergency-use context and FDA interaction.

Resolve the authority, declaration and proposed use

Identify the disease/threat, product, proposed use, population, approval status and responsible FDA center. Locate the actual applicable EUA declaration and current product-specific submission instructions. A public-health emergency announcement alone should not be treated as proof of the required EUA declaration or product eligibility. Pre-EUA discussion can identify gaps; it is not authorization and does not imply FDA has accepted the evidence as sufficient.

Organize the evidence around the decision

Section III.D recommends an organized account of available safety/effectiveness evidence, risks and benefits, and available approved alternatives. Explain the product’s development and regulatory status, proposed administration/use, manufacturing and supply information, and relevant prior interactions. Identify rights of reference where needed. Separate observed findings, extrapolations and unknowns; do not omit negative evidence to make the request appear more mature.

Prepare the operational and information package

Identify proposed user/recipient information, distribution controls, storage/handling, monitoring, reporting and records appropriate to the actual product and proposed conditions. Use current center instructions and templates where applicable; this guide does not supply an authorized fact sheet. Have scientific, manufacturing and operational owners confirm feasibility. A requested condition or shelf-life proposal is not effective merely because it appears in the submission.

Fictional example: prior approval for a different use

A product is approved for one use, but the EUA proposal changes route and population. Do not rely on the approval label alone: explain the differences, assess the resulting evidence needs and obtain the required references. If no applicable declaration is established, continue independent evidence preparation and agency engagement, but do not describe a formal EUA as ready for issuance. An emergency IND may be a different question requiring its own assessment.

Build an evidence record for the exact proposed emergency use

Use the January 2017 guidance as the general framework, then establish current center instructions and the actual emergency-use context. A product's prior approval for another use or a general emergency announcement does not settle the new request.

Build an evidence record for the exact proposed emergency use
Decision areaEvidence to assembleUnresolved question
Authority and scopeApplicable declaration, product category and proposed useDoes the actual declaration support this emergency-use context?
Serious conditionDisease or condition and relevant threatIs the request tied to the condition contemplated by that context?
Potential effectivenessAvailable human, animal and other relevant evidence, with quality and limitationsHow directly does it support this product, route, population and use?
Benefit-riskKnown and potential benefits and risks, including unfavorable findingsWhat uncertainty remains and how does it affect the assessment?
AlternativesApproved options, adequacy for the proposed population and actual availabilityIs a claimed shortage or inadequacy supported rather than assumed?
Manufacturing and supplyActual product, controls, stability, capacity and distribution information as relevantCan the supplied product and proposed use be supported operationally?
Conditions and informationDraft user/recipient information, monitoring, reporting and recordsAre proposed conditions feasible, and which still await FDA determination?

For each evidence item, record the version, data cutoff, source or right of reference, finding, limitations and the question it supports. Avoid one undifferentiated evidence folder. A result for a different formulation, route or population needs an explicit relevance assessment; the presence of a study does not establish its applicability.

The guidance explains the “may be effective” criterion as a different evidentiary standard from product approval, assessed with the totality of available scientific evidence and the other criteria. It is not permission to supply only favorable evidence or to claim effectiveness is established. Identify negative findings, conflicting results and material unknowns alongside the supporting information.

Fictional alternatives exercise: an approved treatment exists, but the requester asserts it cannot meet the proposed emergency need. Separate the questions: what use is approved, whether it is adequate for the actual population and whether sufficient supply is available. Obtain the evidence for each claim. A product being approved does not automatically resolve adequacy and availability; an unsupported statement of shortage does not establish the opposite.

Pre-EUA discussions can occur before issuance of an EUA declaration. The guidance says their existence does not imply that a qualification has been met or all necessary information supplied. Use an evidence-gap register to focus the interaction: question, existing evidence, missing input, proposed work and decision needed. Do not label the product authorized because FDA has opened or reviewed a pre-EUA file.

If an EUA is issued, use the actual authorization, conditions and authorized information as the operative record, and assess subsequent changes through the applicable process. A proposed fact sheet, expiry or distribution condition is not effective merely because it appears in the request. Keep EUA distinct from approval and from IND/expanded-access mechanisms. Use the investigator-brochure guide or initial IND plan only when that separate pathway is the actual task.

Your preparation checklist

0/3 checked

Use this to track your review in this visit. Checks are not saved and do not establish regulatory compliance.

Frequently asked questions

Does FDA review of a pre-EUA package authorize use of the product?

No. The guidance says pre-EUA review does not establish FDA’s view that the product qualifies or that all necessary information has been supplied. Maintain the preliminary status and unresolved questions. Actual authorization and its conditions come from the applicable FDA action, not the existence of a pre-EUA file.

Does an approved alternative always rule out an EUA?

The guidance addresses whether an alternative is adequate, approved and available for the relevant use. It discusses circumstances such as insufficient supply or inadequacy for a special population. Evaluate those facts with evidence; neither the existence of approval nor an unsupported shortage assertion alone settles the criterion.

Is may be effective the same evidentiary standard as marketing approval?

No. The guidance describes a different standard for EUA consideration, assessed using the totality of available scientific evidence together with benefit-risk and the other criteria. That distinction does not justify selective reporting, unsupported claims or omission of material uncertainty about the exact proposed product and use.

Can pre-EUA discussions begin before an EUA declaration exists?

Yes. The guidance contemplates preliminary engagement before a declaration, including discussion of evidence and the appropriate submission vehicle. That preparation does not establish the conditions for issuance or authorize emergency use. Separately verify the actual declaration, current instructions and product-specific criteria for a formal authorization decision.

Sources and revisions

Requirements, source recommendations and editorial preparation advice have different roles. Review the scope and revision of the source you use.

Guidance

FDA: Emergency Use Authorization of Medical Products and Related Authorities ↗

January 2017 final guidance; section III on declarations, criteria, requests and conditions. Reopened September 22, 2026. Current declaration and product-specific instructions still need case-specific verification.

Technical specification · placement only

FDA eCTD v4.0 comprehensive hierarchy ↗

Version 2.2, February 2025. Section 1.19. A heading identifies placement, not mandatory applicability.

Talk with Assyro about your next document