Chapter 13: Organizational Capacity and Key Personnel — Proving You're the Right Team

By now your proposal has made a powerful case: the problem is real and urgent (Chapter 8), your plan is sound and feasible (Chapter 9), it will produce measurable results (Chapter 10), and the budget is necessary and reasonable (Chapters 11–12). But one question still hangs over all of it, unspoken and decisive: can these particular people, in this particular place, actually do what they're promising? A reviewer can believe in the project completely and still decline it because they don't believe in the team — because the most elegant plan in the world is worthless if the reviewer doubts the applicant can execute it. The organizational capacity and key personnel sections are where you answer that doubt, proving not just that the project is good but that you are the ones who can pull it off.

This chapter teaches you to make that case. We will write the capability and environment statement that establishes your organization's fitness, present investigator qualifications and construct the biosketch reviewers actually read, assemble the letters of support and commitment that make credible others vouch for you, and — crucially — show how to establish capacity when you don't have a long track record, as a new organization or an early-career applicant. The reviewer's question is "can they deliver?"; this chapter is how you answer "yes," convincingly.

A note on where this section sits in the proposal. In the reviewer's sequence of questions (Chapter 2), capacity comes after significance and approach — they decide whether the work matters and the plan is sound before they ask whether you can do it. This ordering has a practical implication: capacity rarely wins a proposal on its own (a capable team with a weak project still loses), but it frequently loses one (a strong project with a doubtful team gets passed over). So the capacity section's job is less to dazzle than to remove doubt — to ensure that, having been convinced the project is worth doing, the reviewer is not stopped by a worry that you can't do it. Think of it as clearing the last hurdle rather than starting the race: you've already made the case for the work; now you make the case that it's safe in your hands.

13.1 The Question Capacity Answers

🧩 Productive Struggle: Imagine two proposals with identical projects — same problem, same plan, same budget. One comes from a team that has done this exact work successfully five times; the other from a team that has never done anything like it. Which gets funded, and why? Before reading on, articulate what, precisely, the track record changes about the reviewer's decision, given that the projects are identical. The answer reveals what the capacity section is really for — and it's not about the project at all. It's about risk: the same plan is a safer bet in proven hands, and reviewers, managing risk, fund the safer bet. Hold that insight as you read.

Every reviewer, having assessed your project, turns to assessing you. They are asking, in some form: Do these people have the expertise this work requires? Does this organization have the track record, the staff, the systems, the relationships to carry it out? Is the environment — the institution, the resources, the partners — adequate to support it? Has this team done something like this before, successfully? In short: can they deliver?

🚪 Threshold Concept: Capacity answers the reviewer's silent question — "can these people actually deliver?" The most elegant plan is worthless if the reviewer doubts the team can execute it. So the capacity and personnel sections are not a formality or a résumé dump; they are the proof that your project is in safe hands. This connects directly to the first reviewer fear from Chapter 2 — the fear of championing a proposal that fails. A reviewer who doubts your capacity fears that funding you means funding a failure, and that fear sinks proposals regardless of how good the idea is. Your job is to remove the doubt: to make the reviewer confident that these people, in this place, can do this work — so confident that championing you feels safe.

Notice what this section is really doing: it is de-risking your proposal in the reviewer's eyes. Funders are, in a sense, investors, and every investor asks not only "is this a good idea?" but "is this a team that can execute?" A brilliant idea from a team that can't deliver is a bad investment; a solid idea from a team that clearly can is a good one. The capacity section converts your proposal from a promising idea into a credible, executable plan in capable hands — which is exactly what makes a reviewer comfortable recommending it. And because funders think in terms of long relationships (Chapter 3), they're also asking a quieter question: is this a team and organization worth building a relationship with — one that will steward this grant well and become a reliable grantee? A strong capacity case answers that too, positioning you not just for this award but for the next.

🗣️ From the Review Panel: I have declined proposals with excellent ideas because I didn't believe the team could pull them off — the plan required expertise no one on the team obviously had, or an organization with no track record proposed something far beyond what they'd ever done. And I have funded modest proposals from teams I trusted completely, because I knew the work would actually get done and the money would be well spent. When I read the capacity section, I'm asking myself one thing: if I champion this and it's funded, will these people deliver, or will I be the reviewer who backed a flop? Make me confident in the team, and you've removed my biggest fear. Leave me doubting it, and the best idea in the pile won't save you.

13.2 Organizational Capacity: Proving the Organization Can Do It

For program and nonprofit proposals, the capability statement (or organizational-capacity section) establishes that your organization can carry out the proposed work. It is not a history lesson or a marketing brochure; it is targeted evidence that this organization has what this project requires. The discipline is selection: from everything true about your organization, you choose and present only what bears on this project's specific demands, and you present it as evidence (concrete, results-backed) rather than as self-description. The elements:

• Track record: what your organization has done, especially work similar to the proposed project, with concrete results. "We have run this program at one site for four years, serving [N] students annually with [outcome]" is far stronger than "we are a leading youth organization." Specific, evidenced accomplishments beat adjectives.
• Staff and expertise: the qualifications of the people who will do the work — not full résumés here, but the relevant expertise that matches the project's demands.
• Community relationships and partnerships: the connections that enable the work — school partnerships, community trust, referral relationships — which are often a small organization's greatest asset and hardest for competitors to replicate.
• Organizational systems and grant-management capacity: evidence that you can manage the grant — financial systems, prior successful grant management, the administrative capacity to spend and report responsibly. This addresses a real funder worry, especially about small organizations: can they handle the compliance burden (Chapter 26)?
• Prior grant history: grants successfully received and managed, which signals that funders have trusted you before and you delivered.

📋 Template — The organizational capability statement: Establish, in targeted paragraphs: (1) Relevant track record — what you've done like this, with concrete results. (2) The team — the staff and expertise matched to this project's demands. (3) Relationships — the partnerships and community standing that enable the work. (4) Management capacity — your systems and prior grant management showing you can handle the money and reporting. Every element should answer "can they do this?" — not "are they a good organization in general?" Cut anything that doesn't bear on this project's specific demands.

⚠️ Common Pitfall: The generic "about us." A capability statement that recites the organization's founding date, mission statement, and a list of all its programs — without connecting any of it to this project's specific demands — answers the reviewer's real question ("can they do this?") only by accident. The fix (the same one from the executive summary, Chapter 7) is relevance: name the specific capabilities this project requires, and show you have them. If your project requires running a program at three sites, show you can run programs at multiple sites; if it requires managing a federal grant, show you've managed one. Capacity is always capacity for the proposed work, not capacity in the abstract.

Watch RYCC build its capability statement (composite). Weak (generic): "Founded in 2022, RYCC is a dedicated nonprofit committed to empowering youth through technology. We are passionate about our mission and have a track record of community service." Strong (matched to the project): "RYCC has operated a free after-school coding program at [school] for four years, enrolling [N] students annually with an 85% completion rate and graduates now entering high-school technology tracks — demonstrating that we can recruit, retain, and instruct the population this expansion will serve. Our established partnerships with all three target schools (letters attached) provide the site access, classroom space, and referral pipelines the expansion requires. Our staff includes [instructor credentials], and we have managed [prior grant] successfully, with the financial systems and reporting capacity to administer this award responsibly." Every sentence of the strong version answers "can they do this expansion?" — the track record proves the model and the skills, the partnerships prove the sites are ready, and the grant-management point reassures the funder about stewardship. The weak version asks the reviewer to take RYCC's competence on faith; the strong version proves it.

The grant-management element deserves special attention because it's the capacity that funders worry about most, especially with smaller organizations — and the one applicants most often neglect. A funder is entrusting you with money and will require you to spend it within rules and report on it accurately (Chapter 26). A reviewer assessing a small or new organization silently asks: "can they actually handle the administrative burden, or will the money be mismanaged?" An organization that has successfully managed grants before — spent within budget, met reporting deadlines, passed any audits — can say so, and it's powerfully reassuring. An organization without that history must establish management capacity another way: experienced financial staff, sound accounting systems, a fiscal sponsor, or a board with relevant expertise. Either way, address it — a capacity section that establishes the program expertise but says nothing about grant management leaves the funder's biggest worry unanswered. The ability to do the work and the ability to manage the money are two different capacities, and reviewers check for both.

🔄 Check Your Understanding: A small nonprofit's capability statement thoroughly establishes that its staff can run the proposed program, but says nothing about financial systems or grant management. What worry has it left unanswered, and why does that matter for a funder specifically?

Answer

It hasn't addressed grant-management capacity — whether the organization can spend within rules, track funds, and report accurately. This matters to a funder specifically because they're entrusting money and are accountable for how it's used; a funder fears mismanagement (and the compliance/audit problems that follow) as much as program failure. A small org especially must reassure the funder on this — via prior grant management, sound financial systems, a fiscal sponsor, or relevant board/staff expertise — or the funder's biggest worry goes unanswered.

13.3 Investigator Qualifications and Environment: Proving the Team Can Do It

For research proposals, the same question takes the form of investigator qualifications and environment. Reviewers assess whether the principal investigator and team have the expertise and track record to do the work, and whether the institutional environment — facilities, resources, support — is adequate.

• The investigator(s): their relevant expertise, track record of productivity (publications, prior funded work), and demonstrated ability to do this kind of research. For the PI, the question is leadership: can they direct this project to completion? For co-investigators and collaborators, the question is whether the team collectively covers the expertise the methods require — if the approach needs a skill the PI lacks, someone on the team must demonstrably have it.
• Environment: the institutional resources that support the work — labs, equipment, core facilities, computing, institutional commitment, intellectual community. A strong environment reassures the reviewer that the project has the infrastructure to succeed (and connects to the indirect costs that fund it, Chapter 12).
• Preliminary data as capability evidence: as Chapter 9 noted, preliminary data does double duty — it supports the hypothesis and demonstrates that the team can actually execute the methods. "We generated these pilot data" is proof of capability, not just feasibility.

🔍 Why Does This Work?: Why do reviewers weigh the team's track record so heavily, sometimes seeming to favor established investigators? Because past performance is the best available predictor of future success, and reviewers are managing risk (the first fear again). An investigator who has done similar work successfully is a lower-risk bet than one who hasn't, all else equal. This is rational, but it creates a real challenge for early-career applicants and new organizations, who lack the long track record — which is exactly why Section 13.7 exists. The point for now: reviewers read capacity as risk, and your job is to present whatever evidence you have in the way that most reduces the perceived risk of betting on you.

Dr. Hernandez illustrates how a researcher builds the case (composite). As an early-stage investigator, she can't point to a long record of funded trials — so she assembles capacity from what she has and who she's with. The investigator: her relevant training, her publications in adherence and behavioral intervention, and especially her preliminary data (the pilot), which proves she can execute the key methods. The team: she pairs with an experienced biostatistician co-investigator whose track record covers the analysis expertise she's still building, and a clinical collaborator who brings trial experience — so the team collectively covers everything the methods require, filling any individual gap. The environment: she documents her institution's resources — the clinical partner site providing patient access, the data and computing infrastructure, the institutional commitment to her career — borrowing credibility from a strong environment. The reviewer, assessing risk, sees an early investigator who is nonetheless well-supported: experienced collaborators, demonstrated methods, and a capable institution. The capacity case reduces the perceived risk of betting on a newer PI.

The general principle Hernandez illustrates is worth stating plainly: a team is assessed collectively, so you build the team to cover the project's demands. No single person needs to have every skill; the team, together, must. This is liberating for any applicant who feels under-qualified in some dimension — you don't have to be an expert in everything, you have to assemble the expertise. If your project needs statistical sophistication you lack, bring a statistician; if it needs clinical access you don't have, bring a clinical partner; if it needs evaluation rigor outside your wheelhouse, bring an evaluator (Chapter 10). Each addition, with a biosketch and a commitment letter, fills a specific gap in the team's collective capacity. Reviewers don't expect a single superhuman; they expect a team that, as a whole, can do the work — and a thoughtfully assembled team that visibly covers every demand is often more reassuring than a lone star, because it shows the applicant understood what the project requires and built for it.

13.4 The Biosketch and CV

The biosketch (a structured, abbreviated CV used by NIH, NSF, and many funders) is where individual qualifications are presented, and it is read more carefully than applicants assume. A biosketch is not a full CV; it is a curated, project-relevant presentation of a person's qualifications, usually including a personal statement, education and positions, and selected contributions or publications.

The personal statement is the most important and most underused part. It is a short narrative explaining why this person is suited to this role on this project — an opportunity to connect the individual's background directly to the proposed work. A strong personal statement says, in effect, "here is why I am the right person for this specific role," citing the relevant experience and accomplishments. A weak one is a generic paragraph that could appear on any proposal. Tailor the personal statement to the project; it is the place where a biosketch stops being a résumé and starts being an argument.

📋 Template — A project-relevant biosketch: (1) Personal statement — why this person fits this role on this project, citing the specific relevant experience (tailored, not generic). (2) Positions and education — the credentials, briefly. (3) Contributions / selected publications — the work most relevant to this project, chosen to demonstrate the needed expertise (not an exhaustive list). The whole biosketch should be curated to answer "is this person right for this role?" — every item chosen for its relevance to the proposed work. Follow the funder's required biosketch format exactly (NIH and NSF have specific, evolving formats — a compliance issue, Chapter 15).

✅ Best Practice: Curate every biosketch and CV for the specific project. The temptation is to use one standard biosketch for every proposal, but a biosketch tailored to the project — with a personal statement that connects to this work and selected publications that demonstrate this expertise — is far more persuasive than a generic one. A reviewer reading a tailored biosketch sees a person who clearly fits the role; reading a generic one, they have to infer the fit themselves, and they may not. The few minutes of tailoring per person are among the highest-return edits in the proposal.

A worked personal statement shows the difference. Consider Sam Okonkwo, the doctoral student writing a fellowship (Chapter 6). Generic: "I am a hardworking graduate student with a strong interest in this field and a commitment to research excellence." This could be anyone; it makes no argument. Tailored: "My doctoral training in [field], my preliminary work demonstrating [specific pilot result], and my coursework in [relevant methods] have prepared me to carry out the proposed research. Under the mentorship of [sponsor], whose expertise in [area] complements my training, I am positioned to develop the [specific skills] this project requires and that my career goal of [trajectory] depends on." The tailored version connects Sam's specific background to this specific project and role, names the relevant preliminary work, and — crucial for a fellowship — frames the project as the right vehicle for Sam's development (the fellowship's actual purpose, Chapter 27). A reviewer reading it sees exactly why Sam fits this role; reading the generic version, they see nothing. The personal statement is where a biosketch makes its argument, and Sam's tailored one argues; the generic one merely fills space.

It helps to know what reviewers actually look for when they read a biosketch, because it's less than applicants fear and more specific than they expect. They are not counting publications or admiring prestige for its own sake; they are checking fit and capability for the role: does this person have the specific expertise this project needs, and have they demonstrated they can do this kind of work? A reviewer reading the PI's biosketch wants evidence of the ability to lead and complete a project like this; reading a co-investigator's, evidence of the specific expertise they're brought in for. So curate accordingly: the publications and accomplishments you feature should be the ones that demonstrate the capability this role requires, even if they're not your most prestigious or most recent. A mid-tier publication directly on the project's methods does more work in a biosketch than a high-profile one on an unrelated topic, because it answers the reviewer's actual question — can this person do this? Choose your featured contributions for relevance, not vanity, and the biosketch becomes an argument for the team rather than a list of credentials.

🔄 Check Your Understanding: A co-investigator is brought onto a project specifically for their statistical expertise. Their CV includes a high-profile publication in an unrelated area and a modest methods paper directly relevant to the project's analysis. Which should the biosketch feature, and why?

Answer

The modest methods paper directly relevant to the analysis — because the reviewer's question about this co-investigator is "do they have the specific statistical expertise this project needs?", and the relevant methods paper answers it directly. The prestigious unrelated publication impresses but doesn't answer the actual question. Curate the biosketch for fit to the role, not for prestige: feature the contributions that demonstrate the capability this person was added to provide.

13.5 Letters of Support and Commitment

Letters from others — partners, collaborators, institutions, community stakeholders — make credible third parties vouch for you, which carries a weight your own claims cannot. When you say you can do the work, that's a claim; when a respected partner confirms they'll provide what you need, or a community leader attests to the need from their vantage point, that's corroboration — and corroboration from credible sources is exactly what reduces a reviewer's risk. There are two distinct kinds, and conflating them is a common error:

• Letters of support express endorsement: a stakeholder says they believe in the project and support it. They signal community backing and buy-in.
• Letters of commitment promise something specific: a partner commits to providing space, access to participants, data, staff time, matching funds, or some other concrete contribution the project depends on. They are stronger than support letters because they are binding promises of resources the reviewer can count on.

A proposal that depends on a partner's contribution (a clinic providing patients, a school providing space, an organization providing matching funds) needs a letter of commitment confirming it — without one, the reviewer doubts the contribution is real. Support letters add warmth and backing; commitment letters remove specific doubts.

📊 From the Field: The open secret of letters: you usually draft them yourself. A busy partner or collaborator cannot write you a thoughtful, specific letter on demand, and a generic letter they write quickly is worse than useless. The professional norm — and a genuine kindness to the letter-writer — is to draft the letter for them, tailored to say exactly what the proposal needs (the specific commitment, the specific endorsement), and let them edit and sign it on their letterhead. This is not deceptive; it is how the system works, and it ensures the letter actually addresses what your proposal needs rather than offering vague good wishes. Draft each letter to make a specific point — a concrete commitment, a relevant endorsement — and ask early (Chapter 4), because even a letter you've drafted takes the signer time to review and return.

⚠️ Common Pitfall: Generic, interchangeable letters. A stack of support letters that all say essentially "we think this is a great project and wish them well" adds little — reviewers can tell they're pro forma, and they signal a team assembled at the last minute (Chapter 4). Strong letters are specific: each makes a particular point only that writer can make (this partner commits this resource; this stakeholder confirms this community need; this collaborator brings this expertise). Five specific, differentiated letters beat ten interchangeable ones. If a letter doesn't make a specific, non-redundant point, it's not earning its place.

📋 Template — A letter of commitment (draft for the partner to edit): A strong commitment letter, on the partner's letterhead, makes one specific, binding promise: "On behalf of [Partner School/Clinic], I am writing to confirm our commitment to [Project]. We will provide [the specific resource: classroom space at our site for the after-school program; access to our patient population for recruitment; X hours of staff liaison time], for the duration of the project. We have partnered with [Applicant] for [time] and have confidence in their ability to deliver this program. We are pleased to support this proposal and look forward to the collaboration. — [Name, title, signature]" Notice it does three things: names the specific contribution (not vague support), confirms the existing relationship (signaling the partnership is real), and is binding (a promise the reviewer can count on). Draft this for the partner, tailored to exactly what your proposal needs them to commit, and let them edit and sign it — far better than the vague "we support this great project" letter a busy partner would write from scratch.

🔄 Check Your Understanding: Your proposal's evaluation depends on a partner clinic providing access to 200 patients for recruitment. You have a letter from the clinic's director saying, "We think this is excellent work and wish the team success." Is this sufficient? Why or why not?

Answer

No — it's a letter of support (endorsement) where you need a letter of commitment (a binding promise of the specific resource). The proposal depends on the clinic providing patient access; a reviewer reading only "we wish them success" cannot count on that access and will doubt the recruitment is real. You need a commitment letter confirming specifically that the clinic will provide access to the patient population for recruitment — draft it for the director to edit, naming the concrete commitment.

🗣️ From the Review Panel: I read letters quickly, and I'm scanning for two things: are the depended-on contributions actually committed, and do the letters feel real or pro forma? When a proposal's success rests on a partner providing something — patients, space, data, matching funds — I look for a letter that commits it, specifically; if I find only "we support this great project," I mark the contribution as unconfirmed and the proposal as riskier. And a stack of near-identical glowing letters reads as exactly what it is: letters the applicant rounded up at the last minute, possibly all drafted from the same template without much thought. The letters that help are the specific ones — this partner commits this, this stakeholder confirms this need from their vantage point, this collaborator brings this expertise. Specificity signals a real, planned collaboration; interchangeable warmth signals a hasty assembly. Send me the specific kind.

13.6 Matching Capacity to the Task

The thread running through this whole chapter is match: capacity is always capacity for the proposed work. The reviewer isn't asking whether you're a good organization or a smart person in general; they're asking whether you can do this specific project. So the capacity section's job is to map your qualifications onto the project's specific demands and show the fit.

Concretely: list what this project requires — the expertise, the relationships, the infrastructure, the management capacity — and, for each, show you have it. If the project requires a randomized trial, show the team has run trials. If it requires deep community trust, show you have it. If it requires managing a large federal grant, show you've managed one. Where there's a gap between what the project requires and what you obviously have, that gap is a capacity weakness a reviewer will spot — and you must fill it (add a collaborator with the missing expertise, a letter confirming the missing resource) or address it honestly. The capacity section is, in effect, a checklist: does this team have everything this project needs? Make sure the answer is visibly yes.

🔄 Check Your Understanding: A nonprofit with strong direct-service experience proposes a project that requires rigorous outcome evaluation — a skill it has never demonstrated. A reviewer notices the gap between the project's demands and the team's evident capacity. What are two ways to fill it?

Answer

(1) Add the missing expertise to the team — bring on an external evaluator (Chapter 10) with demonstrated evaluation experience, with a letter of commitment, so the team collectively covers the needed skill. (2) Demonstrate the capacity if you have it in some form — point to any prior data collection or measurement the organization has done, or to staff with relevant training. The principle: where the project requires a capacity the team doesn't obviously have, you must visibly fill the gap (usually by adding someone who has it) rather than hope the reviewer won't notice — because they will.

This matching exercise is worth doing explicitly, as a checklist, before you finalize the proposal. Go through your approach (Chapter 9) and list every distinct capability the project demands — each method, each kind of relationship, each system, each form of expertise. Then, for each, identify who or what on your team provides it and where the proposal shows that. Capabilities with a clear answer are covered; capabilities with no clear answer are gaps a reviewer will find, and you must fill them — add a collaborator, an evaluator, a consultant, a letter — or, if you can't, reconsider whether you should be proposing that element of the work at all. This is the same coherence discipline that governs the budget (every activity funded) and the evaluation (every outcome measured), applied to capacity: every capability the project requires must be visibly present on the team. The proposal that survives this checklist is one the reviewer can't puncture with "but who's going to do the X part?" — because you've already shown them.

13.7 Establishing Capacity Without a Long Track Record

The hardest case — and a common one — is establishing capacity when you lack a long track record: a new organization, an early-career investigator, a first-time applicant. Reviewers favor demonstrated track records (Section 13.3), so how do you compete without one?

You assemble capacity from the evidence you do have:

• Borrow credibility through your team and partners. An early-career investigator pairs with experienced co-investigators or mentors (essential for fellowships and career awards, Chapter 27); a new organization partners with established ones. The team's collective track record fills the individual's gap. A strong mentor or collaborator, with a letter, can substantially de-risk an early-career proposal.
• Show relevant capacity in other forms. A new organization may lack a long grant history but have deeply experienced staff (point to their individual track records), strong community relationships, or relevant pilot work. An early-career investigator has their training, their preliminary data, and often a strong publication start. Present what you have as evidence of capability.
• Leverage the environment. A new investigator at a strong institution borrows credibility from the environment — the resources, the mentorship, the institutional commitment. A new organization with a strong fiscal sponsor or established partners borrows their infrastructure.
• Match the ask to your demonstrated capacity. The surest way to fail the capacity test is to propose something far beyond anything you've done. A new organization should propose a project it can credibly execute, building a track record from smaller successes (the "small grants build to large" pattern from Chapter 1). Propose what you can plausibly deliver, deliver it, and let the track record grow.

🪞 Learning Check-In: If you're an early-career applicant or a new organization, notice the temptation to either overclaim (inflate your thin track record, hoping to seem more established) or apologize (dwell on what you lack). Both hurt. Overclaiming is caught and destroys trust; apologizing volunteers doubt. The confident middle path is to present what you genuinely have — your team, your partners, your environment, your relevant experience in whatever form — as real evidence of capability, and to match your ask to what you can credibly deliver. Everyone established was once new; the ones who broke through didn't pretend otherwise, they assembled a credible case from what they had and proposed something they could actually do.

A worked example ties the strategies together. Suppose a new nonprofit — call it a two-year-old organization with passionate staff but no major grant history — wants federal funding for a program. A reviewer's instinct is to worry: can a two-year-old org manage a federal grant? The new org de-risks itself deliberately. It partners with an established organization that will serve as fiscal sponsor and mentor, borrowing that partner's grant-management infrastructure and track record (with a commitment letter). It foregrounds its staff's individual experience — a program director who ran similar programs for fifteen years at a previous employer — so the people have a track record even though the organization doesn't. It documents its strong community relationships, often a new grassroots org's genuine advantage over a large, distant institution. And, critically, it scales its ask: rather than requesting a large multi-year award beyond anything it's done, it proposes a right-sized project it can credibly execute, planning to build from there. The reviewer's worry — "can this new org deliver?" — is met not with bravado but with a fiscal sponsor's infrastructure, experienced individual staff, real community ties, and a realistic ask. The new organization has assembled, from what it genuinely has, a credible capacity case. That is how the underdog competes: not by pretending to be established, but by de-risking honestly.

📊 From the Field: Many funders deliberately support newer applicants, which is worth knowing if you lack a track record. The NIH designates Early-Stage Investigators (ESI) and gives their applications special consideration, partly to counteract the track-record advantage of established investigators (Chapter 27). Some foundations specifically fund emerging organizations or seed new work. Seed and pilot grants (Chapter 1) exist partly to let newer applicants build the track record that wins larger awards. So before concluding you're too new to compete, check whether your target funder has mechanisms or considerations for early-career applicants or emerging organizations — and if it does, that's often a better-matched entry point than competing head-to-head with established applicants for the flagship award. The funding system has on-ramps for the new; find yours, and the capacity challenge becomes far more manageable.

📐 Project Checkpoint — Draft your capability statement and a support-letter template: For your project, (1) write the capability/environment statement: for a program, your track record, team, relationships, and management capacity, each tied to this project's demands; for research, the investigator qualifications and environment. (2) Identify the specific capacities this project requires and confirm you've shown each — fill any gap (a collaborator, an evaluator, a letter). (3) Draft a biosketch personal statement for yourself (or the PI) tailored to this role. (4) List the letters you need (support vs. commitment), who writes each, and the specific point each must make — and draft one commitment letter you'd send a partner to edit. (5) If you lack a long track record, assemble capacity from your team, partners, environment, and relevant experience, and check that your ask matches your demonstrated capacity. Save it in your "My Proposal" document.

Spaced Review

Retrieve these from earlier chapters without looking back.

1. (From Chapter 2) How does the capacity section connect to the "two reviewer fears," and which fear does it most directly address?
2. (From Chapter 9) The approach claimed the team could execute the methods. How does the capacity section relate to that claim?
3. (From Chapter 12) Your budget justified personnel effort. How does that connect to this chapter?

Answers

1. The capacity section most directly addresses the first fear — championing a proposal that fails. A reviewer who doubts your capacity fears funding a flop; establishing capacity removes that fear and makes championing you feel safe. 2. The approach asserted the team could do the work; the capacity section proves it — providing the evidence (track record, qualifications, environment, preliminary data) behind the claim. If the approach requires a skill, the capacity section must show someone on the team has it. 3. The budget justified the personnel and their effort (the people doing the work); the capacity section establishes that those same people are qualified to do it. The two are linked — the effort you funded and justified must be effort by people the capacity section shows are capable.

Chapter Summary

Key Takeaways

• Capacity answers "can these people deliver?" (threshold concept) — the question that remains after the project is judged. The most elegant plan fails if the reviewer doubts the team. The section de-risks your proposal, addressing the reviewer's fear of championing a failure (Chapter 2).
• Organizational capability (programs) = relevant track record + matched team + enabling relationships + grant-management capacity, each tied to this project's demands. Avoid the generic "about us."
• Investigator and environment (research) = the team's relevant expertise and track record + adequate institutional resources + preliminary data as capability evidence. Reviewers read track record as risk.
• The biosketch is curated, not a full CV; the personal statement (tailored to this role) is its most important, most underused part. Curate every biosketch for the specific project.
• Letters: support (endorsement) vs. commitment (a binding promise of a specific resource). A project depending on a partner's contribution needs a commitment letter. Letters should be specific and non-redundant — and you usually draft them yourself for the signer to edit.
• Match capacity to the task: map the project's specific demands onto your qualifications and show the fit; fill any gap (a collaborator, an evaluator, a letter).
• Without a long track record, assemble capacity from your team, partners, environment, and relevant experience — and match your ask to what you can credibly deliver. Don't overclaim or apologize.

Action Items

• Write the capability/environment statement, tied to this project's demands.
• Confirm every capacity the project requires is shown; fill any gap.
• Draft a tailored biosketch personal statement.
• List and draft your letters (support vs. commitment), each making a specific point.

Common Mistakes to Avoid

• The generic "about us" / capacity in the abstract.
• A generic, untailored biosketch personal statement.
• Generic, interchangeable letters; missing a commitment letter for a depended-on contribution.
• Overclaiming or apologizing about a thin track record.

Decision Framework: Is your capacity case ready?

Ask: (1) Does it answer "can they do this?" — every element tied to the project's demands? (2) Is every capacity the project requires visibly shown, with gaps filled? (3) Is each biosketch curated with a tailored personal statement? (4) Are your letters specific, with a commitment letter for every depended-on contribution? (5) Does your ask match your demonstrated capacity? Any "no" is your next revision.

Looking Ahead

You've proven the team can deliver the project. Now the reviewer asks the question every funder eventually asks: what happens when the money runs out? Chapter 14: Sustainability and Dissemination teaches you to answer it — to show how the project's impact will continue beyond the grant period (sustainability) and how its results and lessons will reach others (dissemination). Funders want impact that outlasts their dollars, and a credible sustainability plan is what reassures them that funding you is an investment with lasting return, not a one-time expense that ends when the grant does.

With Chapter 13, you have now built the full core of the proposal: a problem that matters, a sound plan, measurable outcomes, a justified budget, and a capable team. Pause to appreciate what that means — a reviewer who reaches the end of these components has, if you've done the work, been walked through every question they would ask and given a satisfying answer to each: it matters, the plan works, we'll know if it succeeds, it costs what it should, and these are the people to do it. That is a complete, coherent case for funding. The remaining component chapters (14 on sustainability, 15 on assembly and submission) and Parts III–VI refine and adapt that case for specific funders and circumstances — but the heart of persuasion is now in place. You have learned to build a proposal that answers the reviewer's every doubt, which is, in the end, the whole craft.

Continue to the Exercises, the Quiz, and the two Case Studies (1, 2). The Key Takeaways card is your quick-review anchor.

Next: Chapter 14 — Sustainability and Dissemination: What Happens After the Grant Ends.