Skip to main content

Attendance Submission

Summary​

Submission means a valid daily attendance outcome is saved without approval and is available for authorized review.

Audience​

Employees, managers, HR and attendance administrators, analysts, product owners, and QA engineers.

Confirmed behavior​

A tenant, employee, date, and status are required. Non-approving users are constrained to their own employee context; an actor with approval capability can submit for another employee. Employee activity and joining date are validated when the local profile is available, and manual weekly-off entry is rejected. Values are calculated and normalized before save.

When the actor cannot approve, the outcome remains unapproved or pending review. When the actor can approve, an omitted approval choice results in approved save in the confirmed command flow. The save action is audited. There is no separately named Draft state.

A universal future-date restriction, formal submission cut-off, mandatory note, dedicated bulk-approval workflow, and complete post-submission edit authority are Requires confirmation. Multiple dated rows may be submitted together, but this is not evidence of a separate bulk-approval process.

Source References​

  • microservices/src/attendance-service/Application/Services/AttendanceCommands.cs
  • microservices/src/attendance-service/Api/Endpoints.cs

See Also​

Keywords​

  • Attendance
  • Attendance Submission

Revision Information​

  • Status: Draft
  • Last reviewed: 2026-07-15
  • Review cycle: Quarterly