Help · Choosing LiteEntry

Attendance for restaurants

Shift attendance for restaurants and hospitality — nothing to install, running before service, and each check-in takes about three seconds.

Mount a spare tablet at the entrance or the pass. Staff point their phone camera at the code and tap one button on the way in — the same tap checks them out at the end of service. LiteEntry records who arrived, when, and at which site. That is the whole of it.

There is no app to install, no account for your team to create, and nothing that needs an IT department.

Fast enough for a busy service

Three seconds is the check-in time for an honest scan. The code changes every thirty seconds, so a photographed one expires fast — but the window is generous enough that someone walking toward the door does not miss it.

The button says Check in or Check out depending on what the person did last. Nobody has to remember which they are doing.

No hardware to procure

The display is any device with a browser and a power socket — a spare tablet, an old phone, a TV over the bar. There is no terminal to buy, no badge reader to wire in, and no vendor to call when it stops working. See attendance without buying hardware for what that saves across multiple sites.

If the screen goes offline, Live says so against that location — check-ins are impossible right now — so an empty shift list does not read as a staff no-show.

A manager checking whether the lunch team showed up does not need to be in the building. Open Live on any phone and the current check-ins are there. If someone is missing, you know before service starts, not halfway through it.

Shared devices

A restaurant often has one tablet at the front or the pass. Shared devices are a normal thing, and LiteEntry handles them: device recognition notices when one phone checks in two different people and records the pattern. It never blocks anyone — a genuine shared work phone is allowed through — but repeated pairs of names on one device appear in the report, on the day they happen.

High turnover and seasonal staff

Add a person by name and email. Nothing is sent. They sign in with their Google account the first time they scan, and that is their whole setup before their first shift. When someone leaves, one click disables them — no app to recover, no account to close.

Nothing is installed on their phones, so nothing remains when they leave. For part-time, seasonal, or first-job staff, that is the version of attendance tracking that gets accepted without an argument — there is nothing to demand justification for, because there is nothing to install.

Multiple sites

If you run more than one location, each keeps its own timezone and its own configuration. One report covers all of them, filterable by site and date. Adding a second site is adding a location in the console, pointing a spare screen at its display page, and uploading the team there.

If the restaurant has Wi-Fi, the network check confirms each check-in came from that network — the simplest way to verify the person was in the building, not scanning from the car park.

Every attendance record exports to CSV in one click — names, shifts, and durations, with overnight sessions correctly filed on the day they started. That is the file a payroll process or a week-end labour report needs.

Still stuck? Try the demo — most questions here are quicker to answer by pressing the thing than by reading about it.