The group text that became a scheduling system

A church’s volunteer teams ran on a group text. One person built each rotation by hand, kept track of who was out of town, and — every time someone couldn’t make it — chased replies until somebody agreed to cover. It worked, as long as that one person had the time. When they didn’t, Sunday got uncomfortable.

What I built

A scheduling system that does the coordinator’s job quietly in the background:

Rotations generate themselves, fairly. The system balances how often each person serves, works around the dates they’ve said they’re away, and eases people back in after time off — instead of someone juggling it on paper.
Volunteers handle their own changes. Each person gets a private link — no account, no password. From it they see their dates, mark time away, and swap or request cover without anyone in the middle.
The schedule goes where people already look. It shows up in their phone’s calendar, prints as a clean one-page PDF, and can send optional reminders.
Each team runs its own way. One team rotates individuals; another rotates whole groups. Each team’s leader manages their own team, and each team keeps its own off-weeks.

The design principle

These are people who already know each other and already have each other’s phone numbers. The system isn’t a social app and doesn’t try to be — its job is to handle the logistics and stay out of the way. That’s the bar for any internal tool: people should notice it only when it saves them a conversation.

Why this matters for a business like yours

Swap “volunteers” for “crew,” “techs,” or “front-desk staff” and this is one of the most common back-office headaches there is: shift coverage, on-call rotations, crew assignments, who’s out next week. When it lives in a group text and one manager’s head, it’s fragile — and it’s exactly the kind of thing a business can’t hand off. A system like this turns it into something that runs itself.