Decide what a field draft must survive
“Works offline” is not a complete requirement. A report might remain visible in an open tab yet disappear after the browser is closed. It might survive a restart but still be unavailable to the office. The scope needs to name the interruption and the information at risk.
This fictional review concerns a field note for visit V-26. The organization permits the relevant text to remain on an approved device, but customer attachments are outside the first offline scope.
Separate three observations
The colleague writes a note while the connection is unavailable. The prototype shows “Saved.” The reviewer then checks three different boundaries:
| Boundary | Initial fictional result |
|---|---|
| Move between sections in the same open page | Note remains visible |
| Close and reopen the browser | Note is gone |
| Open the office view | No report received |
The prototype stored the text only in the page’s current memory. The label implied more persistence than the implementation provided. Neither the visible text nor the word “saved” established office receipt.
Choose the needed persistence deliberately
The field team confirms that an interruption can outlast one browser session. A retained text draft therefore belongs in scope. The organization’s information owner approves the specific data and device conditions for that feature.
The fictional implementation stores a draft associated with the user, visit and instruction version through the application’s supported local-storage design. The interface says “Draft on this device — not sent.” Submission has its own state and receiving confirmation.
This choice does not include every possible device failure. Losing the device, clearing browser data and signing out need explicit behavior and instructions. If the organization cannot accept local retention, the alternative is an online-only task with a different operational fallback.
Rehearse the boundaries again
The reviewer writes a new V-26 draft, closes the browser and reopens the application under the intended account. The draft returns with its unsent label. The office still shows no received report.
After reconnecting, the colleague submits. The office opens the complete report against V-26, and the device marks it received according to the application’s confirmation rule. A second draft for V-27 remains separate and unsent.
The test then uses the agreed sign-out behavior. In this fictional scope, sign-out warns about unsent work and requires the user to resolve or deliberately discard it before the local session is cleared. A different user does not inherit the draft.
Preserve the instruction relationship
The draft records which instruction was visible when it was written. If the office has revised that instruction before submission, the application asks for the agreed review rather than treating the old draft as evidence that the new instruction was followed.
This boundary deserves a separate test; successful local persistence does not resolve competing office changes.
The scope record now states what survives a browser restart, what remains only on the device and what establishes office receipt. It lists excluded attachments and device-loss limits. Office and field tool development can use that record to estimate a concrete capability instead of an undefined offline promise.
