Coach scheduling with AI: the monthly rota, without the spreadsheet
Coach scheduling with AI works best split in two. A small scheduling program builds the rota from your rules, and an AI agent handles the conversations around it: asking every coach for their availability, chasing the ones who have not answered, finding cover when someone drops out, and checking every change with you. This guide is for gym and CrossFit box owners who still build the month in a spreadsheet.
What the spreadsheet is really doing
The grid is the easy part. The monthly rota takes an evening or two because of everything around it:
- Collecting availability from every coach, in a dozen different messages and formats, and chasing the two who always answer late.
- Remembering the rules that live in the owner's head: who can take the kids' class, who should not open at 6 am after closing at 9 pm, who wants more hours and who wants fewer.
- Keeping it fair: the early mornings, the Saturday classes and the popular evening slots, spread so nobody feels stuck with the worst of them.
- Handling the swaps once the month starts, usually by phone, often the night before.
An AI agent helps with the first, second and last of these. The third, the grid itself, is a job for ordinary software, and it is worth being clear about why.
Write down the rules in your head
Before anything is automated, the rules have to leave the owner's head. Most fit into a short table. Mark each one as a hard rule (never broken) or a preference (kept when possible). The examples are an imaginary box's.
| Rule | What it covers | Example | Type |
|---|---|---|---|
| The timetable | Every class in the month that needs a coach, by day and time. | Weekdays at 6:00, 7:00, 12:15, 17:30, 18:30 and 19:30; Saturdays at 9:00 and 10:00. | Hard |
| Who can coach what | Classes that need a specific qualification or experience. | Kids' classes and the weightlifting class only with the coaches listed for them. | Hard |
| Limits | Most and fewest classes per coach, and rest between shifts. | No more than 12 classes a week; no 6:00 class after a 19:30 the night before. | Hard |
| Fairness | How early, late and weekend classes are shared out. | Saturdays rotate; nobody opens more than three days in a row. | Preference |
| Wishes | What each coach would like, beyond when they are free. | Two coaches prefer mornings; one wants more hours this month. | Preference |
The monthly cycle, step by step
With the rules written, the month runs on a fixed calendar. The dates below are an example; you choose your own.
- Day 15: the agent asks
Each coach gets a WhatsApp message asking for next month's availability. They answer in their own words: "Mondays not before 9, away 12 to 19, happy to do Saturdays."
- Day 18: it chases
Coaches who have not answered get one reminder. Anything unclear ("maybe the 20th") is asked back, not guessed.
- Day 20: the draft
The scheduling program builds a rota that meets every hard rule and as many preferences as it can, and lists what it could not satisfy.
- Day 21: you decide
You read the draft and the list, move what you want and approve it. Nothing is published before that.
- Day 22: it is out
The rota goes into your booking software (through its API if it has one, or as a file to import), and each coach gets their own classes by message.
Why the AI does not draft the grid itself. A language model is very good at turning "I can do Tuesdays but not the 18th, and only mornings in the second half" into clean data. It is not the right tool for checking twenty rules across a hundred and fifty classes: in a long month it can miss one. A small scheduling program checks every rule every time, and tells you when the rules cannot all be met. So each part does what it is good at, and you get a rota you can trust.
One practical note: a WhatsApp message that the box sends first, such as the monthly request, goes out as a template approved by Meta, and Meta charges for each one delivered. For a handful of coaches a month the cost is small; we explain what WhatsApp charges per message.
Last-minute cover
The rota is monthly; the problems are daily. When a coach writes "sick, can't do 6 am tomorrow", the agent:
- Finds who can take it: coaches who are free, qualified for that class and within their limits, from the rota and the rules.
- Asks them in your order, one at a time or all at once with the first yes taking it, whichever you prefer.
- Checks with you before confirming, or confirms on its own within rules you set (for example, any qualified coach for a regular class).
- Updates the schedule and tells the coaches involved, and keeps a record of the swap for the end-of-month hours.
- Warns you in time if nobody can cover it, with an hour you choose as the deadline, so you are not finding out at 5:45 am.
The agent does the asking and the chasing. You keep the decisions about your coaches.
What stays with you, and when it is worth it
You approve the rota and every exception. Disagreements between coaches, pay and anything personal stay with you; the agent never negotiates for you. Coaches can always reply "call me" and get a person.
It is not worth it for every box. With three coaches and a timetable that never changes, a shared calendar may be all you need. It starts to pay when there are several coaches, classes that change from month to month, frequent swaps, or more than one location sharing coaches. Is an AI project worth building? has five questions to check.
The same agent can also answer members and handle freezes, plan changes and cancellations from your rules; the AI agent for gyms and CrossFit boxes page shows the whole picture.