A connection problem at arrival time should not leave employees guessing whether to keep scanning, send a message or tell a supervisor. A short fallback plan gives the team a clear response while the normal attendance workflow is unavailable.
When using ScanAttendance, confirm the connectivity requirements and any supported offline behavior for your actual plan and devices. Build the fallback around verified behavior rather than assuming a scan has been saved.
Define what counts as an unresolved check-in
Tell employees how to check whether an attendance action was recorded. If confirmation is missing, explain when to stop retrying and contact the designated administrator.
A phone camera reading a QR image does not by itself confirm that the attendance record reached the system. Use the product’s supported confirmation and record view, and test the situation before relying on a fallback procedure.
Choose one person to coordinate the response
Name an administrator and a backup. They should check the situation, tell employees which temporary process applies and decide when the normal routine can resume.
Avoid asking employees to invent separate attendance methods. If every person reports through a different channel, restoring the connection still leaves the administrator reconciling several competing records.
Use a controlled temporary record
If your company authorizes a temporary log, record the minimum information needed to investigate the affected attendance actions. Identify the date, employee, reported arrival or departure time and person receiving the report.
- Mark the log as temporary and awaiting review.
- Keep it in the approved private location.
- Identify which period was affected.
- Give the administrator responsibility for reconciliation.
This is a suggested internal continuity process. It is not a claim that ScanAttendance automatically imports a temporary log or approves replacement times.
Reconcile after service returns
Check the actual attendance records before adding or requesting any correction. A delayed action may already appear once connectivity is restored, depending on the supported setup. Treat an uncertain result as a question to resolve rather than a reason to create another entry immediately.
Compare each affected employee and date with the temporary record. Follow the authorized correction process for genuine gaps and communicate the reviewed outcome. Our missed-scan guide explains how to keep requests and approvals clear.
Practice a small, authorized test
Use a test account or an agreed pilot to walk through missing connectivity, absent confirmation and recovery. Do not disrupt the live workplace network just to test attendance. Ask support to clarify anything you cannot establish safely from the available settings and documentation.
Record what employees saw, what appeared in the attendance history and which administrative action was required. Add those observations to your administrator handover instructions.
Keep the fallback short enough to use
The useful version answers three questions: whom to contact, where to record an unresolved action and who checks it after recovery. Review the process when your plan, devices or workplace setup changes.
Start with ScanAttendance, review current plans or ask sales about connectivity requirements before your rollout.