Zchedule

Restaurant scheduling

Someone called out. Don't start texting everyone

Build the week for the floor and the kitchen on one board. When someone can't make a shift, they post it in the app, coworkers volunteer, and you approve one. The schedule updates itself.

Free for small teams. No credit card.

Updated

Friday at a 60-seat restaurant

Example day

12 PM3 PM6 PM9 PM
Prep cook
9–3
Opening server
10:30–4
Line cook (AM)
10–4
Host
4–10
Server 2
4–11
Server 3
5–11
Bartender
4–12
Line cook (PM)
3–11
Closer / dish
6–12
  • 11:30 AM Lunch opens
  • 5 PM Dinner service
  • 10 PM Kitchen closes
Friday at a 60-seat restaurant (example)
ShiftStartEnd
Prep cook9 AM3 PM
Opening server10:30 AM4 PM
Line cook (AM)10 AM4 PM
Host4 PM10 PM
Server 24 PM11 PM
Server 35 PM11 PM
Bartender4 PM12 AM
Line cook (PM)3 PM11 PM
Closer / dish6 PM12 AM
An example Friday: a light lunch crew, then the dinner staff overlapping from 4 PM.

The week changes after you post it.

A restaurant schedule is two schedules, lunch and dinner, with the kitchen and the floor on each. Then Friday gets busy and someone's car won't start.

Openers and closers
Save your opening, mid and closing shifts once and paint them across the week. A day with nobody scheduled is flagged before it goes out.
Lunch and dinner
Put front of house and back of house on the same board so you can see a thin dinner on Friday while you're still building the week.
Weekend rush
Each person's hours are totalled as you go, so you can see when stacking the weekend pushes your best server toward overtime.
Call-outs
The employee posts the shift for coverage. Everyone else sees it in the app, someone volunteers, you approve. No group chat.
Availability
Servers with a second job or classes set their own availability. The publish check warns you about any shift that clashes.
Clocking in
A tablet by the pass works as a PIN time clock for the whole staff, with lunches. Punches are matched to the schedule.

Call-outs

A call-out becomes one posted shift.

The employee who can't come in posts the shift. Coworkers volunteer from their phones, you see their hours for the week, and you approve one. The published schedule updates, and only the two people involved are notified.

  1. 1
    MarcusEmployeeOpen

    Requests coverage for Fri 4:00–11:00 PM. Note: family thing.

  2. 2
    Priya and TomCoworkers2 offers

    Both volunteer from the coverage board in the app.

  3. 3
    YouManagerApproved

    Priya is at 22h this week, Tom at 38h. You approve Priya.

  4. 4
    SchedulePublished weekUpdated

    Friday close is Priya's. Marcus and Priya are notified.

The parts of Zchedule you'd use

Roles people schedule:ServerHostBartenderLine cookPrep cookDishwasherBusserShift lead

What Zchedule doesn't do: Zchedule doesn't connect to your POS, pool tips or run payroll. It gives you the schedule, the hours and a CSV to take to the system that does.

FAQ

Questions worth answering up front.

They get an email invite and see their shifts in the iPhone app or any browser. A shared kiosk tablet covers clock-in without anyone's personal phone.

No. Drafts stay hidden until you publish, and when you change one shift afterwards, only the affected person is notified.

They're on the same board so you can see the whole day. Give each person a position (server, line cook) and use shift templates for each station's hours.

One flat monthly price per team, not per person. Free covers up to 10 people including you, and every new team starts with 14 days of Pro.

Related

Next week's schedule is getting built either way.

Do it in Zchedule and the next call-out is one posted shift, not thirty texts.

No credit card. The Pro trial starts with your first shift, not today.