As of 13 August 2026, AI can allocate staff to shifts.
This still needs a person who signs their name to it.
Can you do it?
5 minutesto a draft.
30 minutesto something you’d act on.
Cost, all in£0
Skill neededchat-fluent
Who has to check ita colleague
What the alternative costsThe supplied tool list includes no price for a comparable rota service, so no pounds comparison is made.
If this goes wrong: a shift is left short, someone is assigned outside their availability or working pattern, or staff receive an unfair or impractical rota.
What to actually do
Hand it to a person
The route this page recommends
A person who owns the outcome does this end to end, worth it when the failure is dear.
Use a tool built for this
Second choiceDo it yourself
The distant thirdA chat interface, chat-fluent skill, and roughly 30 minutes until you can act on the result.
How to actually do it
- Open a spreadsheet and create separate sections for shifts, staff, availability, leave, skills and rota rules.
- Gather the required coverage for every shift, including location, times, headcount and any mandatory skills.
- Paste each person's availability, role, skills, contracted hours, leave and existing commitments into the matching spreadsheet section.
- Add your workplace rules and preferences, separating hard constraints such as unavailability from preferences such as preferred shifts.
- Paste the completed information into a chatbot with the copyable prompt and ask it to produce the rota, coverage check and list of unresolved conflicts.
- Compare every assignment against the source spreadsheet, then ask a manager to check hours, rest, fairness, qualifications and local employment requirements before sending the approved rota to staff.
Prompt
Create a staff rota from the information below. Allocate each required shift to suitable staff while respecting every stated constraint. Period to schedule: [dates] Locations or teams: [locations or teams] Shifts required: [date, start time, end time, location or team, number of people, required skills] Staff list: [name or staff ID, role, skills, contracted hours or minimum hours, maximum hours if applicable] Availability: [each person's available and unavailable times] Approved leave or absences: [details] Existing commitments: [details] Rules and preferences: [minimum rest, maximum consecutive shifts, weekend rules, fairness requirements, shift preferences, travel or location restrictions, and any workplace rules] Return: 1. A rota table with date, shift times, location or team, assigned staff and skills covered. 2. A coverage check showing whether every shift and required skill is covered. 3. A constraint check for availability, leave, hours, rest, consecutive shifts and stated preferences. 4. A list of conflicts, uncovered shifts and assumptions that need a manager's decision. 5. A short explanation of the main allocation choices. Do not invent availability, qualifications, leave, rules or staff members. Do not treat an unstated preference as a hard rule. If the information is insufficient, ask focused questions before allocating the affected shifts. Mark any item that needs human or employment-law review.
Open it prefilled in ChatGPT or Claude, or copy it into Gemini, which takes no prefill link.
What it gets wrong
- AI cannot know whether an informal arrangement, skill level or staff preference is still current unless you provide it.
- It cannot take responsibility for checking your organisation's employment rules, contracts or local working practices.
- It cannot reliably resolve competing human priorities such as fairness, morale, continuity and a preferred team mix without a manager's judgement.
- It can produce a neat table while missing a hidden coverage, rest or qualification problem, so the rota still needs a structured check.
Even on a YES, the friction has a name: judgement under ambiguity, verification cost and stakes of error.
How we scored this
Five axes, each scored nought to two by hand: ten means AI carries the task cleanly, and the thresholds that turn a total into YES, PARTLY or NO are published in the methodology. Each axis name links to its definition.
| Axis | Score (0–2) |
|---|---|
| Output | 2 |
| Inputs | 2 |
| Verification | 1 |
| Liability | 1 |
| Effort delta | 2 |
| Total | 8 / 10 |
The methodology and its thresholds are published in full.
FAQ
- Can ChatGPT make a staff rota?
- Yes. Give it structured staff availability, skills, leave, shift requirements and rules, and it can produce a draft rota with coverage and constraint checks. A manager must check and approve it before publication.
- Can AI schedule shifts around staff availability?
- Yes, if you provide complete and current availability in a clear format. It should not fill gaps by guessing, and it cannot know whether a last-minute change or informal agreement is valid.
- Can AI make a fair staff rota?
- It can apply explicit fairness rules, such as rotating unpopular shifts or balancing hours, if you define them. Fairness also depends on context, accessibility needs, skills, continuity and staff relationships, so a manager needs to review the result.
- Is AI safe for making staff rotas?
- It is useful for a first draft, but the employer remains responsible for coverage, working patterns, pay-related records and treatment of staff. Check the rota against contracts, workplace rules and current GOV.UK guidance before publishing it.
Nearby answers
Assessed by gpt-5.6-luna (gpt-5.6-luna) on 2026-08-13, second-checked by an independent model. Wrong somewhere? Email [email protected] and it gets re-checked.
The newsletter
AI news, new answers and product picks, straight to your inbox.