A Weekly Volunteer Hours Digest Your Board Will Read

Your board meets monthly. Your volunteer hours change daily. The gap between those two facts is where most coordinators lose the thread, and where a board member asks "so how are we doing on volunteer coverage?" and you reach for a number you do not have.

The fix is small: a one-page digest, sent every Monday, covering the week that just ended. Below is a real one for a fictional food pantry, the Riverside Pantry, for the week of June 9 to June 15. The numbers are invented but the shape is exactly what works.

The digest, in full

Riverside Pantry volunteer hours, June 9 to June 15

Total hours: 214.5 across 31 volunteers. Up from 198 hours and 29 volunteers last week.

By program: Distribution 132, Warehouse 51.5, Front Desk 31.

New this week: 4 first-time volunteers, all on Saturday distribution.

Heads-up: Thursday warehouse ran with 2 people for the 4pm delivery. We need 4. Sign-ups are open.

That is the whole thing. Five short lines. A board member reads it in twenty seconds and walks into the meeting knowing where coverage is thin. Everything below is how you build each line and why the rest got cut.

Where each number comes from

Start with one clean export of the week. If you track sign-ins on a shared tablet or a posted code, you already have timestamped entries. Pull a CSV for June 9 to June 15 and you get rows with a worker name, a start time, an end time, a duration, and any tags. The export also carries a distinct-worker count, which is where the "31 volunteers" comes from. That count matters more than people expect: 214 hours from 31 people is a healthy spread, while 214 hours from 6 people is a burnout risk hiding in a flattering total.

The "by program" split comes from tags. At Riverside, every entry is tagged with one of three program labels at sign-in. Filter the export by tag and the three subtotals fall out. If you have not set up tags yet, that is the one piece of structure worth adding before your next digest, because the program breakdown is the line your board reacts to most.

The week-over-week comparison ("up from 198") is just last week's digest. You do not recompute it. You kept the number, so you paste it. After a month you have a four-week trend without building anything new, and a clean feed into a monthly volunteer summary when the board wants the bigger picture.

The forgotten clock-out problem, and why it does not wreck your total

Someone always forgets to clock out. A Saturday volunteer taps in at 9am, leaves at 1pm, and never taps out. If your system closes that entry at the current time, you wake up Monday with a single 49-hour entry that turns 214 real hours into 260 fictional ones, and your board's first impression is a number you have to walk back.

This is why closing a forgotten entry at its start time plus a cutoff matters for reporting, not just tidiness. The stale entry gets capped instead of running to now, so a missed clock-out never inflates the digest. You will still want to eyeball the longest few entries before sending, but you are correcting minutes, not erasing phantom days.

What to leave out

The temptation is to show everything you collected. Resist it. The digest is not the dataset.

• Per-person hour lists. Thirty-one names with individual totals is a spreadsheet, not a digest. Keep it in the export and pull a person's hours only when someone asks, or when you generate a volunteer hours certificate for a student who needs service credit.
• Exact clock-in and clock-out times. Your board does not need to know that Maria arrived at 8:52. Roll it up.
• Anything you would have to caveat. If Wednesday's count looks off because the tablet was unplugged, fix it or note it in one short line. Do not ship a number you do not trust.
• Money. Hours are not dollars. If a board member wants a "value of volunteer time" figure, that is a separate calculation with its own assumptions, and it does not belong in the weekly operational read.

The one thing you should always include is the heads-up line. Raw totals tell the board what happened. The heads-up tells them what to do. "Thursday warehouse ran with 2, we need 4" is the line that turns a report into a request, and it is the reason a board member forwards the email to someone who can fill the gap.

Making Monday morning take five minutes

The whole digest should cost you five minutes, or you will stop sending it by week three. That means the data has to be ready without chasing anyone. Volunteers sign in with no account and no app, just a name tap or a scanned code, so you are not collecting logins or reconciling who forgot their password. The structure for this lives in the weekly volunteer hours digest setup, which keeps the export columns stable so your Monday routine is paste, compare, and send.

If sign-in itself is still messy, that is the upstream fix. A QR poster at the volunteer table gets people recording their own hours without you standing there, and accurate sign-ins are what make the digest honest.

Write next Monday's digest in the same five lines: total and distinct count, the program split, who is new, and one heads-up. Send it before your inbox fills up. Four weeks from now your board will expect it, and that expectation is worth more than any single report.