Letter of Support for a Grant Proposal

A letter of support is a signed document from someone outside the applicant’s own key-personnel budget line — a collaborating institution’s official, a community partner, a core facility director, a data provider — confirming a specific commitment to a proposed project. Reviewers use it as evidence, not as encouragement: a well-written letter tells a study section exactly what resource, access, or role a named partner has agreed to provide, and a generic one signals that the partner signed something without reading the proposal. Because the two major US funders treat this document category very differently — NIH actively wants it, NSF generally does not — getting the terminology and the agency-specific rule right is itself part of building a compliant application.

Letter of support vs. letter of collaboration vs. letter of commitment

These three terms get used loosely, but they map to functionally different documents, and which one an application needs depends on the funder:

Letter of support (NIH’s umbrella term): a letter from a collaborator, key personnel not on the project’s budget, an institution, a core facility, or another significant contributor confirming their role and the resources or access they will provide. NIH’s NIAID guidance frames this as a “narrow, evidentiary purpose”: the letter exists to confirm a specific fact the application relies on, not to advocate for the project.
Letter of collaboration (NSF’s preferred term, and increasingly used at NIH for the same function): documents an unfunded collaborative arrangement — someone contributing meaningfully to the science without appearing in the budget. NSF’s Proposal & Award Policies & Procedures Guide (PAPPG, NSF 24-1), Chapter II gives this document a prescribed, minimal format: it should state only the collaborator’s intent to participate if the proposal is funded, with no evaluative language about the project’s merit.
Letter of commitment: used when a Funding Opportunity Announcement or program solicitation specifically requires proof that a named individual (often key personnel, a mentor on a training award, or a resource with limited capacity) will actually be available at the level of effort or access claimed in the application — the emphasis is on certainty of availability, not endorsement.

The practical distinction reviewers apply to all three: a support/collaboration/commitment letter documents an operational fact the project depends on. A reference letter, by contrast, speaks to a person’s qualifications rather than a project’s logistics — NIH’s own March 2026 Extramural Nexus guidance on “reference or support” letters draws exactly this line: reference letters are collected for fellowships, mentored Career Development (“K”) Awards, and similar programs to vouch for an applicant’s competence; letters of support are collected to vouch for a project’s logistics.

NIH: letters of support are expected and specifically instructed

NIH’s own guidance is direct that an application should include letters of support “from your institution, key personnel, collaborators, and other significant contributors” whenever their participation is described in the Research Strategy or Facilities & Other Resources sections. NIAID’s grants guidance instructs applicants to have each letter:

Describe the specific type of support being provided — reagents, animal models, human samples, technology access, data, space, or expertise — not a general statement of enthusiasm.
State whether that support is available to the applicant specifically, or to any qualified requester (relevant for shared/core resources, since reviewers read these differently).
Summarize any agreement already in place: rates or pricing for contracted services, authorship expectations, data-sharing terms, or effort commitments.
Be addressed generically (“Dear Reviewer” or “To Whom It May Concern”) rather than to a named program officer, since the assigned study section isn’t known at submission.

Letters attach to the Research Plan, PHS Human Subjects and Clinical Trials Information form, or the relevant supplemental form depending on mechanism — and a specific Notice of Funding Opportunity (NOFO) can require additional letters beyond the baseline expectation, so always check the NOFO’s own instructions before finalizing which letters to collect. This is exactly the kind of detail that’s easy to treat as boilerplate but that a Career Development (K) Award mentor-commitment letter, for instance, actually needs to satisfy in far more specific terms (protected time, mentorship structure) than a core-facility access letter does.

NSF: letters of support are generally not permitted at all

This is the distinction most likely to trip up an administrator moving between agencies, and it is a real compliance risk, not a stylistic preference. NSF’s PAPPG states that letters of support — documents that convey enthusiasm for a project or speak to a PI’s qualifications — are not a standard component of an NSF proposal, and a proposal that includes one without explicit authorization in the program solicitation risks being returned without review. What NSF does permit, and in most collaborative proposals expects, is the letter of collaboration described above, in its prescribed minimal format: a statement of intent to collaborate and/or commit resources as detailed in the Project Description or the Facilities, Equipment and Other Resources section, with no editorializing about the proposal’s significance.

The operational takeaway for a sponsored-programs office managing both NIH and NSF portfolios: never reuse an NIH-style letter of support template on an NSF proposal by default. Check the specific program solicitation first — some do authorize letters of support explicitly — and default to the PAPPG’s letter-of-collaboration language when a solicitation is silent.

Who typically writes one, and what standing they need

The right signatory depends on what the letter is confirming, not on organizational seniority for its own sake — a reviewer checks whether the signer actually has the authority to make the commitment described:

A collaborating institution’s authorized official (department chair, dean, or sponsored-programs signatory) for institution-level commitments: space, matching funds, cost-sharing, or a formal subaward relationship.
A named collaborator or co-investigator not included in the budget, for a specific scientific or methodological contribution — the letter should read as coming from the person actually doing the work, not an administrator writing on their behalf.
A core facility, shared resource, or repository director, for access to instrumentation, biospecimens, datasets, or technical services — ideally stating capacity, turnaround, and any user fees, since these are the details reviewers use to sanity-check feasibility.
A community, clinical, or industry partner’s authorized representative, for site access, participant recruitment, real-world data, or in-kind contributions — particularly load-bearing for community-engaged and dissemination/implementation research, where reviewers weigh partner buy-in directly.

Whoever signs should have the standing to actually deliver what the letter promises. A letter of support signed by someone with no authority over the resource being offered is a real, specific weakness reviewers are trained to notice — it undercuts the very evidentiary purpose the document exists to serve.

What to actually put in the letter

There’s no useful generic fill-in-the-blank template here, because the content that makes a letter credible is exactly the content that has to be specific to the project — a template invites the generic-praise problem this section exists to warn against. Instead, work through these considerations with whoever is signing:

Name the exact commitment, with a number where one exists. “We will provide access to approximately 500 de-identified patient records annually” is verifiable; “we are excited to support this important work” is not. If the Research Strategy or budget justification states a specific figure (hours, dollar amount, sample count, percent effort), the letter should independently confirm that same figure — a mismatch between the narrative and the letter is a red flag reviewers are specifically watching for.
State role and duration. What is this person or unit actually doing on the project, and for how long? A one-time consultation reads very differently from an ongoing collaboration, and the letter should be unambiguous about which it is.
Disclose terms already agreed, not just intentions. Authorship expectations, data-sharing arrangements, cost-sharing or waived/discounted rates, and any conditions on the commitment (e.g., contingent on award of a specific budget line) belong in the letter if they’ve already been discussed — silence here reads as those terms being unresolved.
Avoid advocacy language entirely on NSF proposals, and keep it minimal even on NIH ones. Reviewers are evaluating the science and the feasibility of the collaboration, not counting endorsements; a letter that spends its length praising the PI’s track record is, at best, wasted space and, at worst, read as filler covering for the absence of a real commitment.
Match the letter to what the narrative actually says. If the Facilities & Other Resources section or budget justification describes a resource, a core, or a collaborator’s contribution, there should be a corresponding letter confirming it in the applicant’s own words — not the reverse, where a letter promises something the narrative never mentions.

Drafting a summary of the agreement for the signer, or preparing the letter for their review and signature rather than asking them to write it from scratch, is standard practice at most sponsored-programs offices and is explicitly suggested in NIAID’s own guidance — it keeps the specific, verifiable details consistent with the rest of the application rather than left to the signer’s memory of a conversation that happened months earlier.

Common mistakes that weaken a letter

Generic praise with no verifiable commitment (“we wholeheartedly support this important initiative”) — tells a reviewer nothing about actual involvement.
Submitting an NIH-style support letter on an NSF proposal without solicitation authorization — a compliance risk, not just a stylistic mismatch, since NSF can return the proposal without review.
A letter signed by someone without authority over the resource or commitment being described.
Numbers or terms in the letter that don’t match the Research Strategy, budget, or Facilities & Other Resources section.
Treating the letter as boilerplate collected once and reused across proposals — NIH guidance is explicit that letters should be unique to the specific application, not a recycled form letter.
Missing a NOFO- or solicitation-specific instruction that supersedes the general baseline (e.g., a program that requires letters of commitment with a stated percent effort, or a solicitation that authorizes NSF letters of support in an unusual case).

Frequently asked questions

Does every grant proposal need a letter of support?

No. Whether one is needed depends on whether the application describes a resource, collaborator, or institutional commitment that a reviewer would otherwise have no way to verify. Always check the specific funding opportunity’s instructions rather than assuming a baseline requirement applies.

Can a letter of support be reused across multiple proposals?

Not as a form letter. NIH guidance specifically calls for letters unique to the application, since reviewers can tell when a letter reads as generic rather than tied to the actual project. A reusable summary of the underlying agreement (rates, capacity, standard terms) can speed up drafting a new letter each time, but the final letter should reference the specific proposal.

What happens if an NSF proposal includes a letter of support that wasn’t requested?

Per the PAPPG, NSF may return the proposal without review if it contains a letter of support not authorized by the program solicitation. The safer default on an NSF proposal is a letter of collaboration in NSF’s prescribed minimal format, unless the solicitation explicitly asks for something else.

How is a letter of support different from a biosketch or Current and Pending Support?

A letter of support documents a third party’s commitment to the project. A biosketch documents an individual’s own qualifications, and Current and Pending Support (formerly Other Support) discloses an individual’s other research commitments and resources. All three can appear in the same application but serve different verification purposes for reviewers.

Who should ask the partner for the letter — the PI or the sponsored-programs office?

Typically the PI initiates the request, since they hold the working relationship, but the sponsored-programs or pre-award office often reviews the letter for compliance with the specific NOFO or solicitation’s format and content requirements before submission, and can help draft a summary of the agreement for the signer to streamline the process.

Letters of support sit alongside other pre-award compliance artifacts — the budget justification narrative, biosketches, and Current and Pending Support disclosures — that a proposal-development team assembles before submission. See the grants management hub for the broader pre-award and post-award lifecycle these documents fit into.