Build a Weekly Staff Shift Schedule Around Peak Hours and Availability

Get a one-week shift schedule plus an hour-by-day coverage grid, with labor hours totaled against your budget and every understaffed hour flagged.

You getSchedule table, coverage grid and labor totals

Prompt

Prompt
Act as an operations manager who builds staff schedules for small restaurants, shops and service businesses.

Your job: build a one-week shift schedule that matches staffing to customer demand.

First, ask me these questions in one message, numbered, and wait for my answers:
1. What are your opening hours each day, and which roles must be covered?
2. Who is on staff: name, role, available days and times, and max weekly hours?
3. When are your peak and quiet hours, and how many people do you need at each?
4. Any limits: weekly labor-hour budget, longest allowed shift, required opener or closer?

Rules:
- Never schedule anyone outside their availability or above their max hours.
- No shift under 3 hours. Default max shift is 8 hours if I give none.
- Fill peak hours to the required headcount before adding quiet-time hours.
- Every shift has a start time, an end time and a total in hours.
- Mark every hour below the required headcount as GAP.

Output format:
1. Schedule table: Name | Role | Mon to Sun (shift times) | Total hours | Max
2. Coverage grid: rows = each hour, columns = days, cells = headcount, peak hours marked with *
3. Labor totals: per day and for the week, compared with my budget
4. Gaps and fixes: numbered list with day, hour, shortfall and one concrete fix

End with one line on assumptions you made and the local labor rules (breaks, overtime, minors) I should check.

Example output

Example for: a café open 7am–3pm daily, 6 staff, 170-hour weekly budget. Peaks: weekdays 7–9 and 11–1 (need 3), weekends 9–1 (need 4). Quiet hours need 2.

1. Schedule

NameRoleMonTueWedThuFriSatSunTotalMax
MariaManager/barista7–37–37–37–37–3––4040
TomCook7–37–37–37–37–3––4040
JakeBarista7–1––7–17–17–39–13030
PriyaCashier11–3––––7–37–32024
LenaCook/prep–7–127–12––9–29–22020
SamBarista–––––7–37–31616

2. Coverage Grid

HourMonTueWedThuFriSatSun
7–83*3*3*3*3*32
8–93*3*3*3*3*32
9–10333334*4*
10–11333334*4*
11–124*3*3*3*3*4*4*
12–14*2* GAP2* GAP3*3*4*4*
1–23222243
2–33222232

3. Labor Totals

DayHours
Mon26
Tue21
Wed21
Thu22
Fri22
Sat29
Sun25
Week166 of 170 budget (4 under)

4. Gaps and Fixes

  1. Tue 12–1, short 1: Add Priya 11–2 (3 hrs). She is available Tuesdays and moves to 23 of 24 max. Week total becomes 169.
  2. Wed 12–1, short 1: No one has spare hours that day. Ask Lena to swap her Sun 9–2 for Wed 8–1 if Sam can cover Sunday prep, or cross-train Priya to cover Wednesdays.
  3. Risk, no manager on weekends: Maria is at 40 hours. Name Jake shift lead on Sat and Sun, or move one of Maria's weekdays to Saturday.

Assumptions: shift hours are paid hours with breaks unpaid and not shown. Check your local rules on break timing and overtime before posting.

Written by AI from this prompt. Your results will vary.

Tips and common edits

Why this works

  • Asking for availability, max hours and peak headcount first keeps the schedule real instead of a generic 9-to-5 grid.
  • The hour-by-day coverage grid makes understaffed peaks visible at a glance, and the model has to label them GAP.
  • Totals compared with the labor budget, plus one concrete fix per gap, turn the rota into a decision you can act on.

Use this in ChatGPT, Claude or Gemini before posting next week's rota. Have your opening hours, each person's availability and max hours, and your busiest times ready.

Common edits

  • Change the default 8-hour max shift or add a required 30-minute unpaid break for shifts over 6 hours.
  • Ask for 30-minute rows in the coverage grid if your rushes are short, like a lunch spike.

Prompt details

By
Prompts-GPT editors
Published

Did this prompt work?

Keep exploring

More in Business