Skip to content
Duall Master

Your door is already the time clock

Attendance, derived from the door — not a second device

Because it reuses the same identity, doors, and schedules as access control, attendance needs no extra hardware and no double data entry.

Built for

Realtime status

Built for

Governed actions

Built for

Shared audit

Attendance
Duall Master Attendance module

Operating model

Signal enters the module, context comes from the shared platform, action is preserved in audit.

Capabilities

What Duall Master does for Attendance

This module is designed as a command workflow, not a static admin screen.

01

Clock-in/out derived automatically from door entries

02

Shift, schedule, exception, and review workflows

03

Site-aware reporting for offices, factories, and campuses

04

Audit trail for manual corrections and approvals

Your door is your time clock

Attendance is derived, not punched

The same face, card, or QR entry that opens the door becomes the time record. No second device to install, no card to swipe twice — every recognized entry already carries who and exactly when.

1

Recognized entry

A person is identified at the door by face, card, or QR. That single event already holds who they are and the exact timestamp.

2

Automatic record

The platform turns matched entries and exits into clock-in / clock-out pairs against each person’s shift — no manual punch, no separate terminal.

3

Shifts, leave & reports

Layer in schedules, leave, and exception review, then export approved timesheets to HR and payroll.

Manual corrections and approvals are kept in a full audit trail.

AI Assistant · for Attendance

Just ask.

Operator

"Show today's late arrivals in the Marketing department."

get_attendance_today_summary · filtered query

Meet the AI Assistant →
Attendance workflow
Duall Master Attendance module
1

Signal

Attendance events enter the same realtime operating timeline as access, visitor, video, parking, and audit activity.

2

Context

Operators see identity, policy, site, zone, device, and linked module records before acting.

3

Action

Approvals, overrides, reviews, and notes are governed by role and preserved in audit history.

Hardware

Runs on real Duali devices

Face, card, QR, and NFC terminals, door controllers, and outdoor readers — the same hardware deployed on live sites.

View the full hardware ecosystem
DF-970

DF-970

AI face terminal with touchscreen — face, RF card, and NFC mobile ID at premium doors.

iTOUCH 30A

iTOUCH 30A

Android smart terminal with dual touch screens — card and mobile QR for staffed or self-service access points.

DQ-Mini+

DQ-Mini+

Outdoor all-in-one terminal — reads RF card, QR, and NFC mobile ID, and controls the door.

iTOUCH popX

iTOUCH popX

Wall-mount access terminal — HF/RF card, NFC phone via HCE app, and static or dynamic QR.

DE-620

DE-620

Slim desktop read/write reader for card issuance and credential enrollment.

DE-950

DE-950

IP65 outdoor proximity reader with Wiegand and serial output for access, attendance, or parking.

Field references

Previous deployments related to Attendance

Customer deployments delivering capabilities now packaged as Duall Master — across hospitals, universities, offices, hotels, and event venues.

Operating workflow

From signal to context to action

A attendance workflow should not end in an isolated log. It should move operators from live signal, to useful context, to governed action.

  1. 01

    Map people, teams, schedules, and relevant access points

  2. 02

    Derive clock-in / clock-out automatically from recognized door entries

  3. 03

    Review exceptions, missing events, and corrections

  4. 04

    Export or integrate attendance data with HR and reporting systems

Built on one platform

Attendance runs on the same platform as every other module.

Signal

Context

Action

Audit

Built on a shared foundation

Identity

Users, roles, tenants

Devices

Doors, cameras, intercom

Events

Realtime timeline

Audit

Reviewable actions

APIs

Connectors & flows

Deploy

Cloud · on-prem · hybrid

Each module works on its own — but they share one identity, events, audit, and integration layer, so they are stronger together. Exact scope is confirmed per project.

Product proof

Built for operational review, not just administration.

The module experience is designed around live status, structured records, linked context, and audit-friendly decisions.

Live status and exceptions

Part of the shared Duall Master command foundation.

Identity and policy context

Part of the shared Duall Master command foundation.

Linked event history

Part of the shared Duall Master command foundation.

Reviewable operator actions

Part of the shared Duall Master command foundation.

For

Factories and shift-based workplaces

For

Offices that need access-linked attendance

For

Campuses and institutions with recurring attendance patterns

For

Operations teams reducing manual reconciliation

Platform connection

Stronger because the foundation is shared

Each module uses the same identity, event, audit, integration, and deployment foundation.

Shared identity keeps attendance aligned with access policy
Realtime events reduce stale manual records
Audit history shows corrections and approvals
Integrations can connect HR and payroll systems where appropriate

Next step

See Attendance in context

Discuss your site, module priorities, and deployment model with the Duall Master team.