NSF
NSF EAGER Proposal Template: How to Structure Your 8-Page Project Description
GrantCopilot Team
July 1, 2026
7 min read
TL;DR
An effective EAGER Project Description typically follows this structure: Introduction and vision (1 to 1.5 pages), EAGER justification (0.5 to 1 page), technical approach with specific aims (3 to 4 pages), expected outcomes and significance (1 to 1.5 pages), and timeline with milestones (0.5 page). The entire proposal must make two arguments simultaneously: why the work is too risky for standard review, and why the potential payoff justifies the risk.
Writing an 8-page EAGER proposal is harder than writing a 15-page standard one. Every paragraph has to earn its place, and the structure has to do double duty: presenting your research plan while simultaneously arguing that the work is too risky or unconventional for standard review. This template breaks down the 8-page Project Description section by section, with guidance on what to cover, how much space to allocate, and what Program Officers look for in each part.
Before You Start: Required Components
An EAGER proposal includes more than just the Project Description. Before writing, make sure you have these elements planned:
- Concept Outline and Program Officer concurrence: You must submit a Concept Outline and receive written concurrence from the cognizant NSF Program Officer before submitting your proposal. Upload the concurrence in Research.gov.
- Title format: Your title must begin with "EAGER:" followed by your project title.
- Project Summary (1 page): Separate paragraphs for overview, Intellectual Merit, and Broader Impacts. This is outside the 8-page limit.
- References Cited: Not counted against the 8-page limit but should support your claims.
- Budget and Budget Justification: Must stay within the $400,000 total cost cap (including indirect costs).
- Data Management Plan: Required for all NSF proposals, including EAGER.
- Biographical Sketches and Current & Pending Support: Standard NSF requirements apply.
Section 1: Introduction and Vision (1 to 1.5 Pages)
This section has one job: make the Program Officer understand your idea and why it matters. Do not bury the core concept behind background information.
Start with the big idea. What are you proposing, and why is it potentially transformative? State this clearly in the first paragraph. The PO should grasp the concept by the end of page one.
Then provide just enough context to explain why this idea is worth exploring. Resist the urge to write a full literature review. With 8 pages total, a paragraph or two of targeted context is sufficient. Focus on what makes your approach different from existing work, not on cataloging everything that has been done before.
End this section with a clear statement of your research objectives. What will you investigate, build, test, or explore?
Section 2: Why EAGER? (0.5 to 1 Page)
This section is unique to EAGER proposals and is required, not optional. You must explicitly explain why your work is too risky or unconventional for standard NSF review.
Address these questions directly:
What makes this research high-risk? Be specific. Is the concept untested? Is the methodology unproven? Does it challenge established assumptions in your field? Name the actual risks rather than making vague claims about novelty.
Why would standard peer review not serve this work well? This is the key question. Standard review panels evaluate proposals against established frameworks. If your work is so novel that reviewers would lack the basis to evaluate it, or so unconventional that it would be dismissed without deeper exploration, say so and explain why.
Why is the potential payoff worth the risk? Even risky work needs to lead somewhere. Explain what the field gains if this exploration succeeds, and what you learn even if it does not work as expected.
Section 3: Technical Approach (3 to 4 Pages)
This is the largest section and where most of your proposal's substance lives. Even though EAGER funds exploratory work, the PO needs to see a concrete plan with clear methods and achievable milestones.
Structure this section around specific aims or research tasks. For each one, describe:
- What you will do: The specific research activity, experiment, analysis, or development task.
- How you will do it: Methods, tools, instruments, datasets, or computational approaches you will use. Be specific enough that the PO can evaluate feasibility.
- What constitutes success: Define what a positive result looks like, and equally important, what an informative negative result looks like. In exploratory work, learning that an approach does not work is still a valuable outcome.
- How this connects to the overall vision: Each task should clearly contribute to the research objectives stated in your introduction.
Section 3 (Continued): Handling Risk in the Technical Approach
Because EAGER proposals are inherently risky, your technical approach should acknowledge and address uncertainty. This is not a weakness. It demonstrates maturity and planning.
For each aim or task, briefly note the primary risk and your mitigation strategy. If the initial approach fails, what is your alternative? If a dataset turns out to be unusable, what is your backup plan?
Do not present a risk-free plan. That contradicts the premise of EAGER funding. Instead, show that you have thought through what could go wrong and have reasonable contingencies. The PO wants to see that you will make productive use of the funding regardless of which specific results materialize.
Keep this integrated with your technical description rather than adding a separate risk section. Weaving risk and mitigation into each aim reads more naturally and saves space.
Section 4: Expected Outcomes and Significance (1 to 1.5 Pages)
This section answers the question: if this works, what happens next?
Start with the direct outcomes of the proposed work. What data, tools, methods, or findings will you produce? Then connect those outcomes to the broader field:
- New research directions: How does successful exploration open pathways for larger, standard proposals?
- Field impact: Does this change how researchers think about a problem, or provide tools and methods others can use?
- Broader Impacts: Address NSF's Broader Impacts criterion. With limited space, focus on the most genuine and specific activities. One well-described outreach effort is more credible than a list of vague commitments.
- Connection to future standard proposals: Show the PO how successful EAGER results position you for competitive standard NSF proposals. This frames the EAGER funding as an investment with follow-on potential.
Section 5: Timeline and Milestones (0.5 Page)
Use the remaining space to lay out a realistic 24-month timeline. A simple table or bulleted list works well here. Include:
Key milestones and decision points at regular intervals (quarterly or every 6 months). For each milestone, note what results would indicate the concept is viable versus what would trigger a change in approach. This is especially important for EAGER because the exploratory nature means your plan should be adaptive.
Be realistic about pacing. If you need three months to set up equipment or recruit participants, show that. Program Officers are experienced researchers who can tell when a timeline is unrealistic.
Formatting and Style Tips
A few practical guidelines for the 8-page constraint:
- Use clear section headings. The PO reads your proposal directly, not through a panel summary. Make it easy to navigate.
- Skip the lengthy literature review. A few targeted citations are sufficient. Your References Cited section is not counted against the 8 pages.
- Write in direct, active language. With limited space, every sentence should convey information. Cut filler phrases like "It is widely acknowledged that" or "Research has shown."
- Use figures strategically. One or two well-designed figures can communicate your approach more efficiently than paragraphs of text. But do not overdo it since figures consume page space quickly.
- Check formatting requirements. Follow PAPPG guidelines for font size, margins, and spacing. Shrinking fonts or margins to squeeze in more text will get your proposal returned without review.
- Have someone outside your field read it. The PO may not be a specialist in your exact subfield. Your proposal should be clear to any scientist in the broader discipline.
The 8-page EAGER format forces you to be focused and direct. Every section should serve two purposes: describing your research plan and reinforcing why this work needs the EAGER mechanism. Lead with the vision, be honest about risks, present a concrete approach with clear milestones, and show the PO where successful exploration leads next. For more on EAGER proposals, see our complete NSF EAGER grant guide covering eligibility, Program Officer concurrence, and strategy. For budget planning, read our EAGER budget example with realistic allocations for the $400,000 cap.
Topics
NSF EAGER grant
EAGER proposal template
NSF proposal template
NSF grants
proposal structure
NSF proposal writing
8-page proposal
high-risk research
PAPPG