What a Board Can See

Every board member with fiduciary responsibility knows the discomfort: you're asked to stand behind the organization's revenue outlook, and the report in front of you shows activity and totals. Meetings held, proposals out, dollars year-to-date against goal. All true, all necessary, and somehow not quite an answer to the question you're actually carrying: is next year's revenue real?

When the discomfort goes unaddressed, it tends to pull a board toward one of two unsatisfying paths: deferring entirely (approve the number, hope), or leaning in with the wrong instrument (interrogating totals, second-guessing tactics), which development teams rightly experience as scrutiny without partnership. Neither serves anyone. The team is doing real work; the board can't see it; the report format is what stands between them.

There's a better instrument: three questions that any board can ask, that any strong development operation can answer, and that make the quality of the pipeline visible without a single spreadsheet.

First: of the revenue we're projecting, how much rests on decisions donors have already made, and how much on decisions still forming? This one question makes the forecast's real composition visible. It doesn't criticize the forming decisions; every growing organization runs partly on them, and even a signed commitment isn't a certainty. It simply shows the mixture, which is what standing behind a projection requires.

Second: for our most important open opportunities, what has to happen next, and is it scheduled? Not "how do we feel about the Hendersons." The concrete version: what's the next conversation, what decision does it invite, and when is it happening? A scheduled conversation doesn't make a gift likely. But a pipeline where the major opportunities have designed, scheduled next steps is a knowable asset, while a pipeline that's warm and waiting is a hope with a total attached, even when the totals match.

Third: what did we learn from the decisions that didn't go our way? Renewals that shrank, proposals that concluded in a no, relationships that faded. Organizations that can answer this calmly are organizations improving; the question honors the losses as tuition rather than treating them as failures to be explained away.

Notice what these questions don't do. They don't ask the board to evaluate fundraising technique, which isn't the board's craft. They don't put any individual on the spot. And they give the development team something most report formats never do: a fair way to show the real work, the preparation and judgment behind the numbers, to the people who need to trust it.

A board that asks these questions consistently changes the conversation on both sides of the table. Development starts getting credit for the invisible work of moving decisions, not just the visible moment of receiving gifts. And board members get something genuinely useful to their oversight role: not certainty, which revenue never offers, but an evidence-grounded picture they can stand behind.

If your board packet can't yet answer the three questions, that's not an indictment of anyone. It's just the next thing to build.