Playbook

Late coming: record it, ask why, apply the policy the same way for everyone.

Late marks become arguments when they are noticed by a supervisor, remembered later and applied differently to different people.

The playbook

  1. Set shift times per employee or team.
  2. Compare every check-in with the shift automatically.
  3. Ask for the reason at the moment of the late check-in.
  4. Notify the team lead with the reason.
  5. Apply your late-mark policy in payroll the same way for everyone.

How to measure it

Late check-ins per employee per month, reasons by category, and late marks applied in payroll.

How Xforce does it

Xforce runs attendance, leave, tasks and payroll inside WhatsApp. Employees check in by sharing their live location, which must fall inside the geofence set for that site, and a live selfie; Xforce records the time and asks for a reason if they are late or leave early. Leave is applied for in a WhatsApp flow and approved with one tap; tasks are typed in plain language and closed with photo or file proof; payroll is generated in one click from the hours actually tracked, and payslips arrive in the chat as PDFs. It replies in English, Hindi or Marathi, and managers use a web portal with role-based access.

Questions

How should late coming be recorded?

Automatically, by comparing check-in time with the shift, with the reason asked for at the moment of check-in.

How do I apply a late-mark policy fairly?

Configure it once and let payroll apply it the same way to everyone, using recorded check-in times and reasons.

See it on your own data. Xforce runs attendance with selfie and geofence, leave, tasks and payroll inside WhatsApp. Book a 30-minute working session with an engineer.

General guidance, current as of the date above. Labour-law and statutory rules vary; confirm them with your payroll adviser.