Time Tracking

The security officer clocks in and out for their assignment in the app. The server checks whether the submitted point is within the site's radius, then sets the status and timestamp.

At check-in, the time and coordinates are stored. At check-out, the location is checked, but only the time is stored. This is intentional: it does not create a movement profile, only a single event for each shift start.

Check-in is only possible from the status "accepted", and check-out only from "checked in". The server rejects any other sequence.

The radius is maintained at the site under Orders, Sites, field "Geofence radius (meters)". If nothing is entered, 200 meters applies.

The straight-line distance to the stored site point is measured. A point exactly on the radius still counts as inside. If the security officer is outside it, the clocking attempt is rejected with a notice and no timestamp is created.

Limit: The radius is between 50 and 2000 meters. If it is too small, check-ins fail due to poor GPS reception. If it is too large, the geofence loses its purpose. For most sites, 100 to 300 meters is practical.

If a security officer forgot to check out, the scheduling team enters the actual times afterward. Each row in the hours report has a "Correct times" action for this.

Both timestamps are required. Partial correction is not possible. The assignment is set to "completed" in the process.

A correction is rejected if the end is before the start, the period exceeds 24 hours, check-in is more than 12 hours before the planned start, or check-out is more than 12 hours after the planned end. Assignments with the status "not started", "rejected", or "completed" retain their status.

Missing clock events are detected continuously and appear within a few minutes in the notification center under the bell.

• Advance reminder to the security officer 60 minutes before the shift starts
• "Check-in missing" notification after the grace period, preset to 10 minutes after the shift starts
• "Check-out missing" notification 5 minutes after the shift ends

Nothing is automatically marked as a no-show. The decision remains with the scheduling team.

Configurable for each site: The site form has an Attendance check section. There, you can turn off the notification entirely for this site or set the grace period from 0 to 120 minutes. An empty field restores the 10 minutes. Orders without a site always retain the 10 minutes.

Limit: There is no separate lateness logic. A late check-in reduces the actual minutes but does not initially change billing, see Hours report.