Field operations run on people and paperwork that live far from head office. Technology has to work with that reality, not assume it away.
Design for the connection you don’t have
A system built and tested in an office, on a stable connection, tends to assume one exists everywhere. Field sites often don’t have that luxury. A supervisor recording attendance or an incident needs to be able to capture it offline and trust that it will sync when a connection reappears, not lose the record or block their work until it does.
This changes what “simple” means for field-facing tools. The interface needs to work for someone on a phone in bright sunlight with gloves on, not for someone at a desk with two monitors. Fewer fields, clearer defaults, and a save that never silently fails.
Compliance that travels with the worker
Contractor certificates, permits and inductions expire on their own schedule, often while the person holding them is deployed somewhere without easy access to renew them. A system that only flags an expiry after it happens is already too late; the useful version flags it while there is still time to act, addressed to whoever is responsible for that person’s compliance, not just filed on a record nobody checks.
The same logic applies to site-based operational records more broadly: they are usually captured once, in the field, and then need to reconcile cleanly against office systems like payroll and finance without anyone re-typing them.
“The system that works in the office is not automatically the system that works on site. Design for the connection you don’t have, not the one you wish you had.”
