Handle a dropped connection without duplicate records
Preserve the attempt, verify the result and retry only when needed.
A delayed screen can make it tempting to tap submit again or start on another device. Pause long enough to check what actually happened. The most useful distinction is between a draft still on the device and a signed record that the workspace can retrieve.
Mobile draft recovery helps with interruptions, but it should not be treated as a guarantee that a form completed entirely offline. Confirm the final state after connectivity returns.
Keep the current attempt available.
Leave the signing page open while checking the connection. Note whether the issue happened while loading, entering answers or submitting. Avoid clearing browser data or closing every tab as the first troubleshooting step, because that can remove context you still need to understand the attempt.
Check the workspace for the result.
Once connectivity is available, search Waivers with the participant details and review the signing time and template. If a completed record is present, use that record in the desk workflow. A missing confirmation screen on the guest’s phone does not necessarily mean the submission failed.
Retry the task after identifying the gap.
If no record exists, return to the appropriate form and follow any restored-draft or error instructions. Help the guest finish the required fields and wait for a clear success result. If the device remains unreliable, agree on a single fallback route and verify its final record before continuing.
Try it with a realistic visit.
During a desk rehearsal, discuss what staff should do if the guest’s phone loses connectivity just after submission. One colleague keeps the signing attempt available while another checks Waivers for the record. If the record appears, continue from that result. If it does not, restore the connection and review the form state before choosing one retry route.
The team should be able to distinguish a delayed response, an unfinished draft and a completed record. That distinction avoids duplicate attempts and contradictory instructions. Finish the rehearsal by finding the final record and explaining which confirmation the guest should use at check-in.
Several devices are affected at the venue.
Check the shared network and note when the problem started. Keep a simple record of affected tasks and escalate with the account owner. Do not report that the whole service is down based only on one venue connection or invent an estimated recovery time.
Can staff treat an unfinished draft as signed?
No. A draft is not a completed signed record. Confirm the successful signing result and the corresponding record before treating the paperwork step as finished.
A quick check before you go.