The short version
If you need free time and attendance with solid anti-buddy-punching, Jibble is a good answer and costs nothing. If your arguments are about duration rather than presence, two points a day is not enough evidence.
Side by side
| Jibble | VisitsTracker | |
|---|---|---|
| When location is captured | At clock-in and clock-out | Continuously within your collection hours |
| Points per working day | Two | Roughly one a minute moving, one every five minutes still |
| Dwell / duration on site | Not available from GPS | Arrival, departure and duration per visit |
| Trail and auto clock-in together | Documented as one or the other | Both, by design |
| Offline entries | Recommended to disable | Queued with real times, uploaded in order |
| Mock-location detection | Face spoofing only | Location spoofing detected, marked, excluded |
| Identity at the punch | Face recognition, kiosk, NFC | Optional selfie |
| Free tier | Yes | No, 7-day trial without a card |
Where Jibble is the better choice
Genuinely free
A free core product, not a trial. For a small team watching every cost that is hard to argue with, and we have no equivalent.
Face recognition at the punch
Verification at every clock-in and clock-out, with face-spoofing prevention, plus kiosk mode with NFC tags for shared sites. That is a better answer to buddy punching than ours.
Many ways to clock in
Mobile, desktop, browser extension, shared kiosk, biometric. We are a phone in the field and a console in the office.
Breadth of language and market
Their site runs in around twenty languages. We are English only.
Where we are
GPS at the punch is two points a day
Jibble's own documentation says that when members clock in or out, GPS information is captured with their time entries. That is presence at two instants. It cannot show dwell, a route, the sites visited, or the distance travelled.
You do not have to choose between a trail and automatic visits
Their documentation states you can enable either live location tracking or geofence automation at one time, not both simultaneously. We do both, because the visit is derived from the trail rather than competing with it.
Offline is a normal condition, not a fraud vector
Jibble's own fraud-prevention checklist recommends disabling offline clock-ins to prevent false entries. We queue entries on the phone with the time they really happened and upload them in order. Basements, plant rooms and rural rounds are ordinary, not suspicious.
Their spoofing prevention is about faces, not locations
Jibble's spoofing controls address someone holding a photograph to the camera. That is a real problem and a different one. A mock-location app defeats a geofence by satisfying it, so the control ends up vouching for a false record.
Mileage that cannot be inflated
Distance is derived from trusted readings only, one claim per person per day, and a day under half a kilometre creates no claim rather than a wrong one.
Questions
Does Jibble track location continuously?
It has a live location tracking option, but its documentation says it cannot run at the same time as geofence automation. The GPS attached to a timesheet entry is captured at the punch.
Is Jibble's free plan enough?
For time and attendance on a small team, quite possibly. The question is what you can produce six months later when a customer disputes an hour, and two GPS points is a thin answer.
Which is better against buddy punching?
Jibble. Face recognition at every punch, plus kiosk and NFC modes, is a stronger identity control than our optional selfie. Our strength is what happens between the punches.
Can we export from Jibble into VisitsTracker?
Not directly. You would set us up alongside and run a week in parallel, which is what we recommend anyway: put it on one phone and compare what comes out.
The relevant product pages