Auto-schedule: filling shifts from staffing requirements
Auto-schedule builds a week's rota for you. You tell KAMI how many people each shift needs at each branch, and it fills those shifts with people who can legally work them. Nothing reaches employees until you have reviewed the draft and published it.
Where: Attendance › Calendar › Week › Auto-schedule
You need:
- Run Auto-schedule to build and regenerate drafts
- Publish Auto-schedule to publish them
- Staffing Requirements and Scheduling Rules to set it up
All four are in the Auto-schedule group of Attendance user rights.
When to use this, and when not to
| You want to | Use |
|---|---|
| Fill a week or a month against a headcount, without breaking rest rules | Auto-schedule, here |
| Give someone the same week, every week | An event template as a standard schedule |
| Place a few one-off shifts by hand | The team calendar |
| Offer optional extra work | Open shifts |
| Load a rota planned in a spreadsheet | The Bulk Schedule import. See Standard and dynamic schedules |
Auto-schedule earns its place where the rota changes week to week and the job is covering a headcount: shift work, retail floors, warehouses and plants.
How it works
Auto-schedule works from three things:
- Staffing requirements: how many people, in which position, each shift needs at each branch, on which days.
- Scheduling rules: minimum rest between shifts, most days in a row, most night shifts in a row, and weekly hours.
- The calendar as it is: rest days, approved leave, public holidays and who is already scheduled.
It schedules by branch and position. Anyone at the branch in the right position can fill a shift, whichever department they belong to. Department only decides the overtime budget. A manager's draft only uses people in their own team.
⚠️ A shift only counts when its hours match the requirement's shift exactly. Someone on 07:00 – 15:00 does not cover a 06:00 – 14:00 requirement. Build rotas with the hours your requirements use.
Before you start
- Add your staffing requirements and check the scheduling rules. Both are explained in Staffing requirements and scheduling rules.
- Set overtime budgets if you use them.
- Check positions on employee profiles. A wrong position means that person is never scheduled.

How to build a draft
- Open the calendar on Week, on the first week you want to schedule, and select Auto-schedule.
- Choose the Period: the week in view, the four weeks from it, or the week after.
- Choose one or more branches under Branch, or All branches. Each branch gets its own draft.
- Choose What may change:
| Option | What it does |
|---|---|
| Fill gaps only | Leaves every published shift alone, even ones that break a rule |
| Fill gaps and fix breaches (Recommended) | Also moves published shifts that break a rule |
| Rebuild the whole week | Starts from an empty week. Greyed out once the period has started |
Today and earlier days are never changed, whatever you choose.
- Under When there is a choice, optimise for, choose Lowest cost, Fairest spread of nights and weekends, or Fewest changes.
- Check Never broken, whatever you choose above: rest days, approved leave, public holidays, position match, rest hours, days in a row, nights in a row and weekly hours.
- Select Build draft. You can close the window; you are notified when the draft is ready. Cancel run stops it.

If a shift cannot be filled without breaking a rule, it is left empty and reported. Auto-schedule never breaks a rule to fill a shift.
How to review the draft
The draft opens on the calendar under a Draft schedule bar. Employees cannot see it.
- The figures: Shifts filled, Cannot be filled, Changes to review, Rule breaches and Overtime against the budget, with an estimated labour cost.
- One draft per branch: switch between them in the bar.
- Who is shown: people at the branch, in the positions its requirements ask for.
- Coverage against staffing requirements: pinned under the grid. A red cell is short; select it to see why.
- Select any shift to see why that person was chosen or why it is short. The Rules check is calculated, not AI. If your company has KAMI AI, Kita adds an explanation.
- Actions on a shift: pin or unpin it, Give it to someone instead and pin, Post as an open shift, or Borrow from another line to use someone at the branch in that position outside your team.
- Show: Everyone, Added, Changed or Pinned.
- Regenerate reworks everything not pinned. Over budget, Regenerate within budget tries again inside it.
- Discard throws away the draft and its pins. The published schedule is not changed.
How to publish
- Select Review & publish.
- Check who gets a new or changed schedule, and how many shifts stay unfilled. Tick Post them as open shifts to offer the gaps.
- Edit the Message to affected employees. Where Kita is available it drafts this. Leave it empty to send the standard message.
- Keep Notify the affected employees on to send an email, a push notification and a dashboard notification. Employees whose schedule did not change are not contacted.
- Select Publish.
⚠️ Gaps posted as open shifts cannot be claimed yet, because employees cannot apply for open shifts. See Open shifts.
Over the overtime budget, HR must sign it off:
- Someone with access to all employees ticks I approve … of overtime above budget when publishing. It is recorded against their name.
- A manager limited to their own team sees Request HR sign-off. It goes to their attendance approvers in turn, or to every HR holder if they have none. Approvers see Approve & publish or Decline, with a reason. The manager can Withdraw request.
What Happens Next
- The shifts become calendar events, written in one go, and feed timekeeping and payroll like any other.
- Coverage updates on the requirements page and the calendar.
- A stale draft is refused. If someone changes the calendar for those days after the build, select Regenerate, then publish.
- One open draft per branch. A new build replaces the branch's unpublished draft and its pins. While a draft waits for sign-off, a new build is refused until the request is withdrawn.
Tips
- Start with Fill gaps and fix breaches. It fixes breaches without disturbing anyone else.
- Rebuild only weeks nobody has seen. Every person moved is notified.
- Pin before you regenerate, so agreed assignments stay.
- Build every branch at once on a busy week, then work through the drafts.
- Fix the cause of a recurring gap. The explanation usually names it: too few people in the position, tight rest rules, or too high a requirement.
Troubleshooting
"Set your staffing requirements first" appears. The branch has no active requirements. A paused one does not count.
Every shift in the draft is short. Nobody at that branch is in a position its requirements ask for. Check profile positions.
Coverage says short, but someone is working. Their hours differ from the requirement's shift, or their branch or position does.
Rebuild the whole week is greyed out. The period has started. A week starting today counts as started.
I cannot see the Auto-schedule button. You need Run Auto-schedule, and the Week view.