The Documents Every Grant Application Needs

A grant application draws on a standing document library: proof the organization legally exists, proof of how it is governed, proof of how it handles money, proof of what it does, and attachments written fresh for each proposal. Built once and maintained, the library turns submission into retrieval.

Current figures — verified 2026-08-11

Item	Value	Source
SAM.gov entity registration renewal	Every 365 days	SAM.gov
States requiring charitable solicitation registration	40	National Council of Nonprofits
States requiring an audit in some circumstances	27, with thresholds from roughly $500,000 to $1,000,000 in revenue or contributions	National Council of Nonprofits
Single Audit trigger	$1,000,000 in federal awards expended per fiscal year	2 CFR 200.501
De minimis indirect cost rate	Up to 15% of modified total direct costs	2 CFR 200.414(f)
NIH letter of collaboration length limit	100 words	NIH NOT-OD-26-094

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

Key takeaways

• Most attachments are organizational facts, not writing. Build them once.
• A documentation file is the practical core of organizational readiness.
• Each document has an owner, a refresh cadence, and an expiry.
• Letters of support and letters of commitment are not interchangeable.
• One source of truth per fact; duplicated facts drift and get caught.

What is a grant documentation file?

A grant documentation file is the maintained set of organizational records and reusable narrative that grant applications repeatedly require. The file is not a proposal archive and not a shared drive of old submissions. It is a curated library in which every artifact has a named owner, a date it was last verified, and a date it expires.

The distinction matters because of how deadlines actually fail. Very little of a typical application is genuinely new writing. The determination letter, the board roster, the audited financials, the org chart, and the indirect cost documentation are facts about the organization that exist independent of any opportunity. When those artifacts are missing or stale, the work of finding them consumes the days that should have gone to the project design and the budget.

Two organizing rules make the file usable rather than merely complete. First, one source of truth per fact: the number of people served lives in exactly one place, and every proposal references it, because duplicated figures diverge and a repeat funder will notice the discrepancy. Second, expiration rather than archiving: a statistic or financial figure that has passed its review date is unusable, not merely old.

Which legal documents does a grant application require?

Legal documents establish that the applicant exists as a legal entity eligible to receive the award. Five artifacts cover almost every request:

• Articles of incorporation. The state-filed formation document, showing legal name and formation date. Funders check that the name matches the name on every other document.
• IRS determination letter. The letter recognizing exemption under section 501(c)(3). A replacement affirmation letter can be requested from the IRS, and status can be confirmed through Tax Exempt Organization Search (IRS).
• Employer Identification Number and Unique Entity Identifier. The federal identifiers used on every application. Federal applicants also need an active SAM.gov registration and UEI, which lapses on the renewal interval shown above.
• Form W-9. The taxpayer identification certification most private funders require before releasing a payment (IRS).
• State charitable solicitation registration. Most states require a charity to register before soliciting contributions from their residents (National Council of Nonprofits).

The common failure in the legal category is name mismatch. An organization incorporated under one name, operating under a second, and registered in SAM.gov under a third will trigger a rejection that looks arbitrary and is not. Applicants without their own exemption typically apply through fiscal sponsorship, in which case the sponsor’s legal documents are the ones submitted.

Which governance documents do funders ask for?

Governance documents show that the organization is controlled by a board rather than an individual. Funders request them to test independence, and reviewers read them faster than applicants expect.

The standard set is short. Bylaws establish how the board is constituted and how decisions are made. A board roster listing each member’s name, role, term, and professional affiliation is requested by most foundations; affiliations matter because they reveal both expertise and potential conflicts. A conflict-of-interest policy is the third, and the IRS is explicit about why one exists: the purpose is to “establish procedures that will offer protection against charges of impropriety involving officers, directors or trustees” (IRS). Federal recipients face a firmer version of the same requirement — written standards of conduct covering conflicts of interest in procurement are mandatory under 2 CFR 200.318(c).

Board minutes are requested less often, usually to evidence a specific authorization: approval of a budget, acceptance of an audit, or a resolution authorizing an official to sign. The common failure is a board roster listing people who have stopped attending. Refresh the roster at every annual meeting and after every resignation, not at proposal time.

Which financial documents do grant funders require?

Financial documents let a funder judge whether the organization can absorb and account for the money. The core set is five items, refreshed on a fiscal-year cycle.

• Audited or reviewed financial statements. The most common request. Requirements vary by state and by award size, and a Single Audit is triggered at the federal expenditure threshold shown above (2 CFR 200.501); see the Single Audit for what that examination covers.
• Form 990. The annual information return, which a tax-exempt organization must make available for public inspection along with its exemption application (IRS). Assume every funder has already read it.
• Current operating budget and prior-year actuals. Board-approved, showing the whole organization, not just the proposed project. Funders read the ratio of the request to total budget as a risk signal.
• Indirect cost documentation. Either a negotiated indirect cost rate agreement or a written record of the election to use the de minimis rate; the rules are in 2 CFR 200.414(f) and explained in indirect cost rates.
• Fiscal policies and procedures manual. The written procedures federal awards require, including procedures for payment and for determining the allowability of costs (2 CFR 200.302).

The common failure here is timing. Audited statements are typically finished months after fiscal year end, which means an application submitted early in a fiscal year is submitting a document that is more than a year old. Note the audit completion date on the file’s calendar and warn program staff before the gap becomes a surprise.

Which organizational and program documents belong in the file?

Organizational and program documents describe what the applicant is and what it does, and they are the portion of the documentation file that is genuinely written rather than filed. Six artifacts carry most of the load.

• Mission and history narrative. A dated, versioned paragraph set in short, medium, and long forms, so a 100-word field and a two-page section draw from the same facts.
• Organizational chart. Positions, reporting lines, and vacancies, which reviewers use to check that the proposed project has somewhere to live.
• Staff resumes and biosketches. Federal research applications use a prescribed format; NIH requires a biosketch for each senior or key person and provides format pages and the SciENcv tool for generating them (NIH).
• List of current funders and award history. Names, amounts, and periods. This underpins claims about organizational capacity and is trivially verifiable against a Form 990.
• Program descriptions with outcome data. Per program: population served, activities, service counts, and results, each with a citation and a verification date.
• Evaluation reports and logic models. Prior evaluations, plus a maintained logic model per program that can be adapted rather than reinvented.

The common failure in this category is unlabeled staleness. A service-count statistic with no verification date will be reused for years past the point where it is true, and the first funder to check it against a Form 990 will find the discrepancy.

Which documents are assembled per application?

Per-application documents are the ones that cannot be pre-built because they refer to a specific project, partner, or piece of equipment. Six recur across programs.

• Letters of commitment. A partner states what it will do, for whom, and at what value. Commitment letters carry weight because they are enforceable in spirit and specific in content.
• Letters of support. A third party endorses the applicant without promising anything. Endorsement letters are the weakest attachment in a proposal, and some funders have moved against them: NIH has directed that applications document actual collaboration rather than endorsement, capping each letter at the length shown in the figures above and stating that letters “designed to endorse the application without an intent to collaborate or provide material support” are not permitted (NIH NOT-OD-26-094).
• Memoranda of understanding. Signed agreements with partners specifying roles, data sharing, and money flow. Required whenever a partner receives a subaward.
• Job descriptions. For each grant-funded position, matching the title, effort, and salary in the budget.
• Vendor quotes. For equipment and major purchases, supporting the price in the budget justification and the documented procurement procedures federal awards require.
• Human subjects approvals. Institutional Review Board documentation where the project involves human subjects research, under the federal protections at 45 CFR 46.

The common failure is the identical support letter. Five partners submitting the same paragraph with different letterhead tells a reviewer that the applicant wrote all five, which undercuts the collaboration the letters were meant to evidence.

How do you maintain a grant documentation file?

Maintaining a grant documentation file is a scheduled administrative task, not a project. Seven steps keep it usable:

1. Inventory what exists. List every artifact above, where it lives, and who owns it. Most organizations discover two or three are missing entirely.
2. Establish one location. A single folder structure that finance, program, and development all use. Two locations become two versions within a quarter.
3. Tag every artifact with metadata. Owner, date last verified, next review date, and source citation for anything numeric.
4. Set refresh cadences by type. Registrations on their statutory renewal dates; financials at audit completion; board roster at each annual meeting; program statistics annually; narratives when the program changes.
5. Version the narratives. Name each block by what it answers and what version it is, with a changelog noting why it changed — reviewer critique, new data, or a program change.
6. Index reviewer feedback. Score sheets and summary statements tagged to the narrative block they criticized. This is the highest-value asset in the library and the one almost nobody keeps.
7. Run a pre-deadline check. Before any submission, confirm registrations are active, the financial statements are the most recent complete set, and no cited statistic has passed its review date.

The payoff is measured in days. An organization with a maintained file spends its pre-deadline weeks on project design and budget; an organization without one spends them requesting a replacement determination letter and waiting for a partner to sign a letter drafted the night before.

What goes wrong with grant documentation?

Documentation failures are rarely dramatic. They are administrative, quiet, and disqualifying. Six patterns account for most of them.

• Lapsed registration. A SAM.gov registration that expired between opportunities makes a federal application impossible to submit, and reinstatement takes days that a deadline does not have.
• Name inconsistency. The legal name on the articles, the name in the federal registration, and the name on the letterhead must match exactly.
• Stale financials. Submitting statements two fiscal years old signals either an audit problem or an administration problem, and reviewers cannot tell which.
• Uncited program statistics. A number with no source and no date is unverifiable, and a funder that checks it against a public filing will find the mismatch.
• Letters that promise nothing. Endorsement collected where commitment was required, submitted without the applicant noticing the difference.
• Format noncompliance. Attachments that violate page limits, font rules, or file-naming conventions, which some systems reject automatically before a human reads anything.

Each of these is preventable by calendar rather than by effort, which is why the maintenance schedule is the substantive part of the practice and the file itself is only the artifact.

Frequently asked questions

Do you need a 501(c)(3) determination letter to apply for a grant?

For grants restricted to charitable organizations, yes — the applicant or its fiscal sponsor must be able to produce one. Government grants often extend eligibility to units of government, tribes, educational institutions, and sometimes for-profit entities, in which case the determination letter is irrelevant and the funding opportunity’s eligibility section controls.

How recent must audited financial statements be?

Most funders ask for the most recent completed audit, which is generally the prior fiscal year. Because audits finish months after year end, an application early in a fiscal year will legitimately submit older statements. Include the audit completion date so the funder can see the gap is normal.

What is the difference between a letter of support and a letter of commitment?

A letter of support endorses the applicant. A letter of commitment states a specific obligation: hours contributed, referrals made, space provided, cash matched, or data shared. Reviewers weight commitment far more heavily, and some funders now restrict or exclude pure endorsement letters entirely.

How often should the documentation file be refreshed?

By artifact type rather than on one schedule. Registrations refresh on their statutory renewal dates, financial statements when the audit closes, board rosters at each annual meeting, and program statistics at least annually. Any figure past its verification date should be treated as unusable until re-verified.

Do private foundations require the same documents as federal agencies?

The overlap is large but not complete. Private foundations concentrate on the determination letter, Form 990, audited financials, board roster, and organizational budget. Federal agencies add registration, prescribed forms, indirect cost documentation, and certifications, and they enforce format rules mechanically.

Who should own the documentation file?

One named person, typically in finance or operations rather than development, with authority to require updates from program staff. Files owned by “everyone” are owned by no one, and the failure shows up as a missing document three days before a deadline.

Related topics

• Eligibility and Organizational Readiness — the hub for eligibility, registration, and readiness
• The Grant Readiness Assessment
• Grant Eligibility Explained
• Internal Controls for Grant Recipients

Sources

1. Internal Revenue Service, Tax Exempt Organization Search. https://apps.irs.gov/app/eos/ (accessed 2026-08-11)
2. Internal Revenue Service, “About Form W-9, Request for Taxpayer Identification Number and Certification.” https://www.irs.gov/forms-pubs/about-form-w-9 (accessed 2026-08-11)
3. Internal Revenue Service, “Form 1023: purpose of conflict of interest policy.” https://www.irs.gov/charities-non-profits/form-1023-purpose-of-conflict-of-interest-policy (accessed 2026-08-11)
4. Internal Revenue Service, “Public disclosure and availability of exempt organizations returns and applications.” https://www.irs.gov/charities-non-profits/public-disclosure-and-availability-of-exempt-organizations-returns-and-applications-documents-subject-to-public-disclosure (accessed 2026-08-11)
5. General Services Administration, SAM.gov, “Entity Registration.” https://sam.gov/content/entity-registration (accessed 2026-08-11)
6. Electronic Code of Federal Regulations, 2 CFR 200.302, “Financial management.” https://www.ecfr.gov/current/title-2/section-200.302 (accessed 2026-08-11)
7. Electronic Code of Federal Regulations, 2 CFR 200.318, “General procurement standards.” https://www.ecfr.gov/current/title-2/section-200.318 (accessed 2026-08-11)
8. Electronic Code of Federal Regulations, 2 CFR 200.414, “Indirect costs.” https://www.ecfr.gov/current/title-2/section-200.414 (accessed 2026-08-11)
9. Electronic Code of Federal Regulations, 2 CFR 200.501, “Audit requirements.” https://www.ecfr.gov/current/title-2/section-200.501 (accessed 2026-08-11)
10. National Institutes of Health, “Biosketch Format Pages, Instructions, and Samples.” https://grants.nih.gov/grants-process/write-application/forms-directory/biosketch (accessed 2026-08-11)
11. National Institutes of Health, NOT-OD-26-094, “NIH Is Replacing Letters of Support with Letters of Collaboration to Reduce Administrative Burden.” https://grants.nih.gov/grants/guide/notice-files/NOT-OD-26-094.html (accessed 2026-08-11)
12. U.S. Department of Health and Human Services, Office for Human Research Protections, “45 CFR 46.” https://www.hhs.gov/ohrp/regulations-and-policy/regulations/45-cfr-46/index.html (accessed 2026-08-11)
13. National Council of Nonprofits, “Charitable Solicitation Registration.” https://www.councilofnonprofits.org/running-nonprofit/fundraising-and-resource-development/charitable-solicitation-registration (accessed 2026-08-11)
14. National Council of Nonprofits, “State Law Nonprofit Audit Requirements.” https://www.councilofnonprofits.org/running-nonprofit/nonprofit-audit-guidec/state-law-nonprofit-audit-requirements (accessed 2026-08-11)