Operations
Part of Donor acquisition: judging a channel by retained donors, consent and capacity
Who signs each line of a donor acquisition checklist
Each line of a donor acquisition release checklist needs a named signer and a closing action: audience, claims, consent, cost and measurement, with sample rows.
What to take away
- Every checklist line gets a pass, fail, or accepted exception, and a named signer. A blank line blocks release.
- Each line closes with one actionowner sign-off, program lead confirmation, a named authority check, finance review or a dated decision.
- Consent is checked against the authority that sets it, not against last year's form.
- When you change a claim, a gift array, or an audience, the old approval dies with it.
- File the signed checklist beside the released version, so the next audit starts from evidence.
One line, one signer
A release checklist works when every line has one signer and one closing action. A line nobody signs cannot pass, because nobody can be asked what they checked. Each line also records pass, fail, not applicable, or an accepted exception, with the reviewer, the date and the source.
| Line | Closed by | What the line records |
|---|---|---|
| Audience | Owner sign-off | Segment, exclusions, expected gift range |
| Claims | Program lead confirmation | Each statement about impact, and its program source |
| Consent | Named authority check | Basis for contact, and where it is recorded |
| Cost | Finance review | Budget, expected cost per donor, refund policy |
| Measurement | Dated decision | Retention window, stop rule, review date |
Release Gate Fields
- Audiencesegment, exclusions, gift range
- Claimsimpact statement, program source
- Consentbasis, recorded location
- Costbudget, cost per donor
- Measurementretention window, stop rule
Copy the table into the release ticket before the first send. That gives the team a runnable checklist, not a policy statement.
Two filled-in lines
A pass and a fail show the standard. A pass names its segment, exclusions, reviewer and date. A fail names what is missing, the owner and the recheck date, and it stays a fail until that gap is closed.
| Line | Entry | Result |
|---|---|---|
| Audience | Segment: lapsed monthly givers, 12 to 24 months. Exclusions: major donors. Expected gift range: $20 to $35 typical. | PASS. Reviewer: annual fund manager. Date: 2026-02-03. |
| Claims | Impact claim about meal cost, source FY25 program report page 4. | FAIL. Program lead confirmation missing. Owner: annual fund manager. Recheck: 2026-02-10. |
The pass does not rescue the fail. Release waits until every line is a pass or an accepted exception, so the claims line has to close before the first send.
The consent line: which authority signs
The consent line is checked against the authority that sets the rule. Contact permissions, receipting, and donor data handling are set by jurisdiction, not by house style. In the United States, check IRS rules and state charity regulators.
Canada is the second-market case. The CRA sets receipting and disbursement quota rules, and CASL sets consent and implied-consent windows. Under the anti-spam statute, a person who alleges they have consent has the onus of proving it, so the line needs a recorded basis for contact, not a recollection.
Other Canadian rules can apply, including PIPEDA, BC PIPA, and Quebec Law 25 and Bill 96.
For receipts in the US, an acknowledgment for a gift of $250 or more must name the organization and state the amount of a cash contribution. The receipt check therefore compares the legal name and the amount against the gift record.
Confirm your consent basis and your receipt wording with a qualified Canadian charity lawyer or the CRA before the campaign sends. Cross-border gifts from US donors raise IRS questions that belong with a cross-border giving specialist, not with the campaign manager.
The cost line: spend per retained donor
Cost per acquired donor is the figure most teams report and the one that misleads most. A channel that delivers cheap names and no second gift costs more than a channel with a higher first-gift cost and steady retention.
Work it in your own numbers. Take total spend on the channel, divide by donors acquired, then divide again by the share who give a second time within your retention window. Use a 12 month retention window and compare channels on that second figure.
Your CRM holds the retention data; pull it before you renew a contract. A channel judged on gross gifts alone fails the line, because gross gifts leave out cost and refunds.
The measurement line: one normal path, one failure path
Run the campaign on a defined population with a comparison group, and watch one normal path and one failure path end to end. The measurement line passes only when each check below is ticked.
- The gift array renders and the confirmation email arrives.
- A declined card produces a working retry, not a dead end.
- An unsubscribe removes the contact from every send list.
- The receipt matches the amount and the legal name.
- What you could not verify is recorded, with an owner.
Put the retention window, the stop rule and the review date on the same line, so the decision carries a date.
When an approval expires
An approval expires when the audience, the claim, or the gift array changes. Retest the changed item; do not carry the old sign-off forward. A new claim needs a new program lead confirmation, and a new audience needs a new owner sign-off.
An audit works from the other end. Take one finished campaign inside your donor acquisition scope and recover every approval behind it. Any unexplained blank is a control gap with an owner attached.
Common questions
Can a blank line be released with a note?
No. A blank line blocks release. The line needs a pass, a fail, or an accepted exception recorded with the reviewer, the date and the source behind the decision.
How should results be reviewed?
Review net acquired donors and later retention together, with cost, quality, exclusions, and known limits.
What should a team avoid?
Judging channels by gross gifts without cost or refunds. When an error reaches a donor, preserve the record and correct the public or internal output where it appeared.
