Here's an uncomfortable audit to run after your next board meeting: how many minutes were spent on information that could have been read in advance, versus actual discussion and decisions?
For most volunteer boards, the split is brutal. The treasurer reads the numbers aloud. Each committee chair recaps their month. Someone summarizes the email from the league. Forty-five minutes in, the board has decided nothing. It has listened. Then the real agenda starts at 8:15 p.m., when everyone's tired, and the two genuinely hard decisions get twenty rushed minutes between yawns.
The fix isn't better meetings. It's fewer things in the meeting.
The core principle: meetings are for collisions
A live meeting is the most expensive communication format your organization has. Eight volunteers for two hours is sixteen donated hours, a full workday burned in one evening. That expense is worth it for exactly one thing: collisions. Real-time disagreement, negotiation, trade-offs, brainstorming, the moments where one person's point changes another's mind mid-sentence.
Everything else (status, FYIs, numbers, recaps) is broadcast, not collision. Broadcast doesn't need a room. It needs a place where people can read it on their own time and confirm they did.
Think of it like a courtroom: nobody reads the case files aloud at trial. The briefs are filed beforehand; the hearing is reserved for argument. Boards that read briefs aloud at trial run two-hour meetings to make two decisions.
What moves async
1. All status reports
Treasurer's numbers, committee updates, registration counts, fundraiser progress. Post them 3–5 days before the meeting in a place the whole board shares. The standing rule: reports are posted, not presented. At the meeting, the agenda item shrinks from "Treasurer's report (15 min)" to "Questions on the treasurer's report (3 min)."
2. FYIs and announcements
League rule changes, facility notices, thank-yous, dates. These need zero discussion; they need confirmation of receipt. This is where read tracking quietly changes the game: posting an FYI where you can see who's seen it replaces both the meeting minute and the "did everyone catch my email?" follow-up.
3. Routine and unanimous-by-default approvals
Approving last month's minutes, ratifying a $75 expense within an approved budget, confirming a date everyone already agreed on. Many boards handle these async with a simple thread: proposal posted, reactions to vote, done in a day. (Check your bylaws: most allow action outside meetings with written consent, but the rules vary. Record async votes in your minutes either way.)
4. The first 80% of big decisions
The big stuff still gets a meeting, but the background doesn't. Post the venue comparison, the three quotes, the draft budget a week early, and let the clarifying questions happen in the thread. By meeting night, everyone arrives at the same starting line, and the live time goes to the actual trade-off instead of bringing the room up to speed.
What stays live
Async has limits, and pretending otherwise breaks boards in a different direction. Keep a meeting for:
- Contested decisions. If reasonable members disagree, text threads make it worse: tone vanishes, positions harden, and you get a flame war with reaction emojis. Disagreement is the meeting's whole purpose.
- Anything involving a person. Personnel issues, a problem with a coach, a conflict between volunteers, a sensitive family matter. Never async, ever. These need voices, faces, and no written record of half-formed thoughts.
- Brainstorming and annual planning. Generative discussion needs momentum and riffing. Async kills it.
- The relationship layer. A volunteer board is also a team of neighbors. Some live time, even 15 minutes of agenda-free check-in a quarter, is the glue. Boards that go 100% async get efficient and then get brittle.
The mechanics: where async lives matters
Async-by-email fails for a predictable reason: reports drown between shipping notifications, replies fork into three threads, and nobody can find March's numbers in June. Async needs a place: a private board where topics live in categories, each report is a thread, and the discussion attaches to the thing being discussed.
This is what Roundtable is for in HometownLift: a private message board for everyone with admin or staff access, organized by category (Finance, Events, Facilities, whatever fits your club) with read tracking so the president can see at a glance that six of seven members have read the budget before Tuesday. Because it lives in the same workspace as your calendar, campaigns, and reports, the treasurer's update can sit next to the actual numbers rather than describing them from memory.
A concrete scenario
A 9-member soccer club board ran monthly 2-hour meetings, and attendance was sliding: two members had quietly stopped coming. They switched to a simple rhythm: all reports posted by Thursday, questions in threads through the weekend, meeting Tuesday with a one-page agenda containing only decisions and discussion. First month, the meeting ran 50 minutes. Third month, 40, and the two drifting members came back, because the meeting was now the interesting part: real debate about a field investment and tournament hosting, instead of an hour of recitation. The president's summary: "We didn't shrink the work. We moved the boring part to the couch and kept the part worth driving for."
How to start (gently)
Don't announce a revolution. Change one thing: next month, reports are posted by Thursday and not read aloud. That single rule typically cuts 30–40 minutes. Once the board feels it, the rest (async FYIs, routine approvals, pre-read decision packets) follows by appetite, not mandate.
The bottom line
Move broadcast async; keep collisions live. Reports, FYIs, and routine approvals belong on an organized board where reading is tracked and history is findable. Contested decisions, people problems, and planning keep the meeting: a shorter, sharper meeting people stop dreading. The goal was never fewer hours from volunteers. It's spending those hours on the parts that actually need a room.
If your board wants a private, organized place for the async layer (categories, threads, and read tracking, right next to the club's actual work), see how Roundtable fits in the HometownLift workspace.