Attendance Policy in India: Rules and Free Template

Why Every Indian Employer Needs a Written Attendance Policy

An attendance policy is the single document that decides how your organisation records presence, handles lateness, approves corrections, and converts all of that into a payslip at the end of the month. Get it right and payroll closes in a day with almost no disputes. Get it wrong and your HR inbox fills up with "my punch didn't register", your managers make inconsistent exceptions, and your loss-of-pay calculations become a monthly argument.

For Indian SMBs and startups this matters more than most people expect. You are typically running a mix of office staff, hybrid engineers, field sales teams, and sometimes a plant or warehouse — each with a different definition of what "present" even means. On top of that sit state Shops and Establishments Acts, the Factories Act for manufacturing units, and register and record-keeping obligations that assume you can produce reliable attendance data on demand.

This guide walks through how to write an attendance policy for an Indian workplace end to end: scope, workday definitions, capture methods, attendance statuses, the regularization workflow, late marks, half-days, absenteeism escalation, the link to leave and payroll with worked INR examples, privacy considerations for biometric and location data, rollout, metrics, and a ready-to-adapt template you can lift into your handbook.

What a good attendance policy actually does

A strong policy is not a threat letter. It is an operating manual that answers, unambiguously:

• What counts as a working day and what the expected hours are
• How employees record attendance, and what happens when the system fails
• What statuses exist (present, half-day, absent, LOP, WFH, on-duty, comp-off) and what triggers each
• Who approves corrections, within what window, and with what evidence
• How lateness and absenteeism escalate — fairly, predictably, and in writing
• How each status flows into leave balances and the salary calculation

If two managers in your company would give different answers to any of those questions today, you need this document.

The cost of not having one

Companies without a documented attendance policy usually experience a predictable set of problems:

1. Payroll rework. Attendance data arrives incomplete on the 25th, HR chases managers for approvals, and salary processing slips.
2. Inconsistent enforcement. One team lead marks a 10:45 arrival as fine; another marks it a half-day. Employees notice, and morale drops.
3. Disputes that escalate. Unexplained LOP deductions are one of the most common triggers for grievance escalation and, occasionally, formal labour complaints.
4. Weak records. When an inspector or auditor asks for attendance registers covering a period, scattered spreadsheets and WhatsApp messages are not a credible answer.
5. Invisible absenteeism. Without clean data you cannot see that one shift, one location, or one manager's team is losing significantly more days than the rest.

Scope and Applicability: Who the Policy Covers

Start the policy by defining who it applies to. Vague scope is the most common defect in an attendance policy in India, because Indian companies rarely have one uniform workforce.

Employee categories to name explicitly

• Full-time office employees working fixed or flexible hours from a company location
• Hybrid employees with defined in-office days and remote days
• Fully remote employees who may never touch a physical device
• Field employees — sales, service, collections, logistics — who start their day at a customer site
• Shift workers and factory workers covered by the Factories Act and standing orders where applicable
• Interns, trainees and apprentices
• Contract, third-party or vendor-supplied staff, whose attendance may be recorded for billing but governed by the vendor's own terms
• Consultants and independent contractors, who ordinarily should not be attendance-tracked in the same way as employees

State clearly which categories the policy binds, and which are governed by a separate annexure. Where you operate across multiple states, note that specific working-hour limits, spread-over, overtime rules and register formats vary by state legislation, and that the local rules will prevail wherever they are more favourable to the employee. ### Location and site applicability

If you have multiple offices, plants, or client sites, list them and note where site-specific rules apply. A software office in Bengaluru and a packing unit in Bhiwandi cannot run the same grace period logic. Common site variations include:

• Different shift start times and shift rosters
• Security-gate based entry records versus desk-based punches
• Canteen or break timings that affect net working hours
• Client-mandated attendance systems at deputed locations

Effective date, review cycle and precedence

Every attendance policy should carry a version number, an effective date, an owner (usually the HR head), and a review cadence — annually is standard. Add a precedence clause: where the policy conflicts with an employment contract, certified standing orders, or applicable law, the latter prevails. That single line prevents most interpretation fights.

Defining the Workday, Shifts and Grace Periods

This is the mechanical heart of your attendance policy. Be numeric and unambiguous.

Core elements to define

Practical guidance on grace periods

A grace period is not a right to arrive late; it absorbs traffic, lift queues and biometric queues. Three design choices matter:

1. Length. Ten to fifteen minutes is typical for office roles. Manufacturing and shift-based operations often use five minutes or none, because handover timing matters.
2. Frequency cap. A grace period with no cap becomes the new start time. Most policies allow a limited number of graced arrivals per month — for example three — after which late marks begin.
3. Compensation logic. Decide whether late arrival can be offset by staying later the same day. For knowledge work with net-hours tracking, yes. For shift work with fixed handovers, usually no.

Handling early exits and short hours

Late arrival gets all the attention, but early departure and short total hours cause just as much payroll noise. Define:

• Early exit threshold — leaving more than 30 minutes before shift end without approval
• Minimum hours for a full day — commonly 8 hours net, or 7 hours 30 minutes with manager approval
• Minimum hours for a half-day — commonly 4 hours net
• Below-half-day treatment — under 4 hours net is treated as absent unless regularized

Whatever thresholds you choose, express them in net worked minutes, not in "in-time and out-time only" logic. An employee who punches in at 09:25, leaves at 13:00 for a personal errand, returns at 16:00 and punches out at 18:35 has technically "been present" from 09:25 to 18:35 but worked six hours. If your system only reads first-in and last-out, you will pay for hours nobody worked — and your genuinely diligent employees will notice.

Attendance Capture Methods Compared

Your policy must state which capture methods are approved, for whom, and what the fallback is. Here is an honest comparison of the options Indian employers actually use.

Most Indian SMBs end up with two or three methods running in parallel, and that is fine as long as the policy says who uses what:

• Head office staff: biometric or face device at the entrance, web punch as documented fallback
• Hybrid engineers: web or app punch, with in-office days verified by device punch
• Field sales: mobile GPS punch with geofenced customer locations plus visit logging
• Plant workers: RFID at the gate with biometric verification for shift handover
• Senior leadership: often exempt from punching but still expected to record leave

Write the exemption list down. Unwritten exemptions are perceived as favouritism, and they quietly destroy compliance among everyone else.

Biometric attendance rules worth stating in the policy

If you deploy biometric attendance, address these points explicitly:

1. Enrolment. Who enrols employees, and how a re-enrolment is requested when reads keep failing.
2. What is stored. Modern devices typically store a mathematical template rather than a raw fingerprint image. Say so, and say where it is stored.
3. Failure handling. If the device is down or a read fails three times, the employee informs the reporting manager or security desk, and the day is regularized with that record as evidence.
4. Proxy punching. Punching in for a colleague is a disciplinary matter for both parties. State it plainly.
5. Device tampering. Any attempt to alter device data, use silicone impressions, or spoof GPS is treated as misconduct.
6. Exit. Biometric data is deleted or de-identified within a defined period after separation.

Attendance Statuses: Building a Clean Status Taxonomy

Payroll cannot be automated unless every day for every employee resolves to exactly one status. Define a fixed list and forbid ad-hoc statuses.

Rules that prevent status chaos

• One status per day per employee. If two rules collide, define the precedence order (statutory leave > approved leave > OD/WFH > attendance-derived status).
• No manual overwrite without a reason code. Every override should carry a dropdown reason and an approver name.
• Sandwich rules must be explicit. If an unapproved absence on either side of a weekly off or holiday causes the intervening days to be treated as LOP, say so in writing with an example. If you do not apply a sandwich rule, say that too — silence causes disputes either way.
• Half-day boundaries. State whether a half-day is first half or second half, and how that interacts with leave deduction.

Attendance Regularization: The Workflow That Saves Your Payroll

Attendance regularization is the formal process of correcting an attendance record that does not reflect what actually happened. It is the most-used feature of any employee attendance management system, and the least well-designed part of most policies.

Legitimate reasons for regularization

• Missed punch-in or punch-out (forgot, device queue, phone dead)
• Biometric device or network outage
• Client visit or field work where the geofence did not match
• Travel days, offsite training, or company events
• Late arrival with prior manager approval
• System error, timezone mismatch, or roster misassignment
• Work performed on a weekly off that was approved in advance

Reasons that are not regularization

Regularization is not a way to convert an unapproved absence into a present day retroactively. If someone did not work, the correct outcome is leave or LOP — not a regularized "present". Write this distinction into the policy, because it is where most of the abuse occurs.

A regularization workflow that works

1. Employee raises the request in the HRMS within the defined window, selecting the date, the corrected in/out times, a reason category, and a comment. 2. Evidence is attached where the reason category demands it — for example a client meeting invite, a travel ticket, or a helpdesk ticket for a device failure. 3. Reporting manager reviews within a stated SLA — 48 working hours is a reasonable default. 4. HR reviews only exceptions — requests beyond the window, requests exceeding the monthly cap, or repeat patterns flagged by the system. 5. System updates the attendance record, writes an audit trail entry, and recalculates any dependent leave or payroll impact. 6. Attendance locks on a cut-off date each month. After lock, corrections are handled as a payroll arrear in the next cycle, not as a retrospective attendance edit. ### Windows, caps and cut-offs

Three numbers control whether regularization stays healthy or becomes a monthly free-for-all:

• Request window: typically within 7 calendar days of the affected date, and always before the monthly attendance lock.
• Monthly cap: a limit — commonly 3 to 5 regularizations per employee per month — beyond which HR approval is mandatory. The cap is not a punishment; it is a signal that something structural is wrong.
• Attendance lock date: commonly the 25th or 26th of the month for a month-end payroll. Publish it in the policy and in the HRMS calendar.

Missed punch handling in detail

Missed punches are the number one cause of regularization volume. Reduce them before you manage them:

• Send an automated same-day reminder at shift end to anyone with a missing out-punch
• Allow punch-out from mobile even when punch-in was on a device
• Auto-close forgotten out-punches at the scheduled shift end time, flagged as "system closed", and require the employee to confirm or correct it
• Give security desks and shop-floor supervisors the ability to log a device outage centrally, so all affected employees are auto-regularized instead of raising 60 individual tickets

A single well-configured auto-regularization rule for device outages can remove a third of your monthly regularization requests.

Escalation and audit

Define what happens when a manager does not act within the SLA. The two common designs are auto-approval (fast, but weakens control) and auto-escalation to the next level (slower, but safer). For most Indian SMBs, auto-escalation after 3 working days plus a nudge to the skip-level manager works well. Whichever you pick, the audit trail must record who approved, when, and on what basis — that record is what protects you if the deduction is ever challenged.

Late Marks: Designing Fair, Predictable Consequences

Late marks exist to protect coordination, not to punish traffic. A policy that converts every third late mark into a lost day of pay will feel arbitrary; a policy with no consequence at all will drift.

A balanced late-mark ladder

Principles that keep late marks defensible

• Notice before consequence. The employee should see the count in real time in the HRMS, not discover it on the payslip.
• Progressive, not sudden. Warnings precede deductions.
• Documented exceptions. Medical situations, caregiving responsibilities, public transport disruptions, extreme weather and civic events should be waivable by a manager with a recorded reason.
• Net-hours alternative. For roles where output matters more than punctuality, consider dropping late marks entirely and tracking net hours or core-hours availability instead. Applying factory-style punctuality rules to a product engineering team is a common and costly mistake.
• Consistency. The same rule for everyone in the same category, with exemptions written down.

Late marks versus deduction: be careful

Converting late marks into wage deductions touches wage-deduction rules. Deductions from wages are regulated, the permissible grounds and overall limits are prescribed under wage legislation, and the position is being consolidated under the labour codes. Practical guidance:

• Prefer converting excess late marks into leave adjustment (deducting from CL/EL balance) rather than raw wage deduction wherever balance exists
• Where a half-day LOP is applied, ensure it reflects genuine absence of work rather than a penalty label
• Keep total deductions within statutory ceilings and always issue an itemised payslip showing what was deducted and why
• Have your policy reviewed by your labour law advisor before you enforce any deduction ladder, and re-verify state-specific rules

Half-Days, Short Leave and Partial Attendance

Half-days are where attendance, leave and payroll intersect most awkwardly. Define them once, precisely.

Half-day definitions to include

• Half-day by hours: net worked hours at or above the half-day threshold (commonly 4 hours) but below the full-day threshold (commonly 8 hours).
• Half-day leave: a planned half day of CL/EL, deducted as 0.5 from the leave balance.
• First half vs second half: specify which half is being taken, because it determines whether the employee is expected at the daily stand-up or the evening client call.
• Short leave / permission hours: some organisations allow up to 2 hours of paid permission a limited number of times per month for bank work, school visits or medical appointments. If you offer this, cap it (for example twice a month, non-carry-forward) and require prior approval.

Interaction rules

Absenteeism: Definitions, Escalation and Documentation

Absenteeism is unplanned, unapproved absence. It differs from leave in one respect only — approval. Your policy needs a graduated response that is fair to the employee and defensible for the company.

Categories of absence

• Approved absence: leave applied and sanctioned in advance
• Emergency absence, later approved: employee informs the manager by phone or message on the day and regularizes on return
• Unplanned absence, unapproved: no intimation, no leave balance applied
• Unauthorised continuous absence: multiple consecutive days without contact
• Abandonment of employment: prolonged unauthorised absence beyond the threshold defined in your policy, standing orders or contract

Intimation rules that reduce friction

State exactly how an employee should report an unplanned absence:

1. Inform the reporting manager before shift start, or within one hour of it
2. Use the HRMS or the designated channel, not a casual message to a teammate
3. Apply the leave in the system by end of the same day, or on the first day back for genuine emergencies
4. Provide a medical certificate for sick leave beyond the threshold in your leave policy — commonly 2 or 3 consecutive days

A defensible escalation ladder for absenteeism

Two cautions. First, unauthorised absence is not automatic resignation — abandonment must follow the process set out in your standing orders, contract, and applicable law, usually including written communication to the employee's last known address and a genuine opportunity to explain. Second, never treat statutorily protected absence (maternity, sickness covered by ESI provisions, etc.) under the absenteeism ladder. Get your specific escalation wording checked by your labour law advisor.

Distinguish patterns from incidents

Data beats intuition here. Look for:

• Clustering around weekly offs and holidays
• Concentration within one shift, site, or reporting manager
• Correlation with commute distance or shift timing
• Seasonality (harvest periods, exam seasons, festival travel) that could be better managed by planned leave blocks than by disciplinary action

An absenteeism spike in a single team is far more often a management or scheduling problem than a discipline problem.

How Attendance Links to Leave

Attendance and leave are two views of the same calendar. If they are managed in separate systems, they will disagree, and payroll will inherit the disagreement.

Integration rules to define

• Approved leave overrides derived attendance. If leave is approved for a day, that day should not be recalculated as absent because there was no punch.
• Leave balance checks happen at application, and again at payroll lock. An employee who applies for EL in advance but exhausts the balance through earlier usage must be flagged, not silently converted to LOP on payday.
• Insufficient balance = LOP, disclosed early. Show the projected LOP the moment the leave is applied.
• Comp-off is earned from attendance. Approved work on a weekly off or public holiday generates a comp-off credit with an expiry window (commonly 30 to 90 days). Without an attendance record, there is no comp-off.
• Leave year, accrual and encashment are governed by your leave policy, but the accrual trigger — days worked or days on payroll — comes from attendance data.
• Statutory leave entitlements under Shops and Establishments Acts and the Factories Act, including earned leave accrual based on days worked, depend directly on accurate attendance records. Verify the accrual formula applicable in your state.

A simple monthly reconciliation

Before payroll lock, run this five-line check for every employee:

1. Calendar days in month
2. Minus weekly offs and public holidays = payable working days
3. Minus approved paid leave = days requiring attendance
4. Compare with days present (including WFH, OD, comp-off)
5. Any gap = LOP days to be confirmed

If step 5 is non-zero and unexplained, the record goes to the manager before payroll runs — never after.

How Attendance Links to Payroll: Worked Examples in INR

This is the section your finance team cares about. Every attendance status must map to a payroll instruction.

Step 1: Decide the LOP divisor

The divisor determines the value of one day of pay. Indian employers commonly use one of three:

Worked example 1: Simple LOP with a fixed 30-day divisor

Priya's gross monthly salary is INR 60,000. The company uses a fixed 30-day divisor. In August she has 2 days of LOP.

• Per-day gross = 60,000 / 30 = INR 2,000
• LOP deduction = 2,000 x 2 = INR 4,000
• Gross payable = 60,000 - 4,000 = INR 56,000

Statutory deductions (PF, ESI where applicable, professional tax, TDS) are then computed on the reduced wage components as per the applicable rules, so the net impact is not simply INR 4,000.

Worked example 2: The same LOP under a payable-working-days divisor

Same salary of INR 60,000, August has 31 calendar days, 5 weekly offs and 1 public holiday, so payable working days = 25.

• Per-day gross = 60,000 / 25 = INR 2,400
• LOP deduction for 2 days = INR 4,800
• Gross payable = INR 55,200

The identical absence costs INR 800 more. This is why the divisor must be documented — it is a real money difference, and employees will compare notes.

Worked example 3: Half-days, late marks and comp-off in one month

Rahul earns INR 45,000 gross. Company uses a fixed 30-day divisor. In September:

• 1 full-day unapproved absence with zero leave balance = 1.0 LOP
• 2 half-days below the full-day hours threshold, uncovered by leave = 1.0 LOP
• 8 late marks; policy converts the 7th and 8th into half-day deductions each = 1.0 LOP
• Worked one Sunday, approved, availed as comp-off later the same month = 0 LOP

Total LOP = 3.0 days.

• Per-day gross = 45,000 / 30 = INR 1,500
• Deduction = 1,500 x 3 = INR 4,500
• Gross payable = 45,000 - 4,500 = INR 40,500

Note how the late marks alone cost a full day. That is precisely why the ladder must be visible to the employee in real time and why the sixth late mark should trigger a conversation, not a surprise.

Worked example 4: Overtime for an eligible worker

Suresh is an eligible worker at a covered establishment with an ordinary wage of INR 18,000 per month. He works 10 hours of approved overtime in a month. Assume a 26-day divisor and an 8-hour day for the ordinary hourly rate, and that overtime is payable at twice the ordinary rate as generally prescribed for covered workers.

• Ordinary daily wage = 18,000 / 26 = INR 692.31
• Ordinary hourly rate = 692.31 / 8 = INR 86.54
• Overtime hourly rate at 2x = INR 173.08
• Overtime payable = 173.08 x 10 = INR 1,730.80

Important caveats: overtime eligibility, the applicable rate, the wage base used for the calculation, the maximum overtime hours permitted in a quarter, and the divisor all vary by statute, by state rules, and by whether the employee is an excluded supervisory or managerial category. Treat the arithmetic above as a method, not a legal conclusion, and confirm the parameters that apply to your establishment with your advisor.

Shift differentials and allowances driven by attendance

Attendance also drives several pay elements beyond base salary:

• Night shift allowance — a fixed amount per qualifying night shift, credited from the attendance record
• Attendance or punctuality incentive — a monthly amount payable at, say, 100% attendance with no unapproved lateness
• Field or travel allowance — per day of approved on-duty field work, often tied to geotagged visit logs
• Weekly-off working compensation — either comp-off or paid at a defined rate
• Meal or conveyance reimbursement — sometimes payable per day physically present in office

Each of these needs a rule that a payroll engine can execute without human judgement: a trigger status, a rate, a cap, and an approver.

The attendance-to-payroll handover checklist

1. Attendance lock date reached; regularization window closed 2. Exceptions report reviewed: zero-punch days, excess regularizations, negative leave balances 3. Manager approvals complete; escalations cleared 4. LOP days confirmed employee-by-employee and acknowledged by the manager 5. Overtime and shift allowance data exported with approval references 6. Payroll input file generated with an immutable snapshot of the attendance data 7. Post-payroll: any correction handled as an arrear or recovery in the next cycle, with the original snapshot preserved ## Statutory Registers, Records and Retention

Indian employers are generally required to maintain attendance records and registers under the applicable establishment legislation. The details differ, but the obligations tend to fall into a few families.

• Shops and Establishments Acts (state-specific): registers of employment and attendance, records of working hours, weekly offs, and leave. Formats, retention periods, display requirements and inspection procedures vary by state.
• Factories Act (for factories): registers relating to adult workers, attendance, overtime, leave with wages, and notices of periods of work.
• Contract labour and inter-state migrant workmen legislation: attendance and wage registers maintained by the principal employer or contractor as applicable.
• Wage and social security legislation: attendance underpins wage registers, PF and ESI contribution records, bonus calculation and gratuity service computation.
• The four labour codes: the Code on Wages, the Industrial Relations Code, the Social Security Code and the OSH Code consolidate and simplify many of these obligations, including moves toward electronic registers and combined returns. Implementation timing and rules differ across states; check the current position for each state you operate in before finalising your register strategy.

Practical record-keeping guidance

• Keep electronic records that can be produced as a register. Most modern rules permit electronic maintenance, but the ability to export a readable, chronological, tamper-evident record is what matters in an inspection.
• Retain for the longest applicable period. Retention requirements differ by statute; many employers standardise on a multi-year retention that covers the longest applicable obligation, plus the limitation period for wage claims.
• Preserve raw punch data, not just the derived status. If a deduction is challenged years later, the raw punch log plus the approval trail is your evidence.
• Version your policy. Keep superseded versions with their effective dates, so you can show which rules applied on a given date.
• Do not backdate. Corrections should be recorded as corrections with a timestamp and approver, never as silent edits.

Verify the specific register formats, retention durations and display obligations applicable to your establishments with the relevant labour department or your compliance advisor. Rules change, and they change state by state.

Privacy and Consent for Biometric and Location Data

Attendance systems collect some of the most sensitive data an employer holds: biometric templates and continuous location. India's data protection framework places obligations on organisations that process personal data, including notice, purpose limitation, security safeguards and breach reporting. Even where specific rules are still being operationalised, the following principles are both good practice and the direction of travel.

Principles to build into your attendance policy

1. Notice. Tell employees, in plain language, what is collected (fingerprint template, face template, GPS coordinates, device ID), why, how long it is retained, and who can access it.
2. Purpose limitation. Attendance data collected for attendance and payroll should not quietly become a productivity surveillance feed or an input to performance ratings without disclosure.
3. Data minimisation. Capture location at punch events only. Continuous background tracking of an employee's movements is rarely proportionate and is very hard to justify.
4. Storage limitation. Delete or de-identify biometric templates within a defined period after separation. State the period.
5. Security. Encrypt templates at rest and in transit, restrict administrative access, and log every export.
6. Consent and alternatives. Where consent is the basis for processing, it must be meaningful. Offer a documented alternative — card, web punch or supervisor attestation — for employees who genuinely cannot use biometrics, and for religious or medical objections.
7. Access and correction. Employees should be able to see their own attendance record and request correction — which is exactly what a regularization workflow provides.
8. Vendor controls. Your HRMS or device vendor is a processor. Contract for security, sub-processing limits, breach notification and deletion on exit.

Geofencing without overreach

For field teams, geofencing is legitimate and useful. Keep it proportionate:

• Define geofence radius sensibly (100 to 300 metres is typical) to account for GPS drift
• Capture location only at punch and at logged customer visits
• Disable tracking outside shift hours, and make that visible in the app
• Allow an employee to flag a location mismatch and regularize with a reason
• Never use location data for personal inferences about an employee's life outside work

Have your notice and consent language reviewed by counsel, and revisit it as data protection rules are notified and refined. ## Rolling Out the Policy: Change Management That Actually Works

A technically perfect attendance policy that lands badly will be resented for years. Sequence the rollout.

A 30-day rollout plan

Week 1 — Draft and align. Write the policy using the template below. Align with finance on the divisor, with legal or your advisor on deductions and escalation, and with operations on shift definitions.

Week 2 — Configure and pilot. Set up shifts, grace periods, statuses, regularization workflows and approval chains in your HRMS. Pilot with one team of 15 to 30 people. Run it in shadow mode: capture data, calculate outcomes, but do not apply consequences.

Week 3 — Communicate. Publish the policy, run a 30-minute all-hands walkthrough, record it, and circulate a one-page summary. Train managers separately on approvals, SLAs and how to handle exceptions consistently.

Week 4 — Parallel run. Process one full cycle in parallel with your existing method. Compare the LOP output of both. Investigate every difference — that is where your configuration bugs are hiding.

Month 2 — Go live with consequences enabled, plus a stated amnesty period of one cycle where late-mark deductions are shown but not applied.

Communication that reduces resistance

• Lead with what improves for employees: visible balances, faster approvals, no surprise deductions, quicker payslip queries
• Publish the exact numbers — grace period, thresholds, caps, cut-off dates
• Provide a two-minute demo video of punching, regularizing and applying leave
• Name a single owner for questions and publish the SLA for responses
• Do not launch a new attendance system in the same month as an appraisal cycle or a major salary revision

Manager enablement is the whole game

Most attendance policies fail at the approval layer, not the capture layer. Give managers:

• A weekly digest of pending approvals with an aging indicator
• A short decision guide: which regularization reasons to approve, which to question
• Visibility into their own team's absenteeism and regularization rates versus the company average
• Explicit permission to waive late marks with a recorded reason, so they do not need to break the rule to be humane

Common Mistakes in Indian Attendance Policies

1. Copying a factory policy for a software team. Punctuality ladders designed for shift handovers make no sense for asynchronous knowledge work.
2. No definition of net working hours. First-in and last-out logic overstates work and understates problems.
3. Undocumented exemptions. If leadership does not punch, write it down.
4. No attendance lock date. Without a lock, payroll never gets a stable input.
5. Unlimited regularization. Uncapped corrections turn attendance into a self-reported field.
6. Silent auto-deduction of leave. Any automatic consumption of leave balance must be disclosed and preferably confirmed by the employee.
7. Changing the LOP divisor quietly. This is a pay change in disguise and will be treated as one.
8. Ignoring state variation. One policy across five states, with no state annexures, guarantees a compliance gap somewhere.
9. Treating absence as automatic resignation. Abandonment requires process, notice and an opportunity to explain.
10. Collecting biometrics without notice or retention rules. A privacy problem waiting to become an employee-relations problem.
11. No fallback for device failure. One down device generates a hundred angry tickets.
12. Attendance data living outside the HRMS. Spreadsheets that feed payroll are unauditable and undefendable.

Metrics: What to Track Once the Policy Is Live

A policy without measurement is a document. These are the metrics worth reviewing monthly.

Read them together, not alone. High regularization volume with high approval rates and low absenteeism usually means your capture method is failing, not your people. High absenteeism concentrated in one shift means look at the roster, the commute or the supervisor before you look at discipline. ## Attendance Policy Template You Can Adapt

Copy this attendance policy template into your handbook and replace the bracketed values. Have it reviewed by your labour law advisor before publishing, especially the deduction and escalation clauses.

1. Purpose

This attendance policy establishes the standards for recording working time at [Company Name] and explains how attendance is linked to leave and payroll. It applies from [Effective Date] and supersedes all prior attendance circulars.

2. Scope

This policy applies to all [full-time / probationary / fixed-term] employees at [locations]. [Contract staff / consultants] are governed by [Annexure A]. Where a state-specific rule or certified standing order is more favourable to the employee, that rule prevails.

3. Working hours and shifts

• Standard working day: [9] hours including a [60]-minute unpaid meal break; net working hours [8]
• General shift: [09:30] to [18:30] IST; flexible start window [09:00–10:30]
• Core hours when all employees must be available: [11:00–17:00] IST
• Shift codes and timings: [list]
• Weekly offs: [Saturday and Sunday]; rosters published [7] days in advance
• Holiday calendar: published annually, location-specific

4. Recording attendance

• Approved methods: [biometric device / face recognition / RFID card / mobile app with geofence / web punch]
• Employees must record both an in-punch and an out-punch every working day
• Field employees punch via the mobile app within the geofence of the assigned location
• Sharing credentials, proxy punching or spoofing location is misconduct under [Code of Conduct clause]
• Fallback when a device or the network fails: inform [security desk / reporting manager] and raise a regularization request with the reference number

5. Grace period, late marks and early exit

• Grace period: [15] minutes past scheduled start
• Graced arrivals allowed: [3] per calendar month
• Late marks beyond the allowance escalate as per the ladder in [Annexure B]
• Early exit without approval more than [30] minutes before shift end is recorded as an early exit and may result in a half-day
• Minimum net hours for a full day: [8]; for a half-day: [4]; below [4] hours is recorded as absent

6. Attendance statuses

Attendance for each day resolves to exactly one of: Present, Half Day, Work From Home, On Duty, Approved Leave, Loss of Pay, Absent, Weekly Off, Public Holiday, Comp-off, or a statutory leave status. Precedence: statutory leave > approved leave > on duty / WFH > derived attendance status.

7. Attendance regularization

• Employees may raise a regularization request within [7] calendar days of the affected date and before the monthly lock
• Permitted reasons: missed punch, device or network failure, official travel, client visit, approved late arrival, roster or system error
• Regularization may not be used to convert an unapproved absence into a present day
• Maximum [3] regularizations per employee per month; beyond this, HR approval is mandatory
• Reporting manager to act within [48] working hours; unactioned requests escalate to [skip-level manager] after [3] working days
• Attendance locks on the [25th] of each month; post-lock corrections are processed as arrears in the next payroll cycle

8. Leave interaction

Approved leave overrides derived attendance. Where net hours fall short and leave balance is available, the system will propose a leave application which the employee must confirm within [2] working days. Unconfirmed shortfalls are treated as Loss of Pay. Comp-off is credited for approved work on a weekly off or public holiday and expires [60] days after credit.

9. Payroll impact

Loss of Pay is calculated using a [fixed 30-day] divisor. Per-day pay = [monthly gross] / [30]. LOP days, half-day deductions and overtime are shown as separate line items on the payslip. Any deduction will be applied in accordance with applicable wage legislation and within statutory limits.

10. Overtime

Overtime must be approved in advance by [reporting manager / plant head]. Eligibility, rates and maximum permitted hours are as per applicable law and [Annexure C]. Employees not eligible for statutory overtime may receive comp-off as per Section 8.

11. Absenteeism

Employees must inform their reporting manager before shift start, or within [1] hour of it, for any unplanned absence, and apply leave the same day. Absence of [3] or more consecutive days without intimation will result in a written query, followed by the process set out in [Annexure D] and the applicable standing orders or employment contract.

12. Data privacy

Biometric templates and punch-time location data are collected solely for attendance and payroll administration. Data is stored securely with restricted access and is deleted or de-identified within [90] days of separation. Location is captured only at punch and approved visit events. Employees who cannot use biometric capture may request an alternative method from HR.

13. Records

Attendance records and registers are maintained electronically in [HRMS name] in accordance with applicable establishment legislation and are retained for [X] years. Employees may view their own records at any time in the HRMS.

14. Policy ownership and review

Owner: [HR Head]. Version [1.0]. Reviewed annually or upon change in applicable law. Questions: [hr@company.com]. ## Frequently Asked Questions

1. Is an attendance policy legally mandatory in India?

There is no single statute that says "you must publish an attendance policy". However, employers are generally required to maintain attendance records and registers under the applicable state Shops and Establishments Act, the Factories Act for factories, and related labour legislation, and those obligations are being consolidated under the labour codes. A written attendance policy is the practical way to meet those record-keeping duties consistently and to make wage deductions defensible. Confirm the specific register and record requirements for each state you operate in with the relevant labour department or your advisor.

2. How many late marks can equal one day of loss of pay?

That is a policy decision, not a statutory number. A common design is three graced arrivals per month, notifications from the fourth, a documented conversation at the sixth, and a half-day deduction for each late mark thereafter — meaning two additional late marks add up to one day. Whatever you choose, publish it, show the running count in the HRMS, and prefer adjusting against leave balance over raw wage deduction. Any deduction must comply with applicable wage-deduction rules and limits.

3. Can we deduct salary for a missed punch?

Not for the missed punch itself. A missed punch is a data problem, and the correct remedy is attendance regularization. Deduction should follow only when the employee genuinely did not work and has no leave balance to cover the day. If your system automatically converts missed punches into absences without a regularization window, you will create disputes and, potentially, unlawful deductions.

4. Is biometric attendance allowed in India, and do we need consent?

Biometric attendance is widely used in Indian workplaces and is not prohibited. Because biometric data is personal and sensitive, you should provide clear notice of what is collected and why, limit use to attendance and payroll, secure it properly, define a retention and deletion period, and offer a documented alternative for employees who cannot or will not use biometrics. India's data protection framework is being operationalised, so have your notice and consent language reviewed and refreshed periodically.

5. How does attendance affect earned leave and gratuity?

Earned or privilege leave accrual under most state Shops and Establishments Acts and under the Factories Act is linked to days actually worked in the preceding period, so your attendance record is the source data for accrual. Long periods of loss of pay can reduce accrual and can affect other service-linked calculations. Because the accrual formula and the treatment of LOP differ by statute and state, verify the exact rule that applies to your establishment rather than assuming a uniform national formula.

6. What is a reasonable attendance regularization window?

Seven calendar days from the affected date, and always before the monthly attendance lock, works well for most Indian SMBs. Shorter windows (48 to 72 hours) keep data fresh but generate escalations when employees travel. Pair the window with a monthly cap of three to five requests, an approval SLA of 48 working hours, and auto-escalation to the skip-level manager after three working days.

7. How should we handle attendance for fully remote and field employees?

For remote knowledge workers, track availability during core hours and net worked hours rather than physical presence — a web or app punch tied to SSO is usually sufficient, and outcomes matter more than minute-level punctuality. For field employees, use a mobile GPS punch with geofences around assigned locations, log customer visits, and build in a mismatch-and-regularize path for GPS drift and network dead zones. Do not run continuous background location tracking; capture location at punch and visit events only.

8. What is a healthy absenteeism rate to aim for?

Rather than chasing an external benchmark, set your own baseline. Measure unplanned absent days as a percentage of scheduled workdays for three months, then look at the distribution by team, shift, site and manager. Improvement targets should focus on the outliers. A rising trend in one location or one shift almost always points to a scheduling, commute or supervision issue rather than a workforce discipline issue.

9. Should half-days be defined by hours or by first-half/second-half?

Use both. Define a half-day by net hours worked (commonly at least 4 hours but less than the full-day threshold) so the system can derive it automatically, and require employees applying for planned half-day leave to specify first half or second half so managers can plan meetings and coverage. Also state clearly how a derived half-day interacts with leave balance and with LOP.

Bringing It Together

A good attendance policy is short on rhetoric and long on numbers. It tells an employee exactly when to arrive, how to record it, what to do when the device fails, how many corrections they can request, what happens on the seventh late mark, and precisely how a missed day becomes a rupee figure on the payslip. It tells a manager what to approve and how fast. It tells payroll what to run and when the data is final.

Three things separate the policies that hold up from the ones that get quietly ignored:

1. Every rule has a number. Grace period, thresholds, caps, cut-off dates, divisors, SLAs.
2. Every consequence has a warning before it. Employees see the count and the projected impact before it hits the payslip.
3. Every record has a trail. Who punched, who corrected, who approved, when, and why — retained and exportable.

If you are still stitching attendance together from device exports, WhatsApp approvals and a payroll spreadsheet, the policy alone will not fix the closing-week scramble. The rules need to live inside the system that calculates the salary.

That is where CozyHR helps. CozyHR brings attendance capture — biometric, mobile GPS with geofencing, and web punch — together with shift rosters, an approval-driven attendance regularization workflow, leave balances, comp-off, overtime and payroll in one place, built for Indian SMBs and the compliance realities they operate in. Attendance flows straight into LOP calculation and the payslip, with an audit trail behind every correction.

Adapt the template above, configure the rules once, and let the system do the monthly arithmetic. Try CozyHR and see how much of your payroll week you get back.

This article is general guidance for HR and payroll teams and is not legal advice. Attendance, working-hour, overtime, wage-deduction and record-keeping requirements vary by state and by the nature of your establishment, and are evolving under the labour codes. Verify the current rules applicable to your organisation with the relevant authority or your legal advisor before implementing any policy.