Ask a development director how much grant revenue is coming next year and you usually get one of two answers: a hopeful number nobody can defend, or a shrug. A grant pipeline replaces both with a forecast you can manage. It is your strategic view of grant revenue over the next 12 to 24 months, and it answers three questions in writing: how many grants will we likely receive, when will they arrive, and for how much. Without a pipeline, you are hoping grants will show up. With one, you are planning for them, and you can tell your board the difference.

Why a Pipeline, Not a Wish List

A wish list is a set of funders you would like to have. A pipeline is a set of opportunities with dates, amounts, statuses and probabilities attached, reviewed on a schedule. The difference matters because grant revenue is timing-sensitive: an award that lands in April and one that lands in October fund very different decisions, even if they are the same size. Once every opportunity carries a deadline, an expected notification date and a confidence score, the pipeline stops being a list of hopes and starts behaving like a financial instrument you can plan payroll and programs around.

The portfolio approach borrows its logic from investing. It treats grants the way a stock investor treats assets: diversify across many small bets rather than betting everything on one large grant. That reduces risk and stabilizes revenue. The mechanism is simple. Any single application is binary, funded or not, and no amount of proposal craft removes that. Across a portfolio, the outcomes average out, so one rejection becomes a variance you absorb rather than a hole in the budget. The tradeoff is administrative: more applications means more deadlines, more reports and more relationships to maintain, which is exactly why the portfolio has to be designed rather than accumulated.

The Portfolio Model: Five Categories

The portfolio splits into five categories, each with a target share of grant revenue, its own application rhythm and its own volume. The shares are targets, not rules, and they exist so that no one category can sink the year. Read the grid below as a shape to grow into rather than a quota to hit in month one.

Each category earns its place for a different reason. Major grants carry the portfolio but move slowly, so they have to be started long before you need the money. Mid-level grants are the workhorses: enough volume to smooth cash flow, short enough cycles that a rejection in one quarter can be answered by a submission in the next. Programmatic grants from community and local funders turn around fastest and keep a steady flow of smaller decisions moving. Government grants are highly variable in size, rigid in their timelines and compliance-heavy, which is why they are capped at a modest share here; Government Grants: Federal, State, and Local Opportunities covers the strategy for them. Rapid-cycle grants are the smallest slice because they cannot be planned, only caught.

Building Your Pipeline: The Tracking System

The pipeline lives in a spreadsheet before it lives in any software. Create one row per opportunity and give it these columns, because each one answers a question somebody will eventually ask you in a board meeting:

• Funder name
• Grant amount requested
• Application deadline
• Award notification date, estimated
• Award status: prospect, applied, pending, awarded or declined
• Success probability, the percentage chance of being funded
• Expected revenue, calculated as grant amount multiplied by probability
• Grant period, meaning when the funding would actually start
• Notes: key contacts, special requirements

The column that does the real work is expected revenue, because it forces you to multiply your optimism by your evidence. An ambitious request scored honestly at a low probability contributes little to the forecast, which is the correct answer. Two columns hold the timing: the application deadline tells you when the work has to be done, and the estimated notification date tells you when you will know. The grant period is separate from both, because funders frequently notify months before the money moves, and a pipeline that confuses notification with cash will mislead your cash flow planning.

A Worked Example

Here is a small nonprofit's pipeline in miniature. The table below carries the tracking columns that shape the conversation; in your own version the requested amount and expected revenue columns sit alongside these and produce the totals.

Three lines is not much of a portfolio, and that is the point of the example. Even at this size the pipeline tells you something useful: two applications are already in and one is still a prospect, the deadlines fall close together in late spring, and the confidence spread runs from a likely bet down to a long shot. Summed as expected revenue, a pipeline of this shape represents roughly 10% of that organization's annual budget, which is a realistic starting position for a small nonprofit. It is also a warning: a tenth of the budget is worth having and nowhere near enough to build on, which is why Revenue Diversification for Nonprofits: The 5-Source Model treats over-reliance on grants as a risk rather than an achievement.

Probability Scoring: How Confident Are You?

Success probability should be evidence-based, not wishful. The discipline here is to tie each band to observable facts, not feelings, so that two people scoring the same opportunity land in the same place. Score each opportunity against these bands:

• 90 to 100% probability: a grant you have received before and are reapplying for. The funder has explicitly invited you to apply. You have talked directly to the program officer and they indicated strong interest. You meet all requirements perfectly.
• 70 to 89% probability: you have a relationship with the funder. You meet all eligibility requirements. Similar organizations have been funded. You have strong program outcomes.
• 50 to 69% probability: good fit but some uncertainty. Maybe you are new to the funder. Maybe the requirements are tight. Maybe you are competing against strong similar organizations.
• 30 to 49% probability: weak fit or first-time applicant. Worth pursuing, but do not count heavily on it.
• Below 30% probability: do not apply. The opportunity cost is not worth it.

That last band is the one people argue with, and it is the most valuable. Declining to apply is not pessimism; it is a decision about where a limited number of staff hours go. Every proposal you write at low confidence is a proposal you did not write for a funder who already knows you. Scoring also protects you from the opposite error, which is quietly inflating a number because the budget needs it. If the score changes, something in the evidence should have changed with it, and you should be able to say what.

Revenue Forecasting

Use the pipeline to forecast cash flow, and update it monthly. A forecast built once and left alone drifts away from reality within a quarter, because probabilities move as conversations happen and deadlines pass. The rhythm of an early-year forecast looks like this in practice. January is a submission month: nothing is decided yet, and applications go out for March through May deadlines. February brings notifications on the January submissions, so probabilities get revised on the strength of what you hear. March is when the first awards from those January submissions arrive, which lets you adjust the confidence scores on everything still pending. April brings more awards, and by then the first quarter has a real total rather than a projected one.

This forecasting is what makes grant revenue usable in budget planning. If the pipeline shows less expected revenue in the first quarter than operations require, you have found the gap early enough to do something about it: individual donors, events, or other revenue sources can be mobilized in the months you still have. The alternative is discovering the shortfall when payroll is due. Treat the method as the discipline: compare expected pipeline revenue for the period against operating need for the same period, and act on the difference.

Diversification: Avoid Funder Concentration Risk

A portfolio can be busy and still be fragile if too much of it sits with one funder. The ideal distribution has several dimensions, and it is worth checking all of them rather than counting relationships alone:

• No single funder represents more than 15% of annual grant revenue.
• No single funder category, meaning foundations, government or corporate, represents more than 50% of grant revenue.
• At least 8 to 10 active funding relationships at any time.
• A mix of foundation, government and corporate sources.
• Geographic diversity across local, state and national funders.
• Issue diversity, so that grants are spread across multiple programs rather than concentrated in one.

The failure mode is easy to picture. Suppose half your grant revenue comes from one foundation. If that foundation has a down year or changes its priorities, your revenue crashes, and it crashes on their timetable rather than yours. Category concentration behaves the same way one level up: a portfolio that is entirely government-funded is exposed to a single budget cycle, and one that is entirely corporate is exposed to a single economic mood. Geographic and issue diversity matter for the same reason, because a local funding pool and a single program area are each one shock away from taking the whole portfolio with them.

Pipeline Management: The Monthly Review

A pipeline that nobody reviews is a document, not a system. Put a one-hour pipeline review on the calendar for the first Friday of every month, with the Executive Director, the Development Director and the Finance Director in the room. Finance is not optional here: the whole point of probability-weighted revenue is to connect fundraising activity to cash planning, and that connection breaks if the two functions review different numbers. Keep the meeting to the same agenda every month so it stays short and nobody has to prepare a presentation.

• Update pipeline status: any awards, any rejections, any withdrawals?
• Adjust probabilities based on new information. If you met with a funder and they seemed genuinely excited, that might move an opportunity from 50% to 65%.
• Identify new applications to launch by looking at which deadlines fall next month.
• Review the cash forecast and ask whether grant revenue is on track.
• Problem-solve: if the pipeline shows a shortfall, brainstorm solutions while there is still time to act.

Growth Strategy: Expanding Your Pipeline

Pipelines mature over years, not quarters, and the growth curve is fairly predictable. A first-year pipeline typically holds 5 to 8 active funding relationships. By year two that grows to 10 to 15, and the growth comes from four moves: adding new major grant prospects such as larger foundations and government grants, deepening year-one relationships so that grant size or frequency increases, adding community foundation and rapid-cycle grants, and testing new funding sources such as corporate giving and family foundations.

By year three and beyond, a mature pipeline carries 15 to 25 active relationships, and its internal composition matters as much as its size. The shape to aim for is 4 to 5 major grant relationships, 8 to 10 mid-level grants, 5 to 10 community or rapid-cycle grants, and 1 to 2 government grants if government funding applies to your work at all. Read that list against the five categories above and you will see the same portfolio logic expressed as a headcount: a few large anchors, a broad middle that absorbs variance, and a tail of fast, small opportunities.

The Pipeline Dashboard

Boards do not want your spreadsheet. They want six numbers that tell them whether grant funding is under control. Build a simple visual and put the same measures on it every year, so that the trend is visible even when a single year is noisy. The measures are total grant revenue expected over the next 12 months, that figure as a percentage of budget, total applications submitted in the current year, the success rate calculated as grants awarded divided by applications submitted, the number of active funding relationships, and the largest single funder as a share of grant revenue, which should sit under 15%.

Share the dashboard with the board annually. Its real function is not reporting but framing: it demonstrates that grant funding is strategic rather than random, and it gives the board a way to ask useful questions. A falling success rate suggests targeting or proposal quality has slipped. A rising concentration figure is an early warning long before the funder in question does anything. A flat relationship count next to a rising revenue target says the plan depends on existing funders giving more, which is a legitimate strategy but should be a stated one.

Anti-Patterns

These are the pipeline habits that look like discipline and are not. Each one has a specific failure attached.

• Scoring probabilities to fit the budget. When the forecast comes up short and the numbers move rather than the plan, the pipeline stops being a forecast. Probability changes should follow evidence, such as a conversation with a program officer, not the size of the gap.
• Applying to everything. Volume without fit produces rejections, burns the hours you needed for high-probability work, and teaches your team that grant writing does not pay off. The below-30% rule exists to be enforced.
• Building the spreadsheet and never reviewing it. A pipeline that is updated only when someone asks for it will always be describing last quarter.
• Counting notification as cash. Awards notified in one period and paid in another will wreck a cash forecast that treats the two dates as the same.
• Confusing a busy pipeline with a diversified one. Twenty applications to one category of funder is concentration risk wearing a costume.
• Growing the relationship count without growing the capacity to serve it. Every relationship carries reporting and stewardship obligations, and administrative burden is the real ceiling on portfolio size.

Practice Prompts

• Build the spreadsheet with the nine columns listed above and populate it with every grant opportunity you are currently aware of, including ones you have already decided against. Note how many rows you could not score with evidence.
• Score each opportunity against the five probability bands. For every score above 70%, write the specific fact that justifies it. If you cannot, lower the score.
• Calculate what share of your expected grant revenue comes from your largest single funder, and what share comes from your largest funder category. Compare both against the 15% and 50% guidelines.
• Take your next three months of expected pipeline revenue and set it beside your operating need for the same three months. Write one paragraph on what you would do if the gap were real.
• Draft the six-measure board dashboard using your current numbers, then decide which measure you would least like to explain and why.
• Put a one-hour pipeline review on the calendar for the first Friday of next month and invite the Executive Director, Development Director and Finance Director.

Reflection

Think about the last grant your organization did not receive. How much staff time went into it, what probability would you honestly have assigned it beforehand, and would that score have changed the decision to apply? Then ask the harder version of the question: if you had spent those same hours on the funders who already know you, what would have happened? Most grant programs are not short of opportunities. They are short of the discipline to decline the wrong ones and the record-keeping to notice which ones were wrong. Consider also what your board currently believes about grant revenue, and whether anything you have shown them would let them tell a good year from a lucky one.

Glossary

• Grant pipeline: a strategic forecast of grant revenue over 12 to 24 months, listing each opportunity with its amount, deadline, status and probability.
• Portfolio approach: managing grants the way an investor manages assets, diversifying across many smaller bets rather than concentrating on one large grant.
• Expected revenue: a pipeline column calculated as grant amount multiplied by success probability, used to weight the forecast by confidence.
• Success probability: an evidence-based estimate of the chance an application is funded, assigned from defined bands rather than intuition.
• Funder concentration risk: the exposure created when one funder, or one category of funder, supplies too large a share of grant revenue.
• Award status: the stage an opportunity has reached, recorded as prospect, applied, pending, awarded or declined.
• Grant period: the span during which awarded funding is actually available to spend, which is distinct from the notification date.
• Rapid-cycle grant: a quick-response or time-limited opportunity with very short deadlines, measured in days to weeks.
• Success rate: grants awarded divided by applications submitted over a defined period.

Related Lessons

• The Grant Lifecycle: From Discovery to Closeout
• Funder Research for Small Nonprofits: Free and Low-Cost Methods
• Government Grants: Federal, State, and Local Opportunities
• Revenue Diversification for Nonprofits: The 5-Source Model
• Building an Operating Reserve: How Much, How Fast, Where to Keep It
• When to Say No to a Grant: The Opportunity Cost Framework
• Grant Strategy for Small Nonprofits: Building a Sustainable Portfolio

Closing

A pipeline does not win grants. Proposals, relationships and program results win grants. What a pipeline does is make the whole effort legible: which opportunities are real, which are wishes, when the money would arrive, and what happens to the budget if a particular application fails. That legibility is what lets you say no to a poor-fit funder without guilt, ask the board for patience during a slow quarter without panic, and grow the portfolio deliberately rather than by accident. Start with the spreadsheet, score honestly, review it on the first Friday of the month, and let the discipline compound over the years it takes a portfolio to mature.

Key Takeaways

• A grant pipeline forecasts grant revenue over 12 to 24 months and answers how many, when and how much.
• The portfolio approach diversifies across many smaller bets instead of concentrating risk in one large grant.
• Five categories structure the portfolio: major at 40%, mid-level at 30%, programmatic at 15%, government at 10% and rapid-cycle at 5%.
• Nine spreadsheet columns turn a list of funders into a forecast, with expected revenue calculated as amount multiplied by probability.
• Probability bands must be tied to evidence, and anything below 30% is a decision not to apply.
• Keep any single funder under 15% of grant revenue, any category under 50%, and maintain 8 to 10 active relationships.
• Review the pipeline for one hour on the first Friday of each month with the ED, Development Director and Finance Director.
• Pipelines mature from 5 to 8 relationships in year one to 15 to 25 by year three, and the composition matters as much as the count.

Frequently Asked Questions

How many grants should we target in our first year?

Start with 5 to 8 high-fit prospects rather than applying to 20 poor-fit opportunities. Quality beats volume. As you mature, expand to 12 to 20 prospects. Even large nonprofits rarely manage more than 20 to 25 active funding relationships, because the administrative burden becomes too high beyond that point.

What success rate should we expect?

First-time applicants tend to land at a 20 to 30% success rate, which is roughly one funded application in three to one in five. Experienced organizations reach 40 to 50%. If you are below 20%, one of two things is usually wrong: your targeting is poor, meaning you are applying to bad-fit funders, or your proposals are weak and you need help with proposal writing.

Should we apply to a grant we are not sure about?

Only if the probability is above 30% and the application takes under 20 hours. If you are less than 30% confident and it takes 40 or more hours to apply, skip it, because the opportunity cost is too high. Those 40 hours could go to higher-probability opportunities or to individual donor cultivation instead.

How do we handle seasonal cash flow if grants arrive unpredictably?

Build an operating reserve, covered in Building an Operating Reserve: How Much, How Fast, Where to Keep It, and diversify revenue beyond grants. Grants should represent 20 to 40% of annual revenue rather than all of it. That mix insulates you from the timing variability that no amount of pipeline discipline can remove.