Soliciting and Writing Letters of Support

Letters of support are the proposal's external testimony. The reviewer asks: do other people in the field believe in this person and this project? The letters answer.

## Key Points

- **NIH research grants** typically allow letters from collaborators (specifying the collaboration), but limit other "letters of support."
- **NSF** allows letters of collaboration that confirm specific commitments; letters of support of the proposed work are often discouraged.
- **Foundation grants** often welcome and encourage letters demonstrating community support.
- **Training grants and fellowships** typically require multiple letters of recommendation about the trainee.
- **Career awards** often require institutional commitment letters and mentor letters.
1. **Confirm specific collaborations.** When the proposal claims a collaboration, the collaborator confirms what they will contribute, with specifics: data, samples, expertise, equipment time, sites.
3. **Demonstrate community partnerships.** For community-engaged research and program grants, letters from community partners confirm the partnership is real.
- **Make it early.** Six weeks before the proposal is due, minimum. Eight weeks is better. Letter writers have busy schedules.
- **Provide context.** A one-paragraph summary of the project, the foundation/funder, the deadline.
- **Provide a draft if helpful.** Many letter writers appreciate a draft to revise; some prefer to write from scratch. Ask their preference.
- The Specific Aims page or LOI summary.
- A bullet-point list of what the letter should confirm.

Letters of support are the proposal's external testimony. The reviewer asks: do other people in the field believe in this person and this project? The letters answer.

A strong letter is specific, substantive, and from someone whose name carries weight in the relevant context. A weak letter is generic, brief, and from someone the reviewer doesn't recognize. The variance in quality is large; managing the letters is part of the proposal work.

When Letters Are Required

Different grant programs treat letters differently:

• NIH research grants typically allow letters from collaborators (specifying the collaboration), but limit other "letters of support."
• NSF allows letters of collaboration that confirm specific commitments; letters of support of the proposed work are often discouraged.
• Foundation grants often welcome and encourage letters demonstrating community support.
• Training grants and fellowships typically require multiple letters of recommendation about the trainee.
• Career awards often require institutional commitment letters and mentor letters.

Read the program announcement carefully. Some programs require specific letter content; some allow free-form. Some have a cap on the number; some don't. Compliance matters.

Choosing the Letter Writers

The letters that strengthen a proposal:

1. Confirm specific collaborations. When the proposal claims a collaboration, the collaborator confirms what they will contribute, with specifics: data, samples, expertise, equipment time, sites.
2. Demonstrate institutional commitment. When the institution is committing resources (space, equipment, protected time, salary support), an institutional letter from a department chair or dean confirms it.
3. Demonstrate community partnerships. For community-engaged research and program grants, letters from community partners confirm the partnership is real.
4. Speak to the investigator's track record. When the investigator is early-career or new to a field, letters from senior figures who have worked with them speak to their qualifications. Federal research grants typically don't accept these as separate letters of support; they appear in biosketches and personal statements.

The letter writer's name should mean something to the reviewer. A senior figure in the field, a known community organization, a respected institution. A letter from someone the reviewer doesn't know contributes nothing.

Asking for the Letter

The ask:

• Make it early. Six weeks before the proposal is due, minimum. Eight weeks is better. Letter writers have busy schedules.
• Be specific about what you need. Not "would you write a letter for my grant" but "would you write a letter confirming your role as a co-investigator providing access to the X dataset, with about 10% effort, for our NIH R01 due [date]."
• Provide context. A one-paragraph summary of the project, the foundation/funder, the deadline.
• Provide a draft if helpful. Many letter writers appreciate a draft to revise; some prefer to write from scratch. Ask their preference.

The ask should make the letter writer's job as easy as possible. Time spent writing letters is time the writer is choosing to give you. Reduce the friction.

What to Provide the Writer

Once they agree, provide a packet:

• The Specific Aims page or LOI summary.
• A bullet-point list of what the letter should confirm.
• Example letters they have written for similar purposes (only if you have access).
• The submission deadline and the format (signed PDF, on letterhead).
• The submission method (uploaded by you with the proposal, or sent directly to the funder).

Some letter writers ask for a draft. If they do, write a draft in their voice. The draft is a starting point; they will revise. Most experienced letter writers significantly revise drafts; the draft saves them time, not effort.

When drafting on someone else's behalf, write in the voice you'd want from them. Specific. Substantive. Using their actual relationship with you and the project, not invented hyperbole.

What Makes a Strong Letter

The reviewer reading a strong letter sees:

• A real relationship. The letter writer knows the proposal author. The letter has details only an actual collaborator would know.
• Specific commitments. "I will provide [specific resource] with [specific terms]." Not "I support this project."
• Evidence of collaboration. Past projects, papers, conversations. Continuity, not first-time enthusiasm.
• Distinctive voice. The letter sounds like it was written by the writer, not generated from a template.
• Letterhead and signature. Institutional credibility.

A weak letter:

• Is on a single page, mostly generic praise.
• Doesn't specify any commitment.
• Could have been written by anyone in the field.
• Has obvious template language.
• Is signed without title or affiliation.

Most letter writers can produce strong letters with two hours of effort. Make their job easier; expect the strong version.

When You Are the Letter Writer

When asked to write a letter for someone else's grant, you have responsibilities:

• Write only when you can write substantively. If you don't know the person well or aren't enthusiastic, decline. A weak letter hurts the applicant.
• Be specific. Name the project. Name your role. Specify what you will contribute. Reference past collaboration.
• Be honest. Don't claim more than you can deliver. The applicant may be funded and you'll be accountable for the commitment.
• Be timely. Submit by the deadline. Late letters can disqualify the proposal.

Letter writing is reciprocal in a field. You write letters for others; they write for you. Take the requests seriously.

Coordination with the Submission

Some funders require all letters in a single PDF; others have a separate upload portal. Some letter writers send their letter directly; some send it to you to include.

Confirm logistics:

• Who submits the letter (you or the writer).
• The format (signed PDF, on letterhead).
• The deadline (separate from the proposal deadline if applicable).
• The submission portal credentials if the writer needs to upload.

Then track the status. A week before the deadline, follow up with any writer who hasn't sent or confirmed. Don't be pushy; do remind.

Letter Saturation

Some funders accept many letters; some accept few. The number you submit should be calibrated:

• Federal research grants: typically 0-3 letters of collaboration. More is suspicious.
• Foundation grants: often 3-7 letters. More is fine if substantive.
• Training/career grants: required number specified.
• Major institution-level proposals: 10+ letters showing breadth of support are normal.

Over-submitting weak letters reduces the impact of the strong ones. The reviewer skims the pile; if half are obviously weak, the strong ones lose force. Curate.

Anti-Patterns

Asking too late. A week before deadline. The letter writer can't deliver a strong letter on a week's notice. Ask 6-8 weeks ahead.

No context provided. "Please write a letter." The writer can't write a strong letter without knowing what to confirm. Provide a packet.

Generic letters. No specifics, no real relationship, just praise. Reviewers discount them. Better to have fewer, stronger letters.

Letters that don't match the proposal. The proposal claims a collaboration the letter doesn't confirm; or the letter promises resources not described in the proposal. Reviewers notice; the proposal loses credibility.

Forgotten letters. A required letter doesn't arrive; the proposal is incomplete. Track every letter; follow up before deadline.

Inflated commitments in the letter. The collaborator promises more than they will deliver. After funding, the commitment can't be honored. Damages relationships and future credibility.