Define Lateness Against the Shift, Not the Clock
Lateness only has meaning relative to a scheduled start time, and in most Indian businesses there is more than one. Office staff start at 09:30, the morning factory shift at 06:00, the night guard post at 20:00. A late coming policy therefore defines lateness as check-in after the start time of the employee's rostered shift plus the grace period for that shift. If the roster is wrong, the late mark is wrong, so the roster must be published before the week starts and locked once payroll runs.
The grace period is the buffer after shift start during which arrival is not counted as late. Ten to fifteen minutes is typical for offices; factories and security posts, where a relief cannot leave until the incoming person arrives, often allow only five minutes or none. Grace is a tolerance, not an extension of the start time: an employee who arrives at 09:40 every day against a 09:30 start with 15 minutes' grace is never late by the policy, and the policy should say whether habitual use of grace is itself a performance matter.
A late mark is the record created when check-in falls after grace. Everything else in the policy (counting rules, deductions, warnings) operates on late marks, so define exactly when one is created, that it is created by the system from the check-in timestamp and not by a supervisor's observation, and how it can be disputed.
- Lateness = check-in after rostered shift start plus the shift's grace period
- Grace of 10–15 minutes for offices; 0–5 minutes where a relief must arrive before the outgoing person leaves
- Late marks are generated by the system from the timestamp, never by observation
- Publish and lock the roster so the shift start the late mark is measured against is not in dispute
Counting Rules: The 3-Late-Marks Rule and Its Alternatives
The most common Indian rule is that three late marks in a calendar month convert into a half-day loss of pay, and each further three late marks in the same month convert into another half-day. It is simple to explain, easy to automate, and tolerant of occasional traffic. Its weakness is that it is not proportionate to time: three arrivals at 09:47 against a 09:30 start with 15 minutes' grace cost the employee half a day (4 hours) for 6 minutes of actual lateness. Employees notice this, and some labour officers do too.
Per-minute or per-block deduction is the proportionate alternative. Lateness beyond grace is deducted in blocks (every 15 or 30 minutes late beyond grace equals a deduction of the same duration at the hourly rate), or the total late minutes in the month are summed and deducted at the hourly rate. On a monthly wage of ₹26,000, the hourly rate is ₹26,000 ÷ 26 ÷ 8 = ₹125, so 90 minutes of accumulated lateness costs ₹187.50. This is fairer and tracks the wage law principle of deduction proportionate to absence, but it requires the system to compute it and it removes the behavioural nudge that a half-day rule provides.
The warning ladder is the non-monetary alternative, common for salaried professionals: the first two late marks in a month produce a system notification, the third a counselling conversation, the sixth a written warning, and so on, with no wage deduction. It suits roles where output is measured differently and lateness is a conduct issue rather than a lost-production issue. Many companies combine approaches: a warning ladder for the first few instances and a half-day conversion only from the fourth late mark onward.
- 3 late marks = half-day LOP: simple and common, but not proportionate to minutes lost
- Per-minute or per-block deduction: proportionate and defensible, needs system computation
- Warning ladder: no deduction, escalating conduct steps, suited to salaried professionals
- Hybrid: warnings for the first instances, monetary conversion only from a higher threshold
Early Going, Exceptions and Documentation
A late coming policy that ignores early going is seen as one-sided and encourages employees to leave early to compensate for being marked late. Treat early exit symmetrically: leaving before shift end without approval by more than the grace period is an early-exit mark, counted with late marks toward the same monthly thresholds, or handled on the same per-block basis. An employee who arrives 20 minutes late and leaves 20 minutes early has lost 40 minutes, and the policy should see it that way.
Exceptions must be listed, not left to discretion. Common ones: late arrival on official duty approved in advance (a client visit, a bank errand); a declared transport strike, bandh or severe weather event, where HR announces a relaxed start time for the day; a documented medical emergency; and system or device failure at the site, where the supervisor's confirmation stands in for the timestamp. Late marks caused by an incorrect roster or an unpublished shift change are removed on regularization without counting toward the cap.
Documentation is what makes deductions defensible. Every late mark should carry the timestamp, the shift and grace it was measured against, and any regularization request and decision. Employees must be able to see their late marks as they happen (a push notification at check-in is ideal) and dispute them within a stated window, commonly 3 working days, through the regularization workflow described in our guide to the attendance regularization process. Deductions should appear as a separate line on the payslip with the number of late marks that triggered them.
- Count early-exit marks alongside late marks toward the same thresholds
- List the exceptions: approved official duty, declared transport or weather disruption, medical emergency, device failure
- Notify the employee at the moment a late mark is created and allow a 3-day dispute window
- Show late-mark deductions as a separate payslip line with the count that triggered them
Legality: What Wage Law Allows an Employer to Deduct
Indian wage law (the Payment of Wages Act 1936 for covered employees and, since 21 November 2025, the Code on Wages 2019) permits only listed deductions from wages. Two are relevant here. Deduction for absence from duty is allowed, but only in proportion to the period of absence: an employee who was absent for one hour may have one hour's wages deducted, not a full day's. And fines may be imposed only for acts or omissions specified in a list approved by the appropriate authority, only after the employee has been given a chance to explain, only within a prescribed limit on the total fines in a wage period, and the fines must be recorded in a register and applied for the benefit of employees. Avoid quoting percentages from memory; check the current Code on Wages rules for your establishment.
This has two consequences for late coming rules. A half-day deduction for three late marks of a few minutes each is larger than the proportionate absence, so it sits closer to a fine than to an absence deduction, and it is safest when it is written into certified standing orders or the appointment terms, communicated in advance, applied uniformly, and accompanied by an opportunity to explain. Per-block deductions that match the actual lateness sit squarely within the absence-deduction rule and are the easier position to defend. Either way, deductions must never take a minimum-wage worker below the minimum wage for the hours actually worked.
For employees who are not workers under wage law (senior managers above the applicable wage threshold, for instance), the contract governs, and a documented policy that is part of the terms of employment is generally sufficient. For everyone else, the policy should be filed with or reflected in the standing orders where the Industrial Employment (Standing Orders) Act or the Industrial Relations Code applies. When in doubt, deduct proportionately and escalate conduct issues through warnings rather than through money.
- Absence deductions must be proportionate to the time absent
- Fines require an approved list, an opportunity to explain, a register and a prescribed cap; verify the current rules
- The 3-late-marks rule is safest when in standing orders or appointment terms, communicated and applied uniformly
- Never deduct a minimum-wage worker below the minimum wage for hours actually worked
Sample Late Coming Policy (Full Text)
The clauses below form a complete late coming policy for a company with fixed and rotating shifts. They use the 3-late-marks rule with a warning ladder for conduct and a symmetric early-exit rule. Replace the illustrative numbers with your own and read the legality section above before adopting a deduction rule for minimum-wage workers.
- 1. Purpose. This policy defines late arrival and early departure, how they are recorded, and their consequences, so that punctuality rules are applied consistently across all employees and locations.
- 2. Scope. This policy applies to all employees at all locations. It forms part of the Attendance Policy and is read with the Leave Policy.
- 3. Shift start and grace period. Each employee's shift start and end times are as published in the roster. A grace period of 15 minutes after shift start applies to office shifts and 5 minutes to factory, site and security shifts, or as otherwise stated in the shift template. Grace is a tolerance for occasional delay and not an extension of the shift start.
- 4. Late Mark. A Late Mark is recorded automatically when check-in is recorded after the shift start plus the grace period. Check-in more than 2 hours after shift start is recorded as a Half Day under the Attendance Policy and not as a Late Mark.
- 5. Early Exit Mark. An Early Exit Mark is recorded automatically when check-out is recorded more than 15 minutes before shift end without prior approval. Check-out more than 2 hours before shift end without approval is recorded as a Half Day.
- 6. Monthly counting. Late Marks and Early Exit Marks are counted together per calendar month and reset on the first day of each month.
- 7. Consequences. The first 2 Marks in a month result in a system notification to the employee only. On the 3rd Mark, half a day's wages is deducted and the reporting manager holds a counselling conversation. Each further 3 Marks in the same month result in a further half-day deduction. Six or more Marks in a month result in a written warning; 9 or more result in a show-cause notice under the disciplinary procedure.
- 8. Deduction basis. A half-day deduction equals half of the monthly gross wage divided by the calendar days in the month for monthly-salaried employees, and half the daily rate for daily-rated employees. Deductions are shown as a separate line on the payslip with the number of Marks that triggered them. No deduction under this policy will reduce an employee's wages below the applicable minimum wage for hours actually worked.
- 9. Exceptions. The following are not Marks: (a) late arrival or early departure on official duty approved in advance in the attendance app; (b) days on which HR has declared a relaxed start or early closure due to transport disruption, bandh, severe weather or a similar event; (c) a documented medical emergency; (d) attendance device or app failure at the location confirmed by the site supervisor; (e) Marks arising from an incorrect or unpublished roster, which are removed on regularization.
- 10. Dispute and regularization. An employee may dispute a Mark through the regularization request in the attendance app within 3 working days, stating the reason. The reporting manager decides within 2 working days. Regularizations under clause 9 do not count toward the monthly regularization cap in the Attendance Policy.
- 11. Habitual use of grace. Where an employee checks in within the grace period on more than 12 working days in a month, the reporting manager may discuss punctuality with the employee. No deduction applies to check-ins within grace.
- 12. Managers. Reporting managers are expected to model punctuality, review the team's Marks weekly in the manager dashboard, hold counselling conversations promptly and record them. HR monitors Marks across the Company monthly and reviews any team where more than a quarter of employees reach 3 Marks in a month, since this usually indicates a roster or transport problem rather than individual conduct.
- 13. Appeals. An employee may appeal a deduction under this policy to HR within 7 days of the payslip date. HR decides within 7 working days and corrects payroll in the following cycle where the appeal is upheld.
- 14. Review. This policy is reviewed annually and on any change in applicable law. Amendments are communicated with 30 days' notice and acknowledged in the app.
Automating Late Marks So the Rule Applies Itself
The 3-late-marks rule is only fair when it is applied identically to every employee, and that cannot be done by hand across 200 people and 6 sites. It has to be a shift-level setting: shift start, grace minutes, the late-mark threshold, the half-day conversion count, and the early-exit mirror. The system then creates the mark from the timestamp, notifies the employee, counts marks per month, and hands payroll a number of half-days per employee that no supervisor has touched.
Attend Mitra sets late-mark and grace-period rules per shift template, tracks early exits, records missed-punch regularization with approval and an audit trail, and shows the live monitor of who is present, late or absent at each site. The resulting LOP flows into the attendance-linked payroll run with the per-day divisor you configure, which is the computation explained in our guide to calculating salary per day and LOP. If you are still counting late marks from a biometric export in Excel, the first improvement is to make the rule visible to employees at the moment it applies; the automation follows from that.
- Configure grace, late-mark threshold and half-day conversion per shift template
- Notify employees at check-in when a mark is created so disputes are raised the same day
- Hand payroll a system-computed count of half-days rather than a supervisor's tally
- Review teams with high late-mark rates for roster or transport causes before disciplining individuals