Needs statements often become generic because teams rely on broad statistics instead of evidence that matches the actual population and geography. A structured design review helps the team connect the donor’s question to a project the organization can realistically deliver and measure.
Start with the design decision
Begin by test every major problem claim against current, relevant evidence. Define the choice the team is making and the evidence needed to support it. Good design decisions should be explainable to someone outside the drafting team.
Review the critical dimensions
Focus on problem scale, geography, target population, baseline data, lived experience, service gaps and source quality. Check whether the narrative, budget and workplan all reflect the same assumptions. A strong section in isolation can still create a weak proposal if the rest of the application tells a different story.
Use evidence rather than aspiration
Where possible, use baseline data, prior performance, documented staffing capacity, partner evidence and realistic unit costs. Where information is uncertain, mark the assumption and plan how it will be verified.
Test implementation consequences
Ask what the design requires after award. Every additional location, partner, participant group or activity creates cost, supervision and reporting consequences. If the proposal does not budget those consequences, the design may not be fundable in practice.
Useful review fields
- Design decision.
- Evidence supporting it.
- Key assumption.
- Implementation consequence.
- Budget consequence.
- Owner.
- Decision status.
- Change required.
Example
A proposal cites national youth unemployment to justify a county-level intervention. The review identifies the need for local labor data and recent participant evidence. This type of review makes the project more credible because the team is testing the operating model rather than only polishing proposal language.
Common mistakes
Avoid adding scope without adding capacity, setting targets without baseline logic, assuming partners will perform without verification, or finalizing a budget while the design is still changing. Record major decisions so later revisions remain controlled.
What to do next
Use the Grant Evidence Inventory to test the next design decision and keep the result with the application file.
For practical funding intelligence, subscribe to Africads Grant News. If the design is ready for drafting, GrantsWriterAI can help structure working proposal sections for human review.
Frequently asked questions
What evidence belongs in a grant needs statement?
Use current, relevant evidence showing the scale, severity, population, geography, and consequences of the problem your project is designed to address.
How local should the evidence be?
Use the most relevant level available. National data can provide context, but local or population-specific evidence is stronger when the proposal makes local claims.
Can qualitative evidence be used?
Yes, especially where it explains lived experience or implementation barriers, but it should be gathered and represented responsibly and not replace stronger quantitative evidence when the claim requires it.
How much evidence is enough?
Enough to establish the problem clearly without turning the needs statement into a literature review. Prioritize the evidence that directly supports the donor decision.
What should happen if the best evidence is old?
Explain the date and limitations, look for newer corroborating data, and avoid presenting an old estimate as though it were current.
Conclusion
A strong needs statement makes the case with evidence that is current enough, local enough, and specific enough to support the proposed intervention. Your NGO should remove weak statistics, qualify limitations, and connect the problem evidence directly to the people and places the project will serve.
