The community dinner at the Riverside hall started small enough to organize with a clipboard: a dozen neighbors, one pot of chili, folding chairs. Three years later it fed a hundred people a month, ran on forty volunteers, and lived — all of it — inside a shared spreadsheet that Faith had built one optimistic evening and had been apologizing for ever since.
The spreadsheet had developed opinions. Someone would sort column A alone, and forty names would calmly divorce their forty availability rows, reassigning Ed the retired welder to a casserole he’d never heard of. Cells got overwritten without a trace — Faith once watched three Saturdays of setup crew vanish under a single enthusiastic “YES!!” typed into the wrong box. Half the volunteers opened it on phones, where the columns collapsed into abstract art; the other half got locked out as view-only and just texted Faith their dates instead, which meant the spreadsheet was really Faith, with extra steps.
The breaking point was scheduling itself. Picking next month’s date meant matching dozens of volunteers to candidate Saturdays — cooks to one column, setup to another, cleanup to a third — and the grid said the cooks could do the twelfth while the setup crew existed only on the nineteenth. Faith spent a full Sunday reconciling it, called the twelfth, and watched a dinner for a hundred run on nine volunteers and adrenaline.
The spreadsheet with opinions of its own
Here’s the pattern every organizer of a recurring community meal eventually meets: shared spreadsheets break precisely when participation matters most. The more people who touch the grid, the more ways it shatters — sorts, overwrites, permissions, phones. So participation quietly shrinks to the people willing to fight the tool, and the organizer starts mistaking that shrinkage for apathy. Faith’s volunteers hadn’t stopped caring. They’d stopped opening the file — and every date picked from that thinning grid was a guess wearing a header row.
The spreadsheet didn’t coordinate forty volunteers. It coordinated the twelve who could face it.
It was Gloria, seventy-one, undefeated at texting, who named the fix. “I don’t want your spreadsheet,” she said at cleanup. “Send me something I can answer with my thumb.” So for the next dinner, Faith skipped the grid entirely. She made a poll with four candidate Saturdays and sent one link to all forty volunteers: tap the dates you can come, that’s the whole job.
A poll everyone can answer from a phone
The difference showed up in hours, and it kept showing up all week. The link opened cleanly on every phone in the roster — no login, no app, no view-only purgatory — and there was nothing to sort, overwrite, or destroy. Volunteers tapped yes, maybe, or no beside each Saturday and typed their names, Gloria first among them. People who hadn’t touched the spreadsheet in a year answered from bus stops and break rooms. By Wednesday, thirty-four of forty had responded; the old grid had never heard from more than half.
And the date question — the one that used to cost Faith a Sunday — answered itself. The nineteenth rose to the top with thirty-three hands behind it — cooks, setup crew, and cleanup all in one count, no Sunday of reconciliation required. Faith booked the hall, posted the date, and spent her reclaimed weekend making an absurdly good cornbread. The dinner that month had more hands than jobs, which is the only staffing problem worth having. With Meeting Time, a recurring community meal runs on one link instead of one grid: volunteers answer from any phone with no accounts, nothing can be sorted into chaos, and the date with the most hands rises to the top on its own.