Rotas separates shift requirements, assignments, offers, staff availability, briefs and actual work evidence. A published schedule is planned cover; Attendance establishes reviewed actual intervals and exportable timesheets.
Native My rota and holiday requests
The native app's My rota is a monthly calendar with shift and availability markers. Select several dates to replace their whole-day availability together; existing shifts stay scheduled. Partial saves name the successful count and retain unsaved dates. Shift rows show the actual Site, Space and function, with their published brief.
Scheduled gross pay is an estimate from the person's unambiguous effective hourly terms, less scheduled breaks. Missing, conflicting or non-hourly terms show unavailable; salary is not converted into an hourly rate. Totals cover only loaded shifts at the matching revision, with partial results labelled. Offered shifts show estimated pay and any separate incentive. Claim shift requests manager approval; it does not assign the shift immediately.
Holidays shows recorded annual entitlement and personal requests. Remaining
balance is unavailable until an opening balance is recorded; there is no
balance-entry or accrual workflow. Staff request whole/half working
days and may cancel pending requests. Whole-business people.manage authority
reviews requests with a decision note; a person cannot approve their own request.
Approval records the decision only: it does not cancel shifts, change availability
or create payroll. Employment changes require a fresh request/review. Managers
must check staffing and the separate leave record before approving.
Pay, offers, availability and holiday snapshots recheck access on entry, foreground and explicit refresh, without a polling timer. Schedule and published brief subscriptions retain current source authorization and actor bindings. Personal rota reads require a linked Staff record and Rotas self-service access; Group administrators without employee identity retain management handoffs. Offline users cannot submit these new commands. Errors retain retry context and never become a zero pay estimate or a known leave balance.
The existing web schedule and exchange remain unchanged. Source checks and fictional rendered comparisons separate local evidence from signed-in and installed-device acceptance.
Schedule, exchange and availability screens
| Section | Operator use |
|---|---|
Schedule, /rotas?section=schedule | Week-first planning grid with Site, Space, function, period and person/role filtering, open headcount, assignments, person hours and period totals. |
Exchange, ?section=exchange | Open offers, staff claims and two-sided swap requests with their current decisions. |
Availability, ?section=availability | Record personal availability state and start/end interval. |
Evidence, ?section=evidence | Manager qualifications, recorded work and reconciliation status. |
Attendance, /rotas/attendance | Clock points and policy, manager review, requests, observations, session evidence and exports. |
To build a week, create a shift with function, date, start/end, optional Site and Space, required headcount, break minutes, skills and training requirements. Organisation-wide leaves the Site unset and is available only with whole-business rota management authority, including when the business has no Sites. Choosing a Site keeps the shift and its lifecycle event attached to that Site; a physical Space requires its matching Site. Creation saves a draft; publication remains a separate reviewed action. Retrying the same unchanged creation does not duplicate its draft or audit/event history. A shift's physical Space is independent of its function. Save a useful week as a named template; applying it copies requirements and locations, never staff. Managers can drag people into open places, move assignments or swap placements. The staff list covers the whole business for managers who view people business-wide. A manager limited to several Sites sees staff from every managed Site where they may view people. Each placement rechecks current employment, workplace, availability, qualifications and overlap.
Publish an exact shift or open-cover offer when ready. Offers can include an incentive label and amount. Staff claim a specific offer; managerial approval checks current eligibility before adding the assignment. An employee swap needs both participants' agreement and a manager's decision. Cancelling a shift closes its assignments, claims, pending swaps and brief actions together.
An empty roster offers authorised managers a route to People. A filtered roster with no matches asks the operator to broaden filters. Staff cannot gain another Site's shifts through a personal ownership grant alone.
Shift preparation and demand
The native brief supports checkboxes per assigned person and published version, independently of acknowledgement. An empty checklist never requires acknowledgement; Mark viewed remains available. Whole-business rota managers can configure exact shift-role/weekday checklist defaults. They are combined with manual items when a manager next publishes a brief, then frozen in that version. Changing defaults does not rewrite published work or auto-publish new shifts. Removed assignment, stale progress, retired entitlement and superseded brief versions are refused by the source. This does not create recurring Tasks.
Publish shift preparation captures access notes, stock exceptions and a role checklist. The versioned brief also draws permitted event, booking, maintenance and demand context. Staff can open their brief and record that they viewed it. Source freshness remains visible: missing, stale or oversized contributors do not silently become current facts. Guest identity is not copied into a brief.
Where authorised, the demand panel compares immutable booking workload with scheduled cover and proposes redeployment or open shifts. Acceptance rechecks source revisions, qualifications, availability, overlap and relevant private employment/budget evidence. New proposed shifts remain drafts. Contract-derived warnings are visible only with the required People authority; rota-only readers receive operational coverage and neutral eligibility failures.
A Talent contribution may show confirmed performances beside the schedule. Those acts retain Talent bookings and consent; no employee assignment or payroll row is created. Missing optional modules do not block standalone rota planning.
Clocking and attendance review
Managers create clock points at a Site and choose basic tags with review, secure changing tags, or a tag policy with one-time location evidence. Location configuration includes latitude, longitude, radius and maximum accuracy. Secure key provisioning is separate from policy configuration. New token receipts must be retained when displayed; tokens are not ordinary public directory data.
Staff use the clock journey, including /clock/{token}, to record explicit clock-in, break-start, break-end and
clock-out. They choose an eligible shift at that Site or mark unscheduled work. Observations preserve observed
and receipt time, timezone, policy revision, employment context and verification evidence. Missing required
evidence creates an exception/correction request.
Managers select Site and date range, inspect the original session and actual break intervals, and propose corrected start/end and paid/unpaid break minutes with a reason. Another authorised reviewer decides the timesheet. The original observations remain inspectable; corrections create new evidence. Review rejects stale versions and conflicting intervals instead of silently overwriting them.
When you manage Attendance at two or more Sites, the Site selector opens on All Sites. All lists pending timesheets, staff requests and recorded observations from every Site where you can review, and each decision is still checked at its record's own Site. Clock points, manager work evidence and approved timesheet exports need one chosen Site. With one Site, the screen opens on that Site. Review lists read a bounded window of the business's records; when Review results are limited appears, narrow the date range. Native Attendance review follows the same rule: Attendance site opens on All sites, each row names its Site, and Manager work reconciliation asks which Site to reconcile before it loads manager work evidence.
Older manager-recorded worked minutes are reconciled to an Attendance session with explicit actual times. Their prior approvals are preserved, but they are not an independent payroll ledger. Approved timesheet export freezes a reviewed employer-specific version. Unreconciled source work cannot silently vanish from a period export; exports can be superseded. The current export operation is bounded to 63 days and 500 sessions, so large periods need splitting. An export provides payroll evidence and does not execute payroll.
Offline and access behaviour
Offline clock observations remain pending independent review. A secure tag proves tag evidence, not the capture time or the person's physical presence. An uncertain online attempt keeps the original operation, timestamp and evidence for exact retry; it does not become a new offline punch. Staff cannot relax the clock-point policy. Closing attendance does not close a shift or payroll period.
| Permission | Responsibility |
|---|---|
rotas.view | Read permitted scheduling and personal work. |
rotas.manage | Requirements, assignments, open-cover offers, eligibility and manager decisions. |
rotas.publish | Publish planned shifts. |
rotas.attendance.punch | Record personal clock observations. |
rotas.attendance.review | Review sessions, requests and proposed timesheets. |
rotas.attendance.configure | Clock-point policy and provisioning. |
rotas.attendance.export | Freeze/read authorised timesheet exports. |
rotas.settings.view, rotas.settings.manage | Settings reach and editing authority. |
The general Rotas settings route currently exposes General, Scheduling, Availability and Exchange section shells. It does not itself provide editors for all the defaults described by those headings; actual clock policy lives in Attendance. Every stored Site/Space and contributing source retains its own access restriction on reads, actions and export downloads.