- Hospitality franchise management software
- Roster publishing
Roster publishing · Orbit OS by Operator Systems · stores it runs
Control how rosters are published, store by store
In Orbit OS each business decides, per store, whether a manager publishes rosters directly or needs an owner’s approval, and the database enforces it at publish time. Edits to a published week are staged and go live once, and every change to a roster is logged and cannot be edited.
A published week in the roster builder. Demo business with fictional names.
A manager publishes a roster that breaks the labour plan, and head office finds out when the wages are already earned.
Every published roster with its labour total, and a change log of who published, edited or cancelled what, and why.
Sets the store to publish directly or to require owner approval; approves or declines publish requests; sets the templates, positions and rate templates stores build from.
Rosters that need a second pair of eyes get one before the team is told, and the record of every change survives.
Who does what
Head office sets it. The store runs it.
What head office controls
- Sets, per store, whether the manager can publish directly or must send the roster for owner approval. The rule is enforced when the roster is published, not just shown on screen.
- Sets roster templates, positions and rate templates once for the business; they reach every store it runs. Store managers can also add templates for their own store.
- Sees every published roster and every change to it: who changed what, when and why, in a log that is append-only and kept for 180 days.
What the store does — and, in a franchised store, the franchisee
- Builds the week from the template, by position, with the labour cost visible while building — for roles allowed to see wages.
- Publishes when ready. The team is told once.
- Edits to a published week are staged as pending changes and go live together on “Publish changes”.
- In a franchised store, the publish rule and the approval are the franchisee’s, in their own workspace.
The workflow
How it works, step by step.
- 1Build
The manager starts from the store’s template and lays out shifts by position. The labour total updates as they build, priced by the same engine that prices timesheets.
- 2Publish, or send for approval
The store setting decides. A store on “owner approval” cannot publish until an owner or admin approves — the database refuses it.
- 3Change safely
Edits after publishing are staged, not live, so a busy week is not rewritten shift by shift. “Publish changes” releases them together.
- 4Every change on record
The roster change log records each publish, edit and cancellation with who and why. It is append-only and kept for 180 days.
Questions
Asked before a demo.
Can head office stop a store publishing a roster that breaks the rules?
For the stores its business runs, yes: set the store to require owner approval and the manager’s roster waits for an owner or admin. A franchised store’s rule belongs to the franchisee.
Are staff notified on every edit?
No. Edits to a published week are staged and released together, so the team hears once.
More head-office controls
The other six.
Orbit OS by Operator Systems