Skip to content

borghei/Claude-Skills / research/grants

grants

Verified

Grant writing and proposal architecture: funder fit, proposal structure, budget design, and success-factor scoring. Use when writing a grant proposal, evaluating funder fit, auditing a draft for competitiveness, or planning a budget.

references/proposal-structure-and-narrative.md

View on GitHub
# Proposal Structure & Narrative Reference

Reference for structuring and writing competitive grant proposals.

## 1. The NIH structure (R01 baseline)

| Section | Pages | Purpose |
|---------|-------|---------|
| Specific Aims | 1 | The whole proposal in one page |
| Research Strategy | 12 | Significance + Innovation + Approach |
| Bibliography | unlimited | References |
| Biosketches | 5/person | Investigator qualifications |
| Budget + Justification | varies | Money + reasoning |
| Resources / Environment | varies | Institutional support |
| Other docs | varies | Letters, plans, protocols |

**Specific Aims is the most important page in the proposal.** Reviewers
read it; many decide on it; some don't read further.

## 2. The NSF structure

| Section | Pages | Purpose |
|---------|-------|---------|
| Project Summary | 1 | Overview, Intellectual Merit, Broader Impacts |
| Project Description | 15 | The proposal |
| References Cited | unlimited | Bibliography |
| Biographical Sketches | 3/person | Qualifications |
| Budget + Justification | varies | Money |
| Current and Pending Support | varies | Other funding |
| Facilities | varies | Resources |
| Data Management Plan | 2 | Data sharing |
| Postdoc Mentoring Plan | 1 | If postdocs included |

NSF emphasizes **Intellectual Merit** (excellence of the work) and
**Broader Impacts** (societal benefit, education, diversity). Address both
explicitly.

## 3. Foundation proposal structure

Varies widely. Common sections:

- Cover letter
- Executive summary (1 page)
- Problem statement
- Project description
- Goals + measurable outcomes
- Timeline
- Team
- Budget
- Sustainability plan (post-grant)
- Logic model / theory of change
- Letters of support

Foundations like **measurable outcomes** and **sustainability**.

## 4. SBIR / STTR structure

| Section | Purpose |
|---------|---------|
| Cover sheet | Title, PI, budget |
| Project summary | Public-facing summary |
| Technical narrative | The work |
| Commercialization plan | How you'll commercialize (critical) |
| Key personnel | Team |
| Facilities | Resources |
| Budget + justification | Money |

SBIR/STTR proposals are 50% science + 50% commercialization. A great
science proposal with no commercial path will lose to a mediocre science
+ great commercial proposal.

## 5. The Specific Aims page (NIH-style; adapt for others)

### Structure
1. **Opening hook** (1-2 sentences): the importance of the problem
2. **What's known** (paragraph): current state
3. **What's missing** (paragraph): the gap
4. **What we propose** (paragraph): your hypothesis or central idea
5. **Aims** (3 bullets): each with a single verb + clear outcome
6. **Impact** (1-2 sentences): what changes when you succeed

### Writing rules
- Active voice
- Concrete, not vague
- Specific, not generic
- Reviewer should know the entire proposal from this page

### Example aim structure
> Aim 1: Determine whether [intervention] reduces [outcome] in [population].
> Hypothesis: [specific testable hypothesis].
> Approach: [one-sentence approach].
> Expected outcome: [specific result].

## 6. Significance — the "why care" section

Reviewers care about three significance questions:

- **Scientific significance:** does this advance understanding?
- **Clinical / practical significance:** does this affect lives?
- **Population significance:** how many people, how much impact?

Write the section to address all three. Vague significance kills proposals.

### Common mistakes
- "This is important" (says nothing)
- Citing irrelevant statistics
- Conflating prevalence with significance
- Significance ≠ novelty (innovation is separate)

## 7. Innovation — what's new

Reviewers care about: is the work genuinely novel, or incremental?

### Types of innovation
- **Conceptual** — new theory, framework, model
- **Methodological** — new technique, instrument, design
- **Applied** — new application of existing methods to a problem
- **Translational** — bridging basic and applied
- **Combinatorial** — novel combination of existing pieces

### Mistakes
- Claiming innovation where it's incremental
- Innovation untethered to significance
- "First to" claims that aren't true

## 8. Approach — the workplan

The largest, most-detailed section. Per aim:

- **Rationale** — why this approach for this aim
- **Methods** — specific protocols, tools, populations
- **Statistical analysis plan** — power, sample, models
- **Potential pitfalls** — what could go wrong
- **Alternative approaches** — if Plan A fails, here's Plan B

### Mistakes
- Hand-wavy methods
- No statistical plan
- No discussion of pitfalls / alternatives
- Methods don't match the question
- No timeline or milestones

## 9. Investigator + Environment

Reviewers want confidence the team can execute.

### Strengths to surface
- Prior work in the area
- Track record of completing funded projects
- Methodological expertise on the team
- Collaborative relationships
- Institutional support (cores, infrastructure)

### Common weaknesses
- New PI without prior grants (need mentorship plan)
- Team without one critical expertise (add co-I or consultant)
- No statistical expertise (add statistician)
- No clinical expertise (add clinician if clinical work)

## 10. Narrative discipline

### Lead with the most-important
- Reviewer attention drops as the proposal progresses
- Most-important content in first paragraph of each section

### Use signposting
- Section headers + subheaders
- "Aim 1" returns multiple times throughout for orientation
- Reviewer scans first; reads selected parts

### White space
- Dense walls of text get skimmed
- Reasonable paragraph breaks
- Bulleted lists where appropriate (avoid abuse)

### Visuals
- 1 figure per aim minimum
- Figures earn their space (data, schematic, logic)
- Avoid clipart and decoration

### Citations
- Cite specific work, not "many have studied this"
- Cite recent + foundational
- Cite competitors with respect

## 11. The commercialization plan (SBIR/STTR + corporate)

A real commercialization plan addresses:

- **Market opportunity** — TAM/SAM/SOM (real numbers, not "billions")
- **Customer + need** — specific buyer + their pain
- **Competitive landscape** — who else is doing this
- **Differentiation** — why you win
- **Business model** — how money flows
- **Go-to-market** — first customers, sales motion
- **Regulatory / IP / data strategy** — barriers and protections
- **Team** — commercial expertise (often a gap for academic teams)
- **Funding plan** — beyond this grant (Phase II, Series A, etc.)

Academic teams routinely under-invest in this section; it kills SBIR proposals.

## 12. Common narrative pitfalls

- **Jargon density.** Reviewer outside your subfield gives up.
- **Passive voice everywhere.** Hard to read; obscures agency.
- **Vague claims.** "Significant" without specificity.
- **Over-claiming.** "This will revolutionize…" — reviewers discount.
- **Hidden risks.** Reviewers find them anyway; trust erodes.
- **No alternatives.** Single-point-of-failure narrative.
- **Bad figures.** Reviewer can't decode them.
- **Generic letters of support.** Adds no signal.

## 13. Pre-submission review checklist

- One outside-area reviewer reads the proposal cold
- One inside-area reviewer (skeptic)
- Mock-grade against the funder's review criteria
- Compliance check (page limits, formatting, fonts)
- Letters of support collected
- Budget reviewed by grants office
- All co-Is have read the latest version
- Plain-English summary makes sense to a non-expert

## 14. Common pitfalls

- **Submitting at the deadline.** Last-minute errors abound.
- **Letters of support missing or generic.** Lost weight.
- **Aim creep — proposing too much.** Reviewer sees over-scope.
- **No discussion of pitfalls.** Naive.
- **No statistical plan.** Major weakness.
- **Specific Aims page weak.** Sets the negative tone.
- **Budget mismatched to scope.** Red flag.
- **Plain-English summary too technical.** Public summary is for the public.
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall