A risk-and-mitigation section turns potential weaknesses into strengths. Learn how to write one that funders trust without undermining your proposal.

A counterintuitive truth about grant writing: acknowledging risk honestly often makes a proposal stronger, not weaker.

Reviewers know that real projects face real challenges. Hiring is slow. Recruitment underperforms. Partners change leadership. Funding shifts. A proposal that pretends none of this can happen reads as either naive or evasive. One that names likely risks and explains how you’ll respond reads as the work of an organization that’s run programs before.

This guide covers how to write a risk-and-mitigation section that earns confidence.

TL;DR: Quick Answers

What is a risk and mitigation section? A short proposal section that identifies likely risks to the project and describes how you’ll respond.
Who asks for it? Some federal funders explicitly; many foundations welcome a brief acknowledgement woven into the methods or sustainability sections.
What does it need to include? A handful of credible risks, with specific mitigation strategies and contingency plans.
What’s the most common mistake? Either pretending there’s no risk, or listing risks without credible responses.

Why Risk Sections Help Proposals

Three reasons honest risk handling strengthens proposals:

It signals maturity. A team that names challenges has thought past the application.
It signals capacity. Mitigation strategies show systems and planning.
It preempts reviewer concerns. Reviewers will think of risks regardless; addressing them first shapes the conversation.

For research and demonstration funding (especially NSF/NIH, ED, DOJ, and many federal competitions), a risk section is sometimes required outright. For foundation proposals, weave it in lightly, a few sentences in the methods or sustainability section.

What to Identify

Credible risks for most projects cluster into a few categories:

Personnel risks. Hiring delays, staff turnover, key personnel transitions.

Recruitment and engagement risks. Lower-than-expected enrollment, attrition, no-shows.

Partnership risks. A partner organization changes priorities, loses key staff, or pulls out.

Funding risks. Match dollars don’t materialize on schedule; cash flow tightens; a co-funder pulls back.

External risks. Policy changes, regulatory shifts, public-health disruptions, economic conditions.

Operational risks. Technology failure, data system issues, supply-chain delays.

Program-fit risks. The model doesn’t work as expected for the population; adaptations needed.

Pick the most likely and most consequential risks, not every conceivable one. A risk section listing 15 risks reads as overcautious; one naming 3–5 with credible responses reads as thoughtful.

How to Write a Mitigation Strategy

For each risk:

Name the risk clearly. “If recruitment falls short of the 200-participant target…”
Quantify if possible. “…particularly if enrollment is more than 25% below plan…”
Describe the mitigation. “…we will expand referral partnerships and adjust outreach to address the gap…”
Name the trigger. “…with weekly tracking and quarterly reviews to flag underperformance early.”

Specificity is what separates a credible risk section from a hand-wavy one. “We will adapt” is not a mitigation strategy. “We will activate our two backup referral partners (named in the partnerships section), and shift 25% of outreach budget to direct outreach in the second quarter” is.

Example Patterns That Read Well

“Staff hiring may take longer than the 60-day plan; the Project Director will assume the role provisionally if needed, supervised by the ED, and we have identified two qualified internal candidates as backups.”
“Our primary recruitment partner is reliable, but to mitigate dependence on a single source, we have engaged two additional partners (letters attached), each capable of generating at least 25% of needed enrollment.”
“Match funds are committed for years 1–2 (letters attached). For years 3–5, we have identified three named funders being approached this fiscal year, with a contingency plan to defer specific activities if match shortfalls occur.”

Each names a specific risk, names a specific response, and connects to verifiable facts elsewhere in the proposal.

Common Risk-Section Mistakes

Pretending there’s no risk. Reads as either inexperienced or evasive.
Listing too many risks. Overcaution signals lack of confidence.
Generic mitigations. “We will work closely with our team and partners” means nothing.
Mitigations that aren’t funded. Backup plans that depend on resources the budget doesn’t provide.
Risks that contradict the methods. Identifying a risk that the methods section ignored.
Standalone risk soup. A risk section disconnected from the methods, partners, and budget.

When to Lean Into vs. Soften Risk Framing

For federal research and demonstration proposals, lean in. Detailed risk discussion is expected and rewarded.
For community foundation and family foundation proposals, soften. A short acknowledgement in the methods or sustainability plan is enough.
For proposals to first-time funders, lean in. A risk-aware new applicant earns more trust than an overconfident one.
For continuation proposals to current funders, the relationship may allow more candid discussion than a cold proposal would.

How Grantboost Helps

Risk and mitigation must align with the rest of the proposal, the methods, partners, budget, and sustainability plan all need to back up what you claim you’ll do if things shift. Grantboost helps you develop the proposal as a connected whole in your organization’s voice (see training AI on your past proposals), structured around each funder’s specific risk-handling expectations.

Try Grantboost free and write proposals that handle risk like a mature organization.

Risk and Mitigation Sections in Grant Proposals: How to Show Honest Planning