Every Wednesday night, after the café closed, Tom sat at table four with a cold espresso and did the worst part of owning a small business: the rota. Six part-timers — students, mostly, plus a musician and a new mom — and one owner texting each of them individually. “Can you do Saturday open?” “Any chance you’re free Sunday?” Then he’d wait, thumb hovering, while the schedule he was supposed to post on Thursday assembled itself one delayed reply at a time.
The texts came back on their own schedules. Jess answered in minutes; Omar answered at 2 a.m.; Callie, the new mom, answered whenever the baby allowed. By the time the last reply arrived, the first ones were stale — Jess had since picked up a lab session, and the Saturday she’d promised was gone. Tom would post the rota anyway, and the swaps would begin: a side-channel economy of “can anyone take my shift?” messages he only heard about when nobody showed.
And then there was Sunday. The Sunday morning shift was the rota’s cursed square — nobody volunteered, so Tom assigned it, guessing at who’d mind least. He guessed wrong often enough that Sunday no-shows became a genre. Twice that spring he’d opened the café himself, apron over his church clothes, wondering how six employees could be this hard to schedule.
Six texts, six versions of the truth
The problem wasn’t his staff, and it wasn’t Sundays. It was that shift scheduling by individual text means the owner is the only person who ever sees the whole picture — and he sees it late, assembled from replies that were true at six different moments. Availability collected one conversation at a time is expired by the time it’s compiled. The schedule wasn’t really a plan; it was an archaeology of last Wednesday’s texts.
The rota was stale before it was posted — built from six answers given at six different times, none of them still true.
The fix came from Jess, who’d seen her volleyball club use it. “Why are you texting us one by one?” she asked, watching him hunched over table four. “Send everybody one link.” That Wednesday, instead of six separate conversations, Tom sent one availability poll to the whole team at once: the week ahead, broken into shifts, open and close.
Seeing the gaps before the schedule posts
Each part-timer opened the link on their own phone — no app, no account, no login to forget — and marked every shift yes, maybe, or no in about a minute. For the first time, the whole team’s availability sat in one place at the same moment, and Tom could read the week like a weather map. Saturday open: covered three ways. Tuesday close: thin. And Sunday morning — there it was — Omar, the night owl, had marked it yes. He’d never wanted early weekday shifts; Sundays after gigs, he was up anyway. Nobody had ever asked the question in a way that let him say so.
Now the gaps showed up on Wednesday night, while there was still time to fix them — not on Sunday morning, when the fix was Tom in an apron over his church clothes. Tom filled the thin spots with a single follow-up instead of a swap scramble, posted the rota Thursday, and watched no-shows drop to nearly none. The cold-espresso hour shrank to ten minutes.
That’s the small-business case for Meeting Time in one café: a weekly availability poll the whole team answers at once, no accounts needed and any phone welcome, with every response gathered in one place — so the gaps are visible before the schedule goes up, not after.