Mobile

The whole platform, in a pocket.

Clock in, book leave, snap a receipt and approve requests from a phone, because most of the people using HR software are not at a desk.

Capabilities

What works on a phone

Clock in and out with geofencing

For field teams and multi-site staff, with the location recorded so attendance is evidence rather than assertion.

Leave requests and balances

Check the balance and book time off in a few taps, with the request routing itself to the right approver.

Expense capture at the point of spend

Photograph the receipt when it is handed over, not three weeks later when it has faded in a wallet.

Approvals for managers on the move

Approve or query a request with enough context to decide, so travelling managers are not the bottleneck.

How it fits together

Designing for the people who are not at a desk

Desktop-first HR software quietly excludes the people it most needs to reach. A retail floor, a warehouse shift or a site crew has no desktop, so anything requiring one becomes a supervisor's job to collect and re-enter.

  • Capture at the moment
  • Approvals on the move
  • Works with poor connectivity
ON A PHONEClock in09:02Leave14 days leftExpensesReceipt readMost of the people using HR software are not at a desk.

Mobile

Most of your team is not at a desk

The mobile experience is the primary one for most employees rather than a reduced version of the real thing.

Booking leave and checking a payslip from a personal device

By the numbers

What it looks like in practice

Attendance data is only as good as its collection, and collection is only as good as how easy it is. Making the phone the primary surface is what keeps the data trustworthy.

Offline

Events queued, timestamp preserved

Geofenced

Clock-in where location matters

Primary

Not a reduced desktop view

Any role

Field, shift, manager, salaried

In practice

The same five minutes, on a phone

What each person does, and what it replaces.

  1. Clocking in at a gate

    A single tap with the location recorded, rather than a supervisor noting names on a sheet and re-entering them later.

  2. Photographing a receipt

    Captured when it is handed over, while it is legible, rather than three weeks later from a wallet.

  3. Checking a roster

    The published shift pattern on their own phone, rather than a printed sheet on a wall they are not standing next to.

  4. Booking leave

    The balance and the request in the same place, routed to the right approver without anyone being asked who that is.

  5. Approving on the move

    A manager between sites decides with enough context, which removes the most common bottleneck in any approval chain.

Compared

What each role does on a phone

The primary tasks, not a reduced feature set.

RoleDoesInstead of
Field employeeClocks in, submits a receiptTelling a supervisor to record it
Shift workerChecks the roster, requests a swapA note on a board
ManagerApproves leave and expensesWaiting until back at a desk
Salaried staffBooks leave, downloads a payslipEmailing HR

FAQ

Common questions

Does it work with an unreliable connection?

Yes. Actions are queued locally and submitted when the connection returns, keeping the original timestamp rather than the time of upload.

Do employees need an account to clock in?

Each employee has their own login, which is what makes the attendance record attributable and therefore usable as evidence.

Is geofencing required?

No. It is available where location matters, such as multi-site or field work, and can be left off for teams where it does not.

See it running on your own data.

We will show the module working against records that look like yours, not a generic demo.

Explore more

Attendance

Capture should take one action, and only exceptions should need explaining. Clock-ins, shift…

Employee Self Service

Payslips, leave balances, documents and requests, available to the employee directly instead of…

Expenses

Snap a receipt and the agent reads the amount, date and vendor. Policy decides the route.…