Why shift rules must be written down before software can apply them
Attendance software can only apply the rules you give it. If your policy lives in the supervisor's head ("we let people off if they are a little late on Mondays"), the software will either be too strict or will need constant manual overrides. The fix is to write each rule as a clear statement with a number in it: shift starts at 9:00, grace ends at 9:10, a punch after 9:10 is late, a day with less than a stated number of hours is a half day.
This article helps HR managers, factory administrators, hospital nursing superintendents and school office heads turn their shift policy into rules that software can apply consistently. It covers shift types, grace time, late marks, half days, night shifts, overtime, weekly offs and holidays, and ends with a sample rule table you can adapt. All the numbers in it are examples, not recommendations; your own policy and applicable labour rules decide the real values.
Choosing the shift types your organisation actually runs
Start by listing every working pattern in your organisation, not just the main one. A shift in software is usually a named set of timings: start, end, grace, break and the rules attached to it. Most organisations need fewer shifts than they think, but more than one.
General (fixed) shift
Everyone in the group works the same hours every day, such as an office running 10:00 to 6:00 or school teaching staff on a fixed timetable. This is the simplest to configure and the right default for most office staff.
Rotational shifts
Staff move between shifts on a cycle, for example a factory line where a worker does the morning shift one week and the evening shift the next. The software needs a roster that says who is on which shift on which date, otherwise it cannot tell whether someone arriving at 2 pm is on time or six hours late.
Night shifts
Hospitals, security teams, hotels and continuous-process plants run shifts that cross midnight. These need special handling for the attendance date, which is covered in its own section below.
Split or flexible hours
Some roles work two blocks in a day, or have flexible start times with a fixed number of hours. Decide whether these people are judged on punch times or on total hours, because the rule is different for each.
Grace time, late marks and early exits
Grace time is the number of minutes after shift start during which a punch still counts as on time. It exists because a busy entrance or a slow device should not make punctual people late. Once grace ends, the punch is marked late.
Decide three things in writing. First, the grace period for each shift. Second, what a late mark leads to: nothing more than a report, a count that triggers a conversation, or a deduction after a stated number of lates in a month. Third, whether the same logic applies to leaving early, since an early exit is the mirror image of a late arrival.
A common policy pattern is a fixed number of late marks per month being treated as a half day. If you use one, put it in the employee handbook first. A deduction rule that staff discover only on their payslip causes more disputes than it prevents.
Half-day, absent and missing-punch thresholds
Software needs to know when a day stops being a full day. There are two common approaches, and you should pick one per shift rather than mix them.
- Hours-based: a day with at least the full working hours is present, a day above a lower threshold is a half day, and anything below that is absent.
- Time-based: arriving after a cut-off time (for example two hours after shift start) or leaving before a mid-shift time counts as a half day.
Also decide what happens when there is only one punch in a day. A missing out-punch is usually a forgotten punch, not a half day, so most organisations mark it as an exception for the employee or manager to regularise rather than letting the software guess. Leaving this undecided is one of the commonest causes of salary disputes later, as our article on payroll errors and how to avoid them explains.
Night shifts that cross midnight
A nurse who punches in at 9:50 pm on 14 March and out at 6:05 am on 15 March has worked one shift, not two half days. The software has to tie both punches to the shift's start date. If it does not, the register shows her absent on one day and present without an out-punch on another.
To prevent this, define a punch window for each night shift, for example accepting in-punches from a couple of hours before start and out-punches up to a few hours after end. Punches inside that window belong to the shift. During the pilot, deliberately check a handful of real night shifts, including one at the end of a month, because month boundaries are where night-shift errors usually appear.
Overtime: when it starts and who approves it
Overtime rules need more care than any other, because they turn directly into money. Write down when overtime begins (immediately after shift end, or only after a minimum extra period), how it is rounded (to the nearest quarter hour, half hour or not at all), and whether it is counted daily or weekly.
The most important rule is approval. Calculated overtime should be treated as a claim until a manager approves it. Otherwise a person who stays back to chat for 40 minutes earns the same as one who stayed to finish a dispatch. Approved overtime then goes to payroll; how it reaches the salary sheet is covered in our attendance to payroll export guide.
Overtime pay rates, daily and weekly working-hour limits and rest intervals are set by labour laws and can differ by state and by type of establishment. Confirm the rules that apply to you with your labour consultant or CA before configuring them.
Weekly offs, holidays and working on them
Weekly offs can be fixed (every Sunday) or rotating (each worker gets a different day so the shop or ward stays open). Rotating offs belong in the roster, just like rotational shifts. Holidays are best kept as a holiday calendar per location, since a branch in Jharkhand and a branch in another state may observe different regional holidays.
Then decide the edge cases. If someone works on their weekly off or a holiday, do they get overtime, a compensatory off, or nothing extra? If someone is absent on the day before and the day after a holiday, is the holiday also unpaid? These are policy choices, and the software should apply whatever you decide, consistently, for everyone.
A sample rule table you can adapt
The table below shows how a written policy might look for a single general shift. The values are illustrative only. Copy the structure, fill in your own numbers and get it signed off by management before setup.
| Rule | Example setting | Question to settle internally |
|---|---|---|
| Shift timing | 9:00 to 5:30 with a 30-minute lunch break | Is the break fixed, or must staff punch out and in for it? |
| Grace period | 10 minutes | Is grace the same for all departments? |
| Late mark | Any in-punch after 9:10 | What does a late mark lead to, and after how many in a month? |
| Early exit | Any out-punch before 5:20 | Are early exits with manager permission excluded? |
| Half day | Fewer than a set number of hours worked | Hours-based or time-based for this shift? |
| Missing punch | Flagged as an exception, not auto-marked | Who regularises it and by when? |
| Overtime | Counted after 30 extra minutes, rounded down to half hours, manager approval needed | What do the applicable labour rules require? |
| Weekly off | Sunday | Fixed for all or rotating by roster? |
| Work on a holiday | Compensatory off within the month | Comp-off, overtime or both? |
Setting up these rules in MATROP's attendance software
In our attendance and biometric software, the shift and attendance rules module covers shift timing, grace time, late policy, half day, weekly off, holidays and multiple shifts, including night shifts. Overtime calculation is available as an optional feature, and leave management includes leave types, balances, an approval flow and a holiday calendar, with comp-off available as an option. The rules are applied to punches imported from biometric devices or marked through QR attendance, so late, early-out and overtime are worked out without someone checking registers line by line.
Our implementation begins with a requirements step where your shifts, timings, late rules, departments and branches are recorded. After setup, a pilot of a few days lets you compare the software's results against what your supervisors would have marked, and adjust rules before go-live. If your organisation also processes salaries with us, the same attendance and leave data can feed MATROP payroll software.
If all your staff work one fixed shift with no overtime and you have only a handful of people, a device's built-in report or a simple register may be enough for now. Software earns its place when you have rotating rosters, night shifts, overtime to approve or several branches, which is the situation described in our guide to running biometric attendance across branches.
Questions people ask
Can two departments have different grace times?
Usually yes, by giving each group its own shift definition with its own grace period. Decide whether the difference is truly needed, because every extra shift is one more rule to maintain.
Which date does a punch at 2 am on a night shift count towards?
In most policies it counts towards the date the shift started, so a 10 pm to 6 am shift belongs to the evening it began. Set a punch window for the night shift and test a few real nights during the pilot to confirm the software assigns them correctly.
Should late marks turn into half-day deductions automatically?
Only if that conversion is written in your attendance policy and staff have been told about it. Many organisations prefer the software to flag the pattern and let a manager confirm before any deduction is made.
How do we record a shift swap between two employees?
Enter the swap as a roster change, approved by the manager, before the day of the swap. If it is entered afterwards, both people will be judged against the wrong shift and show false late or absent marks.
