A DARPA Broad Agency Announcement (BAA) white paper is a short, early-stage submission that lets a DARPA program manager screen a proposed research idea before deciding whether to invite a full technical proposal. DARPA’s own solicitation documents refer to this stage inconsistently across BAAs — some call it a “white paper,” others an “abstract,” and both terms describe functionally the same document: a compressed statement of the technical idea, approach, and team, submitted well ahead of (and far shorter than) a full proposal. This page covers how the DARPA-specific version of this stage works. For the general funder-pre-proposal concept across agencies, see CASRAI’s What Is a Research White Paper? guide; for how DARPA fits into the broader Department of Defense research-funding landscape, see DoD Research Funding: DARPA, ONR, AFOSR, ARO, and How the Pieces Fit.
Why DARPA uses a white-paper/abstract stage
DARPA does not run one central BAA. Each of the agency’s technical offices issues its own program-specific and office-wide BAAs, each with its own program manager, technical scope, and evaluation criteria (see CASRAI’s Funding Opportunity Announcement (FOA) entry for how a BAA fits the broader solicitation-document family). Because DARPA programs are typically high-risk, high-payoff efforts organized around a specific technical vision the program manager holds, a full proposal — with a detailed management plan, complete cost proposal, resumes, and organizational documentation — is expensive for both the proposer to write and DARPA to review. The white paper/abstract stage exists to let a program manager quickly assess whether a proposed technical approach is a genuine fit for the program before either side invests in a full proposal. It functions as a screening filter, not a competition decided on complete merit review.
Typical structure and content
Requirements are set by the specific BAA, published on SAM.gov, and vary by program — always follow the exact instructions, page limits, and required sections stated in that BAA’s text rather than any general template. That said, a DARPA BAA white paper commonly covers:
- Administrative information — BAA number, proposer organization, principal investigator and point of contact, and any required cover-sheet fields.
- A statement of the technical problem or opportunity, framed against the specific program’s stated goals rather than the field in general.
- The proposed technical approach and its key innovation, at a level of detail sufficient to judge novelty and feasibility but well short of a full research plan.
- How the proposed work maps onto any technical areas, metrics, or phases the BAA defines (DARPA programs frequently structure work into phases with specific, quantified technical goals).
- A brief statement of team qualifications and relevant prior work.
- A rough estimate of cost and period of performance, at the level of a planning figure rather than a detailed cost proposal.
What a white paper deliberately omits, compared with a full proposal, is the detailed management plan, the line-item cost proposal, statements of work, and supporting administrative documentation (resumes, facilities descriptions, subcontractor agreements) that a full proposal requires. The white paper’s job is to let the program manager evaluate the idea, not to serve as an award-ready package.
Length conventions
DARPA does not apply one fixed page limit across every BAA. Reported conventions across recent DARPA BAAs put an abstract/white paper commonly in a range of roughly a few pages, but individual solicitations — including different DARPA SBIR/STTR components — have specified longer limits for that submission type. Because the binding requirement is always the specific BAA’s own instructions (and submissions are typically enforced programmatically through the submission portal, which will reject a non-conforming file), treat any general length figure as a rough orientation only and confirm the actual page limit, font-size requirement, and file format in the BAA text itself before drafting.
What happens after DARPA reviews the white paper
The program manager (or a review team under the program manager) reads submitted white papers against the program’s technical goals and typically returns one of a small set of outcomes: an invitation (or “encouragement”) to submit a full proposal, a discouragement from submitting a full proposal, or occasionally no further engagement if the BAA does not require individualized feedback. This feedback is usually framed as guidance rather than a binding gate — many DARPA BAAs technically permit a full proposal even after a discouraging response, though proposers who submit despite discouragement are competing without the signal that their concept matched the program’s current priorities. A white paper is a screening step, not a competition with a scored outcome; DARPA generally does not conduct the kind of formal, panel-scored review at this stage that it applies to full proposals.
How a white paper differs from the full technical proposal
| Dimension | White paper / abstract | Full technical proposal |
|---|---|---|
| Purpose | Screen the concept for programmatic fit | Provide a complete, evaluable, award-ready submission |
| Length | Short — a few pages in most BAAs, but solicitation-specific | Substantially longer, with detailed technical, management, and cost volumes |
| Cost detail | Rough estimate or range | Line-item cost proposal, typically with supporting basis of estimate |
| Team detail | Brief qualifications statement | Full resumes, facilities, and organizational/subcontractor documentation |
| Review | Program-manager screening for fit | Fuller technical evaluation against stated criteria, sometimes with external reviewers |
| Outcome | Encouraged / discouraged from proceeding | Selected for award negotiation, or not |
Practical guidance for writing a DARPA BAA white paper
- Read the specific BAA closely before drafting anything. DARPA BAAs vary in required sections, formatting, and submission mechanism (often through a specific DARPA portal referenced in the BAA, not a generic email or SAM.gov upload) — treat the BAA text, not any general guide including this one, as the binding requirement.
- Map your proposed work directly onto the program’s stated technical areas or phases. DARPA program managers typically design a BAA around a specific technical vision with defined goals or metrics; a white paper that doesn’t visibly address those goals is easy to screen out regardless of the underlying idea’s quality.
- Lead with the innovation, not the background. Given the short length, most of the space should go to what is technically new about the proposed approach and why it is credible, rather than a literature review or general problem framing the program manager already knows.
- State a plausible, if rough, cost and schedule. Even at the white-paper stage, an unrealistic cost estimate for the scope described undermines credibility with the program office.
- Do not treat a discouraging response as final if the BAA still technically permits submission — but weigh it seriously; it reflects the program manager’s read on programmatic fit, which a full proposal cannot argue around.
- Follow up appropriately. DARPA program managers vary in how much they engage before a decision; use the contact channel and Proposer Communication Plan the specific BAA specifies rather than assuming a norm from a different agency or a different DARPA office.
Frequently asked questions
Is a DARPA white paper the same thing as an abstract?
In practice, yes — DARPA BAAs use “white paper” and “abstract” to describe the same pre-full-proposal screening submission, with the specific term depending on the office and BAA. Confirm which term the specific solicitation uses and follow its instructions under that heading, since the two terms are not consistently distinguished across DARPA’s own documents.
Is the DARPA white paper stage mandatory?
It depends on the BAA. Many DARPA BAAs require or strongly recommend a white paper before a full proposal will be considered; the specific solicitation states whether it is mandatory, encouraged, or optional. Submitting a full proposal without first submitting a white paper, when one is required, generally means the submission will not be considered.
Can I submit a full proposal if my white paper was discouraged?
Often yes, technically — a discouraging response is typically guidance rather than a formal rejection that closes the BAA to you. But it reflects the program manager’s assessment that the proposed work is not a strong fit for the program’s current priorities, which is exactly the judgment a full proposal cannot easily overturn. Always read the specific BAA’s language on this rather than assuming.
How is this different from an SBIR/STTR white paper?
DARPA’s SBIR/STTR program topics sometimes use their own white-paper-and-pitch process with requirements set by the individual topic (and, in some components, distinct page limits from a standard research BAA). Small-business proposers should follow the specific SBIR/STTR solicitation on DoD SBIR/STTR’s site rather than generalizing from a standard research BAA’s conventions.
Where do DARPA BAAs get published?
Current DARPA BAAs are posted on SAM.gov and on DARPA’s own site, typically under the issuing technical office. Each BAA is the authoritative source for its own white-paper requirements, deadlines, and submission mechanism.
