A fundraising report should not reach leadership until it passes 12 checks across four gates: context, data, calculation, and decision. The purpose of this preflight is not to prove that every number is perfect. It is to make sure the report is fit for the decision, its limits are visible, and someone is accountable for anything that still needs attention.
Use three release statuses. Pass means the check is complete. Pass with note means the limitation is understood, disclosed, and acceptable for this decision. Hold means the issue could materially change the interpretation or action. One hold stops the release.
That rule gives development, finance, marketing, data, and agency teams a shared answer to a practical question: Are these numbers ready to travel?
The 12-point fundraising report checklist
| Gate | Check | Release question |
|---|---|---|
| Context | 1. Decision and audience | What decision will this report support, and who will use it? |
| Context | 2. Period and as-of time | Are the date range, comparison period, cutoff, and timezone explicit? |
| Context | 3. Scope and exclusions | Which gifts, donors, campaigns, channels, and costs are included or excluded? |
| Data | 4. Source freshness | Did every required source update in time for this decision? |
| Data | 5. Completeness and exceptions | Are expected records present, and are missing or rejected records quantified? |
| Data | 6. Identity and duplication | Could duplicate gifts, donors, households, or touches inflate the result? |
| Calculation | 7. Definitions and denominators | Do the labels match the actual formulas, filters, and eligible populations? |
| Calculation | 8. Reconciliation | Do gifts, adjustments, fees, costs, and totals tie back to approved sources? |
| Calculation | 9. Comparison parity | Are current and comparison periods measured on the same basis? |
| Calculation | 10. Segment tie-out | Do channel, campaign, audience, and gift-band segments sum to the reported total? |
| Decision | 11. Interpretation and limits | Does the narrative distinguish fact, inference, and unresolved uncertainty? |
| Decision | 12. Owner and next action | Is the decision, owner, due date, and report version recorded? |
The checklist is intentionally ordered. A perfectly calculated retention rate can still mislead if the report silently changed its eligible donor population. A reconciled revenue total can still be unusable if its cutoff does not match the comparison period. Context errors travel downstream.
Gate 1: Lock the context before reviewing metrics
1. Name the decision and audience
Write one sentence at the top of the review copy: “This report helps [audience] decide [decision] by [date].”
“Review fundraising performance” is not specific enough. “The development director will decide whether to shift October acquisition spending between paid search and direct mail” tells the reviewer which metrics, costs, time horizon, and level of confidence matter.
2. Fix the period, cutoff, and comparison
Show the reporting period and the exact as-of time. Then label the comparison: prior calendar period, prior fiscal period, same campaign day, budget, forecast, or target. If a gift processor closes on one clock and the CRM imports on another, record the chosen cutoff rather than allowing each source to imply its own.
A fundraising data freshness report can help determine whether each source is current enough for the decision. Freshness should be evaluated by source, not assigned to the dashboard as a whole.
3. State scope and exclusions
List the included entities and the meaningful exclusions. Examples include soft credits, pledges, matching gifts, donor-advised fund grants, test transactions, refunded gifts, in-kind support, restricted revenue, agency fees, or staff time.
This is not fine print. A result described as “campaign ROI” means something different when it excludes fulfillment, platform, or agency costs. If the scope would change a reasonable reader’s decision, it belongs beside the metric.
Gate 2: Prove the inputs are usable
4. Check source freshness
For every required source, record its latest successful load, expected cadence, and whether late-arriving data is normal. A source can be technically available and still be too old for a pacing decision.
5. Quantify completeness and exceptions
Compare expected inputs with received inputs. Count rejected rows, unmatched campaign codes, gifts without designations, costs awaiting invoices, and records held for review. Do not hide exceptions in a general caveat. Quantify them and estimate which reported metrics they could affect.
The fundraising exception report offers a useful pattern: turn each material gap into an owned queue rather than a passive warning.
6. Test identity and duplication
Review duplicate keys at the grain used by the report. Gift-level reports need a stable transaction key. Donor-level reports need documented rules for contacts, households, organizations, anonymous gifts, and merged records. Attribution reports also need a rule for repeated touches and cross-device activity.
Record how many duplicates were removed, merged, or left unresolved. “Deduplicated” is not an adequate audit note unless the reviewer can see what counted as a duplicate.
Gate 3: Make the math reproducible
7. Verify definitions, filters, and denominators
For every decision-driving metric, inspect three things:
- Numerator: What event, amount, or person is counted?
- Denominator: Which population was eligible to produce that outcome?
- Filters: Which dates, statuses, sources, gift types, and exclusions shape the result?
Use a reporting rules registry to keep those definitions visible and versioned. A metric label should never be expected to carry the full definition by itself.
8. Reconcile revenue and costs
Tie reported gift revenue to the approved transaction or CRM source, then account for refunds, reversals, chargebacks, reclassifications, and other adjustments. Tie costs to the approved financial or operational source and label estimated, pending, allocated, or excluded amounts.
If adjustments arrived after an earlier report, preserve both the originally reported and current reconciled values. The gift adjustment audit provides a practical model for explaining why campaign revenue changed after the first close.
9. Confirm comparison parity
Ask whether both sides of every comparison use the same calendar logic, gift statuses, attribution window, cost scope, donor definition, and data maturity. If this year includes seven fully settled days and last year includes seven days plus late gifts posted later, the comparison is not yet like for like.
When parity is impossible, do not erase the comparison. Change its status to pass with note and explain the direction of likely bias, or hold it if the mismatch could reverse the decision.
10. Tie segments back to the whole
Sum the segments and compare them with the headline total. Differences may be legitimate: a gift can have multiple assisted channels, a donor can move between gift bands, or an “unknown” bucket may sit outside displayed segments. The report should make that logic explicit.
Use a small tie-out block:
- Headline gift revenue: $500,000
- Displayed channel total: $487,500
- Unassigned source: $12,500
- Difference after explanation: $0
These are illustrative numbers, not a benchmark. The important practice is to explain the bridge instead of letting two plausible totals compete.
Gate 4: Make the report safe to act on
11. Separate evidence, interpretation, and limits
Use three short labels in the review notes:
- Observed: What the approved data directly shows.
- Interpretation: What the team believes may explain the result.
- Limit: What is incomplete, uncertain, or outside the report’s scope.
“Email revenue declined 8%” is an observation. “Message fatigue caused the decline” is an interpretation unless the report contains evidence that isolates that explanation. Keeping the two separate makes the discussion more useful, not less decisive.
12. Assign the decision, owner, due date, and version
A released report should end with the action it supports. Record the decision, accountable owner, next review date, and version. If the report is preliminary, state what will trigger the final close.
This last check prevents a familiar failure: a carefully reviewed report is distributed, discussed, and archived without changing a budget, fixing a data gap, contacting a donor segment, or assigning a follow-up.
Use a pass, note, or hold release rule
Run the preflight with one primary reviewer and one accountable approver. The reviewer performs the checks; the approver accepts any pass-with-note limitations and owns the release decision.
- Mark each check pass, pass with note, or hold.
- For every note or hold, record the affected metric and likely decision impact.
- Resolve all holds before distribution.
- Place accepted notes beside the relevant metric, not in a distant appendix.
- Save the released version with its as-of time and approver.
Start with the next recurring fundraising report. Run the 12 checks once, then convert repeated failures into automated tests, source-level alerts, or clearer reporting rules. The goal is not a longer approval ritual. It is a shorter path from trustworthy numbers to an owned decision.
