A DOD white paper is a short two-to-five-page document that pitches a technical concept or research capability to a Department of Defense agency in response to a specific Broad Agency Announcement, and a usable example follows a predictable structure: executive summary, background, technical approach, team qualifications, and a rough-order-of-magnitude cost and schedule. The pages are few, the formatting rules are strict, and reviewers screen ruthlessly against the criteria in the BAA. Get the shape right and you buy yourself a fair reading. Get it wrong and the paper never reaches a subject-matter expert.
What a DOD White Paper Is and What It Does
The white paper is a screening tool. A program manager at DARPA, the Air Force Research Laboratory, the Office of Naval Research, or another service lab reads your concept, decides whether it aligns with the agency’s stated priorities, and either invites or discourages a full proposal. The Air Force Research Laboratory’s BAA guide defines the document as “a brief (usually 2-5 pages) summary of the proposed technical approach with an accompanying rough-order-of-magnitude (ROM) price.”1BROAD AGENCY ANNOUNCEMENT (BAA) GUIDE FOR INDUSTRY. BROAD AGENCY ANNOUNCEMENT (BAA) GUIDE FOR INDUSTRY
Every white paper answers a specific BAA. Requirements vary between agencies, so read the BAA before you write a sentence. It tells you what technical areas the agency cares about, what a submission must contain, how long it can be, and where to send it. Reviewers evaluate submissions solely against the criteria in that BAA. A technically strong concept that does not address the stated objectives will be screened out.
Your paper needs to connect the proposed work to a defined capability gap for the warfighter. Generic relevance claims fail. DARPA’s own guidance notes that saying an effort “is extremely relevant and will make a significant contribution” without explaining how and to what objective is not detailed enough to score well.2DARPA. DARPA Guide to Broad Agency Announcements and Research Announcements Name the specific problem, explain why current approaches fall short, and state the measurable improvement your concept would deliver.
The Sections a DOD White Paper Must Contain
BAAs differ in the details, but most white papers share the same skeleton. Treat what follows as a working template and adjust it to whatever your specific solicitation demands.
Executive Summary or Abstract
Open with a standalone synopsis that names the problem, the proposed approach, and the expected military benefit. Keep it to one page. A program manager may work through dozens of papers, and this section either earns the reader’s attention or loses it. Lead with results and conclusions rather than trying to compress every detail into the opening. If the evaluator finishes the summary and cannot say what you are proposing or why it matters, nothing later in the document will recover.
Introduction and Background
Set context. Summarize the current state of the technology or policy area and define the gap. Reference relevant prior research, known defense challenges, or work your team has already completed. The purpose is to prove you understand the problem space, not to file a literature review. Keep it short.
Technical Approach
This is the heart of the paper. Describe your methodology, the feasibility of the concept, and how you plan to execute. The AFRL guide directs this section to cover “the nature and scope of the research and the offeror’s proposed technical approach/solution.”1BROAD AGENCY ANNOUNCEMENT (BAA) GUIDE FOR INDUSTRY. BROAD AGENCY ANNOUNCEMENT (BAA) GUIDE FOR INDUSTRY Include preliminary data, modeling results, or a work plan if you have them. A subject-matter expert should be able to read this section and judge whether the concept is technically sound and the risks are manageable.
Many BAAs reference Technology Readiness Levels. TRL is a 1-to-9 scale the DOD uses to gauge how mature a technology is, with TRL 1 covering basic principles and TRL 9 covering a fully proven system. The DOD’s Technology Readiness Assessment Guidebook notes that peer-reviewed white papers can help substantiate a TRL 1 assessment.3Office of the Under Secretary of Defense for Research and Engineering. Technology Readiness Assessment Guidebook If the BAA names a target TRL range, show where your concept sits on the scale and what it would take to move it forward.
Team Qualifications
Most BAAs want a brief description of your organization’s relevant experience and the qualifications of the principal investigator and key personnel. Half a page to one page per person is usually enough. List projects, publications, and patents that show your team can do the work. Cite relevant past performance on DOD contracts if you have it.
Cost and Schedule Estimate
White papers do not require the detailed cost breakdowns of a full proposal, but a credible high-level number is essential. This usually takes the form of a Rough Order of Magnitude estimate. Army guidance defines a ROM as an estimate used “when limited specific information about a system, project or program is available and only high-level requirements have been identified.”4Department of the Army, Office of the Assistant Secretary Financial Management and Comptroller (ASA(FM&C)). Rough Order of Magnitude (ROM) Guidance ROMs are often built by analogy to historical programs and can be presented as a range when uncertainty is high. Pair the funding figure with an estimated project duration. Reviewers use this to gauge whether the concept fits within program budget, not to hold you to a final price.
Conclusion and Next Steps
Close with the expected outcomes and a clear path forward, which usually means asking for the opportunity to submit a full proposal. Leave the evaluator with a concrete picture of what the government gets for its investment and why your team is the right one to deliver it.
Formatting Rules That Get Papers Rejected
DOD white papers are formal and data-driven. Objective tone, precise language, no marketing copy. In a two-to-five-page document every sentence has to carry weight.
Page limits are enforced without discretion. Pages beyond the limit are removed and not reviewed. The AFRL guide warns that improperly formatted submissions get reformatted before the page count is evaluated: if the BAA calls for double spacing and you submit single-spaced text, each page counts as two toward the limit.1BROAD AGENCY ANNOUNCEMENT (BAA) GUIDE FOR INDUSTRY. BROAD AGENCY ANNOUNCEMENT (BAA) GUIDE FOR INDUSTRY Follow every formatting instruction in the BAA to the letter: font size, margins, spacing, file type. These are not suggestions.
Information marking matters even when nothing in your paper is classified. The rules break down by sensitivity:
- Controlled Unclassified Information: if your document contains CUI, place the acronym “CUI” at the top and bottom of each page. Do not add “UNCLASSIFIED” before “CUI.” Federal regulations require documents containing CUI to carry a designation indicator identifying the agency that controlled the information.5Department of Defense. Controlled Unclassified Information Markings6eCFR. 32 CFR 2002.20 – Marking
- Classified material: the overall classification level must appear as a banner at the top and bottom of every page. Portion marking is mandatory. Each paragraph, title, bullet, and figure carries its own classification tag such as (U) for Unclassified, (C) for Confidential, or (S) for Secret.5Department of Defense. Controlled Unclassified Information Markings
- Unclassified, non-CUI documents: portion markings are optional but recommended. If you use them, apply them consistently throughout.
When the BAA includes a marking template, use it. Marking mistakes create real compliance problems for the receiving office, not just cosmetic ones.
Protecting Proprietary Data Before You Submit
Submitting a white paper puts technical ideas in the government’s hands, and federal acquisition regulations offer meaningful protection, but only for data you mark correctly.
Under DFARS 252.227-7016, the government may reproduce your submission to evaluate it, but before any contract award it must use the information solely for evaluation. It cannot disclose your information to unauthorized persons, including potential evaluators who have not been specifically authorized to receive it. After a contract is awarded the government gains rights to use the information internally, but still cannot release it outside the government without your written permission.7Acquisition.GOV. 252.227-7016 Rights in Bid or Proposal Information
The catch matters. Technical data delivered without restrictive markings is presumed to have been delivered with unlimited rights and may be released without restriction. If you want data protected, place restrictive legends on it before submission. The solicitation provision at DFARS 252.227-7017 requires offerors to identify any technical data they assert should carry restrictions and submit that identification with their offer. If you miss something at submission, you have six months after delivery to request permission to add the appropriate legends, but the contracting officer is not required to approve the request.8Acquisition.GOV. Contractor Identification and Marking of Technical Data To Be Furnished With Restrictive Markings Mark the paper before you send it.
What Happens After You Submit
Send the white paper through the mechanism the BAA specifies. Many solicitations use online portals; others accept email to a designated program manager. Papers routed through the wrong channel may never reach a reviewer. Deadlines are absolute, and most portals lock at the cutoff. Portal outages, upload errors, and last-minute registration problems are common enough that experienced submitters aim to file at least a day early.
After submission, the program manager or a panel of subject-matter experts scores the paper against the BAA’s published criteria. Review timelines vary. Some BAAs specify a response window and others do not. For SBIR/STTR programs the DOD anticipates evaluations will be completed within roughly 180 calendar days of the solicitation close.9Air Force. AF 21.B Small Business Technology Transfer (STTR) Proposal Preparation Instructions Other BAAs may respond faster. Check yours, and resist contacting the contracting officer for a status update before any stated window has closed.
The response you receive will either encourage or discourage submission of a full proposal, or it may request a follow-up briefing. An invitation is a strong signal of interest, not a commitment to fund or award a contract. A discouragement still often carries feedback worth using on the next submission.
Why White Papers Get Rejected
Most rejections come from avoidable errors. The concept may be sound while the paper fails to do its job. The recurring problems:
- Misalignment with the BAA. The paper addresses a real problem, but not the one the BAA is asking about. Relevance to stated objectives is almost always the first filter.2DARPA. DARPA Guide to Broad Agency Announcements and Research Announcements
- Exceeding page limits. Extra pages are stripped. If your key technical argument sits on page six of a five-page paper, no one sees it.1BROAD AGENCY ANNOUNCEMENT (BAA) GUIDE FOR INDUSTRY. BROAD AGENCY ANNOUNCEMENT (BAA) GUIDE FOR INDUSTRY
- Vague technical approach. Promising an “innovative solution” without methodology, data, or feasibility gives the evaluator nothing to score.
- Missing cost or schedule information. Without even a rough estimate, a program manager cannot judge affordability.
- Unmarked proprietary data. Sending sensitive technical detail without restrictive legends risks losing control of it.
A white paper is a technical sales pitch with the substance to back it up. The program manager wants three things: that you understand the problem, that the approach is feasible, and that your team can execute. Every sentence should serve one of those goals. If it does not, cut it.