Platform/03/Scheduling and time clock
03 Scheduling and time clock
Build the week in minutes. Then let the floor clock itself.
Drag shifts onto a seven-day grid, clone a good week, publish. When a rep walks in, a beacon clocks them in inside the shift window and keeps a heartbeat while they are on the floor. Leave on paid time and GPS breadcrumbs pick up where the beacon stops. Every threshold is a setting per company, not a constant in the code.
/ Works with
01 The week
Seven days, every rep,
coverage against budget.
Sample week. Hover a shift for the rule behind it.
Templates and cloning
Save a week that worked and reuse it. Shifts carry a job, tags and break rules; a template can be applied per store, per season or per promotion.
Conflicts before publish
Overtime, double-booking, unassigned coverage and days over the labor budget surface before the week goes out. Publishing pushes every affected rep.
Open shifts and availability
Open shifts appear in the app for eligible reps; a claim waits for the manager. Availability reads the approved shift end, so an extension moves it too.
ConnectTeam and the company calendar
Dealers that keep ConnectTeam sync both ways with the schedule as the source of truth; in-house dealers get a nightly backfill from the point of sale. Holidays and events live on one company calendar.
02 The beacon time clock
Presence, not a button.
A small beacon in each store. The app clocks a rep in when the phone enters range from five minutes before the shift, pings every minute while they are on the floor, and closes the punch at shift end with the reason recorded. Silence escalates through warning tiers before anything closes.
| Employee | Store | Shift | Clocked in | Source | Day so far | Presence |
|---|
| Setting | What it controls | Sample |
|---|---|---|
| Clock-in early minutes | How long before the published start the beacon may clock someone in. | 5 min |
| Clock-out cap minutes | How far past the end a punch may run before it is closed automatically. | 15 min |
| Ping interval | Heartbeat cadence while in range. | 60 s |
| Absence grace | Silence tolerated before the first warning tier. | 8 min |
| Silence grace on iOS | Extra tolerance for platforms without background presence. | 4 min |
| Break window | Silence inside a break is not an absence. | 30 min |
| Manual punch evidence | How recent a POS login must be to back a manual punch. | 120 s |
| Max extension minutes | Longest shift extension a manager may recommend. | 120 min |
| End-of-day close | Time after which any open punch closes with reason end-of-day. | 23:30 |
| Stationary flag | A phone that never moves for this long is flagged as possibly left at the store. | 180 min |
| Sales idle flag | Presence with no POS activity for this long is flagged for the manager. | 3 h |
| Presence retention | How long raw pings are kept before roll-up. | 30 days |
A subset of the two dozen beacon settings on the schedule settings page. Defaults ship conservative; nothing blocks a punch.
03 Geofence and breadcrumbs
Record and flag.
Never block.
Geofenced punches
Manual punches carry coordinates and are checked against the store's fence. Out of range, or no coordinates at all, is recorded and flagged for the manager. It is never refused, because a refused punch becomes an argument about pay.
Breadcrumbs off-premises
While the beacon sees the phone, GPS stays off. Leave the floor on paid time and the app leaves a trail until the beacon sees the phone again. A breadcrumb is evidence, not presence: it never counts as being in range. Off per company until switched on.
The day, replayed
The time-clock-today map replays the day per person: beacon segments, trails, silence tiers, punches and their evidence, with the roster beside it.
04 Exceptions
Two-stage extensions.
Overrides with evidence.
- 01Manager recommends
From the phone, against a shift, with the minutes and the reason. Capped by the company's maximum.
- 02HR finalizes
From the approvals queue. The shift's end time moves only on HR approval.
- 03Everything follows
The beacon cap, the silence warnings and availability all read the approved end time, not the request.
| Employee | Request | Evidence | Requested by | Status |
|---|---|---|---|---|
| M. Delgado | Add clock-out Tue 18:31 | POS logout 18:31, last beacon ping 18:29 | Store manager | Awaiting HR |
| S. Whitfield | Move clock-in Wed 09:04 to 09:00 | Beacon first seen 09:04, door sensor 08:58 | Store manager | Recommended |
| T. Nakamura | Reopen auto clock-out Mon 17:32 | Reason shift_end; POS sale at 17:41 | Rep, from the app | Approved, forwarded |
| J. Petrov | Remove duplicate punch Thu | Two manual punches 4 s apart | System | Soft-removed with marker |
Worked time is never hard-deleted. A reconciled punch is soft-removed and the marker says why.
05 What each role sees
Rep
The week, the next shift, the clock with beacon status, silence warnings, open shifts to claim, extension requests, a punch dispute from the stub.
Store manager
The grid, templates, publish, the floor today, overrides with evidence, extension recommendations, scheduled versus worked.
HR and finance
Extension approvals, the override queue, beacon settings per company, presence flags, the map replay, and the hours that flow into payroll.
06 Related
Payroll and pay stubs
FLSA regular-rate overtime, compliance queue, e-signed stubs, provider reconciliation.
/ 10Mobile apps
iOS and Android, one app with a face for every role, push, device trust.
/ 12Security and tenancy
Entra ID sign-in, a database per dealer group, layered permissions, immutable records.
/ allEvery platform page
The twelve deep dives, one per capability, with the overview above them.
→ Start
Put a beacon
in one store.
A pilot store runs the clock for two weeks next to whatever you use today. You compare the hours; the reps compare the friction.
Request a demo