Fast roster
Use clear daily states from one compact list.
Labour attendance
Mark the daily site roster without payroll complexity.
Choose the site and date, then mark Present, Absent or Half day from a fast roster with supported bulk actions and clear save state.
The daily register
Attendance is hard to trust when every site keeps it differently.
Local registers make missing marks hard to see and blur the difference between an app user and a worker physically recorded at site.
A clear path from capture to responsible action.
Each step keeps the record, its context and the next responsibility visible.
- 01
Choose site and date
Open the roster in the correct operating context.
- 02
Review site workers
Keep attendance records separate from application membership.
- 03
Mark the roster
Use Present, Absent or Half day with supported safe bulk actions.
- 04
Save and confirm
See the pending, saved or recovery state honestly.
What labour attendance covers.
Focused capabilities for the complete workflow, described within their supported operating boundaries.
Bulk marking
Apply supported safe bulk actions with confirmation or undo behavior.
Worker context
Keep the selected site workers visible separately from app access.
Supported history
Review the recorded attendance context without implying payroll output.
The complete roster
Status actions and the save path remain reachable on mobile.
The current desktop and responsive evidence shows the same site-worker roster and clear attendance actions.
- Present, Absent and Half day
- Reachable save action
- No biometric or GPS claim
A useful record has a responsible next person.
The feature supports the handoff without blurring who records, reviews or receives the information.
Supervisor
Mark the supported daily site roster quickly.
Project manager
Review the site attendance record and missing context.
Owner
Understand site attendance without opening payroll complexity.
Operational attendance
The roster supports site supervision; it does not calculate payroll.
NIYAM does not promise wage, statutory, biometric or location-surveillance outcomes from attendance.
- Worker and app-user records stay distinct
- Authorised roles control edits
- Payroll and compliance stay outside scope
Questions about labour attendance.
Straight answers about scope, review and responsibility.
Which attendance states are supported?
The Starter roster uses Present, Absent and Half day, with optional detail only when supported by the current contract.
Can teams mark several workers?
Supported safe bulk actions are available with visible confirmation or undo behavior.
Does attendance calculate payroll or track GPS?
No. Payroll, biometric attendance and GPS surveillance are explicitly outside the Starter scope.