Understand how attendance records work in Sanka, including employees, work dates, time entries, breaks, overtime, leave, approvals, public calendar changes, imports, and AI checkpoints.
Last updated: May 29, 2026
The Attendance object records employee work activity such as work dates, start and end times, breaks, overtime, leave, shifts, approvals, and schedule changes. Use attendance records to understand actual work time, review exceptions, support payroll or billing preparation, and keep employee-related work auditable.This reference explains what an attendance record should contain, how it connects to employees and approvals, and what to check before creating, updating, importing, approving, rejecting, rescheduling, canceling, or troubleshooting attendance records with AI, workflows, CSV, public calendar links, or manual entry.
Claude/Codex
Review this attendance record before updating it. Check employee, work date, start time, end time, break, overtime, leave type, approval status, public reschedule/cancel history, related notes, duplicate records, and permissions. Do not update it yet.
Reviewing attendanceI reviewed the attendance record. Confirm employee, date, hours, leave, approval status, duplicate risk, and permissions before updating.
Ask for another attendance check...
What an attendance record represents
An attendance record represents work time or schedule-related activity for an employee on a specific date or shift. It should help your team answer:
Which employee is this record for?
What date, shift, or work category does it cover?
What start, end, break, overtime, or leave values were recorded?
Is the record a draft, submitted, approved, rejected, canceled, or rescheduled?
Who reviewed or approved it?
What source created or changed the record?
Common fields include:
Attendance ID or record ID
Employee
Work date, start time, end time, break time, and timezone
Work type, shift, location, remote/on-site category, and notes
Working hours, overtime, leave type, leave hours, and absence details
Approval status, approver, submitted date, approved date, and rejection reason
Public reschedule or cancel history when customer- or external-facing calendar flows are used
Related files, comments, employee record, tasks, expenses, reports, and dashboards
Source details from UI, CSV, integrations, workflows, public calendar links, or AI-assisted creation
Attendance fields and statuses can vary by workspace. The important rule is that each record should make employee, date, recorded time, approval state, and source clear enough for review.
How attendance connects to other records
Attendance records depend on clean employee and schedule data.
Employees: the person whose work, leave, or shift is being recorded
Absences and leave: leave type, requested time, approval, and absence history
Workspace users: who can submit, approve, edit, or review records
Contracts and work rules: expected hours, employment type, contract period, and work style
Tasks: reminders for missing clock-out time, approval follow-up, or correction work
Expenses: travel, reimbursement, or employee activity that may need supporting dates
Reports and dashboards: monthly hours, overtime, leave use, missing entries, and approval workload
Workflows and actions: reminders, approval routing, exception detection, and status updates
Creating an attendance record does not automatically approve time, calculate payroll, reimburse expenses, bill customers, or change an employee’s contract. Those outcomes depend on approval, payroll, accounting, billing, expense, and workflow processes configured by your team.
Review before changing attendance
Ask AI to review the employee, date, approval state, and time values before updating attendance.
Sample prompt
/sanka Check this attendance record before changing it. Compare employee, work date, start time, end time, break, overtime, leave type, approval status, approver, duplicate records, public reschedule/cancel history, related notes, and permissions. Ask for confirmation before changing approved or submitted time.
For imports or bulk edits, ask for a dry-run review first.
Sample prompt
/sanka Review this attendance import before running it. Map attendance ID, employee, work date, start time, end time, break, work type, overtime, leave type, approval status, timezone, source ID, and duplicate key. List rows that need manual review. Do not import or update records yet.
Expected behavior
When an attendance record is created or updated successfully:
It appears in the Attendance object list unless it is archived, filtered out, or hidden by the current view.
Employee, date, time, break, overtime, leave, status, approver, notes, and custom fields are saved when configured.
Approved or submitted records can be used in attendance reports, dashboards, payroll preparation, billing preparation, or operational review.
Public calendar reschedule or cancel flows can update schedule-related attendance information when enabled and valid.
Workflows and actions can remind, route approval, flag missing entries, or update status when configured.
CSV imports and bulk edits follow required fields, matching rules, permissions, validation, and duplicate handling.
Attendance updates do not bypass permissions, approval rules, required fields, duplicate checks, employee matching, timezone handling, payroll review, billing review, or audit history.
Troubleshooting
An attendance record is missing
Check the current view, archive state, employee filter, date range, status filter, workspace, permissions, import result, and whether the record was created under a duplicate employee.
Hours, overtime, or break time looks wrong
Review start time, end time, break value, work type, timezone, rounding rules, manual overrides, leave type, and whether the record was imported from a different format.
Approval did not run or the approver is wrong
Check approval workflow conditions, employee manager, department, role, permission settings, submitted status, and whether the record was saved as a draft instead of submitted.
A public reschedule or cancel did not apply
Check whether the link is still valid, whether the attendance record exists, whether the requested time is allowed, whether the record was already canceled or approved, and whether the user submitted the change.
Duplicate attendance exists for one employee and date
Check employee matching, import duplicate keys, public calendar submissions, manual creation, and whether one record is a correction or cancellation. Confirm the approved record before archiving duplicates.
AI cannot decide whether this is a bug
Ask AI to compare employee, date, time values, approval status, public change history, workflow history, import mapping, permissions, timezone, related notes, and audit history. Treat it as a possible bug only after confirming setup and source data are correct.
Checkpoints
Before changing time values, approving, rejecting, importing, bulk editing, rescheduling, canceling, or replying to an attendance support question, check employee identity, work date, timezone, hours, leave, approval state, duplicate risk, source, permissions, and audit history.
