Attendance Tracking FAQ

Find answers to common questions about scanning check-ins, resolving sync issues, and correcting attendance logs.

how-to Product: Attendance & Kiosk Engine Reviewed: Tue Sep 08 2026 03:00:00 GMT+0300 (Eastern European Summer Time)

Find answers to common questions about scanning check-ins, resolving sync issues, and correcting attendance logs.


What should I do if a member’s QR code fails to scan?

If a QR code on a member’s phone does not scan (due to a cracked screen or low brightness):

  1. Manual Search: Tap the Search Directory field at the top of the scanning screen.
  2. Type Name: Type the member’s name or household name.
  3. One-Tap Check-In: Tap their profile from the search results to mark them as attended instantly.
  4. Brightness Check: If using physical scanners, ensure the member’s device brightness is turned up to improve scanner recognition.

How can I correct an attendance mistake from a past service?

If you forgot to log attendance or made a mistake:

  1. Navigate to Attendance Logs in the admin dashboard.
  2. Select the specific service or event date from the calendar.
  3. Search for the member’s name on the roster sheet.
  4. Click the checkbox next to their name to toggle their status (Checked In vs Absent).
  5. The system saves the change instantly and updates the member’s engagement score overnight.

How long does it take for offline attendance data to sync to the server?

  • Immediate Detection: The PWA constantly monitors your network connection status.
  • Auto-Sync Trigger: As soon as your device reconnects to a stable cellular signal or Wi-Fi network, the background sync manager activates.
  • Sync Duration: The sync process usually completes within 10 to 30 seconds, uploading all cached check-in records to the parish database. A notification will confirm that all local logs are securely saved on the server.

Do attendance logs automatically trigger pastoral follow-up cases?

Yes, depending on parish settings:

  • The system checks attendance records during nightly processes.
  • If a member crosses your church’s consecutive absence threshold (for example, missing 3 consecutive Sundays), the system automatically flags their profile.
  • A pastoral care case is generated and assigned directly to the member’s family shepherd to coordinate a friendly follow-up.

Was this page helpful?

Let us know how we can improve Koinonia OS documentation.