Skip to main content

Attendance Integration

Audience

Developers, QA engineers, support engineers, security engineers, solution architects, and implementation partners.

Reference Content

This page records source-verified technical behavior and boundaries for the workforce-scheduling capability.

Summary

Attendance is the principal runtime consumer of scheduling. Before calculation, the resolver composes an effective policy for the employee and date. The calculator then normalizes recorded work, derives or recalculates status, and computes overtime, shortfall, and paid units.

Influence

Shift standard hours, overtime threshold, grace, start time, and night classification feed the effective policy. Policy rules can determine attendance status; otherwise the calculator uses fallback thresholds. Weekly-off state is carried alongside the effective values.

Boundary

Scheduling does not own punches, approvals, reopen requests, or attendance records. Changes to configuration affect future calculations and explicit recalculation paths; the source does not prove automatic retroactive recomputation of historical records.

Source References

  • microservices/src/attendance-service/Application/Services/AttendancePolicyResolver.cs
  • microservices/src/attendance-service/Domain/Attendance/AttendanceCalculator.cs
  • microservices/src/attendance-service/Application/Services/AttendanceCommands.cs

See Also

Keywords

  • Workforce scheduling
  • Shift policy
  • Attendance integration

Revision Information

  • Status: Draft
  • Last reviewed: 2026-07-20
  • Next review: 2026-10-20