The Weekly Roster That Takes Three Hours to Build (And How to Sort It Over a Cup of Tea)

Draft for Amber’s review.

You didn’t fail at AI. You hired it badly.

That might sound a bit blunt, but it is usually the truth.

You gave it a vague instruction, pasted in half a spreadsheet, and hoped it would somehow understand your team, your opening hours, everyone’s childcare arrangements, and the fact that Dave cannot work Tuesdays because he plays five-a-side.

Then it produced something useless.

Fair enough. I would be unimpressed too.

But rota planning is exactly the sort of admin work AI can help with, if you treat it like a member of staff. It needs a proper job description, sensible onboarding, clear information, and someone checking its work.

No magic wand. No faff. Just decent management.

Your rota is not difficult because you are bad at spreadsheets

It is difficult because you are trying to hold too many moving parts in your head while the phone rings off the hook.

You are checking:

• Who is available
• Who has booked holiday
• Who is contracted for which hours
• Who can open or close
• Who is trained for each role
• Who has swapped a shift
• Who has called in sick
• Whether you have enough people for the busy periods
• Whether you have accidentally given Sarah every Saturday again

And that is before a customer asks if they can move their booking.

A useful rota starts with information, not names in boxes. Practical rota guidance from RotaCloud recommends gathering availability, planned leave, contracted hours, staffing requirements and expected demand before assigning shifts.

That is the bit most people skip.

Start with one simple rota information sheet

You do not need a new platform for this. A spreadsheet will do.

Create four tabs.

Tab one, staff details

For each person, list:

• Name
• Role
• Key skills
• Contracted weekly hours
• Minimum or maximum hours, if relevant
• Whether they can open
• Whether they can close
• Whether they can work alone
• Any restrictions you need to know about

Keep this factual. Do not add personal gossip or sensitive information that is not needed for scheduling.

Tab two, availability

Use the same format every week:

Name	Monday	Tuesday	Wednesday	Thursday	Friday	Saturday	Sunday
Alex	9am to 5pm	Unavailable	9am to 5pm	After 4pm	Any time	Any time	Unavailable

Ask staff to submit changes by a fixed deadline. For example, Thursday at midday for the following week.

If someone sends availability through WhatsApp, copy it into the sheet. Otherwise, you end up with seven versions of the truth, and none of them agree.

Tab three, leave and changes

Record:

• Approved holiday
• Training
• Known appointments
• Agreed shift swaps
• Sickness
• Any temporary restrictions

A shift swap is not complete until it is recorded and approved. You do not need a committee meeting. You do need a written record.

Tab four, the weekly demand

List your opening hours and the number of people needed for each period.

For a pub, that might be:

Day	Time	People needed	Notes
Friday	5pm to 8pm	4	After-work rush
Friday	8pm to close	5	Live music
Saturday	12pm to 4pm	3	Quieter lunch
Saturday	6pm to close	6	Bookings

Use your past rotas, sales, bookings or footfall to make this more realistic. You are not trying to predict the future perfectly. You are giving the AI a sensible starting point instead of asking it to pluck a rota from thin air.

Give your AI staff member a proper job description

Here is the part you can copy.

Create a new chat or workspace and name it something clear, such as “Weekly Rota Assistant”.

Then give it this job description:

You are the weekly rota assistant for [business name].

Your job is to prepare a draft weekly staff rota using the business opening hours, staffing requirements, staff roles, contracted hours, availability, approved leave, past rota patterns and known events.

You must prioritise safe coverage, accurate hours, fair allocation of evenings and weekends, and each person’s stated availability.

You must never schedule someone when they are marked unavailable or on approved leave. You must not invent staff, availability, qualifications or shift swaps.

If the information is incomplete or two rules conflict, stop and ask a clear question. Do not guess.

You will produce a draft rota, a list of uncovered shifts, a list of possible issues, and a summary of hours assigned to each person.

The manager makes the final decision and must approve the rota before it is shared with staff.

That last line matters.

AI can draft the rota. It does not know your business well enough to publish it without a human check.

Onboard it with real examples, not a giant information dump

Nobody gives a new member of staff every document in the business and says, “Right, off you go.”

You show them how things work.

Give your rota assistant:

1. The staff details tab.
2. The current availability tab.
3. Approved leave and known changes.
4. Your weekly staffing requirements.
5. Two or three previous rotas.
6. A short list of your non-negotiable rules.

Your rules might include:

• At least one trained keyholder on every opening shift.
• Two qualified staff members on a busy Saturday evening.
• No one works a close followed by an early open.
• Do not exceed contracted hours without flagging it.
• Share late and weekend shifts fairly.
• Keep a small amount of capacity available for sickness cover.
• Do not approve swaps automatically.

Then ask it:

Read the information provided. Before drafting anything, list the rules you have understood, the information you are missing, and any conflicts you can already see.

This is your onboarding check.

If it confidently claims that Priya is available on Wednesday when the sheet says she is not, you have caught the problem early.

Use this weekly prompt over a cup of tea

Each week, upload or paste the updated information and use:

Prepare a draft rota for [dates].

Use the attached staff details, availability, approved leave, staffing requirements and previous rotas.

First, check for conflicts. Then create the rota.

Do not schedule anyone outside their availability. Do not schedule anyone who is on approved leave. Keep contracted hours in mind and flag any likely overtime. Make sure the required roles and staffing levels are covered. Allocate unpopular shifts as fairly as possible based on the previous rotas.

Show the result in a clear table with the date, shift time, role and staff member.

After the table, provide:

1. Total hours for each person.
2. Uncovered shifts.
3. Conflicts or risks.
4. Questions I need to answer before approval.
5. A short list of backup staff who may be suitable if someone calls in sick, based only on the information provided.

That should produce a draft, not a final answer.

Read every line.

Does the person opening actually have a key? Has the AI used someone who is on holiday? Has it given one person every undesirable shift because the previous rota did? Has it quietly invented a “flexible” employee who does not exist?

AI is fast. It is not psychic.

Handle swaps and sickness with rules, not panic

For a shift swap, give the AI the original shift, the person requesting the change, the proposed replacement, and the reason.

Ask:

Check whether this shift swap is possible. Confirm that the replacement is available, suitably trained, within their working limits, and not already scheduled elsewhere. Do not approve the swap. List any concerns for the manager.

For sickness, do not ask it to choose somebody at random.

Ask it to show suitable cover based on:

• Availability
• Role and training
• Hours already worked
• Rest between shifts
• Any agreed limits
• Whether the person has opted into extra shifts

Then you decide who to contact.

This keeps the process calm and gives you a record of why the change was made. It also helps protect payroll accuracy and avoids the classic Friday night message, “Hang on, who actually worked this shift?”

Guidance from Bespoke HR also recommends a clear process for shift swaps, advance planning, fair distribution of shifts and a backup plan for unexpected absence.

Do not pretend AI removes responsibility

Here is the honest bit.

This method will not make staffing problems vanish.

It will not solve a shortage of trained people. It cannot make someone turn up when they have decided not to. It cannot replace your knowledge of your team, and it should not make decisions about sensitive employee issues without your involvement.

It can reduce the blank-page problem.

It can compare information quickly. It can spot obvious clashes. It can summarise hours. It can give you a workable first draft while you drink your tea instead of staring at the spreadsheet as if it has personally offended you.

That is the point.

The framework we teach at Phare HR is called Amplified Impact. The idea is simple. Use AI for the repetitive admin, then keep human judgement where it belongs.

This is what proper AI staffing looks like

At Phare HR, we call this Back of House by Phare HR.

AI staff, set up and managed.

The name matters less than the management behind it. A useful AI staff member needs a job description, onboarding, access to the right information, supervision and regular checks.

Exactly like a human member of staff.

If you want the wider explanation, you can read You didn’t fail at AI. You just weren’t shown how.

And if you would like to see the method explained live, the free class "You didn't fail at AI. You hired it badly." is on Friday 25 September 2026, from 12:00 to 13:30 BST. You can register here, with no hard sell.