Skip to main content
LLMs.md

QR & NFC Use Cases

This page describes the typical situations in which employees scan a QR code or NFC chip with the LiteLog app — and what the app does in each case.

Which method is enabled for which situation is configured per property. For a method-by-method comparison, see Login Methods.

Why scan instead of tap?​

Behind the scenarios on this page is one simple promise: employees always check in at the right property, with minimal effort, and leave a verifiable on-site record. That solves several problems of manual check-in at once:

Fewer human errors​

  • Always the correct property: the NFC chip or QR code is the property — there is no list to pick the wrong one from.
  • No accidental wrong-property check-in: if an employee scans the wrong property, the app switches automatically as long as they are authorized (Scenario 8).
  • Check-ins are forgotten less often: the chip at the entrance is a physical anchor in the daily routine — employees notice it more reliably than an app icon.
  • Less correction work for dispatch: wrong or missing check-ins are the single largest source of back-office cleanup. Scan-based check-in cuts that workload noticeably.

Tamper resistance​

  • Physical presence required: an NFC chip can only be scanned with the phone less than 2 cm away. Check-in from home or from the car is out.
  • No buddy-punching: while the chip itself can be handed off, the phone cannot — and the phone is tied to a person.
  • No photo spoof: static QR codes can be photographed. NFC chips cannot be replicated remotely.
  • Tamper-proof contents: LiteLog writes chips as read-only — the content cannot be modified after the initial write.

Verifiable evidence​

  • On-site proof with the real timestamp: every scan is stored with its original time — even when the phone was offline. The portal shows the scan time, not the upload time.
  • Strong in disputes: cleaning, security and care services are routinely asked for solid attendance records. NFC logs are far more convincing than spreadsheets or location pings.
  • Complete tour coverage: for guard tours, the app can enforce checkpoint order — short-cut tours are no longer possible.
  • GDPR-friendly: compared to pure location tracking, NFC stores only the scan time and the scanned property — no continuous location trail.

Faster day-to-day​

  • One second instead of three taps: tap the chip and you're done. No app opening, no property picking, no confirmation.
  • On Android often without launching the app: the phone detects LiteLog chips in the background and opens the correct action automatically.
  • Works offline: in basements, dead zones, or overnight at remote sites — the scan is queued and synced later.
  • Self-explanatory: anyone who can use a smartphone can use LiteLog without training.

Economics​

  • NFC chips cost under 1 € each, are passive (no battery) and last essentially forever.
  • Less back-office work thanks to clean data — payroll runs smoother.
  • A stronger position with clients thanks to verifiable reports (cleaning, security, care).

:::tip Bottom line Every scan prevents three sources of error at once: the wrong property, an inaccurate time, and the "was the employee really there?" question. That's exactly what the scan workflow is built for. :::

:::tip Background vs. active scanning On Android the app detects NFC chips automatically in the background — the employee does not need to open the app. Apple's security model is stricter on iOS: there the employee swipes left in the app to start the NFC reader. :::

Block A — Sign in to the app​

Scenario 1 — First sign-in with a QR code​

For whom: A new employee whose phone is not yet set up in the app. When to use: First sign-in or new device.

How it works:

  1. Manager opens the employee card in the portal and shows the login QR.
  2. Employee installs the LiteLog app and taps "Scan QR code" on the sign-in screen.
  3. Employee points the camera at the QR code.
  4. The app shows "Signing in..." for a few seconds and then opens the most recently used property — or the property selection if the employee is not yet assigned to one.

Troubleshooting:

  • QR code expired → manager generates a new one in the portal.
  • App says "Code invalid" → scan again; a QR code can be used as often as needed until it is revoked.

Scenario 2 — First sign-in with an NFC chip​

For whom: Employees who receive a prepared NFC chip (e.g. a staff tag). When to use: First sign-in in industries that issue chips (security, cleaning).

How it works:

  1. Employee opens the app and taps "Scan NFC chip" on the sign-in screen (optional on Android — the chip is detected automatically).
  2. Employee holds the chip against the back of the phone.
  3. App signs in automatically and shows the assigned property.

Troubleshooting:

  • App does not react → wait 1–2 seconds, the chip must lie flat against the back of the device.
  • For iPhones with a case, hold the chip closer to the top edge.

Re-login​

After a logout, both methods work identically to the initial sign-in. The app remembers the last used property and opens it automatically as long as the employee is still assigned there.

Block B — Tracking work time​

Scenario 3 — Start work time with a QR code​

For whom: An employee who signs in at the workplace using a laminated QR poster or a kiosk display. When to use: Locations that do not have NFC chips installed.

How it works:

  1. Employee opens the app and taps "Scan QR code".
  2. Point the camera at the QR code.
  3. App confirms the check-in and shows the running session.

Scenario 4 — Start work time with a button click​

For whom: Field service, technicians, remote sites without chip or QR poster. When to use: When no on-site binding is required, or when location verification (geofencing) is already enabled.

How it works:

  1. Employee opens the app.
  2. Taps "Sign in".
  3. App starts the session immediately.

Scenario 5 — Start work time with an NFC chip​

For whom: Security, cleaning, caretaker services — industries with NFC chips installed at the location. When to use: When tamper-proof on-site presence verification is required.

How it works:

  1. Employee holds the phone against the NFC chip at the entrance.
  2. App signs in to the work session automatically.

Scenario 9 — Sign out by re-scanning or re-tapping (toggle)​

While a session is open, scanning or tapping again ends the session — regardless of which method started it.

How it works:

  1. At the end of the shift the employee scans the same QR code/chip — or taps "Sign out".
  2. App closes the running session and shows the total duration.

Scenario 10 — Pause and resume by scanning​

Within an active session a pause can be inserted by scanning again. A subsequent scan resumes the work time.

How it works:

  1. While the session is running, the employee scans again → app asks "Start break?" and creates a pause entry.
  2. On return the employee scans once more → app resumes the work time.
  3. The pause appears separately in the log and reduces productive working time, but not on-site presence time.

:::info Which method when? The industry-by-industry recommendation lives on Login Methods → Industry recommendation. :::

Block C — Checkpoints (Guard tours)​

Scenario 6 — Checkpoint via QR code​

For whom: A guard on a tour, in an industry without installed NFC chips.

How it works:

  1. Employee starts the tour in the portal or app.
  2. At each checkpoint, scans the posted QR code.
  3. App confirms with a notice and points to the next checkpoint.
  4. At the end the employee finishes the tour.

Scenario 7 — Checkpoint via NFC chip​

For whom: Guards in industries with NFC chips installed at each checkpoint.

How it works: Identical to scenario 6, except the employee holds the phone against the NFC chip mounted at the checkpoint instead of scanning a QR poster.

:::tip Enforced order If the tour is configured with "Enforce order", the app accepts only the next due checkpoint. An out-of-order scan is rejected with a notice. :::

Block D — Special cases​

Scenario 8 — Accidental scan in the wrong property​

When an employee scans a chip or QR code from a property other than the active one, the app automatically checks whether they have access to that other property.

If they have access: The app silently switches to the correct property and runs the scan there. A short notice "Please choose the correct property" is shown.

If they do not have access: The app shows a notice, ends the running session and returns to property selection. The employee then signs in again at the original or another permitted property.

Special case — administration screens: On screens such as "NFC Reader", "Manage Checkpoints" or "Manage Access Cards", the automatic property switch is disabled. There the app only identifies the chip; nothing else happens.

Scenario 11 — Scanning without internet (offline mode)​

How it works:

  1. Employee scans a known chip or QR code.
  2. App recognizes the chip even without a connection because property and checkpoint data are stored locally.
  3. The sign-in, checkpoint scan or sign-out is saved locally and is automatically uploaded to the portal as soon as the device is online again.
  4. In the portal the entry appears with the original scan timestamp, not the upload time.

Prerequisite: The employee must have signed in online at least once before, so that the app could download the property data.

Scenario 12 — Unknown chip or code​

If a chip or QR code is scanned that is not registered locally or in the portal (for example a foreign NFC chip or an expired login QR), the app shows the notice "Tag not found" and returns to the previous screen automatically. No unintended action is triggered.

Scenario 13 — Wrong chip type for the current task​

Example: the employee is on an active tour and accidentally holds a work-time chip against the phone — or vice versa. In this case the app silently ignores the scan; the running task is not interrupted.

This makes it possible to deploy work-time chips and checkpoint chips side by side at the same location without the two functions triggering each other.

Block E — Setting up chips and cards​

Scenario 14 — Bind a new NFC chip to a property or checkpoint​

For whom: Manager or property lead with the "Create checkpoints" permission.

How it works:

  1. Open the mobile app → "Admin" tab → "NFC Reader" or "Manage Checkpoints".
  2. Choose "New chip" and pick the target property or checkpoint.
  3. Hold an empty NFC chip against the back of the phone.
  4. The app goes through two phases:
    • Phase 1 — Waiting: Phone is searching for a chip. The device may still be moved.
    • Phase 2 — Writing: As soon as the chip is detected, the screen switches to "Please do not move". During this phase the chip must stay in the field.
  5. App confirms the successful write and registers the chip on the server.

Troubleshooting:

  • "Chip already assigned" → the chip was previously linked to another property. Choose "Overwrite" if intended.
  • Write canceled → let the chip rest for a moment and try again.

Scenario 15 — Employee access card​

In high-security or shift-heavy operations, individual employees can be issued a personal NFC access card. When scanned, the app identifies the employee without starting a work session or recording a checkpoint.

Typical uses:

  • Shift handover at a guard post: the incoming guard scans their card on the outgoing guard's phone.
  • Re-login after a session has expired, without having to scan the login QR again.

Access cards are managed under Mobile app → Admin → Manage Access Cards.