When to decline a grant — and how to do it without burning the relationship.

Most nonprofits accept every grant offered. It is an understandable reflex — money is scarce, the board watches the revenue line, and turning down funding feels indefensible in a sector where scarcity is the permanent condition. It is also how organizations end up running programs nobody chose.

There are three legitimate reasons to decline, and they are worth naming precisely so that a decline can be argued rather than merely felt.

One: the restricted scope would pull staff off higher-impact work. This is the most common and the least often articulated. A $60,000 restricted award that consumes 30% of your two best program staff is not $60,000 of value. It is $60,000 minus whatever those people would otherwise have produced, and that subtraction is frequently larger than the award.

Two: the reporting burden exceeds the award's value. Some funders attach quarterly narrative reports, a site visit, and a third-party evaluation requirement to a $25,000 grant. Do the arithmetic honestly, including the finance staff time to track restricted funds separately. Small grants with large compliance tails are a real and underdiscussed drain on small organizations.

Three: the program the funder wants is not one you can run well. Adjacent is not the same as aligned. Organizations routinely convince themselves that a small stretch is manageable, and the stretch is where quality failures and staff burnout originate.

There is a fourth reason that is legitimate but harder: the money is misaligned with the community you serve, in a way your participants would recognize. That one rarely appears in a budget conversation and should.

The mistake nearly everyone makes is treating the decline as a rejection of the funder. It is not. It is a scoping disagreement, and program officers deal with scoping disagreements constantly — it is a large fraction of what the job actually consists of.

The mechanics that work are consistent. Decline early, before the officer has spent internal capital advocating for you. Do it in a call rather than an email, because tone does not survive email and a decline is entirely about tone. Name the specific constraint rather than gesturing at capacity. And — this is the part that changes outcomes — propose the version you would say yes to.

That last move converts the conversation more often than not. 'We cannot staff the four-county expansion at this level, but we could deepen the two counties where our retention data is strongest, at roughly the same budget' is not a decline in the officer's mind. It is a counter-proposal from an organization that knows its own limits, which is a signal they are trained to value.

What to avoid: declining by ghosting, which is the most common form and the most damaging. Declining after the officer has taken it to committee. Citing 'capacity' with no specifics, which reads as either disorganization or a polite lie. And accepting with private reservations you intend to renegotiate later — that is a decline with a delay and a broken relationship attached.

Board management is the other half of this, and it is where most declines die. A board that sees only the revenue line will experience a decline as failure. The fix is to bring the analysis, not the conclusion: the full cost of the award, the opportunity cost of the staff time, and the counter-proposal you made. Boards that see the arithmetic once usually stop asking.

It also helps to keep the record. An organization that has documented three well-reasoned declines has a written standard, and a written standard is what makes the fourth one routine instead of contentious.

Declining well is a relationship-building act. It tells a funder that your yes means something — that when you accept, you have judged that you can deliver, which makes every future acceptance more credible.

Accepting badly is how organizations end up two years into work they never wanted, staffed by people they hired for it, reporting on outcomes they do not believe in, to a funder who would have been perfectly happy with the smaller thing you actually do well.