Every standard proposal section in detail: purpose, expected structure, length, and worked language. Agency-specific variations are noted inline; see the per-agency guides for authoritative formatting rules.
Every proposal needs a concise overview that communicates the essential elements of the research to both technical reviewers and program officers.
Purpose: Provide a standalone summary that captures the research vision, significance, and approach
Length: - NSF: 1 page (Project Summary with separate Overview, Intellectual Merit, Broader Impacts) - NIH: 30 lines (Project Summary/Abstract) - DOE: Varies (typically 1 page) - DARPA: Varies (often 1-2 pages)
Essential Elements: - Clear statement of the problem or research question - Why this problem matters (significance, urgency, impact) - Novel approach or innovation - Expected outcomes and deliverables - Qualifications of the team - Broader impacts or translational pathway
Writing Strategy: - Open with a compelling hook that establishes importance - Use accessible language (avoid jargon in opening sentences) - State specific, measurable objectives - Convey enthusiasm and confidence - Ensure every sentence adds value (no filler) - End with transformative vision or impact statement
Common Mistakes to Avoid: - Being too technical or detailed (save for project description) - Failing to articulate "why now" or "why this team" - Vague objectives or outcomes - Neglecting broader impacts or significance - Generic statements that could apply to any proposal
The core technical narrative that presents the research plan in detail.
Structure Varies by Agency:
NSF Project Description (typically 15 pages): - Introduction and background - Research objectives and questions - Preliminary results (if applicable) - Research plan and methodology - Timeline and milestones - Broader impacts (integrated throughout or separate section) - Prior NSF support (if applicable)
NIH Research Strategy (12 pages for R01): - Significance (why the problem matters) - Innovation (what's novel and transformative) - Approach (detailed research plan) - Preliminary data - Research design and methods - Expected outcomes - Potential problems and alternative approaches
DOE Project Narrative (varies): - Background and significance - Technical approach and innovation - Qualifications and experience - Facilities and resources - Project management and timeline
DARPA Technical Volume (varies): - Technical challenge and innovation - Approach and methodology - Schedule and milestones - Deliverables and metrics - Team qualifications - Risk assessment and mitigation
For detailed agency-specific guidance, refer to:
- references/nsf_guidelines.md
- references/nih_guidelines.md
- references/doe_guidelines.md
- references/darpa_guidelines.md
- references/nstc_guidelines.md
Clear, testable goals that structure the research plan.
NIH Specific Aims Page (1 page): - Opening paragraph: Gap in knowledge and significance - Long-term goal and immediate objectives - Central hypothesis or research question - 2-4 specific aims with sub-aims - Expected outcomes and impact - Payoff paragraph: Why this matters
Structure for Each Aim: - Aim statement (1-2 sentences, starts with action verb) - Rationale (why this aim, preliminary data support) - Working hypothesis (testable prediction) - Approach summary (brief methods overview) - Expected outcomes and interpretation
Writing Strategy: - Make aims independent but complementary - Ensure each aim is achievable within timeline and budget - Provide enough detail to judge feasibility - Include contingency plans or alternative approaches - Use parallel structure across aims - Clearly state what will be learned from each aim
For detailed guidance, refer to references/specific_aims_guide.md.
Articulate the societal, educational, or translational value of the research.
NSF Broader Impacts (critical component, equal weight with Intellectual Merit):
NSF explicitly evaluates broader impacts. Address at least one of these areas: 1. Advancing discovery and understanding while promoting teaching, training, and learning - Integration of research and education - Training of students and postdocs - Curriculum development - Educational materials and resources
Mentoring programs
Enhancing infrastructure for research and education
Open-source software or methods
Broad dissemination to enhance scientific and technological understanding
Policy briefs or stakeholder engagement
Benefits to society
Writing Strategy for NSF Broader Impacts: - Be specific with concrete activities, not vague statements - Provide timeline and milestones for broader impacts activities - Explain how impacts will be measured and assessed - Connect to institutional resources and existing programs - Show commitment through preliminary efforts or partnerships - Integrate with research plan (not tacked on)
NIH Significance: - Addresses important problem or critical barrier to progress - Improves scientific knowledge, technical capability, or clinical practice - Potential to lead to better outcomes, interventions, or understanding - Rigor of prior research in the field - Alignment with NIH mission and institute priorities
For detailed guidance, refer to references/broader_impacts.md.
Articulate what is novel, creative, and paradigm-shifting about the research.
Innovation Elements to Highlight: - Conceptual Innovation: New frameworks, models, or theories - Methodological Innovation: Novel techniques, approaches, or technologies - Integrative Innovation: Combining disciplines or approaches in new ways - Translational Innovation: New pathways from discovery to application - Scale Innovation: Unprecedented scope or resolution
Writing Strategy: - Clearly state what is innovative (don't assume it's obvious) - Explain why current approaches are insufficient - Describe how your innovation overcomes limitations - Provide evidence that innovation is feasible (preliminary data, proof-of-concept) - Distinguish incremental from transformative advances - Balance innovation with feasibility (not too risky)
Common Mistakes: - Claiming novelty without demonstrating knowledge of prior work - Confusing "new to me" with "new to the field" - Over-promising without supporting evidence - Being too incremental (minor variation on existing work) - Being too speculative (no path to success)
Detailed description of how the research will be conducted.
Essential Components: - Overall research design and framework - Detailed methods for each aim/objective - Sample sizes, statistical power, and analysis plans - Timeline and sequence of activities - Data collection, management, and analysis - Quality control and validation approaches - Potential problems and alternative strategies - Rigor and reproducibility measures
Writing Strategy: - Provide enough detail for reproducibility and feasibility assessment - Use subheadings and figures to improve organization - Justify choice of methods and approaches - Address potential limitations proactively - Include preliminary data demonstrating feasibility - Show that you've thought through the research process - Balance detail with readability (use supplementary materials for extensive details)
For Experimental Research: - Describe experimental design (controls, replicates, blinding) - Specify materials, reagents, and equipment - Detail data collection protocols - Explain statistical analysis plans - Address rigor and reproducibility
For Computational Research: - Describe algorithms, models, and software - Specify datasets and validation approaches - Explain computational resources required - Address code availability and documentation - Describe benchmarking and performance metrics
For Clinical or Translational Research: - Describe study population and recruitment - Detail intervention or treatment protocols - Explain outcome measures and assessments - Address regulatory approvals (IRB, IND, IDE) - Describe clinical trial design and monitoring
Demonstrate that the research is achievable and the team is capable.
Purpose: - Prove that the proposed approach can work - Show that the team has necessary expertise - Demonstrate access to required resources - Reduce perceived risk for reviewers - Provide foundation for proposed work
What to Include: - Pilot studies or proof-of-concept results - Method development or optimization - Access to unique resources (samples, data, collaborators) - Relevant publications from your team - Preliminary models or simulations - Feasibility assessments or power calculations
NIH Requirements: - R01 applications typically require substantial preliminary data - R21 applications may have less stringent requirements - New investigators may have less preliminary data - Preliminary data should directly support proposed aims
NSF Approach: - Preliminary data less commonly required than NIH - May be important for high-risk or novel approaches - Can strengthen proposal for competitive programs
Writing Strategy: - Present most compelling data that supports your approach - Clearly connect preliminary data to proposed aims - Acknowledge limitations and how proposed work will address them - Use figures and data visualizations effectively - Avoid over-interpreting or overstating preliminary findings - Show trajectory of your research program
Demonstrate that the project is well-planned and achievable within the proposed timeframe.
Essential Elements: - Phased timeline with clear milestones - Logical sequence and dependencies - Realistic timeframes for each activity - Decision points and go/no-go criteria - Risk mitigation strategies - Resource allocation across time - Coordination plan for multi-institutional teams
Presentation Formats: - Gantt charts showing overlapping activities - Year-by-year breakdown of activities - Quarterly milestones and deliverables - Table of aims/tasks with timeline and personnel
Writing Strategy: - Be realistic about what can be accomplished - Build in time for unexpected delays or setbacks - Show that timeline aligns with budget and personnel - Demonstrate understanding of regulatory timelines (IRB, IACUC) - Include time for dissemination and broader impacts - Address how progress will be monitored and assessed
DARPA Emphasis: - Particularly important for DARPA proposals - Clear technical milestones with measurable metrics - Quarterly deliverables and reporting - Phase-based structure with exit criteria - Demonstration and transition planning
Demonstrate that the team has the expertise, experience, and resources to succeed.
Essential Elements: - PI qualifications and relevant expertise - Co-I and collaborator roles and contributions - Track record in the research area - Complementary expertise across team - Institutional support and resources - Prior collaboration history (if applicable) - Mentoring and training plan (for students/postdocs)
Writing Strategy: - Highlight most relevant publications and accomplishments - Clearly define roles and responsibilities - Show that team composition is necessary (not just convenient) - Demonstrate successful prior collaborations - Address how team will be managed and coordinated - Explain institutional commitment and support
Biosketches / CVs: - Follow agency-specific formats (NSF, NIH, DOE, DARPA differ) - Highlight most relevant publications and accomplishments - Include synergistic activities and collaborations - Show trajectory and productivity - Address any career gaps or interruptions
Letters of Collaboration: - Specific commitments and contributions - Demonstrates genuine partnership - Includes resource sharing or access agreements - Signed and on letterhead
Develop realistic budgets that align with the proposed work and agency guidelines.
Budget Categories (typical): - Personnel: Salary and fringe for PI, co-Is, postdocs, students, staff - Equipment: Items >$5,000 (varies by agency) - Travel: Conferences, collaborations, fieldwork - Materials and Supplies: Consumables, reagents, software - Other Direct Costs: Publication costs, participant incentives, consulting - Indirect Costs (F&A): Institutional overhead (rates vary) - Subawards: Costs for collaborating institutions
Agency-Specific Considerations:
NSF: - Full budget justification required - Cost sharing generally not required (but may strengthen proposal) - Up to 2 months summer salary for faculty - Graduate student support encouraged
NIH: - Modular budgets for ≤$250K direct costs per year (R01) - Detailed budgets for >$250K or complex awards - Salary cap: Executive Level II (updated annually; see NIH Salary Cap Summary) — e.g., $228,000 effective January 1, 2026 (NOT-OD-26-034); cap applies to direct and indirect salaries for awards issued on or after October 1, 2024 (NOT-OD-25-025) - Limited to 1 month (8.33% FTE) for most PIs
DOE: - Often requires cost sharing (especially ARPA-E) - Detailed budget with quarterly breakdown - Requires institutional commitment letters - National laboratory collaboration budgets separate
DARPA: - Detailed budgets by phase and task - Requires supporting cost data for large procurements - Often requires cost-plus or firm-fixed-price structures - Travel budget for program meetings
Budget Justification Writing: - Justify each line item in terms of the research plan - Explain effort percentages for personnel - Describe specific equipment and why necessary - Justify travel (conferences, collaborations) - Explain consultant roles and rates - Show how budget aligns with timeline