Skip to content
  1. Hospitality franchise management software
  2. Exceptions

Approvals and exceptions · Orbit OS by Operator Systems · stores it runs

Resolve exceptions from one queue

Timesheets that differ from the roster, leave, shift swaps, attendance exceptions, roster-publish requests and permission requests land in one approvals queue in Orbit OS, grouped by day, week or person. Every decision is recorded, and approved timesheets are what payroll pays.

The Approvals hub in Orbit OS for a demo business, with the queue of timesheets, attendance exceptions and leave requests awaiting a decision, grouped by week

The Approvals hub. Demo business with fictional names.

The problem

A late clock-in, a missing clock-out and a leave request live in three places, and payroll inherits whatever nobody checked.

What head office sees

One queue of everything waiting across the stores its business runs — how many, how long, by store and by person.

What it can do

Approves or declines each item with the rostered shift and the hours beside it; filters by type, store, date range; groups by day, week, month or person.

The outcome

Nothing reaches payroll undecided, and every decision carries who made it and when.

Who does what

Head office sets it. The store runs it.

What head office controls

  • Sees what is waiting across the stores its business runs, and how long it has waited.
  • Decides roster-publish requests from stores set to require approval, and permission requests.
  • Reads every decision with who made it and when.

What the store manager does

  • Decides timesheets, leave, swaps and attendance exceptions from one queue, with the roster beside each item.
  • Approved timesheets flow to payroll as approved. Payroll never re-decides them.
  • In a franchised store the queue is the franchisee’s own; head office does not see it.

The workflow

How it works, step by step.

  1. Exceptions surface

    A clock-in that differs from the roster, a shift without a clock-out, a leave request, a swap, a roster waiting to publish, a permission request — each becomes an item in the queue.

  2. Group and filter

    By day, week, month or team member; today, the last 7 days, the last 30 or all time; one store or all.

  3. Decide with context

    The rostered shift, the hours worked and the person’s notes sit beside the decision.

  4. Downstream, once

    An approved timesheet is what payroll pays. The decision and its record stay with the timesheet.

Questions

Asked before a demo.

  • What counts as an exception?

    A timesheet that differs from the rostered shift, a shift without a clock-out, an attendance exception, a leave request, a shift swap, a roster waiting for publish approval, and a permission request.

Orbit OS by Operator Systems

See it on your own network.

Book a demo