Renata had chaired the ten-year reunion committee long enough to outlast two treasurers, one venue, and the original group chat. The committee had everything a reunion could need: a shortlist of three venues with deposit quotes, a playlist argued down to the last song of the night, name tags mocked up in the school colors. What it did not have — what it had failed to produce in two full years of monthly meetings — was a date. Eighty classmates, one weekend, and a committee that flinched every time someone said, “So should we just pick one?”
They had tried. The first year, five committee members voted among themselves and announced a June weekend with real ceremony. Within a week the replies rolled in: three weddings, two graduations, one classmate mid-deployment, and a bloc of teachers who pointed out that June belonged to their own students. The second attempt, an October Saturday, collided with homecoming, a half-marathon most of the soccer team had apparently entered, and — Renata still didn’t fully believe this — a regional chili cook-off. Each time the pattern was identical: pick a date in the dark, announce it with confidence, then discover the turnout afterward, one apologetic reply at a time.
So the committee stopped announcing dates and went back to discussing them, which felt safer and accomplished nothing. Venues dropped off the shortlist as their calendars filled. The playlist gained songs. The reunion, technically scheduled for “the fall, probably,” drifted toward becoming an eleven-year reunion with a better excuse.
Why reunion planning always stalls at the date
Here is the trap: with eighty invitees, every date you pick blind is a bet against odds you can’t see. On any given weekend, some fraction of eighty adult lives is already spoken for — weddings, shifts, custody schedules, chili cook-offs. Choose first and ask later, and you learn the answer the worst way possible: in the RSVP count. The committee wasn’t indecisive. It had simply learned, twice, exactly what guessing costs.
They didn’t have a decision problem. They had an information problem — eighty answer keys they’d never once opened.
The fix came from Marcus, the co-chair, who had watched two years of this with increasing serenity. At the next meeting he shared his screen: a poll with four candidate weekends spread across September and October. “We stop picking,” he said. “We ask all eighty, and the weekend picks itself.” He posted one link to the alumni group that night.
Poll the whole class, then book the weekend
The responses started before the meeting adjourned. Classmates opened the link on their phones — no account to create, no app to install, just four weekends and a tap for yes, maybe, or no. The teachers answered from the staff lounge. The deployed classmate answered from eight time zones away, the options shown in his own local time. Renata set a response deadline of two weeks, and by the end of the first one, fifty-eight people had answered — more engagement than any announcement had ever earned.
When the poll closed, there was no debate left to have. The second October weekend stood clear of the field: sixty-one classmates could make it, nine more with a maybe — numbers no committee vote could have conjured. Renata booked the venue that same week, not hoping for turnout but holding it in writing before the deposit cleared. The announcement, when it finally went out, wasn’t a gamble; it was a confirmation. That’s the quiet power of asking first. With Meeting Time, a crowd of eighty is just one shared link — no accounts for anyone, each person seeing their own time zone, a response deadline that keeps the class honest, and the best weekend rising to the top with the attendance already built in.