Funder Communications Best Practices: Reports, Updates, and Stewardship

Definition

Funder communications is the body of writing, calls, visits, and reporting that happens between the moment a grant is awarded and the moment the next proposal is invited. It is distinct from grant writing (the proposal itself) and from grant compliance (the financial and administrative obligations of the award). Funder communications is the relationship layer - what you tell the program officer, when you tell them, in what tone, and what you ask of them in return.

This guide covers the practical cadence and content of funder communication for mid-sized US nonprofits managing foundation, government, and corporate awards. It is calibrated for organizations with 5 to 30 active grants at any time, the typical range for $500K to $10M annual budgets.

Why funder communication matters

The single best predictor of a renewal is not the quality of the original proposal - it is the quality of the relationship during the grant period. Funders renew programs they understand, trust, and feel personally connected to. That connection is built through the small interactions between formal milestones: a phone update when something interesting happens, a thank-you after a site visit, a candid note when something is harder than expected.

Most nonprofits under-communicate. They submit the required reports, comply with the terms, and otherwise go quiet for the duration of the grant period. The funder hears from them again only when the next proposal arrives. Compared with peers who maintain a steady substantive cadence, the silent grantee renews at lower rates, gets smaller renewal amounts, and is invited into fewer special opportunities.

Over-communication is also a failure mode. Generic monthly newsletters, mass email blasts, and “just checking in” emails consume program officer time without delivering anything useful. The standard is substantive cadence - fewer touches, more substance.

The four required moves

A working communication plan for any active grant has four core moves.

1. Timely formal reporting

Every grant has reporting requirements stated in the award letter or the federal Notice of Award. Read them carefully and put every deadline on a shared calendar with a 30-day advance reminder. Submit reports on time, in the format requested, with the data the funder asked for and not the data you wish they had asked for.

Foundation reports are typically narrative-plus-financial, 3 to 8 pages, due 30 to 90 days after the reporting period closes. Federal reports use standardized forms: SF-PPR for performance, SF-425 for financial reporting (Federal Financial Report). Federal reporting cadence is typically quarterly or semiannually, with a final report due 90 days after the period of performance ends.

The most common reporting failure is a budget that does not match the narrative. If the narrative says you served 200 youth and the budget shows 80% of personnel costs spent, the funder will ask why. The narrative numbers and the financial numbers should tell the same story. See the federal grant reporting requirements guide for federal-specific detail.

2. Substantive interim updates

Between formal reports, plan two to four substantive interim updates per year for grants over $25K. An update is a short note (2 to 5 paragraphs, sent by email or in a brief phone call) that conveys one specific thing: a participant outcome, a notable program moment, an early indicator that the work is going well or facing a challenge, an event the funder might want to attend.

Updates should not be retrospective summaries. They should be moments - “Last week, our director of programs wrapped the first cohort and three of the eight participants got jobs in the field. Wanted you to hear it from us before the report.” That kind of message takes the program officer 90 seconds to read and creates a real impression of the work.

Update cadence by grant size:

• $5K to $25K: one mid-period update
• $25K to $100K: 2 to 3 updates per year
• $100K to $500K: 3 to 4 updates per year, plus invitations to events
• $500K+: monthly informal contact during active periods, plus structured quarterly briefings

3. Immediate notification of material changes

Some events require a specific kind of communication: notification, before the funder hears about it from anyone else.

Material changes include:

• Key staff departure (executive director, program director, the named project lead in the proposal)
• Significant budget reallocation (typically more than 10% to 20% across categories, depending on funder rules)
• Major delay in program launch or activity
• Shift in target population, geography, or program design
• Lawsuit, investigation, or significant adverse event
• Loss of a key partner or subcontractor
• Significant change in the organization’s financial position

Notify within 30 days of the change. Federal awards often specify the timing in the terms; missing it can become an audit finding. Foundation rules vary, but the relationship rule is universal: the funder should never learn about a material change from a third party.

The notification should be brief, factual, and forward-looking. State what changed, when, why, and what you are doing about it. Do not over-explain or apologize at length; do not minimize. Give the funder room to ask questions.

4. One face-to-face touch per grant period

Schedule at least one substantive in-person or video call with the program officer during the grant period - separate from a site visit, separate from required reporting. The purpose is to talk through the work, hear how the funder is thinking about the field, and signal that the relationship matters.

For multi-year grants, plan one face-to-face touch per year. For grants over $250K, plan two. For local foundations and community foundations, an in-person meeting is usually possible. For national or out-of-state funders, a 30-minute video call works well.

The touch should be scheduled by the development director and prepared for: review the most recent report and any updates, prepare two or three substantive talking points (program progress, an open question, a moment of pride), and prepare two or three questions for the program officer about the funder’s priorities.

Channel choice

Different channels serve different purposes:

• Email is the default for routine updates, scheduling, and short factual notifications. Keep emails short - 3 to 5 paragraphs maximum. Subject lines should be specific (“Q2 Update on Youth Workforce Grant” not “Quick update”).
• Phone is right for material changes, sensitive topics, and conversations where tone matters. Always offer a phone option when delivering bad news; do not break it in email.
• Video call works well for substantive interim conversations with funders you cannot reach in person. Schedule for 30 minutes, prepare for 20.
• In-person visit is reserved for site visits, capital campaign asks, and significant program milestones. The visit is the highest-leverage funder communication; treat it accordingly.
• Letter is rare but powerful for thank-yous after major events, anniversaries, and personal moments (a program officer’s retirement, a board chair’s recognition).

A useful rule: if the message would change the funder’s understanding of the relationship, use phone or video. If it is informational, email is fine.

Tone and voice

Most nonprofit funder communication errs toward formality and abstract language. The funder reads it, files it, and forgets it. The communication that builds relationships sounds like a human being talking to another human being who cares about the work. Use the program participant’s actual words when sharing a story. Name the staff member who delivered the result. Acknowledge the challenge when it exists.

Avoid:

• “Leverage” used as a verb
• “Stakeholder” without specifying who
• “Impact” without a measurable outcome
• “Game-changing,” “transformative,” “unprecedented” - funders read these all day
• Passive voice that obscures who did what

Use:

• Specific numbers with context (“12 of 40 participants completed certification, up from 8 in the prior cohort”)
• Direct quotes from participants and staff
• Concrete decisions and tradeoffs the team faced
• Honest acknowledgment of what is harder than expected

Specific situations

After a decline

Send a brief, gracious thank-you within two weeks. Do not argue the decision. Ask one question: would the program officer be willing to share what made the request not a fit. About a third will respond with substance. File the response in your CRM next to the application record. If the funder has a reapplication policy, follow it - some require 12 months, some welcome a revised LOI in 90 days. The decline conversation is the one that shapes the next proposal.

After a difficult year

If the program is genuinely struggling - outcomes below target, key staff departures, financial strain - say so directly. Funders prefer candor to spin. The communication should describe what happened, what the team learned, what is changing, and what is being asked of the funder going forward. Funders who learn about difficulty through honest communication often become more committed, not less; funders who feel managed often quietly disengage.

When the program officer changes

When the funder assigns a new program officer to your account, treat it as a re-introduction. Send a one-page summary of the program, your relationship history with the foundation, and the current grant status. Schedule a 30-minute video call to introduce the team. The first six months with a new program officer set the tone for years of future relationship.

When you have nothing new to say

Skip the update. A forced “checking in” message is worse than silence. Wait for something substantive - a participant story, a new outcome data point, an event the funder might want to attend - and send then.

A communications calendar

For each active grant, maintain a simple calendar:

• Required reporting dates (with 30-day advance reminders)
• Planned interim update dates (one per quarter for grants over $25K)
• Planned face-to-face touch (once per grant year)
• Anniversary date (the date the grant was awarded - a useful prompt for thank-you and reflection)

The calendar is most useful when it is shared with the executive director and with program staff. The development director owns execution, but the ED often delivers the most substantive interim updates and most face-to-face touches; program staff often supply the participant stories and outcome data.

Frequently asked questions

How often should we communicate with funders during a grant period?

Beyond required reporting, plan two to four substantive interim updates per year for active grants. The cadence should match grant size: a $250K multi-year grant warrants quarterly check-ins; a $25K one-year grant warrants one mid-period update plus the final report. Communications should be substantive - program progress, a participant story, a notable challenge - rather than “just checking in.” Generic updates damage trust by signaling that you do not have anything specific to share.

When should we notify a funder of program changes?

Immediately when there is a material change: a key staff departure, a significant budget reallocation, a shift in target population, a delay in program launch, or any event that affects what the funder agreed to fund. Most foundations expect notification within 30 days of the change; federal awards often have specific notification requirements written into the terms. Surprising a funder at report time with a change that happened months earlier is the fastest way to lose a renewal.

What goes in a funder report?

Foundation reports typically include: progress against the goals and objectives stated in the proposal, outputs and outcomes data, financial summary showing how funds were spent against the approved budget, success stories or program highlights, challenges encountered and how they were addressed, and plans for the next reporting period or post-grant sustainability. Federal reports add programmatic and financial reporting on standardized forms (SF-PPR for performance, SF-425 for financial). Length runs 3 to 8 pages for most foundations, longer for federal.

How do we handle a site visit from a funder?

Treat the site visit as the most important fundraising event of the year for that funder. Prepare with the program staff who will be present - they should know what to highlight, what numbers to cite, and what stories to tell. Walk the funder through actual program operations, not a slide deck about them. Build in time with program participants if appropriate. Avoid scheduling other meetings or interruptions. After the visit, send a same-day thank-you and a written follow-up within 7 days summarizing what was discussed and any commitments made.

What is the right way to handle a funder decline?

Send a brief, gracious thank-you within two weeks. Do not argue the decision. Ask one specific question: would the program officer be willing to share what made the request not a fit. About a third of program officers will respond with substance. File the response next to the application record. If the funder has a written reapplication policy, follow it. Track every decline as carefully as every award; the patterns across declines often reveal more than the patterns across wins.

Where to go next

For the broader grant lifecycle context, see the grant lifecycle guide. For federal-specific reporting, see federal grant reporting requirements. For the donor-side stewardship rhythm that pairs with funder communications, see the donor stewardship 12-month plan.