Guides · Updated 2026-11-15

How Restaurants and Cafés Can Use AI to Plan Staff Rotas and Shift Schedules

Midweek rota rewrites are normal for a small restaurant or café. ChatGPT, Gemini, Copilot and Grok can draft a rota from availability you have, sort the busier dayparts in your own numbers, and write the change note. They do not know who can run the pass, your wage budget, or local labour rules.

Short answer: keep roles, hours, minimum cover, the rest gap and hour caps you have checked, and a wage budget in US dollars. Paste role codes and recent covers or sales, ask for a table and flags, re-add the totals in a spreadsheet, and publish in your own app. See the AI guide for restaurants and cafés, or take the free 2-minute quiz.

Replace [brackets] with your details. Prompts work in free ChatGPT, Gemini and Copilot, with money in US dollars. This is rota admin, not legal advice. Rules differ by country, region and city: type limits you have checked, and do not post the model's guess.

What goes in the prompt

Put in Leave out
Role codes (FOH-1, GRILL-2) and shifts each code can work Legal names, addresses, phones, dates of birth, ID numbers
Days they can work, and days that are already a no Why they are off: illness, family, pregnancy, religion, a visa
Minimum cover, and who can run each station Pay slips, bank details, tax numbers, warnings
Hour caps, rest gaps and breaks you already use "Whatever the law is" for the model to invent
Rates in US dollars, and your weekly wage budget A chat export, or a photo of a rota with names on it

Plain English, for a small restaurant, café or takeaway. Use only my facts. Keep role codes as written. If a rate, limit or time is missing, write [MISSING]. Do not invent a labour rule, an overtime rate, a break or a forecast. Do not cut cover below my minimum to hit a budget.

Put names back only in your rota app. Read is ChatGPT safe for customer data? before pasting a staff file.

The week, in order

  1. Availability. Code, days they can work, earliest start, latest finish, and days off. Names stay in your sheet.
  2. Approved time off as "unavailable". Leave the reason out.
  3. History you trust: date, daypart, covers or sales in US dollars. No guest names.
  4. Limits you set: minimum people per daypart, who can open or run the pass, max hours, minimum rest, breaks, any tighter cap for younger staff, and the US dollar wage budget.
  5. Draft with prompt 1. [UNFILLED] means that service does not fit. Ask someone trained, or change the floor. Do not say "make it work".
  6. Check the busy service. The person on the pass must be trained. Re-add hours and wages in a spreadsheet.
  7. Publish it yourself. The tool does not message the team. A holiday or closure counts only if you typed it.

Busy periods from your numbers

Rank the dayparts you pasted (prompt 2). You choose next week's cover. A rank is not a forecast: next Friday need not match the last few, and a holiday or function counts only if you type it.

Swaps, time off, and what you send

You approve or refuse. Prompt 3 only tests the request against cover and your limits. Add the first name on the copy you send:

[first name], you're on [day] [start]–[finish] ([station]). [Other name] is off that shift. Reply if this is wrong. [Venue]

[first name], I can't move [day] [daypart]: we would be short on [station], or it breaks our rest gap. You stay on [start]–[finish]. Tell me if another day works. [Venue]

Rota change: [day] [daypart] is now [first name], [start]–[finish], [station]. The old version is out of date. Full rota: [where you post it]. [Venue]

For a day off, record unavailable. Leave the reason, and any form, in your own files.

The wage budget

Type the US dollar rates you pay and the weekly total you will schedule. Prompt 6 shows hours times rate; add that sum in a spreadsheet. Do not drop a closer to force the number. Type any night, holiday or overtime premium you already pay ("hours over [number] a week at [rate] US dollars"), or write [MISSING] so the model does not invent one.

Copy-paste prompts

1. Weekly rota

Rota for [venue], week of [date]. Hours: [opening]. Dayparts: [list]. Minimum cover: [paste]. Codes only: [paste]. Off: [paste]. Limits I checked locally: max [number] hours a day, max [number] a week, at least [number] hours between shifts, breaks: [what you do]. Rates (USD): [code: rate]. Budget: [amount] USD. Table (day, daypart, code, start, finish, hours), then flags and hours times rate. Skip unavailable codes. Do not go under minimum cover. If a daypart will not fit, write [UNFILLED] and stop. No invented law or rate.

2. Busy dayparts

Rank my rows by covers and by sales in US dollars. Flag thin weeks. No percentage forecast. Do not rewrite minimum cover. Exceptions first: [paste]. Table: [paste].

3. Swap

Check this swap against my limits and minimum cover. Yes or no, the limit if no, and two short messages with the times only. Swap: [paste]. Limits: [paste].

4. Time off

Two replies. A: [code] is off [date]; [code] covers [station]. B: refused because [limit I name]; they stay [start]–[finish]; ask which other day works. No private reason. Under 60 words each.

5. A change to the published rota

One note: [day] [daypart] [code] [start]–[finish] [station]. Old rota is out of date. Full rota: [place]. Under 45 words. No reason.

6. Before you publish

Rota: [paste]. Rates in US dollars: [paste]. Budget: [amount] USD. Limits: [paste]. Recalculate line by line. List rows over a limit, dayparts under cover, and whether wages are over budget. Do not rewrite it.

Check the day, the start and the station against the table before you send.

Do not paste the staff file

Codes in the chat, names on the published rota. Leave out contact details, dates of birth, ID, tax and bank numbers, visa scans, health, pregnancy, religion, and the reason for leave. Type the hourly rate. No payroll file and no guest names. You send the messages.

Mistakes

  • Pasting every column of the staff sheet.
  • Posting the model's answer to "what breaks does the law require?" Check an official source where you operate, then type the number.
  • Treating last month's rank as next week's forecast.
  • Trusting the wage total without adding it again.
  • Scheduling someone on a day you marked unavailable, or refusing a swap by repeating a private reason.
  • Cutting cover, or inventing an overtime rate, so the budget looks fine.
  • Publishing the chat instead of the rota the team can see.

A Grok Bot draft you still approve

A Grok Bot AI employee can prepare the table once the prompts work by hand. Check current Grok Bot plans and availability. It runs only with the access, approvals and usage you configure, and it is not guaranteed always-on. The sheet is codes, availability, limits, US dollar rates and covers: no names, no reasons.

On [weekday], read [sheet] and draft with my weekly prompt. Do not schedule unavailable codes or clear [UNFILLED] by breaking a limit. Do not message staff, edit the live rota, or copy the sheet anywhere public. Save it in [folder] and tell me.

Add an "Ask first" rule on messages and on live-rota edits, then post it yourself. Setup is in our Grok Bot guide for small businesses.

Frequently asked questions

How can a restaurant use AI to plan a weekly rota?

Give ChatGPT, Gemini, Copilot or Grok your hours, minimum cover, limits you checked, a US dollar wage budget, and availability as role codes. Check the table, re-add the hours, and publish it yourself.

Can AI forecast busy shifts from past sales or covers?

It can rank the dayparts you paste and flag thin data. That sorts history. It does not predict next week. Add holidays, functions and closures yourself.

How should I use AI for shift swaps and time off?

Note the code, the daypart, and "unavailable" or "swap with this code". Ask if cover and your limits still hold. You decide. The message states the times and leaves the reason out.

What staff details should stay out of ChatGPT?

Skip legal names when a code will do, plus phones, addresses, ID and bank details, health information, and why someone is off. Covers or sales by daypart are enough. Names go back only on your own rota.

It can flag rows past the limits you typed and multiply hours by your US dollar rates. It does not know local labour rules. Check those, and re-add the wages, before you publish.

Can Grok Bot text the rota to staff?

It can draft from role codes for you to approve. Check current plans and availability. It should not message the team or change the live rota, and it is not guaranteed always-on.

Dish wording is in AI for restaurant menus. The wider guide is AI for restaurants and cafés. Prompts for menus, reviews, functions and rosters are in the AI Playbook for Restaurants & Cafés.

Get a plan for your venue: take the free 2-minute quiz.

Get your free AI plan in 2 minutes

Answer 5 questions and get a personalised, copy-paste AI plan for your business.

Start the free quiz