One system in production, described honestly.

A contracting company's payroll ran on a paper hazri register and a supervisor's memory. Attendance was routinely marked from the site office rather than at the gate, overtime was agreed after it had been worked, and every month-end produced the same argument: hours the company could not prove and the client would not pay for.

We rejected the usual framing. Most attendance software tries to stop the worker cheating; the real problem was that the record could not survive scrutiny weeks later. So we designed the punch to produce evidence — the person, the place, the time and a sealed record — and we made the system flag what it could not capture instead of discarding it. A worker whose photo failed still gets a record, marked as an exception for a human to resolve. Throwing that punch away would have deleted the proof that someone was on site.

• Offline-first mobile client, syncing when the site gets signal
• Photo capture, GPS reading and server-set timestamp at every punch
• Exception flagging rather than silent rejection
• Multi-tenant isolation — no company can see another's workforce
• Arabic and English, right-to-left throughout the interface
• Overtime authorisation ahead of payability, month-end lock, payroll exports

In production, not a pilot. The company closes the month on records that carry their own proof, and overtime is authorised before it becomes payable rather than argued about afterwards.

No figures are quoted here. We have not published numbers our customers have agreed to, and an unverifiable metric would be worth less than the sentence it replaced.