Building a Grant Pipeline

A grant pipeline is a staged operating system, not a list. Each stage has an entry condition and an exit criterion, prospects move only when the criterion is met, and the top of the pipeline is sized backward from a target number of awards and a realistic win rate — then capped at the staff hours that actually exist.

Current figures — verified 2026-08-11

Item	Value	Source
NIH Research Project Grant success rate	13.0% in FY2025, from 18.5% in FY2024 and 21.3% in FY2023	NIH Extramural Nexus
NSF competitive-proposal funding rate, FY2025 (all competitively reviewed proposals)	19% — 8,377 awards from 43,532 proposals evaluated	NSF FY2025 Agency Financial Report
Surveyed organizations winning at least one award, by applications submitted (2026 edition)	64.5% at one application; 89.4% at three to five; 93.3% at six to ten	GrantStation, 2026 State of Grantseeking Report
Median largest individual award reported (2026 edition)	$90,000 overall; $240,000 government, $50,000 non-government	GrantStation, 2026 State of Grantseeking Report
Department of Education generic discretionary grant application clearance	40,000 annual responses against 700,000 annual burden hours	reginfo.gov, ICR 202606-1894-001

These figures change. Verify against the linked source before relying on them. Report an outdated figure

Key takeaways

• Every pipeline stage needs a written exit criterion.
• Size the top backward from target awards and win rate.
• Win rates differ by funder type by an order of magnitude.
• Cap the pipeline at real staff hours, not ambition.
• Record no-go decisions; the trend data is the asset.

What is a grant pipeline?

A grant pipeline is a staged, tracked set of funding pursuits in which every prospect occupies exactly one stage and moves forward only when a defined exit criterion is met. The structure borrows from sales pipelines for a reason: both manage a scarce production resource against opportunities with long cycles, hard deadlines, and a majority of losses.

The distinction that makes a pipeline useful is between a list and a system. A list of interesting funders answers no operational question. A pipeline answers four: how many pursuits are in flight, what each one is waiting on, whether the top is wide enough to hit the target, and whether the team has the hours to finish what is already committed.

Two calendars run underneath it. The pursuit calendar carries deadlines, letter-of-inquiry dates, internal review gates, and registration renewals. The post-award calendar carries financial reports, performance reports, and audit clocks for awards already won. Organizations that build only the first calendar win more than they can administer, which is a more expensive failure than losing. The operating structure behind both is covered in building a grants function, and the pipeline itself is the core discipline of finding and qualifying funding.

Pipeline stages are also where honesty gets enforced. A prospect that has sat in “qualified” for eight months without a deadline is not qualified; it is a bookmark. Exit criteria exist so that the pipeline count means something.

What are the stages of a grant pipeline?

A working grant pipeline has seven stages, each with a written entry condition and an exit criterion. Stages that lack an exit criterion silently accumulate prospects, and a pipeline that only grows is a filing cabinet.

The table below defines each grant pipeline stage, what admits a prospect to it, and what must be true before the prospect advances.

Pipeline stage	Entry condition	Exit criterion
Prospect	Funder identified with a plausible match	Funder ID, deadline, ceiling, and eligibility note recorded
Qualified	Hard eligibility and geography confirmed	Pass on eligibility, cost share, and award-size fit; internal program owner named
Go decision	Qualified prospect with a live deadline	Scored decision recorded with rationale, go or no-go
In production	Go decision signed	Compliant reviewed package complete before the deadline
Submitted	Package transmitted	Confirmation and validation captured; full copy archived
Decision	Funder review underway	Award or decline logged with reviewer feedback
Post-award	Award accepted	Reporting calendar, financial setup, and compliance owner in place

Two stages carry most of the value and get the least attention. The go decision stage is where organizational capacity is committed, and it is the only stage whose output is frequently a documented no — which is why the decision must be recorded either way. The post-award stage is where the money is actually kept, and it belongs in the pipeline rather than outside it because it consumes the same staff hours as pursuit.

The gate between qualified and go is the pipeline’s throughput control. Widening it raises submission volume and lowers average quality; narrowing it does the reverse. The mechanics of that gate are the subject of the go/no-go decision.

How many prospects do you need at the top of a grant pipeline?

Size a grant pipeline backward from awards, not forward from enthusiasm. Pick a target number of awards, divide by a defensible win rate to get required submissions, then divide by the pass rates of each upstream gate to get the number of prospects the top of the pipeline must hold.

Win rate has to come from the funder mix, not from a general figure. Federal research competition and foundation grantmaking differ by roughly an order of magnitude, and the measures are not interchangeable. NSF defines its measure precisely — “The Funding Rate is the number of awards made during a year as a percentage of total proposals competitively reviewed” (NSF Funding Profile) — and reports it separately for all competitively reviewed proposals and for research proposals alone, which are different numbers (NSF FY2025 Agency Financial Report). NIH publishes success rates separately from award rates (NIH RePORT, Success Rates). See the current figures above for both.

Work an illustrative case. An organization targets four new awards from a portfolio it expects to win at 25 percent, which requires 16 submissions. If the go/no-go gate passes half of qualified prospects, 32 qualified prospects are needed. If qualification eliminates 60 percent of identified prospects, the top of the pipeline must hold about 80 prospects across the year. At a 13 percent win rate the same four awards require 31 submissions and roughly 155 prospects — the point at which the target, not the pipeline, has to change.

Volume matters, within limits. Survey data shows the share of organizations winning at least one award rising steeply from one application to three to five and again to six to ten (GrantStation, 2026 State of Grantseeking Report, n=1,354). The report states it directly: “As the number of submitted applications increases, so does the likelihood of winning at least one grant.” Paired with a qualification gate, that argues for several well-qualified pursuits rather than one heroic proposal — not for submitting everything.

How long does each pipeline stage actually take?

Cycle time in a grant pipeline is measured in months, not weeks, and the pursuit phase is the short part. Federal timelines are published by the agencies themselves and are the most reliable planning anchors available.

Four published intervals bound federal planning. Opportunities should stay open at least 60 calendar days and never fewer than 30 absent exigent circumstances (2 CFR 200.204). NSF states that “proposers have a minimum of 90 days from NSF’s announcement of a funding opportunity to prepare and submit a proposal,” and that it “strives to be able to tell applicants whether their proposals have been declined or recommended for funding within six months” (NSF, Proposal and Award Process Timeline).

Two more clocks sit outside the proposal itself. NIH standard due dates map each submission cycle to a review month, a council round, and an earliest project start date several months later (NIH, Standard Due Dates), and entity registration takes up to 10 business days to activate and expires every 365 days (SAM.gov, Entity Registration).

Foundation cycles run on a shorter production clock and a hidden decision clock. A letter of inquiry is days of work and a full proposal is weeks, but decisions follow board meeting dates rather than posted deadlines. Ask the program officer when the board meets, and schedule backward from that.

The stage most often mis-estimated is submission itself. A federal application is not submitted when it is transmitted; it is submitted when it validates, and a package that fails validation is rejected rather than late (Grants.gov, Check Application Status). Two business days of validation buffer on every federal pursuit removes an entire category of loss. Sequencing all of this is covered in grant timing and the funding calendar.

How do you plan grant pipeline capacity against staff hours?

Capacity planning converts a grant pipeline from a wish into a schedule. Total available pursuit hours divided by hours per pursuit gives the maximum number of pursuits, and any pipeline larger than that number produces uniformly thin proposals rather than more awards.

Start with the agency’s own estimate of applicant burden. Federal application packages are approved information collections under the Paperwork Reduction Act, and each carries a published estimate of annual responses and total annual burden hours — the Department of Education’s generic discretionary grant application clearance is one example, and dividing its burden hours by its responses yields the agency’s own average hours per application (reginfo.gov, ICR 202606-1894-001). See the current figures above for the values. Those estimates cover form completion and narrative preparation; they do not cover program design, partner negotiation, internal review, or budget development.

Add the uncounted work. Multi-partner federal applications with subawards and cost share spend most of their hours on letters, sub-budgets, and negotiated commitments rather than narrative. Renewals cost less than new competitions. And every award won adds recurring post-award hours for the life of the award — the line item that appears in neither the proposal budget nor the capacity plan.

Work a simple model. A half-time grants role contributing roughly 900 productive hours a year, at 100 hours per federal discretionary application, can carry perhaps six federal pursuits before any post-award reporting. Add reporting for three active awards and the number falls to four. The corrective is to shift mix toward pursuits with a better ratio of expected dollars to hours, or to add capacity before adding pursuits — not to work faster.

How should a grant pipeline be balanced across funder types?

Balance a grant pipeline the way a portfolio is balanced: by combining pursuits with different win probabilities, award sizes, cycle lengths, and compliance costs so that no single outcome determines the year. A pipeline consisting entirely of large federal competitions has a high expected value and a high probability of producing nothing.

Four dimensions do the balancing work:

• Win probability. Renewals and existing-funder requests convert far more often than cold pursuits, and they cost less to produce. They belong in every pipeline as the base layer.
• Award size and cycle length. Government awards run substantially larger than non-government awards at the median, and also take far longer to decide; see the current figures above. Mixing sizes smooths cash timing.
• Compliance load. A small federal award that triggers audit obligations, match documentation, and quarterly reporting can cost more to administer than it delivers. Compliance load belongs in the go/no-go score, not in a post-award surprise.
• Restriction. Project-restricted dollars fund a program; unrestricted or general operating dollars fund the organization. A pipeline made entirely of restricted project grants can grow revenue while starving the core.

Sequence matters as much as mix. Local and regional funders decide faster, ask for less, and produce the track record that larger funders use as proxy diligence. An organization with no grant history that opens with a national competition is asking a stranger to take the first risk.

Diversification also has a ceiling. Every additional funder type adds a distinct application format, reporting cadence, and relationship to maintain. The practical test is whether each funder type in the pipeline has a named owner and a repeatable process; if not, it is not diversification, it is scatter.

What fields does a grant pipeline need to track?

A grant pipeline needs enough fields to answer operational questions and few enough that they get filled in. Eight are non-negotiable, and everything else is optional refinement.

• Funder and program identifiers. Funder name plus the Assistance Listing Number or funding opportunity number for federal pursuits, so the record is unambiguous years later.
• Stage and stage-entry date. Without an entry date, stalled prospects are invisible.
• Hard dates. Letter of inquiry date, submission deadline, internal review gate, and any registration renewal the pursuit depends on.
• Award parameters. Ceiling, floor, expected request amount, cost share requirement, and project period.
• Eligibility and fit notes. The specific reason the organization qualifies, written once, so it is not re-litigated at every review.
• Owner and effort estimate. A named person and an hours estimate; a pursuit with no owner is not in the pipeline.
• Go/no-go score and rationale. Recorded for declines as well as pursuits, because the trend data only exists if losses-not-pursued are logged.
• Outcome and reviewer feedback. Award, decline, score, and any summary statement or debrief, linked to the archived submission.

Reviewer feedback is the highest-value field and the one most often left empty. A declined federal application usually returns criterion-level critique that predicts the next attempt’s outcome, and a declined foundation request often produces a short explanation that redefines fit. Both are reusable. Neither survives unless the pipeline has a field for it and someone fills it in the week the decision arrives.

What goes wrong in a grant pipeline?

Grant pipelines fail in six recognizable ways, and most are capacity failures wearing a strategy costume.

• Chasing every open opportunity. More submissions at lower quality reduce win rate and consume the hours that qualified pursuits needed. Volume helps only when it passes a qualification gate first.
• No exit criteria. Prospects accumulate in early stages, the pipeline count inflates, and forecasting becomes fiction.
• Unrecorded no-go decisions. Declining to pursue is the most common pipeline outcome and the least documented, which destroys the data that would improve targeting.
• Ignoring compliance load. Awards that trigger audit thresholds, match documentation, or heavy reporting can consume more staff time than the grant funds.
• A pursuit calendar with no post-award calendar. Reporting obligations arrive whether or not anyone scheduled them, and they arrive during the next application cycle.
• Planning from a general win rate. A rate that does not name the funder mix describes no real pipeline, and sizing the top from it produces a target that cannot be hit.

The failure underneath all six is treating pursuit as an activity rather than a capacity-constrained process. A smaller, qualified, well-staffed pipeline outperforms a larger one for a structural reason: proposal quality is a function of hours per proposal, and hours are fixed. Feeding that pipeline is the job of how to search for grants, and qualifying what it finds is the job of funder research using Form 990.

Frequently asked questions

What is a realistic grant win rate?

Win rate depends almost entirely on funder mix. Federal research competition and general nonprofit grantseeking differ by roughly an order of magnitude, and the two are measured differently — NIH publishes success rates, NSF publishes funding rates, and surveys usually report the share of organizations winning anything. Any single portable win rate is meaningless without naming the mix.

How many grants should we apply for each year?

Enough to hit the target implied by your win rate, and no more than your hours support. Survey data shows the likelihood of winning at least one award rising sharply from one application to three to five and again to six to ten, but that gain assumes each application passed a qualification gate.

Should post-award work be in the grant pipeline?

Yes. Post-award reporting, financial management, and compliance consume the same staff hours as pursuit, and excluding them from the capacity model is how organizations end up winning more than they can administer. The post-award stage belongs in the pipeline with a named owner.

What should trigger a no-go decision?

Failing any hard gate — eligibility, geography, undocumentable cost share, or a compliance load the organization cannot carry — ends a pursuit regardless of the award size. Soft factors such as fit, relationship, and expected value per hour are scored rather than gated, and the score is recorded either way.

How far ahead should a pipeline be built?

Far enough that no pursuit begins inside the posted window. Federal opportunities can be open for as little as the regulatory floor, registration takes business days to activate, and multi-partner applications need weeks for commitments. Forecast records and prior-year announcements are how the pipeline gets built ahead of the calendar.

Related topics

• Finding and Qualifying Funding — the hub for search strategy, funder research, and pipeline construction
• How to Read a NOFO
• Free Grant and Funder Data Sources
• The Grant Readiness Assessment

Sources

1. GrantStation. The 2026 State of Grantseeking Report (n=1,354; reports on grantseeking during 2025). https://grantstation.com/sites/default/files/imageLibrary/SoG/2026/2026%20State%20of%20Grantseeking%20Report.pdf (accessed 2026-08-11)
2. National Institutes of Health. Fiscal Year 2025 by the Numbers: Extramural Grant Investments in Research. NIH Extramural Nexus. https://grants.nih.gov/news-events/nih-extramural-nexus-news/2026/03/fiscal-year-2025-by-the-numbers-extramural-grant-investments-in-research (accessed 2026-08-11)
3. National Institutes of Health. RePORT — Success Rates. https://report.nih.gov/funding/nih-budget-and-spending-data-past-fiscal-years/success-rates (accessed 2026-08-11)
4. U.S. National Science Foundation. NSF Funding Profile (budget summary tables; definition of funding rate). https://nsf-gov-resources.nsf.gov/files/04_fy2025.pdf (accessed 2026-08-11)
5. U.S. National Science Foundation. FY 2025 Agency Financial Report (competitive proposal, award, and funding-rate trends, Table 1.1). https://nsf-gov-resources.nsf.gov/files/FY-2025-Agency-Financial-Report_0.pdf (accessed 2026-08-11)
6. U.S. National Science Foundation. Proposal and Award Process Timeline (PAPPG 24-1, Exhibit III-1). https://nsf-gov-resources.nsf.gov/files/PAPPG-24-1-ex3_1_0.pdf (accessed 2026-08-11)
7. National Institutes of Health. Standard Due Dates. https://grants.nih.gov/node/1091 (accessed 2026-08-11)
8. U.S. Office of Management and Budget. 2 CFR 200.204 — Notices of funding opportunities. eCFR. https://www.ecfr.gov/current/title-2/subtitle-A/chapter-II/part-200/subpart-C/section-200.204 (accessed 2026-08-11)
9. U.S. General Services Administration. Entity Registration. SAM.gov. https://sam.gov/entity-registration (accessed 2026-08-11)
10. Grants.gov. Check Application Status. https://www.grants.gov/help/applicants/check-application-status (accessed 2026-08-11)
11. Office of Information and Regulatory Affairs. Information Collection Request 202606-1894-001, Generic Application Package for Departmental Generic Grant Programs. reginfo.gov. https://www.reginfo.gov/public/do/PRAViewICR?ref_nbr=202606-1894-001 (accessed 2026-08-11)