Module · Core+

Shifts & Scheduling

Plan shifts per location on a weekly grid, capture attendance from a tablet on the floor, edit hours when reality diverges from the plan. The backbone of every operations workspace, included on every plan from Core up.

Where it lives in the panel

  • /shifts — weekly grid, location filter, drag-to-assign UI.
  • /calendar — calendar view across locations.
  • /edit-hours— bulk edit actual hours when the plan didn't match reality.
  • /locations — list of locations; each has a tablet URL of /location/{id}/tablet.
  • /staff/shifts and /staff/panel — what the staff member sees from their phone.

A normal weekly flow

Most operators publish the schedule once a week and patch mid-week as people swap shifts:

  • Plan — drag employees onto slots in /shifts. Each shift captures date, start, end and assigned employee. Brand and location come from the employee's default unless you override per slot.
  • Validate — pending leave or permission requests for the week appear inline; approve or reject before publishing.
  • Publish — save. Staff see their assignments on /staff/panel immediately.
  • Track — during the week, watch the Alerts page for late-checkout warnings and missed-shift flags.
  • Patch — when reality drifts, use /edit-hours to enter actual start / end times. The original planned shift stays for audit; the actual hours feed payroll.

The tablet check-in flow

Per location, GetUp expects exactly one shared tablet on the floor. The tablet is anonymous — no staff sign-in. It reads the day's schedule and issues short numeric codes; the employee enters the code on their own phone to confirm attendance.

  • Check-in code— issued from 10 minutes before shift start, valid for 10 minutes once shown. If the employee uses the code within 2 minutes of the planned start, the system records the planned start time (the "arrived on time" grace).
  • Check-out code — issued from shift start until 30 minutes after the scheduled end, valid for 15 minutes once shown. The 30 minutes after end count as worked time; anything beyond that is capped.
  • Responsibilities— outstanding tasks for the shift block check-out until they're ticked. See HR & People.
  • Forgot to check out — the auto-checkout cron closes the shift after 24 hours, with a note in the activity log.

What gets recorded per shift

  • Planned start and end (manager input).
  • Actual start and end (from tablet check-in / check-out, or manual edit if the system missed it).
  • Brand and location.
  • Notes — free-text per shift, visible to the assigned employee and managers with shift permission.
  • Activity log entries for every state change: created, published, checked-in, checked-out, edited, auto-closed.

Permissions

Shift permission on a staff record adds /staff/shifts to their sidebar. Without it, they can still check in / out (the tablet is anonymous) but they can't see the schedule from their phone — a manager has to publish it elsewhere.

Where to go next

Something still unclear?

Open a workspace and try it, or email us with your scenario — we reply in hours, not days.