Organizational capacity: proving you can deliver the grant

Every funder reading your proposal is weighing two questions at once: is this a good idea, and is this the right organization to carry it out? The rest of the proposal argues the first. The organizational capacity section argues the second, and it often decides close calls. A brilliant program design from an organization that looks shaky on staffing or finances is a risk most program officers will not take to their board.

The good news is that capacity is mostly about evidence you already have. The work is selecting the right evidence and connecting it to this specific project.

What reviewers are really looking for

Program officers and reviewers read capacity sections looking for reasons to trust you with money. That trust rests on five things:

1. Relevant track record. Have you done this, or something close to it, before? What happened?
2. People. Who will actually run the project, and are they qualified for it?
3. Governance. Is there a functioning board providing oversight?
4. Financial health and systems. Can you account for restricted money, track spending by grant, and survive a late reimbursement?
5. Partnerships. Are the outside organizations your plan depends on actually committed?

Federal agencies formalize this. Before making an award, a federal agency must review the risk posed by an applicant, and the Uniform Guidance at 2 CFR 200.206 lists what that review may consider: financial stability, the quality of management systems, history of performance on prior awards, audit reports and findings, and the ability to implement federal requirements. Private foundations rarely publish a list that explicit, but their due diligence covers the same ground.

Organizational background: history with a point

Most weak capacity sections open with a founding story and a list of every program the organization has ever run. Reviewers skim that. Instead, write your background so each sentence earns its place by supporting this project.

A useful structure:

• One or two sentences on who you are: mission, year founded, where you work, whom you serve, and scale (annual budget, people served).
• Your relevant experience: the programs most similar to the proposed project, with numbers and outcomes.
• Why you are positioned for this work: community relationships, specialized expertise, existing infrastructure, or data no one else has.

Quantify wherever you can, and use outcomes, not just activity counts. "We have served youth since 2009" says little. "Over the last three school years, 82 percent of the 410 students in our tutoring program improved at least one reading level, measured by district benchmark assessments" says a lot, if it is true and you can back it up.

Awards, accreditation, and recognition

Mention licenses, accreditations, and certifications that matter for the work (a licensed childcare provider, an accredited counseling agency, a HUD-approved housing counseling agency). Mention awards briefly and only if a funder would recognize them. A long list of minor honors reads as padding.

Prior grants

Naming other funders that have supported similar work can reassure a reviewer, because it signals someone else did due diligence. Name them only if you have permission or the grant is public, and be accurate about what each grant funded. If you have managed federal awards, say so and say how you performed: on-time reports, no audit findings, successful closeouts. That is exactly what a federal risk review looks for.

Staff qualifications: name names

The single most persuasive capacity evidence is a qualified, named person responsible for the project. Reviewers fund people as much as plans.

For each key role, give:

• Name and title (or "to be hired" with the hiring plan)
• Percent of time on the project, which must match your budget
• Relevant qualifications: years of directly relevant experience, credentials, language skills, lived experience in the community, and prior results

Keep each bio to three to five sentences in the narrative and put full resumes or biosketches in attachments if the funder allows them. Choose the qualifications that matter for this project. A program director's MBA is less relevant to a youth mentoring grant than her eight years running a mentoring program in the same neighborhood.

Positions you have not filled yet

It is normal to propose new staff. Reviewers want to see that you know what you are hiring for and how you will do it. Include a short position description, required qualifications, the salary (consistent with your budget), and a realistic hiring timeline. If someone is already identified, say so. Build the hiring time into your project timeline; a plan that assumes a new coordinator is serving clients in week one is not credible.

Staff the reader will not see

Funders also care about the back office. Briefly name who handles finance (an in-house finance director, a part-time bookkeeper plus an outside CPA, or a fiscal sponsor) and who handles grant reporting and data. For federal applications especially, this is where you show you can manage the compliance load. Our guide to post-award compliance explains what that load involves.

The board: governance as capacity

Funders read your board list to answer three questions: Is it independent? Is it engaged? Does it bring relevant skills?

Strong signals include:

• A board of reasonable size with members who are not staff or relatives of the executive director
• Members with finance, legal, and program-area expertise
• Members who reflect the community served
• Regular meetings with quorum, an audit or finance committee, and annual review of the executive director
• 100 percent board giving, at whatever level each member can manage

That last point comes up often in foundation applications. Many program officers ask whether every board member gives, because it signals the people closest to the organization believe in it. If you have full board participation, say so in one sentence.

For more on how boards can strengthen grant seeking without micromanaging it, see the board's role in grants.

Financial health signals

You do not need to be wealthy to look financially healthy. You need to look in control. Reviewers look at a handful of documents and signals.

Your Form 990 is public. Exempt organizations must make their annual information returns available for public inspection for three years, and services such as ProPublica's Nonprofit Explorer make them easy to find. Assume the program officer has read yours. If your 990 shows a deficit year, a big revenue swing, or a change in leadership, address it briefly and honestly in the proposal rather than hoping no one notices.

For federal funding, know where you stand on audits. A nonprofit that expends $1,000,000 or more in federal awards in its fiscal year must have a single audit under 2 CFR 200.501 (the threshold rose from $750,000 in the 2024 Uniform Guidance revisions). See our single audit guide for what triggers it.

Financial management systems

A sentence or two on how you manage grant funds can prevent a lot of reviewer worry. Mention your accounting software and whether it tracks expenses by grant, how you document staff time charged to grants, who approves expenditures, and that the board reviews financial statements regularly. Federal reviewers in particular are looking for systems that can meet the Uniform Guidance standards; our Uniform Guidance overview covers the basics.

Partnerships: show the commitment, not the friendship

Partners can make a project far stronger, or far riskier. If your plan depends on a school district providing referrals, a clinic providing screenings, or a university running the evaluation, the funder needs proof those partners are actually on board.

In the narrative, describe each key partner in two or three sentences:

• Who they are and why they are the right partner
• Exactly what they will contribute (staff, space, referrals, data, expertise, money)
• How the partnership will be managed (regular meetings, a steering committee, data-sharing agreements)
• History of working together, if any

Then back those descriptions up with documentation. That is where letters and agreements come in.

Letters of support vs. letters of commitment vs. MOUs

These three documents are often used interchangeably, but they do different jobs and carry very different weight with reviewers.

Letters of support

A good support letter is specific and personal. It explains how the writer knows your work and why this project matters to them or their constituents. A stack of identical form letters with different signatures reads exactly like what it is. Three specific letters beat fifteen generic ones.

Letters of commitment

A commitment letter should state concrete, measurable contributions, ideally with a dollar value if they count as match or in-kind. It should be on the partner's letterhead and signed by someone with authority to make the commitment.

Notice what makes that letter work: numbers, dates, a dollar value, and a link to an existing agreement. The reviewer can now treat the referrals and space as real.

Memoranda of understanding

An MOU is the right tool when a partnership involves ongoing operations, shared clients, data exchange, or money changing hands. It typically covers the purpose of the partnership, each party's responsibilities, the term, points of contact, data and confidentiality provisions, and how disputes or termination are handled.

If a partner will receive grant funds to carry out part of the program, you are no longer just describing a partnership. For federal funds, that may be a subaward with its own compliance requirements. Read our guide to subawards and pass-through funding before you sign anything, and have your attorney review agreements that involve money or data.

Practical timeline for letters

Partners need lead time. A realistic approach:

1. Six to eight weeks before the deadline, list every partner your plan depends on and every endorsement that would add credibility.
2. Contact each with a one-page project summary and a draft letter tailored to their role.
3. Ask for signed letters at least two weeks before the deadline.
4. Check every letter for the right funder name, project title, dates, and amounts.
5. Confirm the funder's rules: some want letters attached, some want them addressed to the funder, and some do not accept them at all.

If you are a new or small organization

Capacity sections are hardest for young organizations, but not impossible. Funders who support emerging nonprofits expect a shorter track record. What they need is a credible reason to believe you will manage the grant well.

Lean on:

• Founder and staff experience gained at other organizations
• Board expertise, especially finance and the program area
• A fiscal sponsor, whose accounting systems and compliance experience can stand in for your own (see fiscal sponsorship)
• Pilot results, even small ones, described honestly
• Strong partner commitments from established organizations
• Right-sized requests that match your current scale

Our guide to getting your first grants covers this in more depth, and the grant readiness assessment can help you see where your capacity gaps are before a funder does.

A model capacity section

Here is a compact capacity section for a foundation proposal. Adapt the structure, not the facts.

That section is short, specific, and every claim connects to the project being proposed. It also gives the reviewer concrete facts to repeat when they present your proposal to their board.

Checklist before you submit

• Every staff member named in the narrative appears in the budget at the same percent of time.
• Numbers match your annual report, website, Form 990, and past reports.
• Each partner your plan depends on has a commitment letter or MOU.
• Letters are addressed correctly, dated, signed, and specific.
• Financial attachments are the most recent available and consistent with your narrative.
• Any weakness (a deficit year, a leadership transition, a young organization) is acknowledged with a plan.

For a complete pre-submission review, use our proposal review checklist, and see how this section fits the whole application in the anatomy of a grant proposal.