There's a week in every quarter that executive directors don't talk about much, because it's embarrassing how much of it goes to one document.
It starts with emails to the program leads asking for their numbers. Finance exports something from the accounting system and spends a morning making it look like the version the board is used to. Development pulls totals from the donor database and then has to reconcile them with what finance says actually arrived, because the two systems count a gift on different days. Somebody, and it's usually the same somebody every quarter, builds the slides. On Wednesday afternoon they notice two figures that disagree and lose the rest of the day finding out why. The deck goes out Thursday night. By the Monday meeting the numbers are a week old, and everyone in the room knows it.
I've sat in on the Wednesday-afternoon part of this more than once. Every time, the trouble is assembly. The four things a board wants to see, program activity, money, fundraising and outcomes, live in four different systems that have never met, and somebody has to make them meet by hand.
The assembly is where the week goes. The donor database counts a gift when the pledge was made. Accounting counts it when the cash landed. The program system counts a participant as served when they enrolled. The funder's report wants them counted when they finished. None of these are wrong. They're just different, and the person building the deck has to hold every one of them in their head to get to a single true picture.
Then there's the layout. Boards get attached to a format. Rebuilding it every quarter from raw exports is a craft, and it's almost always the craft of one specific person. Which means the organization's ability to tell its board how it's doing depends on that one person being at their desk and not on leave or ill or gone.
The week of senior time is the cost that's easy to count. The one I worry about more is what the board decides on the basis of numbers that are already stale, or that nobody in the room fully trusts.
When a report takes a week to build, it gets built four times a year. So leadership sees the organization's real position four times a year. In between, the decisions about where the next dollar goes, which program to grow, when to hire, get made on instinct and on the last set of slides. A program that's been losing participants since February turns up in the May report, if it turns up at all, because by May the person building the deck is focused on whatever the board asked about last time.
And there's a quieter thing that happens at the table. Board members are often serious operators from other worlds. When two numbers in a deck don't match, or when a question about last quarter can't be answered until someone goes back to the spreadsheets, their confidence in the management of the place drops a notch. Nobody says anything. It just accumulates.
Shane at American Paragons described the version of this that we built our way out of. Board reports used to be a week of assembling slides. Now they generate from the same data the team works in every day, and the week has turned into something he reviews and sends. What he said mattered more, though, was that he could finally see which parts of the foundation were producing impact and which needed investment, because the numbers were there whenever he looked, not only in the week before a meeting.
That's the actual shift. When program, financial and fundraising information flows into one place on its own, the report turns into a view. The figures are the same figures the staff use every day, so there's nothing to reconcile at quarter end. They were never apart.
The board meeting changes character when that happens. It becomes a conversation about what the numbers mean, because nobody in the room doubts them. The report itself still exists. Boards like a document. It's just generated from the live system, in the layout they're used to, and read by a human before it goes out.
One warning, because this gets sold badly: the dashboard is the last five percent. The real work is underneath: getting departments to agree what a participant and a gift and a dollar mean, connecting the systems so those meanings hold everywhere, and building the reporting into the platform rather than bolting it on top. Once that's done, the dashboard is almost an afterthought.
If you want to know whether this applies to you, pick the one report that hurts most to produce. Trace every number in it back to the system it came from and count the hands it passed through on the way. I've never seen that count fail to get a reaction from a board.