Attendance policy template for Indian offices

This page is an illustrative drafting aid for an attendance policy that Indian offices can adapt. It is not legal advice, not a claim of nationwide compliance, and not a certified handbook. Rules can vary by employer policy, establishment type, state, applicable law, and employment terms. Pending SME review. Do not issue this text unchanged to employees.

Use the sections as a checklist of decisions you must actually write. Fill times, methods, and outcomes from how you run the office. Do not paste invented Shops and Establishments quotas into the blanks. Working hours, weekly offs, and registers can be regulated differently by location and establishment; confirm what applies to you with qualified review before you treat a number as mandatory.

Operational background on how attendance systems usually work sits on the attendance management guide. Product capabilities that can support a written policy — punches, shifts, grace, regularization, calendars — are described on Dayzen attendance management. Neither page is a substitute for your issued policy.

1. Purpose and scope

Drafting notes in italics. Replace with your text.

State why the policy exists: a consistent record of presence for operations, leave interaction, and payroll inputs. Name who it covers (employees, trainees, contractors if you include them) and which locations or legal entities. If some sites use a different punch method or roster, say so here instead of hiding it in a footnote. State the effective date and who owns amendments (HR, operations, or a named role).

Scope should also say what this policy is not: it is not the leave policy, not the code of conduct, and not a payroll-process manual. Point to those documents by name. Sandwich-leave treatment of holidays and weekly offs, if relevant to absence spanning rest days, belongs in leave policy and on the live sandwich-leave guide — do not restate sandwich mechanics in this attendance chapter.

2. Definitions

Define only terms you will use:

• Shift: the published start and end window for a working day or roster slot.
• Punch / attendance mark: the recorded check-in, check-out, or day status.
• Grace: minutes after start (and, if you use it, before end) that still count as on time.
• Late mark: the record after grace is exhausted.
• Regularization: a controlled correction to a punch or day status, not a leave type.
• Weekly off: rostered rest, which is not leave and not a public holiday.
• Half-day (attendance): a presence outcome for part of the shift.

If you use outdoor, on-duty, or work-from-home codes, define them here as attendance types, not as informal chat statuses.

3. Shifts and working hours

Write the shift pattern as company policy: start, end, which days of the week, and whether Saturday (or another day) is full, short, or off. If you run multiple shifts or rosters, say how an employee learns their current window. Do not invent a legal maximum hour cap in this template. Applicable working-time rules may exist for your establishment and location; they are not restated here as a national number.

Name the timezone for each site. Night shifts that cross midnight need a rule for which calendar day the punch belongs to — that is an operating choice you should write, not leave to the device default.

Breaks: if you publish a lunch or tea window, say whether it is paid, unpaid, or outside the shift length you expect. “Flexible break” without a duration is not a rule.

Detail on grace minutes versus late marks belongs in the issued policy and is explained operationally in shift, grace, and late marks. Copy your numbers into this section; do not leave “grace as per HR.”

4. How attendance is recorded (punch methods)

List the methods you actually use as options you have chosen, not as methods every Indian office must use:

• Supervised office punch (device, kiosk, or attended register).
• Application punch with location checks (GPS / geofence) and/or network checks (IP), if you use them.
• Identity checks such as face matching on punch, if you use them — identity is not location proof.

Say which employee groups use which method (office, field, hybrid). If GPS is optional for a role, write that. Do not mandate a method in the handbook that you do not operate. Privacy: state that location or identity data is collected for attendance, who can see it, and that it is not a general surveillance promise.

5. Grace, late marks, and short days

Publish, in numbers:

1. Grace after shift start (and before end, if any).
2. What a late mark does: record only, count toward a monthly cap, require regularization, or contribute to an unpaid outcome under a named rule.
3. When a short day stays paid attendance versus when it needs half-day leave versus when it may become unpaid. That distinction is a policy choice; see the sibling article on half-day attendance versus leave.

Caps on late marks are company design unless a binding instrument you have reviewed says otherwise. Write the cap and the consequence. Silence is not kindness; it is an argument in the last week of the month.

6. Weekly offs and holidays

Weekly offs are rostered rest. Holidays are calendar rest from the holiday list you publish. Neither is a leave balance. Point employees to the holiday calendar and to the leave policy for how leave interacts with rest days. Do not paste sandwich examples here.

If a site has a non-Sunday weekly off, say so in the roster section so payroll and the attendance calendar use the same rest day.

7. Regularization

Name allowed reasons (missed in, missed out, wrong shift, device down), who may apply, who approves, and the cutoff before attendance close. Unapproved exceptions should not silently become LOP unless you published that outcome. Regularization is not a backdoor full-day present for days the person did not work.

8. Auto-absent and auto punch-out (optional outcomes)

If you use them, write them as optional policy outcomes, not as universal system law:

• Auto-absent: no valid punch by a named time produces an absent (or similar) status.
• Auto punch-out: an open check-in is closed at a named time, with a stated effect on hours.

Say whether the employee may still regularize after auto-absent, and until when. If you do not use these jobs, delete this section rather than leaving “as per software.”

9. Outdoor work and work-from-home

Include this section only if you use those attendance types. State how the day is requested or marked, whether a punch is still required, and how it appears on the monthly calendar. Hybrid patterns should name default office days if you have them. Do not treat a chat message as an attendance type.

10. Month-end close

Name the attendance close date or window relative to payroll. After close, punches and regularizations wait for the next cycle unless a named off-cycle exception exists. The people-ops order — attendance, then leave, then calculation — is the same idea as the monthly operating loop. This policy only needs the attendance freeze date and the owner who may declare the queue closed.

Records: say where the monthly calendar and punch logs are kept, who can export them, and how long the company chooses to retain them. Retention here is a company choice you should align with applicable record-keeping duties after review — this template does not invent a statutory retention year.

11. Exceptions

List rare cases you will still handle in writing: disaster days, city-wide transport failure, device outage lasting a full shift, or a declared special working day. Each exception should have an owner and a time-boxed decision. “We will see” is not an exception clause.

12. Employee acknowledgement

A one-paragraph acknowledgement that the employee has read the attendance rules, including punch method, grace, regularization cutoff, and month-end close. Collect it through your joining process or a dated policy update. Acknowledgement does not make an unlawful clause lawful; it only records notice of the version you issued.

---

Adapt every blank. Have the issued version reviewed for your entities and states before you publish it internally. Dayzen attendance can support punches, shifts, grace, break windows, regularization, calendars, and optional auto-absent or auto punch-out jobs; the policy still has to name which of those you switched on. This template stays a draft until SME review. Do not treat the headings as a compliance certificate.

When you revise shifts or punch methods, reissue the same section numbers so managers can find the change. A policy that only lives in an HRMS configuration screen, with no employee-facing text, will not settle a dispute. Configuration should match the issued chapter; if they drift, freeze month will follow the screen and employees will quote the PDF. Pick one source of truth per revision date, and file the acknowledgement against that date.