A donor file can look large while the reachable audience inside it is much smaller.
A donor contactability report measures how many supporters are eligible for a specific outreach and have at least one channel that is both usable and permitted for that purpose. It separates people who are ready to contact from those who depend on one fragile channel, need a permission decision, or require data repair.
That distinction matters before a campaign forecast, stewardship plan, or reactivation audience is approved. A record count is not a reachable audience. Contactability is the bridge between the two.
What is a donor contactability report?
A donor contactability report is a decision-specific view of whether eligible supporters can be reached through email, mail, SMS, phone, or another approved channel. It evaluates three conditions together:
- Usable: The channel value exists and passes the organization’s current validity rules.
- Permitted: The organization may use that channel for the planned message under its policy, recorded preferences, and applicable requirements.
- Relevant: The channel is available for this campaign, stewardship task, or fundraising decision.
A valid email address does not make someone contactable for every purpose. A postal address does not help a campaign that has no mail component. A donor with a global suppression should not be moved into a repair queue simply because the database contains an old phone number.
Contactability is therefore not a permanent donor attribute. It is a status calculated for a named use case and an explicit as-of date.
Do not confuse list size, contactability, and delivery
These measures answer different questions:
| Measure | Question | Typical evidence |
|---|---|---|
| List size | How many records meet the audience definition? | CRM segment or campaign selection |
| Contactability | How many eligible people have an approved, usable path for this outreach? | Channel values, validity, preferences, suppressions, and campaign rules |
| Delivery | How many messages actually reached the destination? | Send, bounce, return-mail, or call-disposition results |
| Response | How many recipients took the intended action? | Clicks, replies, gifts, registrations, or completed follow-up |
Each measure is a denominator for the next. Delivery rate should not be used to hide a contactability problem, and contactability should not be presented as proof that a message was delivered.
The same discipline applies when campaigns overlap. A fundraising audience overlap report can show which supporters are selected for competing asks; the contactability report shows whether those selected supporters can actually be reached through the planned channels.
Use four mutually exclusive contactability states
Start with the eligible audience for one decision. Then assign every person to exactly one state:
- Multichannel ready: At least two usable, permitted channels are available for this outreach.
- Single-channel fragile: Exactly one usable, permitted channel is available. The donor is reachable, but one bounce, returned letter, or preference change could remove the path.
- Permission-limited: A usable channel value exists, but policy, preference, consent, or campaign rules do not permit its use for this outreach.
- Data repair: No usable, permitted channel is available, and the record contains a missing, invalid, stale, or unresolved value that can be investigated without overriding a suppression.
Keep donors who are not eligible for the outreach outside the denominator. That group may include people excluded by the campaign definition, deceased records, anonymous donors, global suppressions, or other organization-specific rules. Preserve the exclusion reason, but do not label those records as contactability failures.
The order matters. Apply eligibility and suppression rules before looking for repair opportunities. Otherwise a well-intentioned cleanup list can become an instruction to contact someone who should remain excluded.
Calculate three metrics that lead to action
1. Contactable donor rate
Contactable donor rate = (multichannel-ready donors + single-channel-fragile donors) / eligible donors
This is the share of the intended audience with at least one usable, permitted path.
2. Multichannel resilience
Multichannel resilience = multichannel-ready donors / contactable donors
This shows how much of the reachable audience can survive the loss of one channel. It is not a reason to use every channel at once. It is a measure of optionality.
3. Recoverable contact gap
Recoverable contact gap = data-repair donors / eligible donors
This isolates records where validation, identity resolution, preference capture, or responsible enrichment may restore a usable path. Permission-limited donors stay separate because the next action is a policy or audience decision, not routine data repair.
A worked example: the file is 10,000, but the reachable audience is 8,200
Suppose a nonprofit selects 10,000 donors for a year-end update and appeal. After applying the channel rules, the contactability report shows:
| State | Donors | Share of eligible audience | Next action |
|---|---|---|---|
| Multichannel ready | 4,900 | 49% | Use the channel plan; preserve preferences |
| Single-channel fragile | 3,300 | 33% | Protect the available path; seek another approved option during normal interactions |
| Permission-limited | 1,100 | 11% | Respect the restriction; revise the audience or approved channel plan |
| Data repair | 700 | 7% | Assign a reason-specific cleanup queue |
The contactable donor rate is 82%: (4,900 + 3,300) / 10,000. Multichannel resilience is 59.8%: 4,900 / 8,200. The recoverable contact gap is 7%.
The operational story is more useful than “we have 10,000 donors.” The campaign can currently reach 8,200. Two in five reachable donors depend on one channel, and 700 records may return to the audience after appropriate repair. The 1,100 permission-limited records should not be blended into that repair target.
All figures in this example are illustrative. Each organization should set channel validity, permission, and review rules with the appropriate internal owners.
Build the report from reason codes, not one blank-field flag
A blank email is only one possible contact gap. The report should preserve the reason a channel failed its rule:
- Missing channel value
- Invalid format or failed validation
- Hard bounce, returned mail, or disconnected number
- Preference or channel-level suppression
- Global suppression or campaign exclusion
- Conflicting values across systems
- Unknown or stale verification status
- Valid channel, but not approved for this message type
Reason codes make the queue assignable. A database manager can investigate conflicting addresses. A digital team can process confirmed bounces. A relationship manager can request an updated preference during an appropriate conversation. A policy owner can clarify an ambiguous rule without asking staff to make individual guesses.
Every repair should retain the source, change date, and responsible owner. If the organization cannot explain why a contact path became usable, the status is not ready for reporting.
Segment contactability before making a campaign decision
A single organization-wide rate can hide the part of the audience that matters most. Break the four states down by:
- New, retained, reactivated, and lapsed donors
- First-gift or most-recent-gift period
- Gift band or relationship tier
- Acquisition source and campaign
- Preferred and available channel
- Assigned relationship manager
- Geography when it changes channel availability
Use those splits to direct effort, not to create a ranking of donor worth. A high-value segment with weak contactability may justify a careful repair workflow. A large single-channel segment may call for a longer-term preference-capture plan. A recent acquisition source with unusually high data-repair volume may have a form, import, or mapping problem.
For email-specific performance after the audience is built, use an email yield report to connect delivered messages with clicks, gifts, revenue, and list health. Contactability is the upstream audience question; yield is the downstream performance question.
Use a decision rule: launch, repair, redesign, or hold
| Finding | Decision | Required follow-up |
|---|---|---|
| Contactable rate and channel mix support the plan | Launch | Monitor delivery and feed failures back into channel status |
| A material gap is concentrated in fixable records | Repair | Assign reason-coded records, owners, and a recheck date |
| The audience depends too heavily on a channel the campaign cannot use | Redesign | Change the audience, channel mix, timing, or forecast |
| Permissions, suppressions, or source conflicts make the reachable audience uncertain | Hold | Resolve the rule or disclose a narrower decision-ready audience |
Set thresholds locally. A broad stewardship update, emergency appeal, major-gift call list, and reactivation test have different channel needs and risk tolerances. The report should show the threshold, owner, and review date rather than presenting a universal benchmark.
Before results reach leadership, apply the fundraising report preflight checklist to the audience definition, data cutoff, calculation, limitations, and action owner.
Where ReportWerks fits
ReportWerks can bring donor, gift, campaign, channel, and engagement data into a connected reporting workflow so teams can compare the planned audience with usable contact paths and downstream results. The necessary inputs still have to exist: stable donor identifiers, documented permission and suppression fields, channel-validity signals, campaign eligibility rules, and clear source ownership.
ReportWerks should not invent missing permission or treat an unverified value as contactable. Its useful role is to make the rules, gaps, and next actions visible beside the fundraising decision they affect.
Start with one campaign and one repair queue
Choose an upcoming campaign, define its eligible audience, and document what makes each channel usable and permitted. Assign every eligible donor to one of the four states, validate a sample against the source systems, and route data-repair records by reason code.
Then compare the planned list with the genuinely reachable audience. That one change gives forecasts a better denominator, gives staff a bounded cleanup queue, and keeps permission decisions separate from data hygiene. The goal is not to contact everyone. It is to know who can be reached appropriately, where that reach is fragile, and what the team can responsibly improve next.
Sources and current ReportWerks pages reviewed October 1, 2026. All worked-example figures are illustrative.
