Is this grant worth pursuing?

Check mandatory eligibility before enthusiasm has a chance to build. It is much easier to set an opportunity aside on day one than after a project team has met three times.

Look for stated conditions covering:

• Legal organization type (incorporated nonprofit, unincorporated group, cooperative, municipality, band or Indigenous governing body)
• Charitable or nonprofit status, including qualified donee requirements where they apply
• Geographic requirements for where you are based, where you operate, or who you serve
• Populations the funding must benefit
• Eligible activities, and activities the program explicitly excludes
• Minimum and maximum funding amounts
• Eligible project start and end dates
• Required matching or cost-shared contributions, cash or in-kind
• Minimum operating history, such as a number of years delivering programs
• Financial thresholds, such as revenue limits or audited statement requirements
• The application deadline and any pre-application or registration step

Where a requirement is ambiguous rather than clearly unmet, note it as a question to resolve. That is a different situation from a firm exclusion, and it is handled in the decision framework below.

Eligibility means you are allowed to apply. Fit asks whether this funder is a sensible match for your organization and this particular project. Many organizations are eligible for programs they are unlikely to compete well in.

To assess fit, compare the program against your project on:

• Funder priorities and the outcomes the program says it wants to support
• Stated program objectives, and whether your project advances them directly or only indirectly
• Target populations, and whether your participants are the ones described
• Eligible outcomes, and whether you can report on them credibly
• Geographic focus, including whether the funder concentrates on specific regions or communities
• Scale of project relative to the examples or ranges the program describes
• Size of request relative to your total organizational budget
• Organizational capacity to deliver the project as described and to meet reporting obligations

A request that is very large relative to your operating budget is not automatically disqualifying, but it usually raises questions about delivery capacity that the application will need to answer with evidence.

There is an important difference between identifying a real organizational priority and then finding appropriate funding for it, and inventing a project because a grant happens to be open.

Grant-driven project design tends to create problems later. Common ones include commitments to activities no one has capacity to deliver, participant targets that were set to match a funding range rather than actual demand, reporting obligations that fall on staff who were never consulted, and programs that end abruptly when the grant closes because they were never part of the organization's plan.

Adapting an existing priority to a funder's framing is normal and often necessary. Constructing a new program from scratch to fit a deadline is a different exercise, and it is worth naming that clearly before proceeding.

Most applications ask you to demonstrate something rather than assert it. Before committing, consider whether your organization can currently show:

• Community need, through consultations, local data, service statistics or documented requests
• Program demand, such as registration numbers, waitlists or referral volumes
• Outcomes from comparable work you have delivered
• Partnerships, ideally in writing rather than as informal conversations
• Delivery capability, including staffing, facilities and relevant experience
• Realistic budget assumptions supported by quotes, wage scales or past actuals

Weak evidence does not always mean "do not apply." It may mean the application needs more preparation than the deadline allows, or that a smaller, better-evidenced request is a stronger use of the same effort. Some funders may also accept qualitative evidence where quantitative data does not yet exist; confirm what the program guidelines ask for.

Effort is not only the writing. Work through the application package and ask:

• How long is the application, and how many narrative questions are there?
• Is a detailed project budget required, and in the funder's own template?
• Are supplier quotes or cost estimates required?
• Are partner letters or memoranda of understanding required?
• Does the board need to approve the application or a resolution?
• Are audited or reviewed financial statements required?
• How many attachments are needed, and do they all currently exist?
• Is there enough time to prepare all of it properly before the deadline?

Then weigh that against the value. A $5,000 grant that requires audited statements, three partner letters, a board resolution and a fifteen-page narrative may be a poorer use of the same weeks than a different opportunity, even when eligibility is strong. The exception is when the effort creates reusable material — a project budget, an evaluation plan, a needs summary — that will support later applications.

Timing failures are among the most avoidable reasons applications are rushed or abandoned. Map the following against the calendar:

• The application deadline, including the time of day and time zone it closes
• The earliest eligible project start date, and whether your project can wait for a funding decision
• Internal approval timelines, including when the board or executive next meets
• Partner availability, particularly for letters that require their own internal sign-off
• Budget preparation, especially if finance staff are in year-end or audit season
• Document collection for anything that must be requested from a third party

Working backward from the deadline usually produces a clearer answer than working forward from today.

Once the review is done, place the opportunity in one of three categories. Recording the reason is useful: it saves repeating the analysis when the program opens again next year.

Pursue

• Mandatory eligibility appears satisfied
• The project aligns with the funder's stated priorities without distortion
• The deadline is manageable with the staff time available
• Evidence and required documents are reasonably available
• The funding amount justifies the effort required

Investigate

• An eligibility requirement is unclear or open to interpretation
• An important document is missing and you do not yet know how long it takes to obtain
• Partnership status is uncertain or unconfirmed
• Project scope needs refinement before it can be described accurately
• Guidelines conflict with the application form, or key details are incomplete

Investigate items should carry a name and a date. If the question cannot be resolved in time, the opportunity moves to pass rather than drifting forward on an assumption.

Pass

• A mandatory requirement is clearly not met
• The project must be substantially distorted to fit the program
• The timeline is unrealistic for the work the application requires
• Organizational capacity is insufficient to deliver or report on the project
• Application effort is disproportionate to the value of the opportunity

A pass is a legitimate outcome, and documenting it gives the board a clear rationale.

If you want a short version to use in a staff meeting, these five questions cover most of the analysis above:

1. Are we clearly eligible?
2. Does the project genuinely align with what this funder supports?
3. Can we demonstrate the need and the outcomes?
4. Can we produce the required information and documents by the deadline?
5. Is the likely value worth the effort?

A hesitant answer to any of them is a signal to investigate rather than to begin drafting.