The client couldn't find HR software built for the reality of a workforce deployed into fragile states. Off-the-shelf systems assume an office, a stable connection, and a staff member whose worst day is a payroll error. This workforce's worst day is an evacuation.
Built end to end over eighteen months: the full employee lifecycle for a distributed field workforce — profiles, timesheets, leave, expense and medical claims, performance, payroll data — plus a Safety module that is the point of the app.
A panic alarm that fires offline and delivers the moment connectivity returns. Movement-risk approvals routed through field security officers. Security-alert broadcasts with staff check-in and crisis-response monitoring. Geolocation and incident reporting.
Same discipline as the vision work elsewhere on this site, in a different domain: a system that has to be right in the field, under bad conditions, or someone gets hurt.
The published panic-alarm workflow uses a durable local queue, retries when connectivity returns and escalation mail after delivery. An offline device can capture the action; remote recipients can act only after it reaches them. That distinction is central to an honest status display and to the operating process around the app.
Movement-risk requests involve field security officers, warden assignment and risk categories. Security broadcasts connect to staff check-ins and crisis-response monitoring. These are different workflows: recording a request locally is not the same as receiving an approval or confirming a person's safety.
The scope covers architecture, implementation, store launch and handover over approximately eighteen months. The client team continues operating and updating the platform. It is not a published guarantee of delivery time under every connectivity condition, and the private client protocols are not disclosed here.
For a comparable field system, begin by defining which actions can be captured offline, how pending work becomes visible and who handles an exception. The offline-first mobile architecture guide turns these into review questions and device tests. The architecture review checklist helps collect evidence before selecting a build approach.