scientific-skills/research-grants/references/darpa_guidelines.md
Mission: Make pivotal investments in breakthrough technologies for national security
Tagline: "Creating breakthrough technologies and capabilities for national security"
Annual Budget: ~$4 billion
Website: https://www.darpa.mil
Key Characteristics:
The DARPA Difference:
Focus: Biology as technology, human-machine interfaces, synthetic biology
Example Programs:
Focus: High-risk, high-payoff research in physical and mathematical sciences
Example Programs:
Focus: Information advantage through computing, communications, and cyber
Example Programs:
Focus: Microelectronics, photonics, and heterogeneous microsystems
Example Programs:
Focus: Technologies for space, air, maritime, and ground systems
Example Programs:
Focus: Near-term technologies for ground, maritime, and expeditionary forces
Example Programs:
Program Managers (PMs):
PM Lifecycle:
Implication for Proposers:
Three Questions Every DARPA Program Must Answer:
What are you trying to do?
How is it done today, and what are the limits of current practice?
What is new in your approach, and why do you think it will be successful?
Additional Considerations:
DARPA Seeks:
Most Common Mechanism: Open solicitations for specific program areas
Characteristics:
Types of BAAs:
Program BAAs: For specific named programs
Office-Wide BAAs: General solicitations by technical office
For Small Businesses:
Proposers Day: Pre-solicitation event
Special Notices: Requests for Information (RFIs), teaming opportunities
Note: Format varies by BAA. Always follow the specific BAA instructions precisely.
Section 1: Executive Summary (1-2 pages)
Section 2: Goals and Impact (2-3 pages)
Section 3: Technical Approach and Innovation (10-20 pages)
Organized by Phase (typical):
Phase 1 (Feasibility): 12-18 months
Phase 2 (Development): 18-24 months
Phase 3 (Demonstration): 12-18 months (if applicable)
Section 4: Capabilities and Resources (2-3 pages)
Section 5: Statement of Work (SOW) (3-5 pages)
Section 6: Schedule and Milestones (1-2 pages)
Section 7: Technology Transition Plan (2-3 pages)
Detailed Budget:
Cost Narrative:
Supporting Documentation:
Attachments:
Primary Criteria (usually equal weight):
Overall Scientific and Technical Merit
Potential Contribution and Relevance to DARPA Mission
Cost Realism and Reasonableness
Capabilities and Related Experience
Technology Transition
DARPA uses this set of questions (created by former DARPA director George Heilmeier):
Your proposal should clearly answer all eight questions.
1. Contact the Program Manager
2. Form a Strong Team
3. Understand the Vision
4. Identify Transition Path
Lead with Impact:
Be Concrete and Specific:
Demonstrate Innovation:
Address Risk Head-On:
Show You Can Execute:
Emphasize Transition:
Procurement Contracts: Most common for industry
Grants and Cooperative Agreements: For universities and nonprofits
Other Transaction Agreements (OTAs): Flexible arrangements
Kickoff Meeting: Program launch with all performers
Quarterly Reviews: Progress reviews (virtual or in-person)
Annual or Phase Reviews: Major assessment points
Site Visits: PM and team visit performer sites
Technical Interchange Meetings (TIMs): Deep dives on technical topics
Monthly Reports: Brief progress updates
Quarterly Reports: Detailed technical reporting
Final Report: Comprehensive program summary
Technical Data and Prototypes: Specified in contract
Artificial Intelligence and Autonomy:
Quantum Technologies:
Biotechnology:
Microelectronics and Computing:
Hypersonics and Advanced Materials:
Space Technologies:
Network Technologies:
✅ Contact PM early - Before writing, discuss your idea ✅ Attend Proposers Day - Essential for understanding program ✅ Form strong team - Complementary expertise, clear roles ✅ Be bold and ambitious - 10x goals, not 10% improvements ✅ Quantify everything - Specific metrics and targets ✅ Address transition - Clear path to operational use ✅ Identify risks explicitly - And explain mitigation ✅ Show preliminary results - Proof of concept or feasibility ✅ Follow BAA exactly - Format, page limits, content requirements ✅ Emphasize innovation - What's revolutionary about your approach?
❌ Don't propose incremental research - DARPA wants breakthroughs ❌ Don't ignore national security relevance - "Who cares?" matters ❌ Don't be vague - Specific objectives, metrics, deliverables ❌ Don't hide risk - DARPA expects and values high-risk research ❌ Don't forget transition - Technology must have path to use ❌ Don't propose basic research - That's for ONR, AFOSR, ARO ❌ Don't exceed page limits - Automatic rejection ❌ Don't ignore PM feedback - They're setting the direction ❌ Don't propose alone if team needed - DARPA values strong teams ❌ Don't submit without PM contact - Critical to gauge fit
Key Takeaway: DARPA seeks revolutionary breakthroughs that advance national security, not incremental research. Successful proposals articulate clear, measurable objectives (answering "what if true?"), demonstrate innovative approaches to "DARPA-hard" problems, include strong multidisciplinary teams, proactively address technical risks, and provide realistic paths to transition. Early engagement with the Program Manager is essential—DARPA is a PM-driven agency where understanding the vision is critical to success.