xl.bio / precision attendancev1.0 · 2026

Biometric attendance · Multi-branch · Real-time

Time, settled
at the device.

The attendance and shift-management platform that talks directly to your ZKTeco biometric terminals. Real fingerprints. Real time. Every branch you operate, on one dashboard.

Devices

ZKTeco

Sites

Multi-branch

Latency

~100ms

Runtime

Cloud

live signal from the field

live·5 devices · secure link

eat utc+3 / now

--:--:--

today / punches

0418

    ingest ok · p99 142ms

    Demo stream · names, branches and devices are illustrative

    connection02° 18' s/36° 49' e/eat · utc+3/ingest p99 142ms/tls 1.3 · sha-256

    what it does

    Five things,
    done properly.

    Most attendance tools stop at logging punches. ZT Biometrics carries the day all the way through — from the fingerprint at 06:42 to the boss-signed leave request, the shift exception, and the employment contract sitting under the employee record.

    1. 01

      Every punch arrives as it happens.

      A small Raspberry Pi agent on your LAN keeps a steady connection to each ZKTeco terminal and streams new fingerprint events straight up to the dashboard — no nightly sync, no manual exports, no rebooting devices to make them talk.

      • ZKTeco F-series, K-series, MB-series and compatible
      • Fingerprint, face and card verifications captured
      • Resilient to LAN drops — punches replay when the link returns

      technical

      biometric devices · on-site agent · secure uplink · per-org keys

    2. 02

      One record per person, across every branch.

      Link each ZKTeco device user to a real employee with shifts, contact details, branch assignment and photo. Manage thousands across multiple organizations from one console without losing scope or visibility.

      • Multi-tenant — organizations, branches, shared devices
      • Secure photo uploads and a rich-text agreement editor
      • Soft-status flags for active / on-leave / suspended

      technical

      encrypted storage · enterprise identity · secure media

    3. 03

      Requests flow the chain, not your inbox.

      Employees file an absence, late-arrival or custom request. It moves through Supervisor → Admin → Boss with full audit trail. Auto-deny quotas keep edge cases from leaking through.

      • Built-in types: absence · early leave · late arrival
      • Custom branch-scoped request types with end-date rules
      • Bypass-supervisor flag for when the chain breaks

      technical

      stage 1 supervisor · stage 2 admin · stage 3 boss · final

    4. 04

      Drafted, signed, filed — in the same place.

      Author contracts in a rich-text editor, render them to PDF for physical signing, scan and re-upload, then have the Boss set the effective and expiry dates. Stored against the employee record forever.

      • Rich-text editor with inline photo support
      • Boss-approved status gates contract activation
      • Automatic expiry and archival as agreements supersede

      technical

      draft → pending → active → expired → archived

    5. 05

      Branch defaults, individual overrides.

      Set shift windows per branch with per-weekday overrides (late opens on Sunday, anyone?). Override per employee for maternity, vacation or special arrangements — without losing the branch baseline.

      • Per-weekday branch shifts (1=Mon … 7=Sun)
      • Personal overrides with reason snapshots
      • Schedule exceptions: holidays, day-offs, branch closures

      technical

      branch defaults · per-weekday overrides · personal exceptions

    under the hood

    Built for the field,
    sealed to the cloud.

    Biometric devices speak a protocol the public web can't reach directly. An on-site agent sits inside your network, talks to each terminal natively, and pushes signed payloads to the cloud over HTTPS. The dashboard never waits on the device. The device never waits on the cloud.

    1. step 1

      Biometric terminal

      device on the wall · biometric capture

    2. step 2

      On-site agent

      single board computer · lan · buffered & resilient

    3. step 3

      Secure API

      https · always-on · authenticated edge

    4. step 4

      Dashboard

      any device, anywhere · fast everywhere

    Resilient by design

    The on-site agent buffers punches locally while the link is down and replays them in order once the cloud is reachable again.

    Authenticated edge

    Each agent uses a per-organization API key. Payloads are scoped, signed and routed to the right tenant on arrival.

    Always-on dashboard

    An edge-delivered dashboard stays fast worldwide. No origin server to keep alive, no warm-up to wait through.

    who sees what

    A clear chain,
    five rungs deep.

    Role-based access maps to how your business actually decides things. Requests flow up the chain in stages — never leak across organizations, never bypass the boss.

    1. 01

      Boss

      Final word on requests, shift exceptions and employment agreements within their org.

      scope · their organization

    2. 02

      Admin

      Manages branches, devices, employees and reviews requests at the second stage.

      scope · branches & members

    3. 03

      Supervisor

      First-stage reviewer for requests from their own branch's employees.

      scope · one branch

    4. 04

      Employee

      Punches in. Files requests. Sees their own attendance, schedule and agreements.

      scope · themselves

    ready when you are

    Plug in your terminals.
    Start measuring.

    Sign in to your existing organization, or get in touch to set up a new one. The Pi agent ships pre-configured for your devices and pairs with the dashboard in minutes.

    Sign inSet up a new org

    no card required · talk to us first