Time Tracking (Property)
On this page you define how your team clocks in and out at this property. You switch time tracking on or off for the property, pick a package (with the LiteLog app, without app or as a custom selection), complete the matching next step and decide whether LiteLog checks the location when someone clocks in.
Navigation: Master Data → Properties → select a property → panel entry "Time Tracking" (group "Features")
What Is This Page For?
The page answers one question: How does my team clock in and out at this property? Everything else around time tracking deliberately lives elsewhere:
- You analyse the recorded work times under Work Times.
- Shifts and series of this property are planned under Time → Operations planning; the Operations planning link at the bottom of the page opens that list with the property filter set.
- The time rules (auto-end, start times, blocked periods, breaks, visit gap) apply as company defaults under Settings → Time rules; deviations per property are maintained in the property settings, section Rules. The Time defaults link at the bottom of the page leads to the clocking method for all properties. The rules are described further down.
Page Layout
From top to bottom:
- Header with the buttons Operations planning (shifts and series of this property) and Time defaults (clocking method and time rules for all properties), the help button, the Shop button (cards, NFC chips and beacons for time tracking) and, as soon as you have changed something, the Save button.
- Card row: first the card No time tracking, then five packages in three groups. Exactly one card is selected.
- Next step for the selected package, always followed by the Location check row.
- With Custom selection, the three blocks Check-in, Check-out and Protection replace the next step.
- The Points card with the property's clocking points, shown as soon as QR code or NFC is selected as a method or web check-in is switched on.
No time tracking
The first card in the row, in the Off column, switches the module off for this property. When selected, LiteLog accepts no booking at this property and the page shows neither a next step nor a method list. When the module is on, employees see time tracking at this property in the app.
- Switch off: click the card No time tracking. Existing bookings are kept.
- Switch on: click any package or Custom selection. LiteLog switches the module on and applies the chosen package in one step.
- The card saves immediately, without Save.
Choose a package
The card row shows the five packages in three groups. A package is a complete state: it sets the same methods for check-in and check-out, switches exceptions off and turns web check-in on or off. Clicking a card selects it; the choice is applied only when you click Save.
| Group | Package | What it sets |
|---|---|---|
| With the LiteLog app | App: scan QR code | Check-in and check-out via a QR code you post at the property. The app scans it. |
| With the LiteLog app | App: tap NFC | Check-in and check-out via an NFC chip at the property. The phone is held to the chip. |
| With the LiteLog app | App: press button | Check-in and check-out via a button in the app, without scanning. Only the location check proves that someone was on site. |
| Without app | Without app: web check-in | The person scans a QR code or NFC chip with the phone camera, lands in the browser and enters their staff number. No app, no account, no login. Web check-in is switched on; app users at the same property use the button. |
| Custom | Custom selection | Opens the three blocks Check-in, Check-out and Protection. Here you combine methods, separate check-out from check-in, allow exceptions or choose beacon as the location check. |
Below each card, Watch in the video jumps to the matching scene of the explainer film. Which package fits when, what the hardware costs and which limits exist is described under Methods, Billing, Limits.
:::info How LiteLog recognises the package The row always shows the package that matches the saved state. If the state matches no package (for example check-out differs from check-in, exceptions are allowed or several methods are combined), the row shows Custom selection. Zone automation and the NFC scanner device do not count here; both are kept when you switch packages. :::
Next step
Below the card row, each package shows the one thing that is still missing. The Location check row always comes last.
App: scan QR code
The Download QR code button opens the download dialog for this property's time-tracking QR code. Print it (laminating recommended) and post it at the property; the app scans it to clock in and out. If the property has no clocking point yet, the first click creates it and then opens the dialog.
App: tap NFC
The chip is bound to the property in the LiteLog app: Manage → Connect NFC → Start time tracking → Select time tracking point → Scan chip. The Order chips button opens the matching selection in the LiteLog shop.
Without app: web check-in
Here the Web check-in link card appears. It belongs to the property's one clocking point and has two modes, chosen in the Type of code field at the top of the card. Both modes can be created and removed independently; changes to the card are saved immediately.
Fixed code to post. The link stays the same. You post it as a QR code at the property or write it to an NFC chip. When you switch to this package, LiteLog creates the fixed link once automatically.
- Copy link for the NFC chip or to pass on.
- Download QR code as PNG for posting.
- regenerate invalidates the previous link; posters and chips then have to be replaced.
- remove deletes the link; old posters then show "This link is no longer active".
Changing code on a tablet. A tablet or screen at the entrance shows a QR code that changes roughly every three minutes. The person scans it with their own phone and lands on the same staff-number page as with the fixed code. A photo of the code is useless after a few minutes. This mode is never created automatically.
- Click Create tablet code.
- Open screen shows the screen page (
/w/screen/…) with logo, the large QR code, the note "Scan this code with your phone to clock in" and the countdown "Code changes in …". A button switches to full screen. - Copy link and open it in the browser on the tablet; the tablet needs a permanent connection.
- Later regenerate (all open screens become invalid) or remove.
At the change, LiteLog still accepts the previous code for one more time window so that a scan right before the change does not fail. An expired code leads to "The code on the screen has expired, please scan the current code again." If the card says "Not enabled on this server yet", the rotating code is not set up on your installation; contact LiteLog support.
How the person books. After the scan, the page "Confirm attendance" opens with tenant, property and point. The person enters their staff number and confirms. The page reports "Clocked in" or "Clocked out" with name and time; when leaving, they scan again. The staff number must be known at the property, otherwise a note appears. Start times, blocked periods and the location check apply here too.
App: press button
Nothing else needs to be set up here. Only the Location check row is shown.
Location check
The Location check row is the last row below the next step for every package, and in the custom selection it sits in the Protection block. It defines whether LiteLog checks at check-in and check-out that the person really is at the property.
| Element | Meaning |
|---|---|
| Switch | On = location check via GPS zone: bookings only count inside the drawn zone. Off = the location is logged but not enforced. The switch is applied with Save. |
| Draw zone / Manage zones | Opens the property's zone dialog. There you draw the area within which clocking is allowed. Zones are saved immediately, independent of the page's Save button. |
| Zone in place / No zone | Shows whether the property has a zone with a drawn area. If the switch is on and there is no zone, the tag is orange: no booking counts until you draw a zone. |
| Beacon | If the check via beacon is selected under Custom selection, the row shows the Beacon tag and the note "Checked by beacon, set under Custom selection." The switch is then on. Switching it off turns the check off; switching it on again sets GPS zone. |
The choice applies to check-in and check-out together. The location proof is set per feature, here for time tracking, on the Incidents & Forms and Rounds tabs for the actions there. The overall view of all three areas including the latest check events is on the Tamper Protection tab. For tamper protection to count as met, GPS zone needs a drawn zone and beacon needs a bound device.
Regardless of the chosen location check:
- The GPS location is recorded at every check-in, check-out, and status change
- The system compares the coordinates with the property's location and marks entries as ONSITE (on site) or OFFSITE (outside)
- In the web portal, administrators see the location history on a map in the detail view of a work time
- The number of offsite entries is highlighted in the timeline
Beacon Range
If the property checks via beacon, a check-in or check-out counts as "in range" when a beacon of the property lies within the threshold distance (property value, default 3 m). When binding a beacon in the LiteLog app, an individual radius can be chosen per beacon; it takes precedence over the property value. Your organisation's shared Eddystone namespace is managed centrally under Settings → Devices → Beacons.
Custom selection
If you select the Custom selection card, three blocks appear one below the other instead of the next step. Everything here is applied only with Save, with two exceptions: zones and the web check-in link save immediately.
Check-in
Multiple selection of the methods for clocking in:
- In the app (button)
- NFC chip
- QR code, with the Download QR code link next to it while selected
- Tablet with rotating code: only visible if this method is already set at the property from the legacy stock (see Kiosks); for new setups use the "Rotating code on a tablet" mode of the web check-in
The app button cannot be combined with NFC chip or QR code. Ticking it replaces the on-site methods, and vice versa. The last remaining method cannot be deselected, so the direction is never empty.
Below are three rows that work in addition to the methods:
| Row | Meaning |
|---|---|
| Without app (web check-in) | Switch for web check-in with staff number. When on, the Web check-in link card with both modes appears below, exactly as with the "Without app" package. The points are listed in the "Points" card. |
| NFC scanner device | A fixed reader at the property, paired via Bluetooth. It books in both directions; the row offers the public link to send and copy, which opens the scanner screen without signing in. |
| Automatically via GPS zone | Shows Active or Off and cannot be switched here: LiteLog enables the automation as soon as at least one zone of the property has Automatic check-in set, and withdraws it when the last such zone disappears. Manage zones opens the zone dialog; zones save immediately. Automatically created bookings appear as "Automatic by zone" in the log. |
Check-out
The switch Check-out uses the same method as check-in is the default. Switch it off and the same method list appears once more for clocking out, for example check-in via NFC chip and check-out via button.
Protection
| Element | Meaning |
|---|---|
| Location check (select field) | Off, GPS zone or Beacon. This is the same setting as the Location check row with the packages; only here can Beacon be chosen. If Beacon is selected and no beacon is bound to the property, the page warns: bind a beacon in the app first. |
| GPS zone (row) | Link Draw zone or Manage zones and the tag Zone in place or No zone, as described above. |
| Allow exceptions at check-in / Allow exceptions at check-out | Allows clocking outside the selected on-site methods, for example via button when the chip is damaged. The person must then enter a reason, which is stored in the log. Applies to on-site methods only; with the app button the row is locked. As long as check-out is "same as check-in", the check-out exception follows the check-in exception. |
| View all in history | Opens the history with the rejected and suspicious booking attempts. Visible with the permission View reports. |
"Points" card
Below the method selection, the Points card lists the property's clocking points with their count. It appears as soon as QR code or NFC chip is selected as a method or web check-in is switched on. A point is the place where the QR code hangs, the chip is stuck or the web check-in link applies; most properties need exactly one.
Saving
As soon as you change something, Save appears at the top right. Until then: "Your selection is applied only when you click Save." If you leave the page with open changes, LiteLog asks "Discard changes?". Zones, the web check-in link and the No time tracking card save immediately regardless.
Kiosks (legacy)
:::note Legacy The former kiosk (shift list with rotating QR code on a tablet, check-in with the person's own app login) is no longer offered for new setups. Use the Rotating code on a tablet mode of the web check-in instead (see above). Properties where the kiosk is still set as a method show it in the custom selection as Tablet with rotating code; existing kiosk screens keep running and can be opened in the app via the Kiosk list. Description of the old interface: Kiosk Check-in. :::
Time rules of the property
The following rules belong to this property's time tracking but no longer sit on this page: you maintain them in the property settings, section Rules; the company default is set under Settings → Time rules.
The Rules section only shows as a row what is set at this property. All other rules sit as pills under Add rule — one rule = one pill, active = row. Clicking a pill switches the rule on and shows its row in its usual place; the ✕ on the row removes the rule again. This also applies to the three pure on/off rules Require time tracking, Automatic breaks and Warn when leaving the property area. Hover over a pill (or move keyboard focus onto it) and a popover explains in one or two sentences what the rule does and when it applies. The "Warn when leaving" pill stays disabled as long as no area is drawn on the map for the property — the popover states the reason. Value rules only turn back into a pill after saving once you have switched them off; the "Warn when leaving" rule saves immediately.
Every row carries a mode selector on the right — the same words as in Settings → Time rules: Default (inherited), Own value, Off. Rules without a default for all properties (auto-end, breaks, travel, blocked periods and the three on/off rules) offer only Own value · Off; with Own value the editor sits right below the row. Rules with a default (start times, visit gap) show the line From the main settings: … when set to Default (inherited); the Edit default link opens the rule page with the default already open. Row titles match the time-rule menu entries: Auto-end, Breaks (maximum break duration) and Travel (visits per week).
View Type
Choose which view the mobile app shows at this property:
| Mode | Description |
|---|---|
| Work time | Standard view with live timer, breaks, and detailed work time tracking |
| Check-in mode | Simplified view — only check-in and check-out, without timer or break function. Optimized for pure attendance tracking |
Enforce Time Tracking
When this option is active, the app reminds employees to start time tracking when working at this property. It is a reminder, not a hard block — actions in the app are not blocked.
Auto-end (Auto-Close)
Define when open work times are automatically ended by the system:
| Setting | Description |
|---|---|
| Fixed time | All open work times are ended daily at a specific time (e.g. 22:00) |
| After duration | Work times are automatically ended after a specific number of minutes |
| Calculation basis | With "After duration", choose the basis: gross (from the start time) or net (only effective work time, breaks are not counted) |
Automatically ended work times receive the system note: "Automatically stopped by the system (maximum shift duration reached)." The system checks open entries up to 4 days back.
There is also the option "End automatically on next check-in": if the same person checks in at another property, the still-open work time at this property is ended automatically — intended for tours where employees work through several properties in a row. With this option the app shows no selection sheet: the running shift ends at the moment of the new check-in, and the employee only sees a short notice. Without the option the app asks and offers three ways, including the backdated check-out. Details: Shift handover to another property.
Start Times
The start times (called "execution windows" until 04.10.2026) define the time windows in which time tracking may be started at the property — separately for weekdays and weekends/public holidays. Outside these windows LiteLog accepts no start, neither in the app (also offline) nor via NFC reader, web check-in, chat or the Public API. Clocking out is always possible; a visit that starts at 09:50 and ends at 10:30 is valid.
A typical case are tenders with fixed cleaning windows, e.g. weekdays 06:00–10:00 and 17:00–21:00, on weekends and public holidays additionally 12:00–14:00.
| Option | Meaning |
|---|---|
| Default (inherited) | The property inherits the windows from Settings → Time rules → Start times; the inherited windows appear in the row as From the main settings: …, Edit default opens the default |
| Own value | Windows for this property only |
| Off | No window rule — only the blocked time windows (below) apply |
With Own value you enter up to six windows (from – to) per day type. The checkbox "Different on weekends and public holidays" opens the second list; without it the weekday windows also apply there. A window may span midnight (e.g. 22:00–06:00). Public holidays come from the property's federal state.
Employees who try to start outside the windows see a note stating from when time tracking is possible again. Manual entries by administration (portal, Public API) remain allowed and are marked in the history as "Outside the execution windows".
Blocked Time Windows
Define up to five time windows in which no check-in is possible. Employees see a message in the app that time tracking is currently blocked and can only check in again after the time window has passed.
Automatic Breaks
Automatic breaks are configured as tiered rules:
- Uniform — the same tiers for all weekdays
- Manual — individual tiers per weekday (Monday to Sunday)
Per rule you define a presence duration threshold and the corresponding break duration: from the configured presence duration onward, the specified minimum break applies. If an employee ends a work time with less break than required, the break time is automatically raised to the minimum value.
The maximum break duration is configurable (default: 720 minutes / 12 hours). If the maximum break duration is exceeded, the break is automatically ended by the system.
Visit gap
The visit gap monitors how much time passes between two attendances at the property — it flags both visits that follow too closely and visits that stay away too long. The rule blocks nothing; it reports through an automation workflow.
You need it wherever a client prescribes a cadence — for example a cleaning contract stating "at least 8 and at most 10 hours between cleaning rounds".
| Field | Meaning |
|---|---|
| Minimum gap | Shortest permitted gap between two visits, in hours. Falling below it means someone returned too early. |
| Maximum gap | Longest permitted gap. Exceeding it means the visit did not happen. |
| Grace period | Minutes that may pass before a report is raised (default 15). It smooths out double punches and short interruptions. |
| Reaction on violation | Which workflow runs. Empty = the property's or tenant's default. |
Default, own values, or off
The mode selector on the right of the row decides where the rule takes its numbers from:
:::info The three options
- Default (inherited) — the property adopts the tenant-wide values. Changing the default later takes effect immediately for every property that inherits it.
- Own value — the property maintains its own numbers, the fields from the table above.
- Off — the rule does not apply to this property, regardless of what the main settings hold. :::
When inheriting, all values come from the main settings — minimum gap, maximum gap per day type, and grace period. There is no mixing of own and inherited individual values: this way it always stays clear where a value comes from.
Tenant-wide default
Under Settings → Time rules → Visit gap you define the values once for the whole tenant — minimum and maximum gap per day type, plus the grace period. When a property is set to “Default (inherited)”, the line From the main settings: … shows which values currently apply; Edit default takes you straight there. If you manage several similar properties, you enter the values there once instead of maintaining them on every property individually; the Per property table on the same page shows the effective value of all properties including its source.
A stored default never arms the rule anywhere on its own. It only takes effect on properties explicitly set to "Default (inherited)". Existing properties with "Own value" or "Off" remain unchanged.
Different values on weekends and public holidays
Many clients prescribe a tighter cadence on weekends and public holidays than on weekdays. There is one additional value each for the minimum and the maximum gap. If they stay empty, the weekday value applies on weekends too.
What counts is the calendar day on which the previous visit ended, in the property's time zone. A Friday evening round whose successor falls on Saturday is therefore measured against the weekday rule.
:::info Where the public holidays come from Public holidays come from the property's public holidays and special dates and follow the federal state recorded when the property was created. If none are stored, a public holiday counts as an ordinary weekday. As soon as you save a weekend value, LiteLog creates the missing holidays automatically. :::
Service hours: "work happens here from … to …"
Enter the period during which work happens at the property at all — for example 06:00 to 21:00. The maximum-gap clock only runs during these hours.
If you have already maintained shift templates for this property, LiteLog suggests the service hours from them: the "Take from shift templates" link appears below the two fields as soon as the templates add up to a sensible span — for example, shifts at 06–10, 12–14, and 17–21 suggest 06:00–21:00. Accepting the suggestion saves it as a fixed value. Later changes to the shift templates then do not adjust the service hours on their own — that is by design: a rule that proves contract compliance to a client must not change unnoticed.
Without this setting the night counts too: if the last round ends at 21:00 and the first one starts at 06:00 the next morning, nine hours lie in between. A maximum gap of six hours would then raise a report every single night, even though everything runs to plan.
Leave the fields empty for round-the-clock sites — continuous patrols, for instance. The rule then behaves exactly as before.
The minimum gap is unaffected by the service hours: too short a gap is a violation regardless of the time of day.
The service window must lie within one day; a window spanning midnight is not currently supported.
Warning When Leaving the Property Area
The rule "Warn when leaving the property area" (mode Own value = on) enables leave monitoring for the drawn property area without you having to create a dedicated zone: if a checked-in employee leaves the premises during their shift, a zone event is created and the employee is warned. The sub-switch Automatic check-out additionally ends the running work time once the leave is confirmed (default: off). How the evaluation works — including buffer and delay — is described under Zones.
Good to Know
:::tip Note
- A package sets check-in and check-out to the same methods and switches exceptions off. Everything else (separate check-out, exceptions, beacon, combinations) is Custom selection.
- The app button and the on-site methods (QR code, NFC chip) exclude each other. Zone automation and the NFC scanner device come on top and are kept when you switch packages.
- Web check-in is a switch of its own. It runs with a staff number in the browser and needs neither app nor account; app users at the same property still use the selected methods.
- The location check via GPS zone needs a drawn zone. Without a zone, no booking counts while the check is on; the row warns with No zone.
- Zones, the web check-in link and the No time tracking card save immediately. Packages, methods, exceptions and the location check only with Save.
- With the location check active, administrators can view the GPS history of every work time on a map. :::
Permissions
:::info Permission To open this page, you need View time tracking or Edit properties. Contact your administrator if you don't have access. :::
| Action | Permission |
|---|---|
| Change and save package, methods, location check | Edit properties |
| Switch time tracking at this site on or off | Edit properties |
| Open the zone dialog | View control points (creating and editing follow the control-point permissions) |
| Open the history of booking attempts | View reports |