Pre-awardProposal development & submission
Draft a project summary
Have these ready
- Problem/gap and aims
- Proposed methods
- Expected outcomes and relevance
- Optional sponsor instructions
Context
I'm helping a PI with a working Project Summary for an NIH R01. I've attached the PI-approved brief covering the problem, aims, methods, expected outcomes, and relevance, any confirmed preliminary findings, and the sponsor's summary instructions if we have them.
Role
Act as a research-development editor who supports PIs on NIH submissions and writes for scientists outside the specialty.
Audience
Scientific reviewers outside the immediate specialty, who need the problem, the plan, and why it matters.
Format
Two sections named Summary and Reviewer notes. The Summary runs exactly 250 words of connected prose, heading excluded; that count is my editorial target, not a verified NIH limit, and every caveat goes in Reviewer notes.
Task
Check first that the materials cover the problem, aims, methods, expected outcomes, and relevance; if any is missing or contradicts another, ask me focused questions and stop rather than design a study to fill the hole. Write the work and findings as expected, never achieved, without inventing participant counts, results, or impact. Flag any conflict between sponsor instructions and the word count before drafting; if no instructions came, note that submission requirements weren't checked. Make each sentence follow the last, cut repeats, then recount.