Engineers spend the day in basements and plant rooms. Any tool that assumes a connection is useless to them by ten in the morning.
Approach
Everything the engineer needs for the day is fetched at the depot and held locally. Reports written offline queue up and sync on reconnection, with conflict handling that favors the engineer on the ground.
Result
Paper job sheets are gone, and reporting that used to arrive a week late now lands the same evening.
Building for people who have no signal
Offline-first is a different discipline from a website that happens to cache. If an engineer opens the app in a basement at nine in the morning, everything needed for the day has to already be on the device, and everything written there has to survive until signal returns.
That forces decisions most web projects avoid. What happens when two people edit the same job. Whether the server or the person on site wins a conflict, which is a business question rather than a technical one. And how much of the day to fetch up front, since fetching too little strands the engineer and fetching too much makes the depot start slow.
Internal tools like this rarely need to be beautiful, but they do need to be fast and honest about state. That work sits under custom development rather than a website build, and it is quoted the same way, fixed against a written scope.
