Everything the console does, module by module.

Out of coverage the punch is written to the phone and syncs on its own — and the worker watches the state change, which is what stops the second punch.

A punch is only valid inside the site boundary, and the boundary is drawn per site.

A tag at the gate or on the vehicle, for workforces that do not all carry a smartphone.

A shared tablet at the entrance, or a printed code that rotates.

A bridge agent reads the ZKTeco, Hikvision or Suprema readers already on your walls.

The reduced working day applied automatically for the dates that apply to it.

Patterns built once and rolled forward, with coverage visible before the week starts.

Per person, per site, per project, and exportable in the shape your client invoices want.

A request rather than an edit, so the correction carries who asked and who approved.

The policy applied consistently instead of remembered differently by each supervisor.

Movement between sites recorded as it happens rather than reconstructed at month end.

What went over, where, and whether it was approved before it was worked.

Tolls pulled in and attributed to whoever was driving at the time.

Registration and insurance dates on the same expiry dashboard as the visas.

Every vehicle, its documents, and the cost carried against it.

Who has which vehicle, from when, with the condition recorded at each handover.

Licence class and expiry checked before an assignment rather than after an incident.

Matched to the driver on duty, with a dispute path that does not run through a spreadsheet.

Where the fleet is, and an alert when a vehicle leaves where it should be.

Harsh braking, speeding and idling — surfaced to a manager, never used to dock pay automatically.

The number that tells you whether a vehicle should be replaced.

Scheduled by distance or date, with the vehicle taken out of the assignment pool while it is in.

Shared vehicles requested through the same approval engine as everything else.

Entities, branches and cost centres, with data and approvals scoped to each.

Separation enforced by the database itself, not by a filter in the application that one missing clause would defeat.

One engine behind every request type, so a policy change is configured once.

Set right to left rather than flipped, in the app and in the documents it generates.

Documented, versioned, and the same API the app itself uses.

What a branch manager sees is a scope, not a screen someone remembered to hide.

Push, email and in-app, with the noise level set per person rather than per company.

Every view of a salary figure written to a log you can query.

Your data out in a shape you can use, without asking for it.

Bulk changes staged, validated and previewed before they are applied.

Modules toggled per company — which is what makes the pricing honest.