Field staff check in and out where the work happens

Cleaning, inspection and maintenance teams spend most of a shift on different floors and units, not at one door. A paper sign-in sheet at the entrance shows who entered the building, not where they started work. Signatures can be added later in bulk, times get rounded, and collecting full pages takes time.

Card readers and biometric terminals are usually installed for building entry. They do not record where staff actually work, and putting a device on every floor or unit is rarely practical. EnaFeedback staff attendance fills this gap with the QR codes, live displays and NFC tags that are already at your locations.

At the location where they start work, staff scan the QR code, the dynamic QR on a live display or an NFC tag. They sign in with their 4-character personnel code or a passkey saved on their phone (Quick sign-in) and check in from the staff hub. When they finish, they scan a location again and check out. The check-out location does not have to match the check-in location; both are recorded.

For each check-in and check-out, EnaFeedback stores whether the location session was verified and fresh. A verified session comes from a live display’s dynamic QR, which refreshes every 15 seconds, or from the trust token on an NFC tag. NFC verification works only in the EnaFeedback mobile app; tapping a tag without the app opens the location in the browser as an ordinary, unverified session, the same as scanning a QR code. Fresh means the action happened within 5 minutes of the scan.

Attendance does not need the Cleaning or Control role. Staff without a role, shown with the “Personel” badge, can still check in and out, send staff feedback and use staff surveys and pages.

Each person can have only one open session at a time. If someone forgot to check out, they close the open session themselves with “I forgot to check out” before checking in again, and the session is marked Forgotten. Open sessions are not closed automatically; they stay open until the person checks out or uses that option.

Because the real end time of a forgotten session is unknown, these sessions are left out of duration statistics, so average working times are not inflated. The forgotten rate appears as its own measure in the reports, which gives you a concrete reason to build check-out into the end-of-shift routine where it is high.

The Check-in / check-out records screen in the admin panel offers an overview, records per person, records by location, check-in locations and per-person statistics. Per-person statistics show verified, fresh and forgotten rates. Each session is listed as Open, Completed or Forgotten.

Export the reports to Excel or download a PDF summary. The Home dashboard also shows attendance next to the other counters. Reviewing records requires the Owner, Administrator or Hygiene manager role, so other admins do not see this data.

There are separate alert rules for check-in, check-out and forgotten check-out. They are off by default; when you turn one on, the default channels are email and in-app, and you can add SMS. A night shift supervisor, for example, can be told when someone checks out or forgets to. During SMS quiet hours, alerts are queued and sent as one digest SMS when the window ends.

Attendance runs on the same staff hub as cleaning and inspection logs. You can read the plan compliance you measure with tracking plans next to who was on site during that shift. Staff cleaning and control performance screens and attendance records share the same people and locations.

Staff attendance collects no biometric data: no fingerprint, face or palm scans. A record holds the staff member’s name, check-in and check-out times, the scanned locations and the verification flags. The Face ID or fingerprint lock in the mobile app is a phone feature used only to open the app.

Personnel codes are stored only as a hash (Argon2id). Staff contact details are masked in the admin panel, and exports are written to the audit log. Each customer runs on a dedicated stack with its own database. This setup supports data minimization; privacy notices and processes under KVKK remain your organization’s responsibility.