Coordinate donor updates with confidence
Fictional example: Northbank Community Partnership brings a central fundraising team together with program teams at several locations. This guide helps fundraising and program staff coordinate donor communication using applicable approved commitments, appropriately cleared stories, supportable impact evidence, and clear role handoffs. It is a working reference—not a donor record, approval decision, or live work queue.
Choose the right next move
Use each scenario to identify what can be assembled and what needs an accountable owner.
- Evidence is ready; audience is clear A program owner has verified the reporting period and outcome, and the relationship lead has identified the intended donor audience. Assemble the update against the applicable approved commitment and route the draft through the communications review.
- The story is compelling, but its use is unclear A field colleague shares a participant story, but the team cannot confirm that the proposed donor-facing use is covered. Hold the story and identifying details; ask the designated story-use owner to resolve the permitted use. Consider verified, non-identifying program evidence only if it is suitable for the update.
- The request crosses programs or locations A relationship lead requests an outcome summary spanning two locations with different program owners. Ask each relevant owner to verify their own portion, and clarify the applicable commitment and reporting scope before combining information.
Worked handoff: a proposed program story
Northbank example: a program colleague offers a participant story for a donor update due next week.
- Relationship lead: state the intended audience, applicable commitment, requested content, and deadline. Do not describe the story as cleared.
- Program evidence owner: verify the outcome, reporting period, scope, and source for each proposed impact claim.
- Story-use owner: resolve whether the proposed story and details may be used for this audience and purpose.
- Communications reviewer: review the assembled draft after the relevant checks are resolved; return unclear claims or uses to the responsible owner.
If commitment scope, evidence, or story use remains uncertain, pause that element and route the question to its accountable owner instead of filling the gap with an assumption.
Four checks before a donor update
Illustrative Northbank coordination reference—not policy, a system of record, or a live queue.
| Check | What it establishes | Accountable role | If unclear |
|---|---|---|---|
| Stewardship commitment | The approved promise or reporting scope relevant to this request and relationship | Relationship lead | Confirm the applicable commitment and its audience, program, and location scope |
| Story use | Whether the proposed story and details are cleared for the intended purpose and audience | Story-use owner | Hold the story and route the permitted-use question to that owner |
| Impact evidence | The verified outcome, source, time period, and population or program scope behind a claim | Program evidence owner | Return the claim for source and scope verification; do not estimate or combine unlike measures |
| Ownership | Who coordinates the request, verifies program information, resolves story-use questions, and reviews the draft | Relationship lead coordinates; relevant owners resolve their checks | Pause the affected element and ask the designated service owner to clarify the handoff |
Who owns each handoff
These role-based cards describe responsibilities in the fictional Northbank example, not named employees. The relationship lead coordinates the request; subject owners resolve questions within their remit. When a request spans locations, each relevant program owner verifies their own scope before information is combined.
Ownership and questions
Content owner in this fictional example: Public Service and Program Operations. Send an outdated-reference or guidance correction through the relationship lead, naming the stewardship commitment or evidence definition that needs clarification.
The relationship lead coordinates the request. Questions about commitment scope, evidence, and story use go to the respective accountable owners; unresolved cross-team conflicts go through the organization’s designated service owner.