Connectivity problems may affect recognition, recording and parent messaging differently. The exact behavior depends on the installation architecture. Instead of assuming every function works offline, identify which steps require connectivity in your institution’s setup.
1. Locate the interruption
Is the tablet disconnected, is the institution’s internet unavailable, or is only one service affected? Note the error and event time. Staff should check other devices on the same network. A working camera view does not by itself prove that an event reached the server.
2. Verify offline capabilities in advance
Ask the provider how recognition, event creation and later transfer behave without connectivity. If local recording is supported, clarify the device, duration and conditions. Discuss the scope of your BE Soft installation with support. Do not build continuity plans around unverified features.
3. Use a controlled temporary register
If system recording cannot be confirmed, authorized staff should use the institution’s temporary attendance method. Clearly record student identity, event type and time. Do not distribute these records casually. Check notifications separately rather than assuming parents received messages.
4. Reconcile after connectivity returns
Compare system events with staff records individually. Verify any automatic transfer; otherwise use the approved correction method. Avoid recording the same entry twice. If delayed messages are sent, ensure wording distinguishes the original event time from the sending time.
5. Test the plan outside normal operations
Observe device and record behavior in a controlled trial recommended by the provider without disrupting arrivals. Random network changes or shutting down the system during peak hours are unsuitable tests. Identify responsible staff, support contacts and daily checks.
Plan continuity for your installation
Backup connectivity alone does not complete preparation. Record verification and notification checks also matter. Discuss connection requirements and a practical staff workflow with BE Soft.