Automation should assist, not override
A roster is full of judgement calls: who works well together, who is stretched this fortnight, who is closest to a client's needs. Good automation surfaces the obvious matches and leaves the judgement to you.
Start from a base roster
Set up the recurring pattern of shifts each site runs: the shape of a normal week or fortnight. That base roster is the foundation the recommendations build on, so you are never starting from a blank page.
Factor in the shifts staff want
Staff can register interest in the shifts that suit them. When BondiByte generates recommendations, that interest is part of the picture, so the roster leans towards work people have actually put their hand up for.
Review, then publish
Recommendations are a starting point, not a decision. You review what the engine proposes, adjust anything you want, and nothing reaches your team until you publish it. The roster is always yours.