Donor relationships
A weekly donor follow-up routine your team can keep
Build a weekly donor follow-up routine with clear owners, useful notes and respectful contact preferences. Includes a downloadable CSV template.
By Relae team4 min read
A donor follow-up plan turns the context of a relationship into a next step someone can complete. It helps your team remember a promised introduction, respond to a question or share an update that matters to that person.
For a small team, the weekly review should produce a usable work list. It should also make space for a deliberate decision to wait. Sending a message simply because a task is overdue can be less helpful than checking whether the conversation still makes sense.
Begin with promises and preferences
Gather open actions from recent conversations, gifts, meetings and events. Check that each action has an owner, a reason and enough context to complete it. Pull urgent donor questions and unfulfilled promises forward before adding speculative outreach.
Review contact preferences before assigning a channel. A phone number or email address in a record does not, by itself, settle whether a particular communication is appropriate. Follow your organization's applicable contact rules and documented preferences.
The Donor Bill of Rights is an ethical reference for professional relationships and truthful responses to donor questions. Apply that principle by making your notes and tasks serve the conversation rather than treating a donor as a sequence to run.
Keep a separate place for acknowledgment work so a fundraising conversation does not obscure a basic thank-you. Where another colleague owns the response, confirm the handoff rather than sending a competing message.
Write the next action so another person could do it
A good action states the outcome and the context. “Ask the program lead for the accessibility update requested on Tuesday” tells a colleague what to do and why. “Call donor” requires them to reconstruct the relationship first.
Include a due date tied to a real commitment or a sensible review point. Record whether the date means contact is promised, internal preparation is needed or someone should reconsider the next step. That distinction keeps reminders from turning into automatic pressure on donors.
Use the donor follow-up CSV template for a simple starting point. It contains headings and one clearly fictional example. Replace the example, keep the file access-controlled and link to your authorized donor record rather than copying sensitive notes into several spreadsheets. The template is a planning aid, not a Relae import format.
The most useful fields are donor reference, relationship owner, reason, next action, due date, permitted channel, status and outcome. Add more only when the team uses them to make a decision.
Run a short review around decisions
Choose a regular time when the people responsible for relationships can make commitments. Work through four questions:
- What did we promise, and what needs a response now?
- What has changed enough to alter a relationship plan?
- Which actions can we realistically complete before the next review?
- Where do we need information, an introduction or a decision from someone else?
Select a manageable list based on the time and people available. If a task repeatedly rolls forward, clarify its purpose or remove it. A permanently overdue list hides the work that matters.
Look at context as well as giving. A first-time supporter who asked a specific question may need an immediate reply. An established supporter may have asked for no contact during a particular period. The right action can be an internal note to respect that preference.
A fictional example: change the plan when context changes
In this fictional example, Cedar Gallery plans to invite a supporter to discuss a new education project. Before the meeting, the supporter emails asking for a written update instead because they are travelling.
The relationship owner marks the proposed meeting action as changed, records the request and assigns a colleague to prepare the update. The original date remains useful as context, but the team does not keep chasing the meeting. Once the update is sent, the owner records the outcome and decides whether any further step was actually agreed.
A completed task now represents a real action. The next task reflects the donor's response. A second colleague can understand the relationship without reading an entire inbox.
Close the loop and inspect the routine
At the next review, distinguish completed actions, actions waiting on someone else and actions that no longer apply. Record the outcome before creating another reminder. Do not infer a donor's motivation from silence; record the observable fact and use judgment about whether to follow up.
Relae's donor record connects giving history, notes and relationship actions. See working a donor record and moves and the scorecard for the product workflow. The small-team donor management guide shows how that routine fits into the wider record.
Review whether promises are being kept and colleagues have enough context to act. Those questions tell you more about the health of the process than the number of tasks created. A useful weekly plan leaves your team knowing which relationships need attention and who will take the next step.
Written by the Relae team. These guides share practical workflows and clearly labelled examples. Product documentation describes individual features; local rules and your organisation’s policies govern your own records and reporting.
Explore product help