Donor management that gives a small team more reach

Donor management connects what someone has given, what matters to them and what your organization should do next. For a small fundraising team, the aim is to make informed decisions without needing a different person to assemble every part of the picture.

A useful donor record helps a colleague answer three questions: What do we know? What have we promised? Who is taking the next step? More fields do not automatically make those answers clearer. Start with a dependable record and a routine your team can keep running during a busy campaign.

Build a record that supports a conversation

Keep identity, giving and relationship information distinct. An address change should not rewrite a gift. A colleague's interpretation should not look like something the donor actually said.

Use a shared minimum record:

• A stable donor identifier, name and verified contact details.
• Giving history with original transaction references and sources.
• Communication preferences, restrictions and the source of each preference.
• Relevant conversations with dates and factual notes.
• A relationship owner and the next agreed action, where appropriate.

Record only information your team has a legitimate reason to use. Give people access according to their responsibilities. The Donor Bill of Rights, developed by fundraising professional bodies, provides a useful ethical reference for acknowledgment, confidentiality and professional relationships.

Before importing several files, agree which system owns changes to names, addresses and preferences. If you already have a CRM, decide how it fits into the process. Our guide to reconciling giving alongside an existing CRM explains that handoff.

Choose priorities using evidence and judgment

A list ordered by lifetime giving tells you one thing. It does not tell you who is waiting for a promised call, who has just raised a concern or who wants to understand a particular program.

Start each week with three groups: people who need an acknowledgment or response; people with an agreed next step; and relationships worth reviewing because something meaningful has changed. A new gift, event conversation or unanswered question can create context for a thoughtful action.

Use ratings to organize attention, then check the evidence behind them. A score cannot establish a person's willingness to give. Nor should an estimated capacity become an instruction to ask for a particular amount. The person responsible for the relationship needs to decide whether the proposed step is appropriate.

Relae connects a donor's giving record with relationship work, ratings and next actions. See how donor records work and how ratings work for the product's approach.

Give every commitment an owner

A relationship can involve several colleagues while still having a clear owner. That person coordinates the next step and checks that messages fit together. Someone else can complete an individual task without taking over the relationship.

Write actions as observable outcomes. “Send the access-program update requested at the event” is actionable. “Stewardship” is a category. Add a due date when there is a real commitment or useful review point, and distinguish a reminder to reconsider from a promise to contact someone.

Keep notes concise enough that another colleague can continue the conversation. Record what happened, what the donor requested and any promise your team made. Avoid speculation about personal circumstances. Close completed actions and create a new one only when there is a reason.

A fictional example: one relationship, several signals

In this fictional example, Harbor Arts has a development lead and a part-time administrator. A supporter makes a gift through an online page, attends a performance and asks a board member about relaxed performances. Those signals sit in three separate places.

The administrator checks the gift against its source and links it to the existing donor. The development lead records the question as a dated conversation, checks contact preferences and assigns herself an action to send the requested program information. The board member can see that the follow-up has an owner.

The useful change is shared context. The team can respond as one organization without each person repeating the research or assuming someone else has replied.

Review the routine before buying more complexity

Run a weekly check on unresolved records, overdue promises and relationships with no clear owner. Look for causes: incomplete imports, unclear responsibilities or actions that were too vague to complete. Use the weekly donor follow-up guide to turn the review into a working habit.

When evaluating donor management software, try the same representative scenario in each product. Bring a small, approved sample with a duplicate, a refund, a contact preference and a real follow-up question. Ask how you inspect matching decisions, correct a mistake, restrict access and export your records. Your team should be able to explain the result without relying on the vendor to interpret it.

Explore Relae's workflow to see how giving records and relationship work connect. Start with one dependable weekly routine, then expand the parts that help your team act with greater confidence.