Special #2
Kill the group text: put the schedule somewhere real
Kill the Group Text: Put the Schedule Somewhere Real
Sample content: draft write-up for review
Every story in here is a composite from my own years on the line. Names changed, notifications still haunt me.
I once ran a whole kitchen’s schedule out of a group text called “KITCHEN FAM 🔥🔥.”
Forty-one people. Three of them had quit. One was a guy’s mom. Don’t ask.
Every Sunday night I posted a photo of a schedule I’d written on the back of a produce invoice. Blurry. Slightly stained with demi. Then the swaps started. “Can anyone take my Friday?” “I got you.” “Wait, I thought Marco had it.” Somebody replied with a thumbs-up, which in that chat could mean yes, no, or “I’m at a wedding.”
By Friday at 4 p.m., two people showed up for the same grill shift and nobody showed up for sauté. I worked sauté. Of course I did.
The group text is not a schedule. It’s a crime scene with emojis.
What the schedule actually has to do
Forget software for a second. Whatever you use, a napkin, a spreadsheet or an app, it has to do these things or it’s going to bite you in the ass:
- Post it one to two weeks out, and keep it. Same place every time. Not a photo, not “check the chat.”
- Hold everyone’s availability in writing. School, second jobs, custody days. If it lives in your head, you’ll forget it at the worst possible moment.
- Track time-off requests so “I asked you three weeks ago” stops being a fight.
- Run swaps through you. They can find their own cover, but you approve it, and the schedule updates. Otherwise payroll and reality drift apart and you find out at the end of the month.
- Warn you before overtime. The cook who always says yes is usually already at 38 hours.
- Catch clopens before you post. Nobody closes and opens. That rule only works if something checks it.
- Show labor against sales. Even roughly. You want to know Tuesday is overstaffed before Tuesday, not after.
- Prove people saw it. “I didn’t know I was on” is the oldest excuse in the book. Kill it.
Napkin, spreadsheet or app?
Be honest about your size.
Six people and one location? A shared spreadsheet can do most of this. Lock the template, post it in one place, and write the swap rule at the top. It’s free, and free is a beautiful number.
Bigger crew, or you’re drowning? That’s when an app earns its keep. Swaps, time-off requests, availability and overtime warnings all in one place. Most of them let cooks see the schedule and trade shifts from their phone, which is where your crew lives anyway.
Whatever you pick, check three things before you commit: does it work with your POS and payroll, what does it cost at your headcount, and will your least techy cook actually open it? If your dishie can’t figure it out, it doesn’t work.
How to switch without a mutiny
- Pick a start date two weeks out and announce it at pre-shift. Twice.
- Load availability first. Have everyone fill it out before you build a single shift.
- Run both for one week. App plus a printed copy by the time clock. Then kill the paper.
- Close the group text for scheduling. Seriously. Mute it, rename it “MEMES ONLY,” whatever. Swaps that happen in the chat don’t count.
- Answer questions for a week without sighing. You will want to sigh. Don’t.
What I use (and the part where Shifty gets paid)
When I finally dragged my kitchen off the group text, we went with 7shifts. It’s built for restaurants, it handles availability, swaps, time-off and overtime warnings, and my crew actually used it, which is the only review that matters. Plenty of good managers use Homebase or Sling instead. Try a couple and pick the one your crew will open.
If you want to kick the tires, check out 7shifts here.
Straight talk: if you sign up through that link, Shifty gets a cut. It doesn’t cost you anything extra, and we’d tell you to fix your schedule either way.
Your schedule is the first thing your crew reads every week. Make it something they can trust.
Heard? Heard.