How to Write a DARPA BAA White Paper

Defense Grant Writers · January 6, 2026

DARPA Broad Agency Announcements represent some of the most technically demanding and competitively reviewed solicitations in the federal funding landscape. Unlike standard SBIR proposals, DARPA BAAs often require a two-step process: a white paper screening followed by a full proposal invitation. Understanding this structure is critical to your success.

The Two-Step Process

Most DARPA BAAs begin with a white paper submission. This document, typically 5–8 pages, serves as a screening tool. DARPA program managers review white papers to assess whether the proposed concept is responsive to the topic requirements and demonstrates sufficient technical understanding. Only firms recommended after white paper review are invited to submit full proposals.

This means your white paper must accomplish two things simultaneously: demonstrate deep technical credibility and clearly articulate why your approach is novel. You have limited space to do both, so every paragraph must earn its place.

Key Elements of a Strong White Paper

The white paper should open with a clear problem statement that demonstrates you understand the specific challenge DARPA is trying to solve - not a generic restatement of the topic description, but an informed articulation of why existing approaches fall short. This is where many proposals fail: they describe what they want to build rather than why current solutions are inadequate.

Your proposed approach should be specific enough to differentiate from competitors but not so detailed that you exhaust your page count. Focus on the key technical innovation - what makes your method fundamentally different from the state of the art. Support performance claims with data, references, or preliminary results where possible.

Team qualifications matter more in DARPA submissions than in most SBIR proposals. DARPA reviewers want evidence that your team has the specific technical expertise to execute the proposed work. Generic biosketches are insufficient - directly connect team members' prior work to the technical challenges in your proposal.

Common Mistakes to Avoid

The most frequent mistake is treating the white paper as a shortened version of a full proposal. It is not. The white paper is a persuasion document - its purpose is to convince the program manager that your concept warrants a full review. Do not include detailed work plans, budgets, or milestone charts at this stage.

Another common error is failing to address the specific evaluation criteria listed in the BAA. DARPA evaluates proposals against stated criteria, not general technical merit. If the BAA lists "technical feasibility" and "potential for military application" as criteria, your white paper must explicitly address both.

Finally, do not assume familiarity. Write as though the reviewer is technically sophisticated but has not read your previous publications. Define acronyms, explain your unique terminology, and make the logic of your approach self-contained within the document.

From White Paper to Full Proposal

If your white paper is selected, the full proposal phase requires substantially more detail: a complete technical volume (typically 15–20 pages), cost proposal using DARPA's template, commercialization strategy, and compliance documentation. The timeline between white paper notification and full proposal deadline is usually 30 days, so having a proposal-ready team is essential.