BARDA EZ-BAA Fast-Turn Playbook: What We Sequence First

Published 2026-07-09. 7 min read. By Health Security Practice, BARDA, NIH & ASPR Programs.

How we help teams hit short EZ-BAA windows without burning the submission on registrations, scope creep, or a full-solicitation narrative.

Day 0–2: fit and registrations, not drafting

We stop teams from opening Word first. Confirm EZ-BAA topic fit, entity eligibility, and SAM.gov / registration blockers. If registrations are missing, we build a parallel track—drafting against the active instructions while ops catches up—so the window does not close on admin work.

Scope to one countermeasure story

EZ-BAA reviewers punish unfocused platform pitches. We narrow to one health-security use case with clear deployability, then map every paragraph to the published evaluation language. If the science needs a full BARDA track, we say so before you fund the package.

Compliance matrix before narrative polish

For fast turns we lock the matrix early: required sections, page limits, formatting, and submission portal steps. Technical polish comes after we know the package is submittable—not the other way around.

Final 48 hours: packaging and evaluator navigation

We run a packaging QA gate—file names, forms, signatures, and internal consistency—then a red-team read for evaluator navigation. The goal is a concise, scorable package, not the longest possible document.