Grant Proposal Example: From Review Criteria to a Draft Spine
A worked grant-proposal spine that shows how need, aims, method, feasibility, and impact depend on one another.
Next step
Choose the next useful decision step first.
Use the guide or checklist that matches this page's intent before you ask for a manuscript-level diagnostic.
Quick answer: A useful grant proposal example shows how the problem, aims, evidence, method, feasibility, and impact depend on one another. It is not text to copy. Start from the current funding opportunity and review criteria, then use examples to diagnose structure, not to inherit outdated forms, page limits, or another project's scientific logic.
Evidence basis: We reviewed NIH's Write Your Application and Sample Applications and Documents, plus NSF's Preparing Your Proposal, on September 3, 2026. Agency and opportunity instructions control; this example does not predict a review outcome or funding. The worked example below is fictional Manusights editorial judgment, not an agency template.
Check whether reviewers can follow your proposal's decision logic.
Gather the controlling inputs
Input | Record before writing | Why it controls the draft |
|---|---|---|
Opportunity | Purpose, eligibility, deadlines, budget, and special instructions | A generic good proposal can still be nonresponsive |
Review criteria | The questions reviewers are asked to judge | Each major claim needs an evidence owner |
Project decision | What becomes possible if the work succeeds | Prevents aims from becoming unrelated activities |
Feasibility record | Preliminary evidence, team, environment, access, and alternatives | Ambition must be paired with an executable path |
Submission process | Institutional approvals, forms, attachments, and internal deadlines | Narrative quality cannot repair a late or noncompliant package |
Expected output: a one-page decision spine that connects need to aim, aim to test, test to interpretation, and interpretation to impact.
Worked fictional example
Opportunity fit: A program seeks practical methods to reduce delayed detection of antimicrobial resistance in regional hospitals.
Weak premise: Antimicrobial resistance is a major problem, and machine learning may help.
Decision-ready premise: Regional hospitals lack enough resistant-case volume to calibrate local early-warning models. The project will test whether a transportable model using routinely collected laboratory features improves time-to-alert without an unacceptable false-alert burden across three hospitals.
Proposal section | Example draft spine | Reviewer question answered |
|---|---|---|
Need | Current alerts arrive after confirmatory testing, limiting earlier isolation decisions | Is the problem consequential and specific? |
Aim 1 | Develop the model using prespecified routinely collected features | Is the approach technically coherent? |
Aim 2 | Externally validate discrimination, calibration, and alert burden at two hospitals | Will the evidence travel beyond one site? |
Aim 3 | Simulate workflow consequences under predefined thresholds | Does performance change a real decision? |
Risk plan | If transport fails, recalibrate intercepts and compare a simpler rule-based baseline | Are alternatives proportionate and informative? |
Impact | Produce a validated decision rule and implementation boundary, not a claim of immediate clinical benefit | Is the promised outcome supported? |
The example works because each aim changes the confidence of one eventual decision. It would weaken if Aim 3 introduced an unrelated survey simply to make the proposal look broader.
Convert criteria into an evidence ledger
For every review criterion, list the sentence-level claim, supporting evidence, location, and residual risk. A criterion should not be answered only by adjectives such as innovative, rigorous, experienced, or transformative.
Significance needs a defined unmet decision, affected population, and consequence. Approach needs a design capable of distinguishing the proposed explanation from plausible alternatives. Investigators and environment need project-relevant capability and access, not biography volume. Impact needs a credible result-to-use bridge.
Learn from public samples safely
Read a sample beside its summary statement when both are available. Mark where reviewers found the question important, the approach credible, or a weakness unresolved. Then close the sample and rebuild the structure for your opportunity.
Public samples may use older forms and requirements. NIH explicitly directs applicants to current instructions, and NSF notes that solicitations can modify general guidance. Never copy human-subjects language, data plans, facilities descriptions, letters, or budgets without checking whether they truthfully describe your project and current rules.
Readiness check
Run the scan while the topic is in front of you.
See score, top issues, and journal-fit signals before you submit.
Diagnose common failure states
Symptom | Diagnosis | Recovery |
|---|---|---|
Aims read as separate projects | No shared decision or dependency | Write the final project decision, then keep only aims needed to support it |
Innovation is a list of technologies | Novelty is disconnected from the problem | Explain which limitation the new approach removes and how the test will show that |
Feasibility is asserted | Access, preliminary evidence, or alternatives are missing | Add the minimum proof and a bounded fallback path |
Impact promises adoption or health benefit | The proposed work stops earlier in the evidence chain | State the actual deliverable and next validation step |
Example language dominates the draft | The team copied a surface structure | Rebuild from the opportunity's criteria and this project's evidence ledger |
Completion checklist
- The current opportunity and agency instructions are saved with access dates.
- Every aim supports one central project decision.
- Each review criterion maps to inspectable evidence.
- Methods, analysis, sample, access, and alternatives are feasible.
- Risks are paired with informative recovery paths.
- Human-subjects, animal, data, budget, and institutional requirements are reconciled where applicable.
- Public samples informed structure but no borrowed claim misrepresents the project.
- The internal submission deadline and responsible owners are confirmed.
Use this example if
Use it to inspect decision structure after reading the live opportunity. Think twice if you are tempted to copy sample language, inherit an old requirement, or force aims that do not share one project decision.
Run a final proposal-readiness review.
Sources accessed September 3, 2026.
- Write Your Application, NIH Grants & Funding.
- Sample Applications and Documents, NIH Grants & Funding.
- Preparing Your Proposal, U.S. National Science Foundation.
Frequently asked questions
No. Use public samples to study decision structure, then follow the current opportunity instructions and write evidence specific to your project.
It should show a consequential problem, a feasible and discriminating plan, a capable team and environment, and an outcome that advances the funder's stated goals.
The current funding opportunity and agency application guidance control. Program-specific instructions can modify general guidance.
No. Examples demonstrate possible approaches under earlier competitions; they do not predict review or replace current requirements.
Before you upload
Choose the next useful decision step first.
Move from this article into the next decision-support step. The scan works best once the journal and submission plan are clearer.
Use the scan once the manuscript and target journal are concrete enough to evaluate.
Private API processing. Your manuscript is not used to train models.
Put the guidance to work
Choose the practical next step for your research.
Start with the question in front of you, or use the guided learning path when you want a clearer view of the full publishing process.