What each flag means
Flags point a reviewer at something worth a look. They never stop a punch or an entry, and they never change the hours.
| Flag | What happened | What to check |
|---|---|---|
| Outside the site boundary | The phone was further from the site than its boundary allows | GPS drift near the building, or a punch from elsewhere? |
| Not at any site | Nowhere near a site, and remote clock-in isn't allowed | Were they working somewhere else that day? |
| Away from the rostered site | Clocked in at a different site from the rostered one | Were they sent to another job? Move to a site if the shift belongs elsewhere |
| Clocked out at another site | The day ended inside a different site, and they didn't tap Move | Split at… to fix the day |
| Move cancelled | Tapped Move to next job, then Arrived back at the same job and project, so nothing changed | Information only: no travel line, no split |
| Ended while travelling | Clocked out while still travelling, and said they hadn't arrived at a job | Should the trip be paid? Set travel if needed |
| Long trip between jobs | A drive took much longer than its distance suggests | A detour, or a stop for supplies? Set travel to pay a set time |
| No location / Imprecise location | Location was off, refused or very rough | Ask them to allow precise location |
| Simulated location | The phone reported a faked location | Worth a conversation |
| Remote | Away from every site, where remote is allowed | Information only; not sent for review |
| Sent offline / Offline, time not verified / Offline, device clock disagreed / Sent more than a week late | Punched without a connection and sent later | The time used is the device's time since start-up, not its clock; check anything unusual |
| Arrived out of order | Punches reached the server in an odd order | Usually harmless after a long offline spell |
| New device / Revoked device | First punch from this device, or from one switched off | Is it their phone? |
| Forgot to clock out | The shift was closed automatically | Ask for their real finish (they can enter it from the Clock card) |
| Added by a manager | A missed shift added in Approvals | Who added it is in the Audit log |
| Times corrected | An accepted correction changed the times | The original punches are kept |
| Typed, not clocked | Hours typed while clocking in is required | Why wasn't it clocked? |
| Needs a work type | The project has work types but none was chosen | Ask them to add one |
| Late for rostered shift | Clocked in later than Late after | Did the roster change? |
| Left before rostered finish | Clocked out early by more than Late after | Agreed early finish? |
| Not rostered | Clocked in with no shift (only if that setting is on) | Casual pick-up, or a missing roster entry? |
Breaks and pay add these:
| Flag | What happened | What to check |
|---|---|---|
| No break recorded | A rostered unpaid break wasn't recorded and nobody answered at clock-out; paid in full | Did they take it? Set break if so |
| Worked through break | They said at clock-out they worked through it; paid | Confirm it, or Set break |
| Break shorter than rostered | A real break, but more than 5 minutes shorter than rostered; paid exactly | Break rules in their award? |
| Stayed past rostered finish | Paid as rostered, but clocked out later than Late after allows | Approve the extra with Set hours that count, or leave it |
| Break confirmed at clock-out | They said they took it; the break was recorded | Information only |
| Break set by a manager / Hours set by a manager | A manager changed it before approving | The reason is in the Audit log |
| Rostered break taken off | An older rule took the rostered break off automatically | Shown on entries from before How clocked time is paid |
Example: Jake's Monday shows Long trip between jobs: 95 minutes for a 12 km drive. He'd stopped at the tile supplier. Sam taps Set travel, enters 25 minutes with the reason Supplier stop, not a trip, and approves.