| Employee | Position | Site | Rostered | Clock in | Clock out | Break | Location | Clock | Contacted |
|---|---|---|---|---|---|---|---|---|---|
| Pending | |||||||||
| No shifts for this filter. | |||||||||
Loading trends…
Behaviour over time
Distinct shifts per week with a missed clock, an off-site clock-in, or location services off. Downward = improving.
Repeat clock offenders
Only workers with ≥4 shifts who miss more than 1 clock per 4 shifts — occasional slips are excluded. Sorted by total missed clocks.
| Employee | Bucket | Shifts | Missed in | Missed out | In fail % | Out fail % | Trend | Contacted |
|---|---|---|---|---|---|---|---|---|
| repeat | ||||||||
| No clock offenders for this window/region. | ||||||||
Location services off
Clocking in with GPS off — contact to enable location services.
| Employee | Bucket | Times | Contacted |
|---|---|---|---|
| None for this window/region. | |||
Off-site workers
Frequently clocking in off-site — click a worker to see the sites/distances (worker issue vs wrong geofence).
| Employee | Bucket | Off-site | Contacted |
|---|---|---|---|
|
·
·
Loading…
|
|||
| None for this window/region. | |||
Off-site by site — geofence check
Many workers off-site at the same site usually means the FoundU radius is too tight or the site coords are wrong. Not region-filtered.
| Site | Off-site clock-ins | Workers | Typical distance |
|---|---|---|---|
| site pin likely wrong | |||
| No off-site sites for this window. | |||
Ute movements vs allocations
Navman (TN360) trips for each work ute, checked against its FoundU allocation for the day. A ute that moved on a day it wasn't allocated is flagged — split into ended at a rostered site (taken to work without being booked) and off-site travel (possible personal use). Trips to a WorkCon office or yard aren't travel, so a ute that never left base isn't listed at all. Trips sync overnight.
| Date | Ute | Rego | Status | Allocated to | Trips | Km | Moving | Where it went |
|---|---|---|---|---|---|---|---|---|
| — |
Navman fleet → FoundU utes
Tick Track for each work ute and link it to its FoundU ute record (the "Ute …" employee its allocations are booked under). Vehicles left unticked are ignored. The FoundU list grows as ute allocations are seen — if a ute is missing, run Sync now after a day it was rostered, or type its FoundU employee id.
TN360_API_KEY.
| Track | Rego / Navman name | Display label | FoundU ute | FoundU employee id | |
|---|---|---|---|---|---|
Allocator slots
Each slot maps FoundU roster managers to a region and role. The board buckets every worker by their shift's manager using these mappings — a worker whose manager isn't mapped shows under Brisbane / Labour. Changes apply on the next board refresh (within 10 minutes).
| Region | Role | FoundU managers | Report email | |
|---|---|---|---|---|
|
|
Special case workers
Trusted workers who submit their hours at the end of the week instead of clocking in. They're left out of the failed-clock-in lists and shown as a side table on the Missing Hours sheet. Changes apply to the next pipeline run.
Trusted workers who submit their hours at the end of the week instead of clocking in. This list is kept per company — these are 's workers only.
| Name | FoundU employee ID | Added | |
|---|---|---|---|
View as
Pick a role in the bar at the top of the page to run the board — and the main app — with that role's permissions instead of your own. Development permission only. Your identity doesn't change: anything you save while viewing as a role is still saved as you.
| Role | Permissions | Companies |
|---|---|---|
|
|