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.
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.
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.
What Attendance does for you.
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.
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.
A month register by team or person, late, absent and overtime reports, corrections with a reason approved by the manager, and reminders.
A suggested path for Attendance. What you can do depends on your access in the app.
Locations, shifts and people.
Staff punch in and out.
Approve corrections and read the register.
Live host, inventory, governance, health checks, verification, dependencies and history.
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.
Leave belongs to Leave; pay belongs to Payroll; project time belongs to Timesheets; the people list belongs to People.
5 of 18 required controls are configured. Catalog deployment and inventory maturity remain independent until every required control is present.
attendances.appneural.com
No remediation required.
No remediation required.
No remediation required.
No remediation required.
Configure or repair: Repository exists.
Configure or repair: Business owner exists.
Configure or repair: Product owner exists.
Configure or repair: Technical owner exists.
Configure or repair: Maintaining team exists.
Configure or repair: Documentation exists.
Configure or repair: Architecture documentation exists.
Configure or repair: Security review is current.
No remediation required.
Configure or repair: Dependencies exist.
Configure or repair: Consumers exist.
No remediation required.
Configure or repair: SLA or SLO exists.
Configure or repair: On-call exists.
Configure or repair: Release exists.
No remediation required.
Configure or repair: Infrastructure drift is clear.
No remediation required.
No remediation required.
No remediation required.
No remediation required.
Configure or repair: Repository exists.
Configure or repair: Business owner exists.
Configure or repair: Product owner exists.
Configure or repair: Technical owner exists.
Configure or repair: Maintaining team exists.
AI outputs are saved as drafts with evidence references. They never replace verified catalog fields automatically.