Automatic Assignment

The Shifts Are There. Now Fill Them.

Building the shape of a week is the easy half. The hard half is deciding who works each shift — around availability, rest periods, weekly hour caps, required skills, and the running argument about who got the last three Saturdays. Automatic assignment does that pass for you: pick a range, and Shiftavo proposes a full staffing plan for it. The engine is a constraint solver, not a language model — it doesn't guess and it doesn't hallucinate a schedule that breaks the law. What comes back is ordinary draft assignments in the calendar you already use, so you can change any of it before anyone sees a thing. Automatic assignment is part of Plus, and the 30-day trial runs on Pro — so you can put a real week through it before you choose.

How It Runs

Four Steps, One Staffed Month.

01

Pick the range.

A day, a week, a month — up to eight weeks in one run. Plan one location at a time or, if your role covers the whole company, every location at once.

02

Decide how far it may reach.

By default it only touches shifts nobody has seen yet. You can also let it fill vacancies on published shifts, or re-plan those too. The choice is yours per run, not a setting somebody made once — and each option spells out what it means for your team before you pick it.

03

Let it solve.

A typical week takes a few seconds. It fills every shift toward its target headcount — the position's, or the demand forecast's share for those hours — works around availability and working-time rules, evens out hours across the people on contracts, and on request favors the people who worked the same shifts last time.

04

Read the report, then publish — or undo the lot.

Every assignment it wrote, listed — with any validation issue sitting directly underneath the change that caused it. Adjust what your judgement says to adjust, then publish the normal way. Changed your mind entirely? One button reverses the run, so trying it costs you nothing. What has moved on since stays as it is: an assignment someone answered, edited, offered on the marketplace or already worked.

What You Get

A Plan You'd Have Written Yourself.

Legal by construction

Rest periods and hour caps aren't suggestions.

Daily and weekly limits, minimum rest between shifts, maximum consecutive days, approved absences, required skills — these are hard limits in the calculation. A shift is left empty before any of them is broken. And if a published shift already breaks a rule, the run plans around it and flags it rather than refusing to work.

Fair without the spreadsheet

Hours land where the contracts say they should.

People on contracted hours are moved toward those hours instead of whoever happens to be easiest to place. Casual staff stay exempt. Stated availability beats mere absence of a conflict, so volunteering for a window actually counts for something.

Honest about gaps

It tells you what it couldn't do.

A shift it couldn't staff is reported with the reason — nobody qualified at that location, nobody available that morning, or candidates who all would have breached a rule. No silent holes, and no pretending a week is covered when it isn't.