Start donor segmentation with four action rules

Donor segmentation for nonprofits should produce a different next action, not merely a smaller list. Before you save a segment, write four rules: who enters, who exits, what your team does, and what suppresses that action. If one rule is missing, the segment is not ready to use.

That discipline matters more than starting with a long menu of donor types. A lean team needs lists it can explain, test, and retire.

Begin with the decision

Current segmentation tools can filter contacts in many ways. Microsoft for Nonprofits' current preview segmentation report includes constituent type, donor status, giving range, age, donation date, and location. DonorDock says its current CRM can filter by giving history, frequency, recency, tags, custom fields, and interests, then use those segments for automations or targeted messages.

Those options are inputs, not a strategy. Start by finishing this sentence:

When a contact enters this segment, our team will ______.

“Understand our donors better” is too vague. “Review new online donors every Friday and assign the next follow-up” is usable. So is “exclude active monthly donors from this one-time-gift appeal.” The action tells you which records matter and how precise the segment must be.

Do not infer a donor's motivation, capacity, or preferred message from a convenient field. Use facts your system actually records: completed gifts, dates, recurring status, event participation, communication preferences, and accountable staff decisions.

Give every segment four rules

Write one small action card for each segment.

1. Entry rule: the observable condition that adds a contact. Name the record, status, and time window. “New donor” might mean a contact whose first completed gift arrived during a period your team defines.
2. Exit rule: the event that removes the contact. A new-donor segment could end after a second completed gift, after the follow-up window closes, or after a staff review. Choose one rule that matches the action.
3. Next action: the message, review, or assignment triggered by membership. Name the owner and cadence. A saved list that nobody opens does not need to exist.
4. Suppression rule: the condition that blocks or delays the action. Recorded communication preferences, an unresolved identity question, or an active payment-recovery workflow may take priority.

The exit rule is the part most likely to be skipped. Without it, a contact can remain “new,” “lapsed,” or “needs follow-up” long after the label stops being true. That stale membership becomes hard to distinguish from current work.

Keep the segment definition beside the saved filter. Record its owner, creation date, and review date too. A teammate should not have to reverse-engineer what “Fall appeal list 2 FINAL” means.

Start with three useful examples

Your first segments should match work your team already intends to do. These three patterns are safer than copying another nonprofit's thresholds.

New-donor review

• Entry: first completed gift within your chosen review window.
• Exit: staff review completed, second completed gift, or window closed.
• Action: verify contact details and assign the next appropriate follow-up.
• Suppression: unresolved duplicate-contact review or a recorded communication restriction.

If identity is uncertain, resolve it before treating two records as two people. Use the three donor-duplicate checks rather than expanding the audience with uncertain records.

Active recurring-donor stewardship

• Entry: recurring plan is active and at least one payment has completed.
• Exit: plan ends, payment state moves into an exception workflow, or the stewardship period closes.
• Action: send the update or complete the review designed for current recurring donors.
• Suppression: a failed payment already has an automated retry or staff owner.

A recurring donor can belong to several analytical groups, but that does not justify competing messages. If a payment fails, the four-state recovery workflow should control the next operational action until the exception is resolved.

Lapsed-donor review

• Entry: no completed gift since the date your organization defines.
• Exit: a new gift completes, a staff decision removes the contact, or the review period ends.
• Action: inspect the record and decide whether the planned outreach is appropriate.
• Suppression: a more recent gift exists in another system, identity is unresolved, or communication preferences block the channel.

There is no universal lapse window or major-gift threshold. Your campaign cycle, giving frequency, data completeness, and internal policy determine the useful boundary. Document it instead of hiding it inside a filter.

Resolve overlaps before sending

One contact may qualify as new, recurring, event-attending, and locally based. That overlap is useful for analysis. It becomes a problem when four lists produce four simultaneous actions.

Set a priority rule for each campaign or review cycle. For example, an active service exception can outrank routine outreach, a specific event message can outrank a general newsletter, and a recorded communication preference always controls the channel. These are operating examples, not universal priorities; your team owns the final order.

Create the final audience from current records, then keep one visible reason for inclusion and one visible reason for any suppression. Tags can help describe a contact, but a tag alone should not quietly authorize a message forever.

Test five records before launch

Use five real-shaped contacts to test the rules:

1. A first-time donor whose gift completed yesterday.
2. An active recurring donor with no exception.
3. A recurring donor whose latest payment failed and already has an owner.
4. A contact who appears to be duplicated under two email addresses.
5. A formerly lapsed donor who gave again this morning.

For each record, ask: Did the contact enter for the stated reason? Is the next action unambiguous? Does a higher-priority condition suppress it? What exact event removes the contact?

The segment passes only when those answers match the action card. Re-run the five cases after changing a filter, importing history, or moving to a new system.

CharityStack currently keeps contacts, subscriptions, receipts, and payouts tied to each gift and lets teams query fundraising data through its assistant. Its first-party site labels segmentation and automated engagement as coming soon, so do not plan around that availability yet. Use the four-rule test to evaluate the donor records you can operate today and any future outreach tool before it reaches a live audience.