Guide clusterGrants & Proposals
Diagram a grant proposal by mapping one aim to one outcome. Write a single gap statement, give each aim its own box with the deliverable it produces, connect the aims so earlier results feed later ones, add feasibility evidence that makes each step credible, and finish with the outcome a program officer can report. Keep the figure to one direction.
What this page covers
- One aim, one box, one deliverableThe single most useful rule for proposal diagrams is that each aim should produce exactly one thing that can be listed in a final…
- Chaining aims rather than listing themMany proposals present aims as a parallel list…
- Showing feasibility without crowding the figureFeasibility evidence is what separates a diagram that reads as ambitious from one that reads as credible.
- Matching the diagram to the funder's review criteriaFunders publish their review criteria, and the diagram is the fastest place to show that you have read them.
One aim, one box, one deliverable
The single most useful rule for proposal diagrams is that each aim should produce exactly one thing that can be listed in a final report. If an aim produces two deliverables, it is usually two aims. If it produces none, it is an activity, and a reviewer will treat it as a description of effort rather than a plan for results.
Write the deliverable as a noun phrase: a validated assay, a calibrated model, a curated dataset with documented provenance, a tested prototype. Then place it directly beneath the aim that produces it, so the reader can move vertically from intention to output without hunting.
If you cannot name the deliverable, the aim is not yet a plan.
Chaining aims rather than listing them
Many proposals present aims as a parallel list, which tells the reviewer that the parts are independent and could be funded separately. If your project genuinely depends on sequence, the diagram should show it: the output of aim one becomes the input of aim two, and so on. A chained diagram also justifies the budget, because it explains why the second piece of work cannot start before the first finishes.
Chaining carries one risk. A purely linear chain of dependent aims looks fragile, because any failure ends the project. When the sequence is real, pair it with a stated fallback at the riskiest link, so the reader sees that you have planned for the branch rather than ignored it.
Write the gap as one sentence naming what is not yet known and why it matters for practice or policy.
Draft each aim as a verb plus an object, then rewrite it so it names the deliverable it produces.
Draw links only where a real dependency exists, and label each link with what passes along it.
Mark the aim with the highest technical risk and write a short fallback beside it.
Close with the outcome, expressed in the terms the funder uses in its own program description.
Remove every box that serves presentation rather than the argument.
Showing feasibility without crowding the figure
Feasibility evidence is what separates a diagram that reads as ambitious from one that reads as credible. Preliminary work, pilot data, access agreements, established collaborations and validated protocols all belong in the figure, but they belong in small supporting elements rather than as full boxes competing with the aims. A short annotation under the relevant aim is usually enough.
Distribute feasibility signals rather than grouping them. A block of preliminary work placed at the top of the diagram reads as a claim that the team is generally capable, which reviewers weigh lightly. The same evidence attached to the specific aim it de-risks is weighed much more heavily, because it answers the question the reviewer is asking at that moment.
Matching the diagram to the funder's review criteria
Funders publish their review criteria, and the diagram is the fastest place to show that you have read them. If the criteria mention training and mentorship, a small element showing the roles and development plan belongs in the figure. If they emphasize broader impacts or translation, the final box should use the funder's own vocabulary rather than a synonym you prefer.
This is not about keyword matching. It is about removing the work a reviewer would otherwise have to do. When the diagram's labels echo the criteria, the reviewer can award credit without translating between your framing and theirs, and translation is exactly where reviewers run out of patience.
| Funder emphasis | What the diagram should make visible |
|---|---|
| Intellectual merit | The gap statement and the reasoning that links aims in sequence |
| Feasibility | Preliminary results and access placed beside the aim they de-risk |
| Training and personnel | Roles, skills brought, and the capability each aim develops |
| Translation and impact | The user, the form of the result, and the decision it informs |
| Data and sharing | Where outputs will be deposited and how reuse is enabled |
Formatting rules that survive a review panel
Panels work through many proposals in a short window, often on screens of varying quality and sometimes in printed packets. Use a font size that remains readable at half size, rely on position and labels rather than color to convey grouping, and avoid thin gray lines that disappear when printed. Where the funder imposes a page limit, remember that a diagram which saves narrative words must still earn its space.
One more constraint is worth respecting: the figure should be understandable to a reviewer from an adjacent field, because panels are rarely composed only of specialists in your subarea. That is a design requirement, not a simplification. It usually means replacing acronyms with short plain-language labels and letting the caption carry the technical detail.
- Keep the caption self-contained and free of acronyms that appear only in the figure.
- State the reading direction explicitly in the caption if the flow is unusual.
- Confirm the figure is legible after the PDF is compressed by the submission system.
- Check that the diagram and the aims text use identical numbering and wording.
Worked example
Worked example: a coastal erosion monitoring proposal
A team seeks support to build an early-warning capability for shoreline change at two regional sites. Their original figure listed four aims side by side: instrument deployment, data processing, model development and stakeholder engagement. The panel feedback on a previous submission had been that the pieces seemed disconnected.
The redesigned figure chains the aims. Aim one deploys a sensor network and produces a quality-controlled time series at a fixed cadence. Aim two uses that series to calibrate a shoreline change model, with the calibration report as its deliverable. Aim three validates the model against an independent survey campaign and produces a documented error profile. Aim four converts the validated model into a monthly advisory that a coastal manager can act on, with the advisory format as the deliverable.
Feasibility evidence is distributed rather than pooled. A pilot deployment at one site sits beside aim one, an access agreement with the regional authority sits beside aim three, and a named manager who has agreed to trial the advisory sits beside aim four. The riskiest link, calibration with sparse observations, carries a one-line fallback stating that the team will fall back to a coarser spatial resolution and report the loss of precision.
The final figure closes with the outcome the program description names: a transferable monitoring capability that other regions can adopt. Reviewers can trace the argument down a single column, and every arrow is labeled with the artifact that travels along it.
Common mistakes
Frequently asked questions
How many aims should appear in a proposal diagram?
Three or four is typical and usually sufficient. More aims spread the same budget thinner and make the dependency chain harder to see. If you have five genuinely distinct pieces of work, consider whether two of them are steps inside a single aim instead.
Should the diagram appear in the project description or the budget justification?
Put it in the project description where the aims are explained, and refer back to it in the budget justification when linking a cost to a step. Submitting the same figure twice wastes space that the narrative could use.
Is it acceptable to use an AI tool to help draft the proposal diagram?
It is reasonable to use an assistant to organize content you have already written and to suggest a layout. It cannot judge whether your aims are fundable or whether the budget matches the plan, and it should never be used to generate claims, preliminary results, or citations. The intellectual content stays yours.
What if the funder does not allow figures in the narrative?
Some programs restrict figures or count them against the page limit. In that case, build the diagram for your own use first, then convert it into a short ordered list of aims and deliverables. The exercise of drawing it still improves the narrative.
Sources and further reading
- Grants and funding process, including application structureU.S. National Institutes of Health
- Grant application guidance and reporting expectationsBill & Melinda Gates Foundation
- Funding opportunities and proposal preparationU.S. National Science Foundation
- Recommendations for the Conduct, Reporting, Editing and Publication of Scholarly WorkInternational Committee of Medical Journal Editors
- ORCID - persistent identifiers for researchersORCID
These are the organisations whose published guidance the recommendations on this page follow. Listing them does not imply that they endorse Pathform AI, and this page is not affiliated with them.