Per-site radius
Default 50 metres. Tighten to 20m for a small office. Loosen to 200m for a quarry or campus. Set once per site, per geofence — no global guesswork.
Loading…
Mobile attendance
HelloTime is a GPS attendance app and geofence time tracking system built for field teams. Use it as construction attendance software or a security agency attendance app — with mock-location detection, offline clock-in and server-side fence enforcement.
On Android, HelloTime reads the system isFromMockProvider flag and routes spoofed fixes to the manager-review queue instead of payroll. iOS does not expose a mock-location flag, so the server runs a physics check — impossible velocity, teleport jumps — on the raw fix before it ever counts as a clock event.
Define each site once
Admin adds a site with latitude, longitude, address, timezone and a radius. The default radius is 50 metres; managers can dial it tighter for a small office or wider for a sprawling campus, per site. For irregular sites — industrial estates, multi-building campuses, narrow alleys — HelloTime also accepts a GeoJSON polygon instead of a circle.
Workers get a clock-in prompt at the gate
Crossing into a site geofence fires a transition event on the worker's phone. HelloTime pops a 'clock-in available at <site>' prompt — no continuous polling, no battery drain.
Server validates every clock event
Phones lie. Every clock event is re-validated on the server against the device-reported coordinates and the site's lat/lng/radius. Out-of-fence events are rejected before they reach payroll.
Mock-location detection on Android
On Android, HelloTime checks the system's `isFromMockProvider` flag. Spoofed locations from fake-GPS apps are flagged and routed to the manager-review queue instead of becoming a payable hour.
GPS is messy. HelloTime treats the messiness as a managed input, not as the worker's problem.
Default 50 metres. Tighten to 20m for a small office. Loosen to 200m for a quarry or campus. Set once per site, per geofence — no global guesswork.
HelloTime treats first-fix accuracy as advisory and re-checks on a brief settle window. Workers don't get blocked because GPS landed 15m off in a tunnel of buildings.
Geofence enforcement falls back to the kiosk path: where GPS is unreliable, the site's tablet kiosk handles the clock-in and the geofence check is skipped server-side for that device.
Every clock event stores the lat/lng/accuracy that produced it, plus the site it was matched to. Disputes get resolved with data, not memory.
Uses the OS-level Geofence API for transition events — battery-friendly, no foreground polling. Mock-location detection is on by default.
Uses Core Location's region monitoring for the same transition-event model. iOS does not expose a mock-location flag, so server-side validation does the lifting.
Both platforms write events through the same gRPC pipeline. The server is the source of truth — no client-only trust, no payable hour without a server-side fence match.
Lost connectivity at site is normal. HelloTime queues the clock event in SQLite and syncs the moment the phone reconnects. Idempotency keys (deviceId + localTimestamp) prevent duplicate writes.
Geofencing tells you who clocked in at which site. For travelling field crews — service techs, sales reps, delivery drivers — HelloTime adds a live map and a team heatmap on top of the same GPS stream that powers mileage tracking. No separate tracking vendor on the worker's phone.
Once a worker starts a trip in the mobile app, HelloTime streams GPS fixes back to the server through an AppendMileageGpsPoint streaming gRPC. Managers see the field team on a live map in the web console — no separate tracking vendor, no second app on the worker's phone.
Every trip ends as a polyline on the worker's own timesheet with start and end markers. The manager console rolls trips up into a team heatmap so you can see where field staff spent time over a week or month — useful for territory coverage and route review.
Managers see the whole field team on one map — real-time GPS fixes, trip polylines and site markers. No separate tracking app.
HelloTime ships a sensible default and lets managers dial it per site — no support ticket needed. Customers report Truein's per-site geofence configuration as one of its rougher edges.
Fake-GPS apps are a rampant deskless attendance fraud. HelloTime checks `isFromMockProvider` on Android out of the box and routes flagged events to the manager queue.
Phones use OS geofence transitions. Kiosks use the site they're paired to. Web admin sees the same event log. One pipeline, one source of truth.
Hubstaff's GPS module was designed for travelling sales reps; geofences are coarse and the workflow is built around tracked time, not gated clock-in. HelloTime's geofence is the gate.
HelloTime rejects out-of-fence clock events at the server. Hubstaff customers report users still getting time logged even outside the assigned area, leaving payroll to clean up.
Geofence attendance is part of HelloTime's published Attend SKU at ₹99 promo / ₹199 list — half the cost of Hubstaff's Field plan. Tickets answered in IST. GST invoicing in HelloBooks.
Site-based crews, multi-branch operations, field service teams. Geofencing pairs with face recognition and the tablet kiosk so the same worker can clock in from a phone at the gate or a tablet on the wall — and end up on one timesheet.
Construction & site teams
Per-site geofence with 50m default.
Manufacturing & factories
Plant-perimeter geofence, mock-location flags.
Retail chains
One geofence per store, central roll-up.
Security agencies
Rotating posts, server-side fence enforcement.
Facility & cleaning services
Multi-client routes, geofence per stop.
Face-recognition attendance
Geofence + face = no buddy-punching.
Tablet kiosk mode
Tablet on site for indoor / no-GPS shops.
HelloBooks payroll
Geofence-validated hours flow to payroll.
All HelloTime features
Browse the full feature index.
Best attendance app in India
Compare top attendance apps for Indian teams.
Face recognition attendance
Add face verification to every clock-in.
Kiosk mode
Wall-mounted tablet clock-in for sites.
Construction
Site attendance software for builders.
Security agencies
Guard-post attendance and patrol tracking.
Pricing
Transparent plans for teams of any size.
FAQ
A GPS attendance app uses the worker's phone location to verify they are at the assigned site when they clock in or out. HelloTime combines GPS coordinates, geofences and server-side validation so hours are tied to real on-site presence.
An admin draws a circle or polygon around each site. When a worker crosses the boundary, the phone fires a transition event. HelloTime prompts them to clock in and validates the coordinates on the server before recording the time.
On Android, HelloTime checks the system isFromMockProvider flag and sends spoofed GPS events to a manager-review queue instead of payroll. On iOS, server-side physics checks flag impossible velocity or teleport jumps.
Yes. If the site has poor connectivity, HelloTime queues the clock event in local SQLite and syncs it when the phone reconnects. Idempotency keys prevent duplicate punches.
The default is 50 metres per site, but managers can tighten it to 20 m for small offices or widen it to 200 m for large campuses, quarries or construction yards. Irregular sites can use a GeoJSON polygon instead of a circle.
Yes. Construction crews get per-site geofences that match moving yards and multi-gate sites. Security agencies use guard-post geofences, rotating posts and patrol routes; flagged events go to a supervisor queue.
Yes. HelloTime works as both construction attendance software and a security agency attendance app, combining GPS geofencing, face recognition (early-access pilot), kiosk mode and an offline queue in one system.
Free forever for 1 user. No credit card. Paid from £2.99/seat, billed monthly.