Board Reporting Without Pulling Reports: The ED’s Fundraising View (2026)
The board pack is the most expensive document your organisation produces and one of the least read.
It takes two days somewhere between finance and development. It arrives full of totals against budget. And at the meeting a trustee asks a question it does not answer, usually some version of “are we going to make it?”, at which point somebody says they will follow up.
The problem with the standard nonprofit board fundraising report is not effort or software. It is that most board fundraising reports describe what happened, while boards need to know what is about to happen and what they are supposed to do about it.
Quick answer: Boards need pipeline and trajectory, not just totals against budget. Report on where money is coming from next, what changed, what is at risk, and what you need from them. Use AI to assemble and draft, never to interpret. Keep it to one page plus an appendix.
Why the standard pack fails
It is backward-looking. Revenue to date against budget. That is history, and by the time a board sees it, it is at best a month old.
It has no pipeline. The number that predicts the next two quarters, what is in cultivation and at what stage, is usually absent entirely, because it lives in the development director’s head or in a CRM nobody else reads.
It does not distinguish signal from noise. A 12% variance might be one delayed grant or a structural collapse in individual giving. Presented as a variance, it looks identical.
It gives the board nothing to do. Trustees who receive information without a decision attached will either rubber-stamp or ask questions that send staff away to prepare more information. Both waste everyone’s time.
What actually belongs in it
Five sections. One page. Everything else is appendix.
1. Where we are, in three numbers
Revenue to date against target. Same point last year. Projected year end, with the assumption stated.
That third number is the one boards want and rarely get. It requires judgement, which is exactly why it should come from a human and why it should carry its assumption in the open: “assumes the two pending foundation decisions land, which is roughly 60% likely”.
2. What is coming, by stage
The pipeline. Major gift prospects by cultivation stage, identification through qualification, cultivation, ask and stewardship, with totals at each. Grants pending with decision dates. Anything time-bound.
This section is what turns a report from history into a forecast, and it is the section most commonly missing.
3. What changed since last time
Three to five bullets. New significant prospects, anything lost and why, notable shifts in retention or recurring revenue, anything that alters the year-end projection.
Boards remember change far better than levels. A trustee will not retain that you are at 63% of target. They will retain that a major donor stepped back and why.
4. What is at risk
Named, with a number and a mitigation. Concentration risk if one funder is a large share of income. Recurring revenue leaking through failed payments, which is worth surfacing because it is fixable and quantifiable, and most organisations lose 10 to 15% of monthly recurring revenue to unrecovered failures. Capacity risk if a gift officer has left and a portfolio is unowned, which is exactly the handover problem and a legitimate board matter.
A board that hears about risks early forgives them. A board that discovers them at year end does not.
5. What we need from you
The section that makes the rest worth writing. Specific asks: three introductions, two thank-you calls, a decision on the campaign timeline. Named where possible.
Ending a board report with a request rather than a summary changes what a board meeting is for.
Where AI helps, and where it must not
Assembly. Pulling figures from the CRM, the donation platform and finance into one place. This is tedious, error-prone, and the largest share of the two days. Genuine win.
Drafting. Turning your bullets into readable prose in your organisation’s voice, and producing the narrative sections that always get written last and worst. Gratefully drafts “stewardship notes, thank-yous, board updates, briefings” in your voice, which is precisely this job.
Surfacing what changed. Diffing this quarter against last and flagging what moved is a comparison task, and doing it by hand is why nobody does it properly.
Not interpretation. The projection, the assumption behind it, the judgement about which risk is material: those are yours. A board is being asked to govern on the strength of that judgement, and it needs to be a person’s.
Not the ask. What you need from the board comes from knowing your trustees. No tool knows which one will actually pick up the phone.
The tooling
For the executive view specifically, Gratefully is our pick. It gives executive directors “the cultivation picture in one view, without pulling reports”, along with quarterly growth summaries showing untapped revenue with quarter-on-quarter trends, lapsed recoverable donor counts, and pipeline totals by stage. Those map almost exactly onto sections two and four above, and it drafts the board update as well.
The practical value is that the pipeline picture exists continuously rather than being reconstructed the week before every meeting. It is an intelligence layer rather than a CRM, so it reads what you already have. Its limits are the same as ever: it depends on your records, and its pricing is demo-gated. Our Gratefully review has the detail.
The alternatives are real. Most modern CRMs will produce a pipeline report if the stages are maintained, and Bloomerang, Virtuous and DonorPerfect all do this adequately. DonorDock has board reporting as a named feature. And a competent general-purpose AI assistant will draft the narrative from your bullets perfectly well, without a new subscription.
The honest summary is that the reporting problem is usually a maintenance problem. If cultivation stages are current, most tools will report on them. If they are not, no tool invents a pipeline.
Practical notes
One page plus appendix. Trustees read one page. Detail belongs behind it for the two who want it.
Same shape every time. Comparability across meetings is worth more than a better layout each quarter.
Send it three days ahead. A pack handed out at the meeting gets read during the meeting, which means it gets skimmed.
Do not present it. Assume it was read, ask for questions, spend the meeting on decisions. Reading a report aloud to a board is the single most common waste of governance time in the sector.
Say what you do not know. Boards handle uncertainty well when it is stated and badly when it emerges. “We do not yet know how the grant will land, decision expected 14 October” is a perfectly good line in a board pack.
Frequently asked questions
How often should we report fundraising to the board?
Every meeting, in the same format. Quarterly is typical. Consistency matters more than frequency because it makes trends visible.
What is the one number boards most want?
Projected year end, with the assumption behind it stated. It is the number that determines whether they need to act, and it is the one most often missing.
Should we show individual donor names to the board?
For major prospects and trustee-linked relationships, usually yes, with care. Consider what your privacy policy allows and whether trustees have signed confidentiality undertakings.
Can AI write our board report?
It can assemble the figures and draft the prose, which is most of the time cost. It should not produce the projection or the judgement about risk, because those are what the board is governing on.
How do we get trustees to actually help with fundraising?
End every report with specific, named, small asks. Three introductions beats a general request for engagement, every time.
Our CRM cannot produce a pipeline report. Is that a tooling problem?
Usually it is a maintenance problem. Most CRMs report on cultivation stages if the stages are being kept current. Check that before concluding you need to buy something.
The bottom line
Boards do not need more fundraising information. They need less of it, arranged around what happens next and what they can do.
Three numbers, a pipeline by stage, what changed, what is at risk, and what you need from them. One page. Same shape every quarter. Sent in advance and not read aloud.
Use AI to assemble and to draft, which is where the two days actually go. Keep the projection, the risk judgement and the ask firmly human, because those are the parts the board is relying on you for.
Written by
FazFaz is the founder of AIToolsBakery. Every tool on this site is personally tested with real-world writing tasks before a single word gets published. Sponsored content is always clearly labelled.
Read more about how we test →