Building a Grants Function

A grants function is the standing machinery that finds, qualifies, wins, and administers grant funding. Building one means assigning eight recurring jobs to named people, running a pipeline and two calendars, maintaining a content library, and building post-award capacity before pursuit volume rises.

Current figures — verified 2026-08-11

Item	Value	Source
Organizations where one to two people were directly involved in grantseeking (2026 edition)	67.1% of respondents	GrantStation, 2026 State of Grantseeking Report
Won at least one award, by volume submitted (2026 edition)	64.5% at one application; 89.4% at three to five	GrantStation, 2026 State of Grantseeking Report
Award rate by funder type (2026 edition)	private foundations 81.2%; corporate 78.2%; community foundations 74.7%; federal 49.6%	GrantStation, 2026 State of Grantseeking Report
Median largest individual award (2026 edition)	$90,000 overall; $500,000 federal; $25,000 community foundation	GrantStation, 2026 State of Grantseeking Report
NIH research project grant success rate	13.0% (FY2025), from 18.5% (FY2024) and 21.3% (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
Circulated estimate of hours per proposal	15–20 foundation; up to or over 100 federal	Instrumentl, compiling Charity Science
Practitioner estimate of hours per proposal	15–25 for a short foundation proposal; 100+ for federal or capital	Puget Sound Grantwriters Association
Conventional cost to raise one dollar	grants $0.20; major gifts $0.05–$0.10; events $0.50 of gross; direct mail acquisition $1.00–$1.25	Greenfield benchmarks, via ABHE
Single Audit threshold	$1,000,000 in federal awards expended per fiscal year	2 CFR 200.501

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

Key takeaways

• Eight jobs always exist; maturity means naming who owns each.
• Build the post-award compliance calendar before raising pursuit volume.
• Separate the people who win money from the people who administer it.
• Win rate is a portfolio metric dominated by funder mix, not writer skill.
• The content library, not the writer, is the durable organizational asset.

What is a grants function inside an organization?

A grants function is the standing set of people, decisions, and records that carries funding from prospect to closeout. Eight jobs exist in every organization that takes grant money, whether or not anyone is assigned to them, and a grants function is simply the state in which each job has a named owner.

The eight recurring jobs are prospect research, the go/no-go decision, project design, budget development, narrative writing, compliance review and submission mechanics, post-award financial management, and post-award programmatic reporting and closeout. In an organization without a grants function, jobs one through six get done in a rush and jobs seven and eight get done badly, late, or not at all.

A grants function is not a person. Treating it as a person — “we hired a grant writer, so we have a grants program” — is the most common structural mistake in the field, because six of the eight jobs sit outside writing. The rest of managing the award describes what those six actually require.

Scale sets the shape, not the existence, of the function. Survey data from grantseeking organizations shows most run the entire process with very few people involved (see current figures above), which means the design question at small scale is not “how do we staff eight roles” but “which handoffs will we write down.”

How does a grants function mature, and in what order do you build it?

A grants function matures along a ladder from opportunistic to systematic. At the opportunistic end, someone writes a proposal when they hear about an opportunity. At the systematic end, a pipeline, two calendars, a content library, and a documented decision process operate whether or not any individual is present.

The order of construction matters more than the speed. Six steps, built in sequence, produce a function that survives staff turnover:

1. Build the post-award compliance calendar first. Every financial report, performance report, subaward report, inventory cycle, audit date, and closeout clock for every award already held. Federal closeout obligations run on defined deadlines (2 CFR 200.344), and the calendar is what makes them survivable.
2. Stand up the pipeline. A single record per opportunity with funder, deadline, ceiling, eligibility finding, owner, and stage. Stage definitions are covered in building a grant pipeline.
3. Write the go/no-go rubric and publish the weights. A documented, scored go/no-go decision with a named decider is what converts enthusiasm into capacity planning.
4. Assemble the content library. Organizational identity, financials, capability narratives, program modules, evidence with verification dates, policies, and archived submissions with reviewer feedback.
5. Add an internal review gate staffed by someone who did not write the proposal.
6. Separate pre-award from post-award ownership as soon as headcount allows.

Two calendars, not one, is the distinguishing mark of a mature grants function. The pursuit calendar holds deadlines, letters of inquiry, internal gates, and registration renewals. The compliance calendar holds every obligation created by awards already won. Organizations that keep only the first calendar lose money in the second.

Who does what in a grants function, and how do you source those roles?

Role assignment in a grants function follows headcount, but one boundary holds at every size: the people who win money should not be the only people who administer it. Pre-award optimizes for submission deadlines, post-award optimizes for reporting deadlines, and when one person holds both, post-award loses invisibly until an audit.

The table below shows how the eight jobs typically distribute across three scales of grants function.

Scale	Pre-award ownership	Post-award ownership	Structural risk
One person	One generalist	Finance and program staff	Handoff undefined
Small team	Director, writers, coordinator	Dedicated grants manager	Review gate skipped
Institutional office	Sponsored programs office	Sponsored projects accounting	No owner of the whole award

The institutional failure mode inverts the solo shop’s. Functions become so specialized that no one owns the award end to end, and closeout falls between the pre-award office and accounting. The federal side of that pattern is documented: the Government Accountability Office found approximately $994 million remaining in expired grant accounts in one federal payment system at the end of fiscal year 2015, with more than half of the affected accounts past their expiration date by one to three years, and attributed the delays to both grantee failure to submit final reports and agency failure to process them (GAO-16-362).

Sourcing follows the bottleneck, not the budget. Four patterns cover most situations: a project-based consultant when pursuit volume is low and program design is already solid; a consultant with federal specialization paired with an internal owner for a first federal pursuit; in-house staff once pursuits recur and funder relationships and the content library become the asset; and post-award or grants-management staff first whenever the organization is winning but drowning in reports. Professional bodies exist for each side — the National Grants Management Association for post-award and compliance, and NCURA for research administration.

What artifacts does a grants function need?

A grants function runs on seven artifacts, and the absence of any one of them shows up as rework. Artifacts are what survive turnover; institutional memory held in one person’s head is a single point of failure with a resignation date.

• Pipeline tracker. One row per opportunity, with stage, owner, deadline, ceiling, eligibility finding, and decision record — including the noes, which are the only source of trend data on what the organization declines.
• Two calendars. The pursuit calendar and the post-award compliance calendar, maintained separately because they compete for the same hours.
• Content library with version control. Every block carries an owner, a last-verified date, a source citation, and a record of which funder saw it. Statistics expire rather than age.
• Budget templates. Correct cost categories, fringe and indirect worksheets, and the organization’s indirect rate election documented once (2 CFR 200.414).
• Go/no-go rubric. Published weights, written anchors, a named decider, and a recorded rationale for every decision.
• Funder relationship record. Contacts, conversations, prior submissions, reviewer feedback, declines and their stated reasons, and reporting history.
• Compliance policy set. Written procurement, cash management, allowability, and time-and-effort procedures, which the Uniform Guidance effectively requires through the internal control standard (2 CFR 200.303).

Reviewer feedback deserves particular attention because it is the highest-value asset almost nobody indexes. A critique tagged to the specific content block it hit turns a decline into a library improvement. An untagged critique turns into a feeling.

How many proposals can one grant writer produce at quality?

Reliable public benchmarks for grant writer output are scarce, and any figure claiming precision should be treated skeptically. What a grants function can work from is per-proposal hour estimates published by practitioner sources, divided into available hours to model capacity rather than to measure it.

Two independent practitioner estimates converge on the same shape: short foundation proposals take tens of hours and federal proposals take a hundred or more (see current figures above, from Instrumentl compiling Charity Science, and from the Puget Sound Grantwriters Association). Neither is survey research. Both are worth using as planning anchors precisely because they agree.

The arithmetic that follows is modeling, not measurement. Start from a full-time person’s productive hours after leave, meetings, and administration. Subtract the hours that post-award administration consumes for awards already held — reporting, drawdowns, monitoring, closeout. Divide what remains by the per-proposal estimates for the organization’s actual funder mix. A federal-heavy portfolio yields a much smaller number than a foundation-heavy one at identical headcount, which is the whole point of doing the division rather than quoting an industry average.

Two constraints break the model in practice. First, proposals are not evenly distributed; federal deadlines cluster, and a calendar with three federal deadlines in one month cannot be staffed by an annual average. Second, quality is not linear in hours — the marginal proposal written by an exhausted person in the last week of a quarter is not the same product as the first one.

The honest planning rule is to size pursuit volume against post-award capacity rather than writing capacity. An organization that can write twelve proposals and administer four awards has a capacity of four.

What win rate should a grants function expect?

Win rate for a grants function is a portfolio metric shaped mostly by funder mix, competitiveness, prior relationship, and organizational track record. Treating win rate as a performance review of the writer produces bad management decisions, because the same person moving from foundation work to federal research competitions will see the number collapse for reasons unrelated to skill.

Comparison is harder than it looks because “win rate” is computed at least four incompatible ways: awards divided by applications submitted; applications funded divided by applications reviewed; the share of organizations receiving at least one award; and dollars awarded divided by dollars requested. The National Science Foundation defines its measure explicitly — “The Funding Rate is the number of awards made during a year as a percentage of total proposals competitively reviewed” (NSF Funding Profile) — reports it separately for all competitively reviewed proposals and for research proposals alone (NSF FY2025 Agency Financial Report), and the National Institutes of Health separates success rate from award rate for the same reason (NIH RePORT).

Three usable anchors exist, all in the current figures above. Federal research agencies publish program-level rates that are far lower than any general-purpose benchmark. Surveys of nonprofit grantseekers report award rates by funder type that are far higher, because they measure organizations receiving at least one award rather than proposals funded. And the same survey data shows that award likelihood rises sharply with application volume, from a single application to three to five.

The volume finding is the most actionable and the most easily misread. Moving from one pursuit to a small qualified portfolio changes outcomes substantially; moving to indiscriminate submission does not, because the added applications fail the fit test that drives the result. Volume paired with a go/no-go rubric is a strategy. Volume alone is a way to lose hours.

What does it cost to raise a dollar through grants?

Cost per dollar raised is fundraising expense divided by gross revenue for a channel. The convention the field quotes for grant writing comes from James Greenfield’s fundraising benchmarks, reproduced by the Association of Fundraising Professionals and most practitioner sources (see current figures above for the full method comparison).

Those benchmarks are decades old and should be cited as the field’s convention rather than as current measurement. There is also no standard for what belongs in the numerator: guidance from higher-education associations excludes the chief executive’s salary, IRS Form 990 uses different rules, and most organizations report functional-expense estimates rather than activity-based costs. One practitioner analysis of the metric puts the limitation plainly: “Using cost to raise a dollar as a tool to compare charities has no basis since there is no standard for computing the figure” (NonProfit PRO).

Four adjustments make the grant figure usable inside one organization. The conventional grant number assumes the grant is won, so the denominator excludes every losing proposal — in a federal environment with single-digit or low-double-digit success rates, blended pursuit cost is dramatically worse. It excludes post-award administration, which is a real recurring cost of the revenue. It ignores restriction, since a restricted dollar is worth less than an unrestricted one. And it ignores audit exposure: crossing the Single Audit threshold adds an annual obligation regardless of how cheaply the award was won (2 CFR 200.501).

Used as an internal, per-channel, year-over-year measure, cost per dollar raised tells a grants function whether it is getting more efficient. Used to compare organizations, the metric is noise.

What goes wrong when organizations build a grants function?

Six failure modes account for most grants functions that stall, and five of them are visible before the damage lands.

• A strong front end and no post-award capacity. The organization wins something it cannot administer, and the cost shows up as findings, disallowed costs, and staff attrition rather than as a missed proposal.
• One person holding both calendars. Pursuit deadlines are loud and reporting deadlines are quiet, so the quiet ones slip until the Single Audit surfaces them.
• No content library, only files. Every proposal restarts from a previous proposal, so an out-of-date service number propagates for years and eventually reaches a repeat funder who notices.
• Win rate treated as an individual metric. Leadership benchmarks a writer against a portfolio average from a different funder mix, and the organization retreats from competitive federal programs for the wrong reason.
• No recorded noes. Only wins get logged, so the pattern — the organization declines everything with a cost share requirement — never becomes visible enough to fix at the balance sheet.
• Hiring writing capacity to solve a program-design problem. No writer can make an undefined program fundable; that work belongs in organizational readiness first.

The pattern beneath most of these is sequencing. Organizations build the exciting half of the function and defer the boring half, then discover the boring half was the one carrying the legal obligation.

Frequently asked questions

What is the first hire for a grants function?

The first dedicated hire depends on the bottleneck. An organization with defined programs and no proposal capacity hires writing capacity. An organization already winning awards and missing reports hires post-award and compliance capacity first. Hiring a writer into a reporting backlog reliably makes the backlog worse by increasing award volume.

How do you separate pre-award and post-award work in a small team?

Separation at small scale means separating the calendar and the accountability, not the people. Assign post-award obligations to a named owner with protected hours, review the compliance calendar at a standing meeting the pursuit calendar cannot displace, and make final report submission a condition of opening the next pursuit for the same funder.

Do you need grants management software to build a grants function?

Software is not required to build a grants function, and it does not substitute for defined stages, owners, and decision records. A spreadsheet with disciplined stage definitions outperforms a system nobody updates. Tooling helps once volume makes manual tracking unreliable, which for most organizations arrives well after the process does.

How long does it take to build a grants function?

Building a working grants function is paced by documentation rather than hiring. The compliance calendar and pipeline can be built in weeks. The content library takes a full cycle of proposals and reports to populate honestly, since blocks are only trustworthy once verified against a real submission and a real report.

Should a board member be involved in grant decisions?

Board involvement belongs at strategy and relationship, not at opportunity selection. A board member’s funder contact is a scoring factor in the go/no-go rubric, not an override of eligibility or capacity. Boards add most value by approving the pursuit portfolio annually and asking whether post-award capacity matches the plan.

What does a grants function owe subrecipients?

A grants function that passes money through takes on monitoring obligations that scale with the subaward. Verification of exclusion status, subaward identification data, risk assessment, and follow-up on findings are all required of pass-through entities. The obligations are covered in subrecipient monitoring and belong on the compliance calendar from the first subaward.

Related topics

• Managing the Award — the hub covering reporting, prior approval, monitoring, audit, and closeout
• Hiring a Grant Writer
• Grant Reporting Requirements
• Building a Grant Pipeline
• The Grant Readiness Assessment

Sources

1. GrantStation, The 2026 State of Grantseeking Report, n=1,354 respondents; 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, March 12, 2026. 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, “NIH Success Rates,” RePORT. 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) — and 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)
5. Instrumentl, “Grant Statistics and Trends,” compiling Charity Science estimates of hours per proposal. https://www.instrumentl.com/blog/grant-statistics-and-trends (accessed 2026-08-11)
6. Puget Sound Grantwriters Association, “How to Hire a Freelancer.” https://www.grantwriters.org/nonprofit-resources/how-to-hire-a-freelancer/ (accessed 2026-08-11)
7. D. Clay Perkins, “How Much Does Fundraising Cost?”, Association for Biblical Higher Education, reproducing James M. Greenfield, Fund-Raising: Evaluating and Managing the Fund Development Process (1999) and AFP figures. https://www.abhe.org/wp-content/uploads/2025/02/D-Clay-_Perkins_Cost-to-Raise-a-Dollar.pdf (accessed 2026-08-11)
8. Duke Haddad, “Is Cost to Raise a Dollar an Important Metric?”, NonProfit PRO, September 13, 2019. https://www.nonprofitpro.com/post/is-cost-to-raise-a-dollar-an-important-metric/ (accessed 2026-08-11)
9. U.S. Government Accountability Office, Grants Management: Actions Needed to Address Persistent Grant Closeout Timeliness and Undisbursed Balance Issues, GAO-16-362, April 14, 2016. https://www.gao.gov/products/gao-16-362 (accessed 2026-08-11)
10. Office of the Federal Register, 2 CFR § 200.303, Internal controls, eCFR. https://www.ecfr.gov/current/title-2/section-200.303 (accessed 2026-08-11)
11. Office of the Federal Register, 2 CFR § 200.344, Closeout, eCFR. https://www.ecfr.gov/current/title-2/section-200.344 (accessed 2026-08-11)
12. Office of the Federal Register, 2 CFR § 200.414, Indirect costs, eCFR. https://www.ecfr.gov/current/title-2/section-200.414 (accessed 2026-08-11)
13. Office of the Federal Register, 2 CFR § 200.501, Audit requirements, eCFR. https://www.ecfr.gov/current/title-2/section-200.501 (accessed 2026-08-11)
14. National Grants Management Association. https://www.ngma.org/ (accessed 2026-08-11)
15. National Council of University Research Administrators. https://www.ncura.edu/ (accessed 2026-08-11)