Find your fit
Who it is for
The vendor targets teams working on site, in the field, remotely or in hybrid arrangements. A shared kiosk or mobile clock can suit a worksite, while web and desktop clocking fit computer-based teams. Choose only the clock methods your workers actually need.
Managers responsible for reviewing a pay period can compare time entries and calculated payroll hours before approval. Employees can see their own timesheets; access to team timesheets is limited to permitted owners, admins and managers.
The work it supports
Core capabilities
Workers can clock in and out through web, mobile or desktop apps, a shared kiosk, a Chrome extension, or Slack and Teams. Jibble assembles the resulting events into timesheets. Test one normal shift and a missed punch with your chosen device path before inviting everyone.
Team timesheets have daily, weekly and monthly views, while individual users can inspect their own entries. The detailed view separates tracked hours from payroll hours; an edit to payroll hours without changing an entry requires a reason. Compare a sample overtime week to your expected calculations.
Pay periods can run monthly, twice a month, every two weeks or weekly. After a period ends, a permitted manager can approve and lock its timesheet, then reopen it if correction is needed. The help page warns that changing the pay-period cycle permanently deletes prior pay-period data, so decide that cycle before relying on historical records.
Owners, admins and managers can export timesheets on all plans as CSV or XLS, with date and member filters. Review raw entries and totals before handing the file to payroll; an export still needs to be reconciled in the employer’s own pay process.
Owners and admins can set device restrictions, time tracking rules and reminders. Mobile and desktop apps can capture clock events offline. A short test with a reconnect and a manual correction is useful before relying on the data for pay-period approval.
Optional verification includes GPS location, geofencing and face recognition. GPS capture is a mobile setting that requests location permission and attaches a location to clock events. Face verification can be used for a shared kiosk or individual time entries; the vendor says face data and clock-in photos are involved. Review employee notice, consent, retention and local requirements before turning on either option.
Jibble also describes optional desktop screenshot capture. It requires desktop-app permission and has configurable storage settings. Decide whether this data is necessary for the timekeeping use case and test what managers can actually see.
Understand the offer
Pricing and getting started
Jibble advertises a free-forever plan for unlimited users, and its free-plan help page mentions clocking, timesheets, GPS, face recognition, leave and exports. Verify the exact current limits in a trial account before counting on a particular advanced control.
New signups begin with a 14-day trial. The help page says entering payment details during the trial does not charge until it ends, so check the selected plan and end date before adding a card. The English pricing links redirected to Jibble’s homepage during this research, leaving paid rates unverified.
Upgraded plans are billed per seat upfront. A user consumes a seat when added, even without accepting an invitation, and the owner also consumes one; separate organizations are billed separately. Count actual people and organizations when estimating a paid plan.
Added seats are prorated and charged during a billing period, while reducing seats takes effect at renewal. Plans auto-renew unless cancelled. Jibble labels the dollar figures in its help examples as sample amounts, so request a live account quote instead of treating those examples as current rates.
Look a little closer
Before you choose
Pilot one pay cycle with test users: clock a normal shift, a break, an offline event and a corrected entry; then compare personal/team timesheets, approval status and the exported CSV/XLS file with your payroll process.
Set the pay-period cadence before collecting live history. The vendor’s warning about permanent deletion when that cycle changes warrants an export and a deliberate administrator review before any later edit.
For a location or biometric rollout, confirm the chosen plan and device support, then document what is captured, who sees it and when it is deleted. A basic clock workflow can be evaluated without enabling these optional controls.
10 distinct sources behind this profile. Research observed Oct 18, 2026. Features and offers can change.
View sources and research →
