Skip to content
Duall Master

Workforce events from real access data

Build attendance records from real site events

Attendance becomes stronger when it shares identity, access points, schedules, and audit history with the operating platform.

Built for

Realtime status

Built for

Governed actions

Built for

Shared audit

Attendance operations
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

Access-based clock events and attendance records

02

Shift, schedule, exception, and review workflows

03

Site-aware reporting for offices, factories, and campuses

04

Audit trail for manual corrections and approvals

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.

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

    Capture attendance events from approved site movement

  3. 03

    Review exceptions, missing events, and corrections

  4. 04

    Export or integrate attendance data with HR and reporting systems

Module operating model

Attendance depends on the same operating foundation.

Tap any layer to see how it helps a buyer evaluate the platform.

Step 01

Signal

Doors, visitors, cameras, intercoms, parking, and devices generate live operational signals instead of isolated alerts.

01Signal

Doors, visitors, cameras, intercoms, parking, and devices generate live operational signals instead of isolated alerts.

02Context

Each signal becomes useful because operator, person, role, site, zone, policy, and related module records are shown together.

03Action

Teams approve, deny, review, escalate, annotate, or link evidence without leaving the command surface.

04Audit

Every decision keeps the who, what, when, why, and related evidence needed for handoff, reporting, and investigation.

Module model for buyers: each product works on its own, but gains value from shared identity, events, audit, and integrations.

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.