The staff rota

Back Office → Rota is where you build next week. It is a plan, kept separate from who actually clocked in — publishing a roster never invents attendance, so your labour figures and cash-ups stay about what really happened.

30.1 Building a week

Add a shift with the person, the times and any unpaid break. Aura works out the hours and what the week will cost, using each person's current pay rate — a forecast has to price at what you'll actually pay.

Nobody can be double-booked. Two shifts that overlap are refused, including at two different branches. A shift ending at 17:00 and another starting at 17:00 is fine — that's a handover, not a clash.

30.2 Publishing

While you're building, the roster is a draft: only managers can see it. Nobody asks about a shift that was never meant to exist.

Publish makes the week visible. Staff then see who's on and when — but never the cost figures. Publishing again doesn't disturb the shifts already published, so "when did this go up" keeps meaning what staff care about.

Staff see their own shifts under their rota view.

30.3 Rostered against worked

Rota → Variance puts the plan next to the reality: hours rostered, hours worked, and the difference in money.

Each person gets a verdict — on the roster, over, or under — judged proportionally, so fifteen minutes over a four-hour shift isn't flagged while fifteen minutes across a 40-hour week isn't ignored either. Two cases you especially want to see: someone rostered who never clocked in, and someone who worked without being rostered. Both get a line.