A proposal is an argument, not a description. This module builds the argument: a problem worth solving, a solution proportionate to it, and the evidence that you are the one to deliver it — written so specifically that a skeptical reviewer relaxes.
1. The problem-solution arc
Strong proposals move through a recognizable arc: here is a significant problem (bigger than my organization), here is a credible solution (sized to the problem), here is why now (the moment makes it urgent) and why us (we bring the missing capability). Each beat earns the right to the next one.
Arc: significant problem → credible solution → why now → why you.
Activities are mechanisms; the solution is the outcome they produce.
State the change you will cause, not the work you will do.
Own your real scope — honest pilots beat inflated promises.
2. Specificity beats jargon
Jargon is the sound of vagueness dressing up. Every buzzword a reviewer must decode costs you trust; every concrete number, named method, or dated milestone builds it. "Improve outcomes" is air. "Reduce 30-day readmissions from 18% to 12% across our two campuses" is a commitment a reviewer can score.
Concrete numbers, named methods, dated milestones — every paragraph.
If a competitor could paste your sentence into their proposal, rewrite it.
Small pilot data beats large adjectives.
Track record is evidence: years, people reached, budgets delivered.
3. Significance and broader impacts
Reviewers ask a question applicants forget: why does this matter beyond your organization? Significance is the ripple — the field, the region, the policy, the population that benefits even if it never touches your project directly.
Answer "why does this matter beyond us?" explicitly.
Learn the funder’s name for it — broader impacts, systems change, scale — and use it.
Promise shareable models and findings, not national transformation.
Proportionate significance triggers belief; grand claims trigger doubt.
4. The first page
The project summary is the most-read, least-drafted page in most proposals. It travels alone — into review panels, program officer briefings, sometimes the funder’s leadership deck. Write it as if it were the only thing they read, because sometimes it is.
The summary travels alone — make it self-sufficient.