Clock-in/out Tagging

Add Clock-in/out tags to a shift timeline

For shift work, the clock-in/out actions by the worker determine when the shift starts and ends. Tracking the location and time of these actions is therefore important to confirm the shift started and ended at the expected location and time and establish proof of work.

HyperTrack makes it very easy for you to add clock-in/out tags to a shift timeline. You can do this by creating geotags associated with the relevant HyperTrack order_handle which is the unique shift identifier like a unique shift_id for instance.

To add clock-in/out tags to order timeline you have to call the addGeotag(order_handle, order_status, metadata) SDK method from your worker app. The doc links are shared below:

• iOS, Android, React Native, Flutter, Ionic Capacitor, Cordova, Web

Please see this code example on how to send the clock in tag for a shift at Gotham city hospital:

// create new geotag metadata payload
val payload = mutableMapOf<String, Any>()

// add event details from the example above
payload["facility"] = "Gotham city hospital"

// add order handle
val orderHandle = "!!Use your unique shift id !!"

// add order status ClockIn
val orderStatus = OrderStatus.ClockIn

HyperTrack.addGeotag(orderHandle, orderStatus, payload, expectedLocation);

The clock-in/out geotags serve as an additional data point to the existing order timeline events (such as arrival to, or an exit from, an order's destination).

🚧

Clock-in/out geotags are created in your worker app through the HyperTrack SDK.

📘

If your worker's device is temporarily disconnected due to a network loss, order geotags generated by your workers will be captured offline and sent to HyperTrack once connection is restored.

Timeline Annotations

Clock-in and Clock-out tags are annotated in the order timeline. Our Geotags feature can be used in conjunction with a Proof of Work order to add custom annotations or events to the order timeline by populating the order_handle metadata field in the Geotag.