Multi-Segment (Multi-Duty) Attendance

Purpose - Lets an employee record several check-in/check-out pairs in one day so that time spent at school and time spent on assigned duties are both attributable to the correct engagement. 

Who Can Use It

Employees whose organisation has this feature enabled at the server. Read-only views (calendar, history) always render multi-segment days regardless. 

Key Capabilities 

• Records up to eight check-in/check-out pairs per day. 
• Each pair carries a context: School Attendance, Duty (with the associated duty), or Shift.
• Employees see per-leg times, worked hours, and late/early remarks on their calendar and history views. 
• The app's "Available Actions" endpoint returns exactly what punches are open and which duty each one refers to, so the employee never has to guess. 

How to Use It 

• On a day when a duty is scheduled, open the attendance screen. The app lists the available actions ("Check-In — School attendance", "Check-Out — Duty — Board exam invigilation", and so on). 
• Punch in for school in the morning. 
• When leaving the school for a duty, punch out for school and then punch in for the duty (which may be from a different location if the duty allows). 
• When the duty is done, punch out for the duty and, if returning to school, punch in for school again. 
• Punch out at the end of the day. 

Rules & Restrictions 

• Available only when the multi-segment feature is enabled on the server for the day; older client builds and legacy days continue to see a single-pair day. 
• Total pairs on a day cannot exceed eight. 
• A day that has already begun on the legacy single-pair model stays single-pair until the next calendar day. 
• Every segment obeys the same geofence, timing, and remark rules as the ordinary attendance flow.