Most attendance policies fail because they state intentions instead of rules. Here is a template built from decisions, not adjectives.
An attendance policy is the written rule set that turns attendance data into fair, predictable outcomes. It should answer six questions without ambiguity: when does the working day start, what counts as late, what counts as a half-day, how does leave interact with attendance, what happens when someone forgets to mark a day, and who decides in a dispute. Everything below is a clause you can copy and adapt — each with a note on the decision behind it.
Read enough small-business handbooks and a pattern appears. The attendance section is one page of sentiment — punctuality is important, employees should inform their manager, repeated lateness may attract action — and zero decidable rules. Then an actual case arrives: someone was 12 minutes late four times this month. Is that a late mark? Does it reduce pay? Nobody knows, so it gets decided ad hoc, differently each time, and the perception of favouritism starts.
A policy is enforceable when a person with no context can read it, look at the register, and reach the same conclusion you would. That means thresholds, not adjectives.
Template:
The standard working day is 09:30 to 18:30, including a 45-minute break. The standard working week is Monday to Friday. Employees on shift or field rosters follow the timings published in their roster, which override these hours. The company's published holiday calendar lists non-working days for the year.
The decision behind it: state hours per role group, not per person, or you will be maintaining a spreadsheet of exceptions within a quarter. Point at the holiday calendar rather than restating it — the calendar changes yearly, the policy should not have to.
Template:
A grace period of 15 minutes applies to the shift start time. Check-in after the grace period is recorded as a late mark. Three late marks in a calendar month are treated as one half-day for payroll purposes. Late marks do not carry over between months.
The decision behind it: pick a grace window that reflects real commute variance (10–20 minutes is typical), then set a conversion rule so lateness has a defined, bounded cost. A rule with no consequence is ignored; a rule that deducts pay per minute is punitive and creates resentment. Three-strikes-equals-a-half-day is a common middle ground. The arithmetic and the fairness trade-offs are worked through here.
Template:
An employee who works less than four hours in a day, having checked in, is recorded as a half-day. An employee who does not check in and has no approved leave for that day is recorded as absent. An absent day is unpaid unless it is covered by approved paid leave applied for retrospectively and approved by the reporting manager.
The decision behind it: the half-day threshold must be a duration, not a judgement. Four hours out of eight is the obvious split. State clearly that absence without approved leave is unpaid — this single sentence prevents most month-end arguments.
Template:
Approved paid leave is recorded on the attendance register as leave, not as absence, and does not reduce pay. Approved unpaid leave is recorded as leave and does reduce pay for those days. Approved work-from-home is a full working day and is recorded as WFH. Leave applications must be submitted in advance except in cases of illness or emergency, which must be reported to the reporting manager on the same working day.
The decision behind it: this clause exists because approved leave being marked absent is the single most common cause of a wrong payslip. Make the mapping explicit. Keep paid and unpaid leave visibly separate throughout — the reasoning is here — and treat work from home as its own status rather than folding it into "present".
Template:
If an employee misses a check-in or check-out, they must raise a correction request within three working days, stating the actual times and the reason. The reporting manager approves or rejects it. Corrections raised after the monthly attendance cut-off (the 25th) will be adjusted in the following month's payroll. Original entries are retained alongside approved corrections.
The decision behind it: people will forget to punch — the question is whether your system has a route for it or forces a WhatsApp message to HR. Give it a deadline, an approver and an audit trail. More on doing corrections without destroying the record.
Template:
Employees working away from a company location check in and out using the company system on their own device. The location reported by the device at the moment of check-in and check-out is recorded with the attendance entry. Location is not collected at any other time. Attendance records, including location, are visible to the employee themselves and to authorised company administrators only, and are retained for [X] years.
The decision behind it: if you capture location, disclose it here, in the policy, before you switch it on. Say what is captured, when, who sees it, and for how long. The practical detail is covered here.
Template:
Persistent unexplained absence or lateness will be discussed with the employee by their reporting manager in the first instance, followed by a written note to the employee's record if the pattern continues. This policy is reviewed annually. Any change is communicated to all employees before it takes effect.
The decision behind it: escalation should start as a conversation. Also note the last sentence — a policy changed silently is a policy you cannot enforce against anyone who did not know.
This template covers company rules, not statutory compliance, and the two are different things. In India, working hours, overtime, weekly rest and record-keeping obligations come largely from state Shops and Establishments Acts (or the Factories Act for manufacturing), and they vary by state. Some states require attendance and wage registers to be maintained in a prescribed form and retained for a set period.
Before you finalise a policy, check the specific requirements for the state you operate in, and confirm your record retention meets them. If you have employees in several states, the strictest requirement is usually the safest baseline. When in doubt, take local professional advice — this article is general guidance, not legal advice.
| Typical grace period | 10–20 minutes after shift start |
|---|---|
| Common late-mark rule | 3 late marks in a calendar month = 1 half-day |
| Common half-day threshold | Less than 4 hours worked in an 8-hour day |
| Correction window | Within 3 working days of the missed punch |
| Monthly cut-off | Around the 25th, so payroll has a stable dataset |
| Must be stated explicitly | Which statuses are paid, and which reduce pay |
| Review cadence | Once a year, communicated before it takes effect |
A workable attendance policy states working hours and the working week, the grace period and what counts as a late mark, the half-day threshold, how absence is treated, how approved leave and work-from-home appear on the register, how a missed punch is corrected and by when, how location is handled for field staff, and what happens when a pattern of absence continues.
Ten to twenty minutes after shift start is typical and reflects genuine commute variance. The important part is not the exact number but that it is written down, applied to everyone identically, and paired with a defined consequence once it is exceeded.
Three late marks in a calendar month converting to one half-day is a common and defensible rule. It gives lateness a real, bounded cost without deducting pay minute by minute, which employees experience as punitive. Whatever you choose, state whether late marks reset each month.
Usually it sits alongside the contract as a company policy that can be updated, rather than inside the contract itself, which typically needs the employee's agreement to change. Reference the policy in the contract and confirm employees have received the current version.
Once a year is enough for most small businesses, plus whenever working patterns change materially — new shifts, new locations, a shift to hybrid work. Communicate any change before it takes effect; a rule changed silently cannot be fairly enforced.
Yes. Company rules sit on top of statutory requirements, which in India come mainly from state Shops and Establishments Acts or the Factories Act, and cover working hours, overtime, weekly rest and register-keeping. Requirements vary by state, so check the rules for each state you operate in and take local professional advice for your specific situation.
A policy is only as good as the system applying it. Merik holds the rules that this template describes — grace windows, late marks, half-day thresholds, holiday calendar — and applies them to every employee identically, so the register reflects the policy without anyone doing the arithmetic by hand.
Employees mark their own attendance and raise leave or work-from-home requests from their dashboard; approvals update the attendance record directly, so approved leave never appears as absence. Where a day still needs changing, an admin edits it in the attendance grid — note that this replaces the previous value rather than keeping it alongside. At month-end, the payable days that payroll uses are the same days the register shows — see the attendance and leave modules, the full feature list, or how it works.
A clear, consistent rule set removes disputes and keeps payroll accurate.
How to handle missed punches and corrections with an audit trail.
Four statuses, anchor-day rules, WFH as a request, location at the punch only.