Most nonprofit leaders approach grants as an unqualified good: more funding is better, and the answer to a grant opportunity is always yes. But strategic nonprofit leaders know that some grants are liabilities disguised as opportunities. The difference between successful organizations and struggling ones often isn't how many grants they pursue but how strategically they choose which ones to say no to. Declining a grant opportunity is one of the most sophisticated grant management decisions you can make.
Saying no to a grant requires courage. There's funding on the table, your organization needs money, and someone worked hard to find this opportunity. Rejecting it feels reckless. But pursuing every grant regardless of fit depletes staff energy, creates program chaos, damages relationships with actual partners, and often results in failing to deliver promised outcomes. Strategic organizations build frameworks for saying no to poor-fit grants.
The Opportunity Cost Framework: What Are You Giving Up?
The most powerful argument for saying no to a grant is opportunity cost: What else will your staff not be able to do if they spend time pursuing this grant? If your grants manager has 40 hours per month available for grants work, and this proposal will require 30 hours, she can only pursue one other grant opportunity that month. Is this the best use of her capacity, or would her time be better spent on a different opportunity with higher likelihood of success?
Evaluate every grant against your capacity and your pipeline. If you already have strong, well-matched grants in your pipeline that you're actively developing, adding another marginal opportunity might dilute your energy and hurt your chances of winning the stronger opportunities. Sometimes the best use of your capacity is focusing deeply on fewer, better-fit prospects rather than spreading yourself thin across many mediocre ones.
Consider program opportunity cost too. If this grant requires you to develop a new program component you're not ready for, what existing programs will suffer while staff attention is diverted to the new work? If you're already running programs at capacity and this grant requires expansion, where will the staff time come from? Grants that require mission expansion or program changes have hidden costs. Be realistic about whether those costs are worth the benefit.
Mission Drift: Recognizing When Grants Pull You Off-Course
Mission drift is the gradual shift from your core mission toward funder-defined priorities. It happens subtly. A funder announces funding for a program that's somewhat related to your work. Your organization is cash-strapped, the funding is substantial, and you convince yourself that serving this population or delivering this program "aligns with our values." A few years later, your organization has shifted dramatically from its original mission.
Mission drift is insidious because it happens with good intentions. You're still helping people; you're just helping a different set of people than your mission describes. But the consequences are serious: staff who joined your organization to do the original mission become demoralized. Your original beneficiaries no longer see your organization as fighting for them. Your board becomes confused about what the organization actually does. And when funding for the drifted program ends, you've lost the capability to return to your original mission because staff have left, partnerships have shifted, and your reputation has changed.
Combat mission drift by evaluating every grant explicitly against your mission. Ask: Does this program serve the population described in our mission? Does this work toward the change we're trying to create? Or are we pursuing it primarily because funding is available? A helpful framework: would we do this program if it came with no funding, just because it's part of our mission? If the answer is no, the grant isn't worth pursuing.
Some funders explicitly support mission-driven organizations. During conversations with potential funders, listen for language about "flexibility" or "supporting your priorities." These are positive signals. Funders who say "we need a program in X area; can you do it?" are more risk for mission drift. The former supports you; the latter tries to redirect you.
Capacity Alignment: Honest Assessment of What You Can Actually Manage
One of the most common reasons organizations decline grants (or should) is honest assessment that they lack capacity to manage the grant responsibly. This includes three types of capacity: staff capacity, systems capacity, and financial management capacity.
Staff Capacity. Do you have staff with the skills to deliver this program at the quality level it deserves? If a grant requires hiring new expertise you don't currently have, can you recruit and onboard that person? Can your program management team supervise and support them effectively? If the answer to any of these is no or uncertain, the grant is too ambitious right now. It's better to honestly say, "We'd love to do this, but we lack the staff expertise to deliver it well. We're building toward it," than to accept a grant you're not ready for.
Systems Capacity. Do you have the operational infrastructure to manage this grant? Government grants require detailed financial tracking, reporting, and documentation. Do you have accounting systems sophisticated enough? Do you have grants management systems? Data collection procedures? If you're a small organization just starting to use grants management software and you win a complex federal grant, you've likely set yourself up for compliance problems. Match your systems capacity to grant complexity.
Financial Management Capacity. Can your accountant manage another grant without being overwhelmed? If your organization is small and your bookkeeper already works 50 hours a week, another $100,000 grant is not a win; it's a burden. Additionally, can your organization cover cash flow gaps? Some grants reimburse expenses, meaning you must spend your own money first and then invoice the funder. If your organization lacks cash reserves, this can create serious cash flow problems.
Many organizations damage their reputation by accepting grants they can't manage well. Funder disappointment comes not from ambitious organizations that tried and partially succeeded, but from organizations that accepted grants, failed to deliver or report, and created compliance headaches for funders. Say no to grants you're not ready to manage.
Funder Risk Assessment: Is This Funder Worth the Relationship?
Not all funders are created equal. Some are wonderful to work with: clear requirements, responsive staff, flexible when challenges arise, genuinely interested in your organization's success. Others are nightmares: unclear requirements, unreachable staff, inflexible about any deviation from the grant agreement, more focused on compliance than partnership.
Before you commit to a grant, assess the funder. Is the program officer responsive when you call with questions? Do they have a reputation in your nonprofit community (ask peers: have they worked with this funder? What was it like?)? Do their grant guidelines make sense, or are they confusing and contradictory? Have they previously worked with organizations like yours, or is your organization their guinea pig?
Some funders are worth the effort because they're building long-term relationships. If a funder has supported other organizations in your sector well and is known for renewing grantees, the first grant might be a starting point for a multi-year relationship. But if a funder has a reputation for being difficult, unpredictable, or creating more problems than they solve, you might say no. A grant from a difficult funder might cost you more in staff stress and compliance headaches than the money is worth.
Saying No Strategically: How to Decline and Preserve Relationships
If you've decided to say no to a grant, decline thoughtfully. You might want to work with this funder in the future. Preserve the relationship. Send a brief email to your contact at the funder: "Thank you for bringing this opportunity to our attention. After careful assessment, we've decided to pass on this grant cycle. We're not quite ready to deliver this program at the quality level it deserves, but we're building toward it. We'd welcome the opportunity to discuss it again in 18 months when we've strengthened our capacity. In the meantime, we remain interested in your other funding opportunities."
This communication: expresses appreciation, explains your decision honestly without being defensive, signals continued interest in the relationship, and opens the door for future engagement. Many program officers respect organizations that turn down grants when honest about capacity limits. It demonstrates maturity.
Some opportunities might be good fits in the future but not now. Keep these on your radar. Document your reason for declining: "Grant is good fit, but we don't have systems capacity yet. Revisit in 12 months after grants management software is implemented." When systems improve, you can reach back out to the funder.
Frequently Asked Questions
What if our board pressures us to pursue a grant we don't think is a good fit? Have a conversation with the board about your grant strategy. Share your pipeline and your criteria for evaluating opportunities. Explain why this particular grant doesn't meet your criteria. Ask them to trust your assessment. If they still insist, you have a governance problem that's bigger than this one grant; it likely indicates the board doesn't understand nonprofit strategy. Address the root issue.
How do we know if we're being too selective and missing real opportunities? Look at your success rate. If you pursue 10 grants and win 3-4, your strategy is working. If you're only winning 1 in 10, either your grants are poorly matched or your proposals are weak. Assess which. You might be too selective (targeting only perfect-fit grants when you need to pursue more good-fit ones), or you might be not selective enough (pursuing marginal grants and getting rejected). Track your pipeline metrics.
Should we ever pursue a grant that doesn't align perfectly with our mission if we really need the money? Rarely. There are better funding sources than mission-drifting grants. Consider: can you build unrestricted revenue sources (individual donors, major gifts, recurring giving programs)? Can you pursue government contracts that align with your mission? Can you explore corporate partnerships? Usually, mission-aligned funding exists; it might just take more work to find.
How do we communicate decline to our team if staff has invested time researching the grant? Thank them for their research. Explain that you've decided to redirect that work toward higher-priority opportunities. This teaches your team that not every grant is worth pursuing, which builds a culture of strategic selectivity.