Donor Qualification: A Working Guide to Who Earns a Place in the Portfolio

What is donor qualification?

Donor qualification is the process of confirming that a prospect belongs in an active major-gift portfolio. It converts a name with an estimated capacity rating into either a qualified prospect with a strategy, or a disqualified one that goes back to annual giving.

It sits between identification and cultivation. Identification produces candidates, usually from screening, giving history or referrals. Qualification is where a human being finds out whether the candidate is real. Cultivation is what you do once the answer is yes.

The stage is the most skipped and the most expensive to skip. An officer who never disqualifies is carrying dead weight that looks like a pipeline.

What qualification actually tests

Three criteria, and a prospect needs all three.

Capacity. Can this person give at a level your organisation counts as major? Set that floor explicitly first. It might be $5,000 in a small shop or $100,000 at a large institution. A capacity rating from a screening is a starting hypothesis, not a qualification. Screening data is a snapshot built from public records, and it ages. If you want the detail on where that data comes from and what it can and cannot tell you, we wrote a separate guide to wealth screening and continuous monitoring.

Affinity. Is there a reason this person would give to you? Wealth with no interest in your mission is not a prospect, it is a name. Michigan's policy is explicit that assignment takes account of demonstrated interests, affinity, degree relationship and established institutional relationships, not capacity alone.

Access. Can you get a meeting? A prospect you cannot reach is not qualified, however good the rating looks. This is the criterion most often skipped, and it is the one that quietly fills portfolios with names nobody has ever spoken to.

The three interact. High capacity with weak affinity is a cultivation problem worth solving. High affinity with no access is usually a referral problem. High capacity with neither is a disqualification.

The qualification visit

Qualification usually resolves in a conversation. The point of that conversation is not to ask for anything. It is to find out whether the other two criteria are real.

You are trying to leave with answers to three questions: What does this person care about in our work? What is their relationship to us actually like, as opposed to what the database says? And is there a reason to meet again that they would agree to?

A clear "not now" is a successful qualification visit. It changes your strategy, which is what the stage is for. Apra practitioner guidance defines a significant activity as one that moves the relationship forward or determines a disqualification. Both outcomes count.

Expect a meaningful share of the names entering qualification to leave. That is the stage working, not failing.

What published policies actually require

Here is where most advice on this topic gets vague. Real institutions publish their prospect management policies, and those policies contain specific operating rules. They also disagree with each other, which is the most useful thing about them.

Read that table again and notice what it does not contain: a standard. Berkeley gives six months to qualify. Michigan uses six months to mean something different, the horizon for an intended visit. GW's process could run a full year. Three credible institutions, three incompatible clocks.

That is the finding. Published numerical rules are institutional governance choices, not validated sector benchmarks. Anyone who tells you that three attempts is best practice, or that six months is the industry standard for qualification, is quoting one university at you.

So do not copy a number. Choose one, write it down, and use it as a trigger to review rather than a verdict.

Count moves, not touches

A stalled prospect can look active indefinitely if routine communications keep resetting the clock. A routine bulk newsletter send, by itself, is a recorded touch, not a move.

Teams need a shared definition. Ours is: a meaningful move produces new information, a new commitment, a decision, or a donor-specific next step.

A conversation that clarifies philanthropic interests counts. An accepted meeting counts. An introduction from a board member counts. A proposal discussion counts. A clear "not now" counts, because it changes what you do next.

A newsletter, an automated message or a generic event invitation should not automatically count merely because the CRM recorded it. Note the hedge, and keep it. A personalised event invitation that produces a real conversation genuinely is a move. What should not happen is a stagnation clock resetting because a bulk email went out.

The portfolio review: four questions

For every actively assigned prospect, a review should answer four questions. Berkeley requires at least four portfolio reviews a year; quarterly is therefore a reasonable cadence to consider.

1. Do we still have credible evidence of capacity and institutional fit or affinity?
2. What have we learned from reciprocal engagement since the last review?
3. What is the next donor-specific move, who owns it, and by when?
4. If the prospect has passed our own time-in-stage or outreach trigger, what documented evidence justifies keeping them?

The first three test whether the assignment is active in substance rather than only in the database. The fourth preserves judgment without making judgment invisible.

Five destinations, not two

The mistake is treating review as a binary: keep or drop. Most stalled prospects belong somewhere in between, and collapsing the options is what makes teams avoid the decision entirely.

The distinction that matters most is between "not ready now" and "not a prospect." UNC told Apra Connections it codes emerging-wealth prospects and revisits them after several years, removing the code only if they never reach principal-gift capacity. Berkeley's own "Disqualified" status is framed as not a major-gift prospect at this time, with the reason recorded.

Long-term monitoring and recycling are the two destinations that need a mechanism, and this is the practical problem with both. A prospect you have parked is a prospect nobody is watching, and the whole justification for parking rather than disqualifying is that circumstances change. A job change, a company sale, a board appointment, a liquidity event: these are the reasons a recycled prospect becomes worth working again, and none of them announce themselves in your CRM. Whether you solve that with a calendar reminder, a saved query or continuous monitoring, the parked file needs some way of telling you when it has changed. Otherwise "monitoring" is just a nicer word for forgotten.

Do not automate the exception

Rules are most useful when they surface the cases that need a human. They are least useful when they execute automatically.

Michigan's policy says plainly that the donor relationship is paramount and its assignment guidelines are not absolute where circumstances suggest another course. When LSU Foundation rebuilt thirty portfolios, its team found that database information rarely represented the whole relationship. Gift officers reviewed the proposed changes, and leadership approved the exceptions.

The lesson is to make exceptions inspectable rather than invisible. "I know them" is not evidence. "The dean has agreed to make an introduction next month, review after that attempt" is.

A workable exception policy fits in four lines. Fill in your own answers:

• Trigger: when must this record be reviewed?
• Evidence: what counts as a meaningful move or a reasonable attempt?
• Destination: active, monitor, recycle or disqualify?
• Exception: who approves it, on what evidence, and when is the next review?

Where data ethics fit

Removing someone from a portfolio and removing them from your database are different decisions, and conflating them causes trouble in both directions.

CASE instructs fundraising professionals to safeguard prospect information and to retain only information relevant to cultivation, solicitation and stewardship. AFP's code of ethical standards emphasises donor privacy, data protection and a donor's ability to ask that their information not be used going forward.

Neither says that ending an active assignment requires deleting a constituent record. But inactive status is not a justification for holding irrelevant personal detail indefinitely either. Separate the three questions: should this prospect remain actively worked, should they remain identifiable for future review, and what personal information does your own privacy and records-retention policy allow you to keep?

Frequently asked questions