An internet interruption should not leave staff uncertain about how to record arrivals. Confirm the selected device’s actual behaviour and prepare an approved fallback.
A practical starting point
A terminal remains powered during a network interruption, but reception does not know when events will appear in the cloud or whether messages will be delayed.
Turn the idea into a working routine
- Ask the provider to demonstrate the configured device’s offline and recovery behaviour.
- Prepare a supervised fallback that records verified arrivals without creating uncontrolled duplicate lists.
- After recovery, reconcile pending events and communicate any necessary corrections through approved channels.
Measure what matters
Track the completeness of the reconciled register and the time taken to resolve pending events.
Assuming every device stores and synchronises events in the same way can lead to missing or duplicate records.
What should the team agree before putting this into practice?
Agree what staff should do during an interruption and who confirms the system has recovered before normal messaging resumes.
MAKE IT PRACTICAL
Your planning checklist
Use this checklist during a team discussion. It tracks your planning progress, not a score of your institution’s quality. Selections stay in this page and are not submitted.
A continuity plan starts with verified device capabilities.
About this archive: 22 May 2025 is the collection’s reference date. This article was prepared and published on 7 November 2026. It is AI-assisted editorial content; examples are illustrative and do not describe a specific customer deployment.
