Attendance

Attendance defines a small record structure for daily check-in, check-out, lateness, and absence. Its recommendation is one row per person per day, with rules limited to cases that actually occur. The proposed process runs from a daily log through late or absent flags, correction requests, manager approval, and a monthly report. An owned regularisation step helps keep corrections accountable without turning the template into surveillance.

The skill separates advice, review, build, and conversion requests. Advice receives a direct response; a review checks the process shared by the user. A requested build produces artifacts after essential missing facts are resolved. Otherwise the default is a short recommendation and an offer to generate a relevant template.

Intake covers fixed or flexible hours, night shifts, check-in and check-out methods, self-recording versus automatic recording, late tolerance, half-day rules, and any geofence requirement. It also asks about the existing biometric, app, paper, or other process, disputed cases, and whether the desired output is a record, payroll-input structure, or report. Questions are limited to missing facts, asked one at a time; unknown answers are not invented.

Use it for an attendance tracker, daily attendance sheet, check-in/check-out log, or late-and-absent tracker. It fits Starter stage in the Manage layer. A request can be:

We need attendance for payroll and half-days are a mess.

The template does not calculate payroll, tax, leave balances, or KPIs. It does not enforce punctuality, geofence location, or make payroll decisions. Overtime and payroll connections are later additions if needed. It provides no automation, reminders, or synchronization. Legal, tax, and HR review remains necessary before real decisions use the design.

The fifteen fields are Attendance Record, Employee Name, Department, Date, Check-in Time, Check-out Time, Hours Worked, Work Mode, Attendance Status, Late (Minutes), On Approved Leave, Manager, Regularisation Requested, Notes, and Attendance ID. Check-in and check-out times are text, while Hours Worked and Late (Minutes) are numbers. Leave and regularisation flags are booleans; Date is a date and Notes is long text. No relation fields are defined.

Attendance Status starts with Present, Late, Absent, On Leave, Half Day, and Holiday. These options can be renamed to match the business. A status field represents a record design, not automatic classification.

Requested CSV, SQL DDL, JSON Schema, or Notion mapping derive from one field list. CSV and JSON use matching display names, and SQL identifiers are normalized and documented. Excel-compatible CSV uses UTF-8 with a byte order mark and needs date and number formatting after import. A workbook requires a specific request. Templates stay empty; explicitly requested examples must be clearly synthetic.

Notion output is routed to notion-manual-import for mappings, import instructions, and verification. Manual artifacts need no connection. Live workspace changes require verified access, the target, authorization, and successful tool evidence.

Sensitive review inputs should be minimized and generated templates kept empty; privacy and disciplinary cases need qualified human review.