Somewhere on next Tuesday's agenda, between the roof estimate and the budget line for youth camp, is five minutes for “how did the fall festival go.” Whoever runs the event will hand over a report. Most of those reports get a polite nod and a question about the cost of the bounce house, because the report answered the wrong question.
A board member skimming a page between other items is not trying to relive the event. They are trying to answer one thing: is this worth doing again, and is it working better or worse than last time. Everything else is detail they will ask for if they need it.
The three numbers that actually get read
Strip the report down and a board only needs three figures, in this order.
- Total attendance, next to the last few times you ran it. Not a bar chart with six colors — just this year's number beside last year's, and the year before that if you have it. A church fall festival that pulled 140 people this year against 155 and 148 the two years prior tells a board something in two seconds: roughly flat, slight dip, worth watching but not alarming.
- First-timers, or however you define a new face. An event that draws the same 130 regulars every year is a fellowship event, and that is a fine thing to be. An event that draws 130 people and 20 of them are new is doing something different — it is a door, not just a gathering. The board should know which one they funded.
- What happened to the new faces afterward. This is the number most reports skip entirely, and it is the one that turns “we had a good turnout” into “here is what the turnout produced.” If twenty people were new, how many showed up again within a month, joined a group, or ended up in a follow-up conversation with someone on staff. Even a rough count — “six of the twenty came back the following Sunday” — is worth more than a headcount alone.
Everything past those three is optional context: weather, a competing event in town, a new volunteer team, a schedule change. Put it in a sentence or two under the numbers, not in a narrative that makes the board hunt for the point.
Who is actually reading this, and when
It helps to picture the actual reader. A board member at a church of 150 is usually reading your report in a folder alongside four or five other items, in a meeting that runs an hour and a half on a weeknight after a full day of work. They are not going to study a chart. They are going to glance at a number, decide whether it needs a question, and move to the next item. Write for that glance, not for the version of the reader who has time to dig.
That means the order of information matters as much as the content. Put the headline number first, in large enough type that it does not require reading a caption to understand. Put the comparison right next to it, not two paragraphs later. If a board member has to flip a page or scroll to see whether this year was up or down from last, you have already lost the five seconds you had.
Why the single-year number fools people
A board that only ever sees this year's total has no way to tell a real shift from ordinary variation. 140 people sounds fine on its own. It sounds different next to three years of 155, 148, and 140 — a slow, steady slide that a single snapshot would have hidden. The comparison is not decoration. It is the part of the report that actually informs a decision.
The same logic applies going the other direction. A board that sees only “down from last year” without three or four years of context might overreact to a normal dip caused by a rainy Saturday. Neither error is really about the event. Both are about a report that only had one data point to work with.
What one bad number should and should not trigger
Say the fall festival is genuinely down this year, not by a rounding error but by a real margin — 110 people against 155 and 148 the two years before. The temptation for whoever runs the event is to either bury the number in a longer paragraph or to over-apologize for it. Neither serves the board well. The useful move is to state the number, state what you know about why, and state what you do not know.
“Attendance was 110, down from an average of about 150 the past two years. It rained most of the afternoon, which likely cost us some walk-up families, but that alone probably does not account for the full drop.” That sentence gives a board everything it needs: the number, an honest partial explanation, and an acknowledgment that the explanation is incomplete. A board reading that trusts the next report more than it would trust one that either hid the drop or overclaimed to know exactly why it happened.
What a single down year should not trigger is an immediate decision to cancel the event. One year is one data point. It is the three- to five-year comparison, mentioned earlier, that tells you whether this is a blip or the start of a pattern worth addressing. A report that gives the board that context does the board's job for it in the best sense — it keeps them from overreacting to noise.
What to leave out, on purpose
The instinct when building a report for the board is to include everything you tracked, because it took effort to track it. Resist that. A page with fourteen numbers gets skimmed for none of them. A page with three numbers gets read for all three.
Leave the registration list, the volunteer schedule, and the vendor invoices out of the board packet entirely — those belong in your own files, available if someone asks, not printed for a group that is not going to read them anyway. If you are already keeping event registrations in one place, pulling the headcount and the new-face count for a report takes minutes rather than an evening of cross-referencing a sign-in sheet against a membership list.
Reading attendance without pretending it explains itself
Attendance numbers, event or weekly, tend to get over-interpreted in both directions — treated as proof of momentum when they are up, and proof of decline when they are down. The same discipline that applies to Sunday attendance applies here: look at the trend across several instances of the event before drawing a conclusion, and say plainly when you do not know why a number moved. A board that trusts your reports will forgive an honest “we're not sure why turnout was soft” far more readily than it will forgive discovering later that a number was quietly left out.
Turning a good event into a report on what came next
The hardest number to get, and the most valuable one, is what happened to a first-timer after the event ended. That takes someone actually following up — a name handed to a greeter, a conversation the following Sunday, a note in a file somewhere. If your church already has a habit of turning a guest into a next step with a name and a date attached, the event report almost writes itself: you already know how many people from the fall festival got a follow-up, because someone owned that follow-up and it is sitting in front of you. Without that habit, the number does not exist to report, no matter how good the event was.
SundayBridge keeps event registrations, attendance history, and the follow-up board attached to the same person record, so the “what happened next” question has an actual answer instead of a guess. It will chart this year's turnout against past years automatically, which is the comparison that makes the report worth five minutes of agenda time instead of a shrug.
A report a board member can actually skim
Put the three numbers at the top, in that order: total against history, new faces, what happened to them. One sentence of context below each if it is needed. Nothing else needs to be on the page unless someone asks a follow-up question, and if they do, you can answer it from the same records without rebuilding anything.
A board that gets this every time an event happens starts trusting the reports enough to stop asking about the bounce house and start asking the question that actually matters: should we do this again, and is it working.