Blog
CrooHQ Blog · Operator notes

Your Schedule Shouldn't Live in a Group Text

Jordan Andrian
Jordan Andrian, Founder, CrooHQ
· 3 min read
Line cook in a black apron checking a shift-swap text on his phone in a restaurant kitchen

The schedule gets posted, and then the real schedule starts in the group text.

"Can anyone cover Saturday?" "I'll take it." Three thumbs-up, one missed message, and Saturday at 11 you're short a person because nobody updated the actual schedule.

I've had this happen in my stores more times than I can count. Nobody did anything wrong, exactly. Everybody thought somebody else had it handled.

Group texts are great for memes, not staffing

I'm not anti group chat. It's a great way to share a funny video, remind people about a team meal, or celebrate a good week. But it's a terrible place to run a schedule.

Here's why. A group text has no single version of the truth. Messages scroll away. People mute the thread because it's noisy. Someone says "I got it," but did the manager see it? Did the person who asked for coverage see it? Did anyone change the actual schedule?

Swaps get lost, people miss messages, and the manager is the last to know.

What goes wrong on the floor

These are the ones I see over and over:

The real cost

The obvious cost is being short-staffed on a busy shift. Everyone works harder, guests wait longer, and your best people get burned out covering gaps.

The quieter cost is trust. When the schedule isn't reliable, people stop trusting it. They start texting the manager to double-check. The manager becomes a human switchboard, answering "am I on tomorrow?" all day instead of running the shift.

What works

What works is simple: swaps and pickups happen in one place, the manager approves them, and the schedule updates itself. Everyone sees the same version. No more "I thought you had it."

You can get most of the way there with some ground rules, even before any software:

  1. One source of truth. Pick one place where the schedule lives, and say it out loud: if it's not on the schedule, it's not real.
  2. Requests go in writing, in one place. Not scattered across private texts and the group chat. One channel, one format: who, which shift, who's covering.
  3. Manager approves every swap. A quick yes or no. This is where you catch overtime, training gaps, or putting two new people on a close together.
  4. Update the schedule right away. The approval and the schedule change happen at the same moment, not "later."
  5. Confirm with both people. The person giving up the shift and the person taking it both get a clear confirmation.
  6. Keep the group chat for the fun stuff. Seriously. Let it be the place for shout-outs and memes.

The whole point is that nobody has to remember anything. The schedule remembers for them.

What changes when you get it right

When swaps live in one place, a few good things happen fast. Saturdays stop surprising you. Your manager stops being the switchboard. Your crew trusts the schedule, so they check it instead of asking. And when someone does need coverage, it gets filled faster, because the request goes to the right people instead of disappearing into a thread.

It also makes the hard days easier. When someone calls out last minute, you already have a clean picture of who's working and who's available. That's half the battle in handling the 5 PM call-out.

Why I built CrooHQ

I built CrooHQ because I wanted my own stores to stop running on group texts. It's the stuff nobody wants to touch, handled at the store: swaps and pickups requested in one place, approved by the manager, and the schedule updated on its own. Everyone sees the same version, every time.

Your crew's HQ. Built for operators, by operators.

Run the shift, not the spreadsheet.

Your crew's HQ, built for operators, by operators.

Jordan Andrian
Jordan Andrian, Founder, CrooHQ
Ran four restaurant locations over 12 years before building CrooHQ.