VAQT Neo

Biometric attendance for the office, the gate, and every site in between.

Neo is the cloud console behind the punches. It holds workforce data and site rules, pairs arrivals and departures into a clear day, and keeps records you can trust — wherever people check in.

VAQT Neo attendance console overview

What the console does

It turns individual punches into a day you can report on.

Neo keeps the workforce list, applies the rules that were active when someone punched, pairs entries and exits across gates, and keeps a history of changes — what HR and finance need when attendance becomes a payroll question.

  • Arrivals and departures pair into one coherent day, even across different doors.
  • Late punches are judged by the policy that applied at the time.
  • Offline buffers sync in order so events are not lost or duplicated.

Inside Neo

What you manage in the application.

How Neo works

Workforce

People and credentials live in one place. Once enrolled, someone can be recognized across your terminals.

Policies

Shift rules and grace periods use the policy that was in force when the punch happened — not today’s rewrite of yesterday.

In and out pairing

Enter through one gate and leave through another; Neo resolves that centrally into one day.

Devices

Neo terminals and many existing third-party devices can report into the same console.

Offline behaviour

Terminals keep working when the network drops, then sync events in order when they reconnect.

Audit history

Corrections leave a trail. Last month’s attendance stays last month’s attendance.

Software

Neo is the console.

Pairing, reporting, and policy live here. Start with how Neo works if you want the fuller explanation.

Read how Neo works →

Hardware

Terminals capture what happens at the door.

Lobbies, remote sites, and field teams all create events. Neo hardware is built for those places, and existing devices can often join the same estate.

Look at the devices →

In practice

What people ask us to confirm early.

  • Terminals keep working offline and sync events in order when the connection returns.
  • You can keep much of the hardware you already own and still bring records into Neo.
  • Enrolment travels with the person across your device estate — not restart at every door.
  • Late data is judged by the rules that applied at the time, and changes leave an audit trail.
  • A terminal will not record on a clock it does not trust.

If this sounds like your sites, walk through Neo on a demo.

Bring questions about gates, offline periods, or devices you already have.