Skip to app details
Back to app library
APPNEURAL APP FAMILYPeople & HR

Attendance

Who came, when, and for how long

Record who came, when and for how long: staff punch in and out on a phone or a kiosk, managers approve corrections, and Payroll gets a month summary.

01 / OVERVIEW

See where it fits in your day.

Staff punch in and out on a phone with the server's time and, when the business wants it, the place and a selfie; a location can be a geofence that is off, optional or required. A kiosk page /kiosk/<token> takes a code with a PIN or a personal QR for each location. Shifts can cross midnight, with grace, late, half-day and overtime rules, weekly rosters, one-day overrides, weekly offs and holidays per location. Each day gets a status by rule (present, late, half day, absent, leave, holiday, week off) and is pending until the day is over. Corrections are requested with a reason and approved by the person's manager, with the old punch kept. The register and reports show the month by team or person with CSV and print. Leave and People are read through service bindings when connected. GET /api/v1/summary?month= gives each employee's loss-of-pay days, worked and overtime hours for Payroll (Payroll does not read it yet). Reminders for a forgotten punch out and for people not yet in run every 15 minutes; webhooks punch.in, punch.out and regularisation events; an optional Claude month summary. Selfies are stored in R2. Not built: overtime pay, comp-off, Indian holiday seeding. The kiosk QR is a secret like a PIN.

A LOOK INSIDEExample layout · sample content
Today
PersonInStatus
AaravattendanceEXAMPLE
Meerapunch inEXAMPLE
RohankioskEXAMPLE
02 / CAPABILITIES

Built around the work you do.

What Attendance does for you.

01

Punch

Punch in and out on a phone with the place checked against the location's radius and an optional selfie, or at a kiosk with a code and PIN or a personal QR.

02

Rules

Shifts that cross midnight with grace, late and half-day rules, weekly rosters, holidays and weekly offs, and leave from the Leave app when connected.

03

Review

A month register by team or person, late, absent and overtime reports, corrections with a reason approved by the manager, and reminders.

03 / GETTING STARTED

Start small. Build from there.

A suggested path for Attendance. What you can do depends on your access in the app.

01

Set up

Locations, shifts and people.

02

Track

Staff punch in and out.

03

Review

Approve corrections and read the register.

YOUR NEXT MOVE

Make Attendance part of your workflow.

The app opens in a new tab, so your ecosystem stays close.

Open app
05 / CATALOG DETAILS

The registry record.

Live host, inventory, governance, health checks, verification, dependencies and history.

Catalog surfaceDEPLOYEDHEALTHY
InventoryACTIVE1 items
P2VERIFIEDPUBLISHED
Overview

Purpose and boundaries

Staff punch in and out on a phone with the server's time and, when the business wants it, the place and a selfie; a location can be a geofence that is off, optional or required. A kiosk page /kiosk/<token> takes a code with a PIN or a personal QR for each location. Shifts can cross midnight, with grace, late, half-day and overtime rules, weekly rosters, one-day overrides, weekly offs and holidays per location. Each day gets a status by rule (present, late, half day, absent, leave, holiday, week off) and is pending until the day is over. Corrections are requested with a reason and approved by the person's manager, with the old punch kept. The register and reports show the month by team or person with CSV and print. Leave and People are read through service bindings when connected. GET /api/v1/summary?month= gives each employee's loss-of-pay days, worked and overtime hours for Payroll (Payroll does not read it yet). Reminders for a forgotten punch out and for people not yet in run every 15 minutes; webhooks punch.in, punch.out and regularisation events; an optional Claude month summary. Selfies are stored in R2. Not built: overtime pay, comp-off, Indian holiday seeding. The kiosk QR is a secret like a PIN.

Attendance for a connected domain's team: punches with server time and a place check, kiosks with a code and PIN or a personal QR, shifts and rosters, holidays, day status by rule, corrections approved by a manager, a register and reports, and a month summary for Payroll.

Leave belongs to Leave; pay belongs to Payroll; project time belongs to Timesheets; the people list belongs to People.

Priority
P2
Portfolio
People & HR
Capability
People & HR
Technical owner
Not configured
Runtime
Cloudflare Workers / OpenNext
Last verified
2026-11-18 14:03:16
Semantic inventory

Every number says what it counts

1Catalog itemstrackedEntityCount · catalog-api:live
Production-ready gate

Governance evidence required

5 of 18 required controls are configured. Catalog deployment and inventory maturity remain independent until every required control is present.

MissingBusiness owner
MissingProduct owner
MissingTechnical owner
MissingMaintaining team
MissingGitHub repository
ConfiguredProduction URL
ConfiguredHealth endpoint
MissingDocumentation
MissingArchitecture document
MissingCurrent security review
ConfiguredData classification
MissingDependencies
MissingConsumers
MissingSLA / SLO
MissingOn-call
MissingLast release
ConfiguredLast verification
ConfiguredDeprecation status
Catalog details

attendance schema v1

Catalog-specific metadata is not configured.
Live host

Where it runs

attendance.appneurox.com DEPLOYED

attendance.appneurox.com

Worker
attendance-catalog
Health
HEALTHY
Last deployment
2026-11-18 14:03:16
DNS & routing

Confirmed infrastructure only

Provider inspection appears after Cloudflare credentials are configured. Mutations require dry run, idempotency and explicit confirmation.
Repository & architecture

Technical context

APPNEURAL-Catalogs/attendance-catalogLOCAL · NOT CONFIGURED

Documentation

Documentation and architecture evidence are not configured.
Dependencies

Registered relationships

No dependency edges are registered. Nothing has been inferred.
Operations

Checks and verification

No health checks have been recorded.
Security

Review posture

Security review not configured. This does not mean the catalog is secure or insecure.
Automatic reconciliation

GitHub · Cloudflare · DNS · catalog APIs

No synchronization run has completed yet. The scheduled Worker records missing credentials as Not configured, never as success.

Drift findings

No drift has been recorded.
Evidence & history

Trust record

Verification is verified. Run verification to store check-level evidence, confidence, expiry and remediation.

AI workspace

Human-reviewed drafts

AI outputs are saved as drafts with evidence references. They never replace verified catalog fields automatically.

App libraryOpen app