Your organization should not treat the risk section as a place to hide weaknesses. Institutional donors generally expect credible applicants to understand what could disrupt delivery and to show practical mitigation that matches the scale of the risk. A strong risk narrative demonstrates that your NGO or CBO can distinguish between manageable uncertainty and threats that require executive attention.
Write about material risks, not generic ones
Risks should arise from the actual project design, geography, partner model, procurement plan, safeguarding environment, cash-flow structure, or evidence base. Generic entries such as “staff turnover” or “political instability” add little unless the proposal explains why they matter to this specific project and what your organization will do about them.
Use a risk narrative table
| Risk | Trigger or signal | Mitigation | Residual risk |
|---|---|---|---|
| Supplier delay | Lead time exceeds plan | Early procurement and backup suppliers | Possible activity delay remains |
| Partner underperformance | Late reports or weak evidence | Phased disbursement and closer monitoring | Lead may need to reallocate work |
| Safeguarding incident | Complaint or disclosure | Reporting pathway, trained focal points, escalation | High-impact risk cannot be eliminated |
| Currency movement | Rate moves beyond planning range | Forecast review and donor-approved flexibility | Purchasing power may still change |
Explain likelihood, impact, and ownership
Your organization should show why each material risk matters, which part of the project it could affect, and who is responsible for monitoring it. A low-likelihood but high-impact safeguarding risk may deserve more management attention than a more frequent but minor operational issue. Ownership should sit with the role that can actually act on the risk.
Detailed example: procurement delay with real mitigation
Imagine your NGO is applying for a USD 500,000 health grant that depends on imported diagnostic equipment being available by month three. The supplier lead time is estimated at 10–12 weeks, customs delays are possible, and community screening cannot begin without the equipment. Writing “supplier delays may occur and will be monitored” would not reassure a donor.
A stronger narrative would explain that procurement begins immediately after award, two qualified suppliers have been identified, technical specifications are pre-cleared, the workplan includes a four-week buffer, and temporary referral arrangements exist if equipment arrival is delayed. The proposal still acknowledges residual risk because not every delay is controllable, but it shows the organization has thought through the operational response.
Do not pretend mitigation removes all uncertainty
Good mitigation reduces probability, impact, or recovery time; it does not always eliminate the risk. Your executive team should be comfortable describing what remains after mitigation and when the issue would be escalated to the donor, board, or senior management. Overconfident language can look less credible than a realistic residual-risk statement.
Risk narrative checklist
- Risks are specific to the actual project.
- Likelihood and impact are proportionate to the context.
- Mitigation describes real actions rather than vague monitoring.
- One role owns each material risk.
- Escalation triggers are defined.
- Residual risk is acknowledged.
- Budget and workplan include the cost or time required by mitigation.
- The proposal risk section can transfer directly into implementation monitoring.
What institutional donors and boards are likely to expect
Institutional donors usually expect the organization to recognize material delivery and compliance risks before award. Boards should pay particular attention to risks that could create reputational, safeguarding, legal, or unrestricted financial exposure. A realistic risk narrative therefore supports both proposal credibility and governance.
What to do next
If the project is funded, transfer the final proposal risks into the live Grant Risk Register so commitments made during application are not forgotten during implementation. If your team needs drafting support, GrantsWriterAI can help structure the working narrative after the risks and evidence are defined.
Frequently asked questions
What risks should an NGO include in a grant proposal?
Include risks that are specific and material to the project, such as procurement delays, partner underperformance, safeguarding, data quality, currency movement, staffing gaps, political disruption, or regulatory dependencies. Avoid generic risks with no clear connection to the design.
Will mentioning risks make the proposal look weak?
Not if the risks are realistic and paired with credible mitigation. Institutional donors generally expect applicants to understand what could disrupt delivery rather than pretend uncertainty does not exist.
What is residual risk?
Residual risk is what remains after mitigation is applied. Your organization should be comfortable acknowledging that some uncertainty cannot be eliminated completely, especially for safeguarding, market, political, or partner risks.
How detailed should mitigation be?
Specific enough to show what your organization would actually do, who would act, and when escalation would occur. Phrases such as ‘we will monitor the risk’ are too weak unless they explain the response.
Should proposal risks be used after award?
Yes. Transfer material proposal risks into the implementation risk register so the commitments made during application are not forgotten once delivery starts.
Conclusion
A strong risk narrative does not promise a risk-free project. It shows that your organization understands the threats that matter, has practical mitigation, knows when to escalate, and can explain what exposure remains after those controls are in place.
Put this guide into practice
Free resource: The Funding Checklist. Use this free guide to apply the article’s advice to your next funding decision or application.
Optional paid resource: Nonprofit Grant Proposal Templates. Proposal, concept note, budget, logframe, M&E and donor-document starting points. Review the product details and current price before purchasing.
