Demonstrating Organizational Capacity

Organizational capacity is the proposal section answering whether an applicant has already done work of this kind at this scale. Reviewers weigh verifiable artifacts — audited financials, named staff with percent effort, prior award performance, signed commitments — far above assertions of enthusiasm or intent.

Current figures — verified 2026-08-11

Item	Value	Source
NIH Early Stage Investigator eligibility window	Within 10 years of the terminal research degree or end of post-graduate clinical training, with no prior substantial NIH independent research award	NIH Early Stage Investigator policy
Audited financial statements NSF may request from a prospective new awardee	Previous two years	NSF, Information for Prospective New Awardees

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

Key takeaways

• Capacity is proved by artifacts, not adjectives.
• Federal agencies run a separate risk review outside peer review.
• An unnamed project director is an unscoreable project director.
• Letters of commitment name a resource; letters of support name a feeling.
• New organizations borrow capacity rather than claim it.

What is organizational capacity in a grant proposal?

Organizational capacity is the part of a grant proposal that proves the applicant can execute the work described everywhere else in the application. Funders read it as a risk assessment covering six things: track record, staffing, systems, financial stability, governance, and partnerships. The section carries a burden of demonstration, not description.

The capacity section sits at a specific point in the argument that runs through every part of a grant proposal: the need is real, the design would address it, and the applicant can actually run it. A proposal can win the first two and lose on the third, and reviewers say so in plain language. The Tinker Foundation lists among its published reasons for declining a request that “the applicant organization does not appear to have the capabilities or credibility to execute the work,” singling out proposals for work outside an applicant’s existing geographies or communities (Tinker Foundation).

Organizational capacity breaks into six components that reviewers evaluate separately, and a strong showing in one does not compensate for a gap in another:

1. Track record. Work of comparable type, population, and scale, with numbers attached.
2. Staffing. Named people, their qualifications, and the share of their time the project buys.
3. Systems. Accounting, procurement, time-and-effort documentation, and data collection that already run.
4. Financial stability. Reserves, audit history, and the ability to operate while waiting for reimbursement.
5. Governance. A board that meets, sets policy, and reviews finances.
6. Partnerships. Documented commitments from organizations whose participation the design depends on.

What evidence of organizational capacity do reviewers accept?

Reviewers accept evidence that a third party could verify without taking the applicant’s word for it. Program data from the applicant’s own records, audited statements, prior award numbers, signed commitments, and named personnel all qualify. Statements of dedication, mission alignment, and readiness do not, because they are unfalsifiable.

The table below pairs common capacity claims with the artifact that converts each one from assertion into evidence. Every row on the left appears in real proposals unaccompanied; every row on the right is what makes it count.

Capacity claim	Artifact that proves it
Long service to this population	Unduplicated participants served by year, from program records
Staff have the right expertise	Named biosketches or résumés, with percent effort in the budget
The organization is financially stable	Audited financial statements, operating reserve in months
Federal funds are managed well	Prior award numbers, closeout dates, clean audit findings
Partners are committed	Signed commitment letters naming resource, quantity, duration
Systems already exist	Written procurement, payroll, and cash management policies
The board governs actively	Meeting frequency, committee structure, board-approved policies
The organization can scale	The last scale-up, with before-and-after numbers

Candid’s summary of what funders look for in a proposal makes the financial half of this explicit: funders “want to see that the organization is financially sustainable; they want to see who else has invested in the program; and they want to offer support to an already viable and well-supported program” (Candid). Co-investment is itself a capacity signal, because it means someone else already conducted diligence.

Quantity of evidence is not the goal. Three specific, verifiable claims outperform two pages of organizational history, and the history belongs here rather than in the statement of need, where it displaces the community condition the funder asked about.

How do federal agencies assess organizational capacity before an award?

Federal agencies assess organizational capacity twice: once through peer review of the proposal narrative, and once through an administrative risk review that the applicant never sees. The Uniform Guidance directs agencies to evaluate financial stability, quality of management systems, history of performance on prior awards, audit findings, and the ability to implement statutory and regulatory requirements (2 CFR 200.206).

The same rule requires agencies to check the non-public segment of SAM.gov before making an award where the federal share is expected to exceed the simplified acquisition threshold, and states that the record “must demonstrate a satisfactory record of administering programs or activities under Federal financial assistance or procurement awards, and integrity and business ethics” (2 CFR 200.206). An agency may still fund an applicant whose record falls short, but only by attaching specific conditions that mitigate the risk (2 CFR 200.208).

Agencies apply the same logic to organizations they have not funded before. NSF states that it “will determine if your organization is financially viable, including an ability to sustain normal operations without NSF funding,” and may request audited financial statements, income statements, cash flow statements, and federal tax returns (NSF, Information for Prospective New Awardees). NSF also reviews whether an accounting system can classify costs as direct, indirect, or unallowable as they are incurred and track them by award (NSF, Accounting System Reviews). Organizations new to NSF, or without an active award in the previous five years, should expect a request for organization and management information (NSF PAPPG).

The practical consequence is that the capacity narrative and the back-office reality have to match, because a separate office checks the second one. Internal controls described in a proposal but absent in practice surface at the first monitoring visit.

How should a proposal present key personnel and percent effort?

Key personnel should be presented by name, with a qualifications summary, a defined role, and a percentage of effort that appears identically in the budget. Reviewers evaluate whether specific people can do specific tasks. An unnamed position offers nothing to evaluate, which is why a to-be-hired project director reads as risk rather than flexibility.

Federal criteria are written at that level of specificity. The Department of Education’s general selection criteria direct reviewers to consider the project director’s “qualifications, including relevant training and experience,” and separately the qualifications of other key personnel, alongside the “extent to which the time commitments of the project director and principal investigator and other key project personnel are appropriate and adequate to meet the objectives of the proposed project” (34 CFR 75.210). NIH’s simplified review framework asks reviewers to “evaluate whether the investigator(s) have demonstrated background, training, and expertise, as appropriate for their career stage, to conduct the proposed work,” and to identify gaps explicitly when they exist (NIH).

Four presentation choices carry most of the weight in the key personnel subsection:

1. Biosketches, not résumés. A biographical sketch summarizes qualifications relevant to the proposed project; NIH’s version is generated through SciENcv and paired with a supplement (NIH). A general CV forces the reviewer to do the selection work.
2. Percent effort stated once, consistently. The effort in the narrative, the effort in the budget justification, and the effort in any commitment letter must be the same number.
3. Named where possible, staged where not. If a role must be filled after award, name the supervisor, the qualifications required, the hiring timeline, and who covers the work in the interim.
4. An organizational chart plus a management plan. The chart shows reporting lines; the management plan shows milestones, responsibilities, and decision points. The Department of Education criteria ask for “clearly defined responsibilities, timelines, and milestones for accomplishing project tasks” (34 CFR 75.210).

Is a letter of commitment stronger than a letter of support?

A letter of commitment is stronger than a letter of support because it names a resource the signer will provide. A letter of support conveys endorsement and says nothing verifiable. Reviewers weight the two differently, and some agencies accept only one of them.

The table below distinguishes the four letter types that appear in grant proposals, with what each one actually establishes.

Letter type	What it establishes
Commitment	A named resource, quantity, and duration the signer will provide
Collaboration	Intent to collaborate or commit resources described in the proposal
Support	Endorsement of the project’s importance
Reference	An individual’s qualifications, typically for fellowships and career awards

Agency rules diverge sharply. NSF prescribes a single-sentence format for letters of collaboration — an intent “to collaborate and/or commit resources as detailed in the Project Description or the Facilities, Equipment and Other Resources section” — and states that letters of collaboration “should be limited to stating the intent to collaborate and should not contain endorsements or evaluation of the proposed project.” NSF adds that unauthorized letters of support “may be returned without review” (NSF PAPPG).

Research development offices summarize the distinction the same way: a commitment letter “indicates the signatory’s intent to commit resources to the funded project as specified in the letter,” while a support letter “expresses the organization’s knowledge and support of the project” (University of Chicago Office of University Research Administration).

Research administration guidance summarizes the same split: a commitment letter “documents an institution’s formal participation in a project and specifies the resources or responsibilities being committed,” while a support letter “expresses endorsement of the proposed project” and “does not obligate institutional resources” (University of Texas at El Paso Research Development).

Two mechanical rules apply regardless of funder. The signer must have authority over the resource being promised, and the number in the letter must match the number in the narrative and budget. A mismatch between a partner’s stated contribution and the applicant’s budget is one of the few discrepancies a reviewer can catch in a single pass.

How do you show organizational capacity when the organization is new?

A new organization shows capacity by borrowing it, by presenting adjacent track record honestly, and by proposing a scope proportionate to what it has actually run. The capacity section rewards incumbency, and pretending otherwise wastes the page. The workable strategies are structural rather than rhetorical.

There are five legitimate routes for an organization without a matching track record:

1. Fiscal sponsorship. A fiscal sponsor supplies legal status, audited financials, and accounting systems, and becomes the accountable recipient. Name the sponsor and the division of responsibilities explicitly rather than obscuring the arrangement.
2. Partner-held capacity. Place the functions the organization lacks with a partner that has them, and document the arrangement with a commitment letter and a budget line, not a mention.
3. Adjacent track record. Individual staff experience counts when it is attributed and dated. Work done by named staff at prior employers is evidence about those staff, and should be labeled as such.
4. Staged scale-up. Propose a first phase at a scale the organization has demonstrably run, with defined criteria for expanding. Reviewers discount a proposal that jumps an order of magnitude with no intermediate step.
5. Named new capacity. State plainly what the grant would build, who would build it, and by when. An acknowledged gap with a plan reads better than a silent one a reviewer discovers.

Some funders build counterweights into the process. NIH identifies Early Stage Investigators and prioritizes meritorious R01-equivalent applications from them for funding (NIH). Others reserve tracks for first-time applicants or smaller organizations. Finding those tracks is a search problem rather than a writing problem, and it belongs in the readiness stage rather than the drafting stage.

How does prior award performance follow an organization?

Prior award performance follows an organization through federal records that later reviewers and awarding officials consult directly. Late reports, unresolved audit findings, and closeout problems are recorded in the responsibility and qualification records agencies must review before making an award (2 CFR 200.206).

Performance also enters the proposal itself. NSF requires results from prior NSF support for each principal investigator and co-principal investigator covering the previous five years, reported under separate Intellectual Merit and Broader Impacts headings (NSF PAPPG). A prior award described without results is a weakness a reviewer will name.

Audit history carries the longest tail. Findings from audits conducted under the Uniform Guidance are one of the five risk factors agencies weigh, which means a repeat finding can shape award conditions years later (2 CFR 200.206). Organizations approaching the Single Audit threshold should treat the resulting record as a permanent part of their capacity narrative.

Positive performance compounds in the same way. A closed award with met targets, clean reports, and a final report that reads as candid is the single most efficient capacity artifact an organization can hold, and it costs nothing beyond doing the work properly.

What goes wrong in the organizational capacity section?

Capacity sections fail in predictable ways, and most failures substitute a claim for an artifact. The seven most common are avoidable at the drafting stage without new evidence.

1. Aspiration in place of track record. Commitment, passion, and readiness are not scoreable. Replace each with a number and a date.
2. An unnamed principal investigator or project director. Reviewers evaluate people. A vacancy at the top of the chart converts a scoreable criterion into an unknown.
3. Effort that contradicts the budget. A director at 50 percent in the narrative and 20 percent in the budget signals that nobody reconciled the documents.
4. Generic partner letters. Interchangeable letters with the same paragraphs signal that the applicant drafted them and the partner did not read closely.
5. Organizational history relocated into the needs statement. History belongs in capacity; the need belongs to the community.
6. Systems described in the future tense. “We will implement time-and-effort documentation” tells a reviewer that the system does not exist yet.
7. Scope disproportionate to demonstrated scale. Proposing to serve ten times the largest cohort the organization has ever served, with no intermediate stage, invites the feasibility objection.

Frequently asked questions

How long should the organizational capacity section be?

Capacity sections typically run one to three pages in a federal application and one or two paragraphs in a foundation proposal, but the funder’s stated limit governs. Length is less predictive than specificity: a one-page section with named staff, dated program data, and signed commitments outperforms a three-page organizational history.

Should a small organization disclose that it has never managed a federal award?

Yes, paired with what mitigates it — a fiscal sponsor, an experienced finance contractor, a partner acting as prime, or documented systems. Federal agencies check prior award history independently under 2 CFR 200.206, so an omission is discoverable. A named gap with a named mitigation is a stronger position than silence.

Can consultants count toward organizational capacity?

Consultants count when their role, qualifications, and effort appear in the narrative and the budget, and when the arrangement is documented. A consultant filling a core project role should be presented like any other key person. Capacity assembled entirely from consultants raises a durability question reviewers will ask.

What is the difference between capacity and readiness?

Capacity is the ability to perform the proposed work; readiness is the ability to receive and administer the award. Registrations, financial systems, and policies belong to readiness. Staff, track record, and partnerships belong to capacity. Funders assess both, and a proposal can pass one while failing the other.

Do foundations assess capacity as rigorously as federal agencies?

Foundations assess capacity less formally but often more consequentially, because a program officer’s judgment is not constrained by a published rubric. Site visits, financial statement review, and reference conversations with other funders serve the function that the federal risk review serves. Published decline reasons frequently cite capability and credibility directly.

Does a strong capacity section rescue a weak project design?

No. NIH’s reviewer guidance states that appropriate expertise and resources cannot make a project of limited importance more impactful, and that gaps in expertise can only worsen the overall score. Capacity is treated as a condition of feasibility in most rubrics, not as a source of upside.

Related topics

• Writing the Proposal — the hub covering what each proposal section is asked to prove
• The Anatomy of a Grant Proposal
• Writing the Project Design
• Writing for the Reviewer
• Writing a Sustainability Plan

Sources

1. Electronic Code of Federal Regulations, 2 CFR § 200.206, Federal agency review of risk posed by applicants. https://www.ecfr.gov/current/title-2/section-200.206 (accessed 2026-08-11)
2. Electronic Code of Federal Regulations, 2 CFR § 200.208, Specific conditions. https://www.ecfr.gov/current/title-2/section-200.208 (accessed 2026-08-11)
3. Electronic Code of Federal Regulations, 34 CFR § 75.210, General selection criteria. https://www.ecfr.gov/current/title-34/section-75.210 (accessed 2026-08-11)
4. U.S. National Science Foundation, “Information for Prospective New Awardees.” https://www.nsf.gov/awards/first-time-awardees (accessed 2026-08-11)
5. U.S. National Science Foundation, “Accounting System Reviews.” https://www.nsf.gov/awards/accounting-system-reviews (accessed 2026-08-11)
6. U.S. National Science Foundation, Proposal and Award Policies and Procedures Guide (NSF 24-1), Chapter II: Proposal Preparation Instructions. https://www.nsf.gov/policies/pappg/24-1/ch-2-proposal-preparation (accessed 2026-08-11)
7. National Institutes of Health, “Simplified Peer Review Framework.” https://grants.nih.gov/policy-and-compliance/policy-topics/peer-review/simplifying-review/framework (accessed 2026-08-11)
8. National Institutes of Health, Evaluating Applications Under NIH’s Simplified Review Framework. https://grants.nih.gov/sites/default/files/Simplified-Review-Reviewer-Guide-to-Evaluating-Applications.pdf (accessed 2026-08-11)
9. National Institutes of Health, “Early Stage Investigator Policies.” https://grants.nih.gov/policy-and-compliance/policy-topics/early-stage-investigators (accessed 2026-08-11)
10. National Institutes of Health, “Biographical Sketch Format Pages, Instructions and Samples.” https://grants.nih.gov/grants/forms/biosketch.htm (accessed 2026-08-11)
11. University of Chicago, Office of University Research Administration, “Letters of Commitment, Collaboration, and Support.” https://ura.uchicago.edu/resource-library/letters-commitment-collaboration-and-support (accessed 2026-08-11)
12. Tinker Foundation, “Why Was My Letter of Inquiry Declined?” https://tinker.org/why-was-my-letter-of-inquiry-declined/ (accessed 2026-08-11)
13. Candid, “Green Flags Funders Look For in Your Grant Proposal.” https://candid.org/blogs/green-flags-funders-look-for-in-your-grant-proposal/ (accessed 2026-08-11)
14. University of Texas at El Paso, Research Development, “Institutional Letters of Support, Commitment, and Collaboration.” https://www.utep.edu/research/proposal-development/proposal-development-process-and-timeline/letters-of-support.html (accessed 2026-08-11)