Grant Program Management: What It Means to Run a Grant Program (Not Just Receive One)

A foundation that awards $500,000 in grants without written selection criteria has not run a grant program - it has made a series of personal decisions with the organization’s money, creating self-dealing exposure under IRC 4941 if any award benefited a disqualified person, taxable expenditure exposure under IRC 4942 if any award cannot be documented as serving a charitable purpose, and reputational exposure if the lack of documented criteria becomes public in a funding dispute.

Grant program management is the operational infrastructure that converts charitable intent into legally defensible, organizationally sustainable grantmaking. For foundations and government agencies that run grant programs, this infrastructure is not optional - it is the difference between a grant program and a discretionary fund.

Grant Program Management vs. Grant Administration

The term “grants management” is used by both grantees (nonprofits managing their received grants) and grantmakers (foundations managing their grant programs). The operational requirements are nearly opposite.

Grant administration - the grantee perspective - involves receiving an award, complying with its conditions, documenting expenditures, submitting reports, and satisfying the funder. The grantee answers to the funder’s requirements.

Grant program management - the grantmaker perspective - involves designing award criteria, soliciting and reviewing applications, selecting grantees, executing grant agreements, monitoring grantee performance, and reporting on overall program outcomes to the grantmaker’s board and funders. The grantmaker answers to its own governing documents, its board, and (for private foundations) to the IRS.

The distinction matters when a nonprofit transitions from receiving grants to awarding them - for example, a community development organization that receives a federal grant to administer a small business lending program and must re-grant a portion to qualifying businesses. That organization is simultaneously a grantee (managing the federal award) and a grantmaker (awarding sub-grants). The operational requirements of each role must be managed separately.

What Running a Grant Program Operationally Requires

A functioning grant program requires five operational components. Organizations that have a grant budget but lack any of these components are operating at legal and reputational risk.

1. Written program guidelines. A document that describes: the program’s charitable purpose, eligibility requirements for applicants (geographic scope, organizational type, project type), award size range and typical grant period, application process and timeline, and selection criteria. Without written guidelines, selection decisions cannot be defended as objective, and the program cannot scale without degrading consistency.

2. Application and review system. A process for receiving applications (online form, email submission, letter of inquiry followed by full proposal), reviewing them against documented criteria, and documenting the selection rationale. At minimum, each application requires a written review record showing how it was evaluated against the stated criteria.

3. Grant agreement infrastructure. A standard grant agreement template that includes: the award amount, grant period, permitted use of funds, reporting requirements, conditions the grantee must meet, and the grantmaker’s right to require repayment if funds are misused. The grant agreement is the legal instrument that makes monitoring enforceable.

4. Grantee monitoring system. A process for confirming that grantees used funds for the stated purpose, met reporting deadlines, and satisfied any special conditions. For private foundations, this is not optional - it is required to avoid taxable expenditure classification under IRC 4942.

5. Program reporting system. A process for aggregating grantee outcomes data and reporting on program performance to the board, to the foundation’s own funders (if applicable), and to the public through Form 990-PF or the foundation’s website.

Grant Program Policies: What You Need in Writing Before the First Award

Before making any grant, a grantmaking organization needs four written policies.

Grant program policy: defines the program’s purpose, eligibility criteria, geographic scope, award types and sizes, and funding cycle. This document is typically public-facing - it is what prospective grantees read to determine whether to apply. It should be approved by the board before the program opens.

Conflict of interest and anti-self-dealing policy: identifies who is a disqualified person under IRC 4941 (for private foundations) or who has a conflict of interest (for public charities and government agencies), and the procedure for disclosing and managing conflicts. For private foundations, the policy must prohibit all self-dealing transactions, not just “material” ones - IRC 4941 applies to any direct or indirect transaction between the foundation and a disqualified person regardless of dollar amount.

Expenditure responsibility policy: for private foundations that intend to make grants to organizations that are not public charities - foreign organizations, LLCs, for-profit companies, or other non-qualifying organizations - the expenditure responsibility procedures required under IRC 4945 must be documented before making such awards. Expenditure responsibility requires a pre-grant inquiry into the organization’s use of the funds, a written grant agreement with specific IRS-required terms, grantee reporting to the foundation, and annual reporting on Form 990-PF Schedule I.

Grantee monitoring and reporting policy: defines what grantees must report, how often, and in what format, and the procedure for reviewing reports and documenting the review. A monitoring policy that is not actually implemented provides no legal protection - courts and the IRS look at practices, not policies.

Application Review Systems: How to Structure Selection Without Bias

Application review systems that lack documented criteria and scoring are vulnerable to challenges - from declined applicants, from the IRS on audit, and from the foundation’s own board when a funding decision is questioned.

A defensible application review system includes:

Documented criteria with weights: explicit selection factors (alignment with program goals, organizational capacity, clarity of approach, community need, sustainability plan) with relative weights. These criteria should appear in the program guidelines so applicants know what is being evaluated.

Standardized review instrument: a written scoring rubric that reviewers complete for each application, scoring each criterion on a defined scale. The rubric creates a written record of why applications were funded or declined and allows comparison across applications.

Reviewer conflict declaration: before reviewing any application, each reviewer declares any relationship with the applying organization. Any reviewer with a conflict recuses from that application’s review. The recusal is documented.

Review documentation retained: completed review rubrics for all applications - funded and declined - retained in the program files. This documentation is requested by auditors and may be subpoenaed in litigation.

Decline notice requirements: applicants who are declined should receive a written notice. The level of feedback provided (no feedback, brief rationale, detailed feedback) is a program policy decision. Whatever the policy, it should be applied consistently.

For private foundations, the IRS may examine application review records during an audit to confirm that grants were awarded on an objective, charitable basis rather than to benefit disqualified persons. Documented criteria, independent review, and retained decision records are the primary defense.

Award Documentation: What the Grantee File Must Contain

The grantee file for each award is the grantmaker’s compliance record. For private foundations, it is the documentation that grants were made for charitable purposes. For government grantmakers with pass-through federal funds, it satisfies the documentation requirements of 2 CFR 200.332.

Each grantee file should contain:

• The completed application or letter of inquiry
• All supplemental materials submitted (financials, IRS determination letter, organizational information)
• The completed review rubrics and scoring documentation
• The board or committee resolution approving the award
• The fully executed grant agreement (both parties signed)
• All correspondence with the grantee from application through closeout
• All progress and final reports submitted by the grantee
• Documentation of the program officer’s review of each report
• Any modification requests and approvals
• Documentation of grantee monitoring activities (site visit notes, phone call logs, review of financial statements)
• Final payment confirmation

If a grant is subject to expenditure responsibility requirements, the file must also contain the pre-grant inquiry documentation, the IRS-required grant agreement terms, and the grantee’s verified reports.

Grantee Monitoring: The Legal Requirements and Practical Approaches

Grantee monitoring requirements differ based on the grantmaker’s legal structure.

Private foundations must ensure that grants serve the stated charitable purpose to avoid taxable expenditure classification under IRC 4942. The minimum monitoring standard: the foundation must receive a report from each grantee describing how funds were used and confirming that the grant was used for the purposes stated in the application. The program officer must review the report and document the review. A grant that receives no report and generates no monitoring documentation is a taxable expenditure risk.

Public charities that make grants (community foundations, federated funders, social venture funds) have no IRC 4942 obligation but typically maintain monitoring for accountability and board reporting purposes.

Government agencies with pass-through federal funds have the most prescriptive monitoring requirements. Under 2 CFR 200.331-200.332, pass-through entities must: review financial reports and performance reports submitted by subrecipients, monitor subrecipient activities to ensure compliance with federal requirements, perform risk-based monitoring procedures calibrated to the subrecipient’s prior performance and audit history, and review subrecipient Single Audit reports when the subrecipient expends $1,000,000 or more in federal funds (raised from $750,000 for fiscal years ending September 30, 2025 or later) in a year.

Practical monitoring approaches for foundations:

Report review: the minimum. A grantee submits a progress or final report; the program officer reads it, notes any concerns, and files it in the grantee record. For grants below $25,000 with low-risk grantees, this is typically adequate.

Site visit: for grants above $50,000 or grants where program delivery complexity warrants it. A visit to the grantee’s program site to observe delivery, review records, and meet with staff. Site visit notes are filed in the grantee record.

Financial review: for larger awards or grantees with prior compliance concerns. Review of the grantee’s financial statements or audit report to confirm financial health and appropriate use of funds.

Risk-based monitoring: calibrating monitoring intensity to grantee risk factors - new organization, weak prior financial reports, complex program model, organizational leadership change. Higher-risk grantees receive more intensive monitoring; lower-risk, track-record grantees receive lighter-touch oversight.

Reporting to Your Own Funders About Grant Program Outcomes

Many grantmaking organizations are themselves grant-funded - community foundations receiving government contracts, federated funders like United Way chapters receiving campaign distributions, government agencies with federal and state appropriations. These organizations are simultaneously grantmakers and grantees, and they must report upward on their grant program outcomes in addition to reporting downward to their own grantees.

The reporting challenge: aggregate outcome data across a portfolio of grantees requires standardized outcome measures across all awards. If each grantee reports in their own format with their own metrics, aggregating portfolio performance requires manual data transformation that is slow and error-prone.

A grant program designed for upward reporting requires:

Standardized outcome measures: a defined set of outcomes that all grantees in the program are expected to report, built into the grant agreement and reporting template from the start. Grantees report against these shared measures; the grantmaker aggregates across the portfolio.

Reporting template: a standardized form that collects the required data points in a consistent format, reducing grantee interpretation variance.

Data aggregation system: a grants management platform (Fluxx, Submittable, Foundant) or a structured data collection process that enables portfolio-level reporting without manual data entry. Organizations that collect grantee reports as PDF attachments and summarize them manually for board reports are one person’s departure away from a reporting failure.

Attribution language: in the grantmaker’s report to its own funders, clear language about what outcomes are attributable to the grant program versus other factors. Funders that expect attribution claims the grantmaker cannot support are setting up a compliance problem; setting expectations about what the data shows (grantee-reported outcomes, not independently verified causal claims) protects against that problem.

DEFINITION

Grantmaker

An organization that awards grants to other organizations or individuals - foundations, government agencies, corporate giving programs. Distinct from grantees (organizations that receive grants). Grant program management is the discipline of running a grant program as a grantmaker.

DEFINITION

Self-dealing

Under IRC 4941, any direct or indirect financial transaction between a private foundation and a disqualified person (substantial contributors, foundation managers, certain family members). Self-dealing transactions are subject to excise taxes regardless of whether the transaction is at fair market value.

DEFINITION

Taxable expenditure

Under IRC 4942, expenditures by a private foundation that do not serve a charitable purpose, including grants to non-qualifying organizations without expenditure responsibility procedures, grants to individuals without IRS approval, and grants for non-charitable purposes. Taxable expenditures are subject to a 20% excise tax on the foundation.

DEFINITION

Expenditure responsibility

The set of pre-grant due diligence, grant agreement, and monitoring procedures that allow a private foundation to make grants to non-public-charity organizations (such as for-profit companies or foreign organizations) while avoiding taxable expenditure classification under IRC 4942. Requires a written grant agreement, reporting by the grantee, and annual reports to the IRS on Form 990-PF.

DEFINITION

Grantee monitoring

The process by which a grantmaker verifies that grantees are using funds for the stated charitable purpose and meeting the conditions of the grant agreement. For private foundations, adequate monitoring is required to avoid taxable expenditure classification; for government grantmakers with pass-through federal funds, monitoring is required under 2 CFR 200.331-200.332.