Designing a job form for patchy mobile reception
Plan saving, retries and image uploads for workers who cannot rely on a constant connection.
A field worker can complete a careful site report and lose it at the final submit button. The screen may look mobile friendly while the workflow still assumes a constant connection. Regional work makes that assumption especially worth questioning.
Before choosing an offline feature, find out where the form is used. Is reception absent for a whole shift, or does it briefly drop during travel between jobs? Are devices shared? Do workers attach large photographs? Each answer changes the design.
Show what has actually been saved
Distinguish a draft on the device from a report received by the office. Use plain status messages such as “Saved on this device” and “Sent to the office”. A reassuring tick with no explanation can leave both sides believing something different.
Let the worker resume a draft without re-entering routine details. When a submission is retried, the system should recognise the same report instead of creating another job. Test this by interrupting the connection at the moment the worker presses submit.
Give photographs their own recovery path
Uploading six full-size images can take longer than sending the form itself. Show progress and explain whether it is safe to leave the page. If one image fails, preserve the text and successful uploads. Staff need to know whether a report is complete or still waiting for attachments.
Local device storage also introduces risk. A lost or shared phone should not expose customer details indefinitely. Agree what is saved, for how long and what the worker can do before handing a device to someone else. Sensitive field work may require a different approach.
Try a real working day
Acceptance should include the phones, routes and gloves or site conditions that matter to your team. A desktop browser with its network switched off is a useful development test, but it does not establish that the workflow works on a regional visit.
MDN's explanation of offline web operation gives technical background for your developer. Our field tools service turns the practical decisions into a testable first release.