Check-in and Check-out Methods
You decide per property which methods your employees use to check in and out. Check-in and check-out can be configured separately — for example check-in via NFC, check-out via app button.
:::tip Security? → NFC Tag For security services, NFC tags are the standard. They are tamper-resistant (physical proximity required), work offline and cost under 1 euro per tag. See the industry recommendation below. :::
:::info Packages since October 2026 Since October 2026 you pick the method in the portal as a package in three groups: With the LiteLog app ("App: scan QR code", "App: tap NFC", "App: press button"), Without app ("Without app: web check-in") and Custom ("Custom selection"). Which method fits when, what the hardware costs, how LiteLog bills and which functions do not exist: Methods, Billing, Limits. :::
:::info Concrete use cases Who scans when, which screen appears, and what happens if someone scans in the wrong property: QR & NFC Use Cases. :::
Method comparison
| Method | How it works | Hardware / Setup | Speed | Tamper resistance | Offline | Recommended for |
|---|---|---|---|---|---|---|
| NFC tag | Hold smartphone against an NFC tag attached to the location | NFC tags (~€0.50 each) glued on site | under 1 sec | High — physical proximity required, no photo or location spoofing possible | Yes | Security (standard), cleaning, janitorial |
| Web check-in without app | The person scans a fixed QR code or NFC chip at the point with the phone camera, lands in the browser and enters their staff number. No account, no login. | QR poster or NFC chip at the point | 5-10 sec | Medium — the fixed code can be photographed; the staff number must be known at the property | Phone needs network | External companies, subcontractors, temporary staff without the app |
| Rotating code on a tablet (mode of the web check-in) | A tablet at the entrance shows a QR code that changes roughly every three minutes. The person scans it with their own phone and enters their staff number in the browser. | Tablet, room PC or display + Wi-Fi | 5-10 sec | High — a photographed code expires after a few minutes | Tablet and phone need network | Care (reception desk), schools, entrance areas |
| QR code (static) | Printed QR code at the location is scanned with the app camera | Printout (laminating recommended) | 2-3 sec | Low — code can be photographed | Yes | Low-friction attendance recording without high security requirements |
| Button click | Employee taps "Check in" / "Check out" in the app | None | Instant | Low — no on-site binding (unless the location check is active) | Yes | Field service, trust-based teams |
| NFC scanner device | A permanently installed Bluetooth NFC reader at the property reads the employee chip | External NFC scanner + paired device | 1-2 sec | High — the chip must be physically present | Device must be paired | Fixed entrances with high throughput |
| Beacon (Bluetooth) | During check-in/check-out the app automatically verifies Bluetooth proximity to a beacon mounted at the property | BLE beacon at the property (battery-powered) | Automatic during check-in/out | High — physical proximity proof, no GPS needed | Yes — the check runs locally | Additional on-site proof without GPS, e.g. basements, halls |
| Automatically via GPS zone | The app automatically checks the employee in as soon as they enter a zone with automatic check-in — only with the app active | Draw a zone with "Automatic check-in on entry" in the portal; the method is then enabled automatically | Automatic on entering | Location-based — multiple confirmations across several position reports | — | Properties with a drawn premises area; works in addition to QR and NFC |
| Manual check-in (Portal) | Supervisor checks an employee in or out from the portal | None | — | Audit-logged (with supervisor name) | — | Corrections, sickness coverage, forgotten check-ins |
:::info Beacon is a proof layer The beacon is not a check-in method of its own, but a proximity proof on top of the button, QR and NFC methods: the actual check-in/check-out still happens via button, QR or NFC — the beacon additionally proves physical presence. The range is configurable per property (default: 3 m); the beacon is bound in the LiteLog app. Details: Beacon Range. :::
:::info External NFC scanner As a special case LiteLog also supports external NFC readers paired via Bluetooth. These are only used in high-security environments (e.g. hospitals, military facilities). Contact your account manager if needed. :::
:::info "Automatic by zone" is not selected manually The method "Automatic by zone" does not appear as a selectable option in the method configuration: LiteLog enables it on the property automatically as soon as a zone with "Automatic check-in on entry" active exists, and removes it again once the last such zone is gone. It works in addition to the configured methods — including on properties that require QR or NFC scans. Automatic check-in and check-out is logged as the method "Automatic by zone". Details: Automatic check-in. :::
Industry recommendation
:::tip Which method for which industry?
Security services: NFC tags are the standard. The employee must be physically at the tag — no manipulation via photo, app spoofing or location fake is possible. Tags are cheap (under 1 euro per piece), work offline and need no power supply on site. Typical setup: one NFC tag per property or per guard point.
Cleaning: NFC tags per room or floor. Combined with routes you get a complete room-by-room proof of work. Alternatively a static QR code at the cleaning supply room.
Care services: Rotating code on a tablet at the reception desk or NFC per residential unit. Both options are GDPR-compliant and unobtrusive for residents. The tablet works for central entrances, NFC for decentralised areas.
Janitorial services: NFC per property — faster than the app button when visiting many sites per day. Employees do not need to actively open the app.
Field service / service technicians: App button with active location check (GPS zone). The system automatically checks whether the employee is on site at check-in (ONSITE/OFFSITE). :::
Allow exceptions
Per property you can enable the options "Allow exceptions on check-in" and "Allow exceptions on check-out" separately. When active, employees can also check in or out with a method that is not enabled — but they must enter a reason, which is stored in the log.
Typical use case: NFC tag is damaged → employee checks in via app button with a reason, supervisor sees the note in the log.
Where do I configure the methods?
Per property under Master Data → Properties → select a property → "Time Tracking". In the card row you switch the module off with the No time tracking card or pick a package: "App: scan QR code", "App: tap NFC", "App: press button" or "Without app: web check-in". For each package the page shows the next step (download QR code, bind and order chips, web check-in link) and the Location check row with switch and zone link. Only "Custom selection" opens the individual choice in three blocks: Check-in (In the app (button), NFC chip, QR code as multiple selection; plus web check-in, NFC scanner device and zone automation), Check-out (same as check-in or own methods) and Protection (location check Off / GPS zone / Beacon, exceptions, history).
→ Full guide: Time Tracking (Property)
:::warning Incompatible combination The app button cannot be combined with NFC chip or QR code. Ticking it in the custom selection replaces the on-site methods, and vice versa. Reason: the button does not enforce on-site presence and would defeat the other methods. Web check-in (its own switch), the NFC scanner device and the automatically enabled method "Automatically via GPS zone" are exempt: they can exist alongside either. :::
Where do I bind NFC tags to my property?
NFC tags are written in the mobile app and assigned to a property or control point. Procedure:
- Open the mobile app → "Admin" tab → NFC Reader
- Scan a blank NFC tag
- Link the tag to the desired property / control point
→ Detailed guide: Manage Control Points (Mobile)
Where do I set up a tablet at the entrance?
A tablet or screen at the entrance is set up as Rotating code on a tablet, a mode of the web check-in. In the property under "Time Tracking", pick the package "Without app: web check-in" (or switch on "Without app (web check-in)" in the custom selection), set the Web check-in link card to Rotating code on a tablet and click Create tablet code. Open screen shows the page with the QR code that changes roughly every three minutes; open the link on any tablet, room PC or display in a browser. Employees scan the code with their own phone and enter their staff number, without app and without login.
→ Guide: Time Tracking (Property)
The former kiosk (shift list with QR code, check-in with app login) is legacy and no longer offered for new setups: Kiosk Check-in.
Which QR code do I use for time tracking?
For time tracking there is one specific QR code per property — and the system contains other QR codes that do not work here. This is the most common mix-up.
- Time-tracking QR (the right one): Download it in the property — at the top of the property header via the "QR code" button. Print it (laminating recommended) and post it at the entrance. This code represents this property and checks in/out for work time.
- Control-point QR (NOT for time tracking): The QR code of a control point belongs to routes and is only for the route scan. If an employee scans it to check in or out, it fails — it points to a control point, not to the property's time-tracking tag.
- Web check-in QR: The QR code from the Web check-in link card (fixed code for posting or rotating code on a tablet). It is scanned with the phone camera, not with the app, and leads to the staff-number page. The rotating code is never printed.
In short: For time tracking, use the static time-tracking QR from the property's "QR code" button — not the control-point QR of the routes.
Why does the QR code not work?
If a scan is rejected during check-in/check-out, it is almost always one of these causes:
| Cause | Solution |
|---|---|
| Wrong QR — it is a control-point QR (route), not a time-tracking QR | Use the QR from the property's "QR code" button. |
| QR method not enabled — in the "Check-in / Check-out Method" accordion, "QR code" is not activated for check-in/check-out | Enable QR code as a method — or use "Allow exceptions" (with a reason). |
| Time tracking disabled for the property | Enable the feature in the property's "Time Tracking" tab. |
| Outside the time window / blocked — check-in only within the check-in window; a blocked time window rejects scans | Check the shift's check-in window and blocked time windows. |
| Location check (GPS zone) — with the active location check the scan must happen on site (ONSITE); OFFSITE is blocked | Scan directly at the property, with GPS/location permission active. |
| Rotating code on a tablet expired — the code changes roughly every three minutes; after the change the previous one is still accepted briefly | Scan the code currently displayed on the screen again. |
| Static QR regenerated — after regeneration the old printout is invalid | Print and post the new time-tracking QR. |
:::tip Quick test Does a QR fail for one employee but work for others? Then it is usually the method/permission or the location (OFFSITE). Does it fail for everyone? Then it is usually the wrong QR (control point instead of time tracking) or time tracking is disabled for the property. :::
Permissions
| Action | Permission |
|---|---|
| Configure methods per property | Edit properties |
| Bind NFC tag to property | Create control points |
| Create web check-in link and tablet code | Edit properties |