Attendance rules people accept as fair

Attendance is the quietest source of conflict in a company. On its own it is just timestamps. At the end of the month it becomes deductions, overtime and leave balances, and every unstated assumption in between turns into an argument with a person in it.

One rule, not four rival ones

The most common failure is not a harsh policy. It is several policies coexisting: the attendance screen decides a day one way, the payroll run decides it another, a report applies a third interpretation, and an employee with no assigned shift is handled by a fourth rule that nobody wrote down.

The result is that the same day is present in one screen and absent in another, and both are produced by the system. Once that happens, no amount of explaining recovers trust, because the employee is right - the numbers do disagree.

Fix it by deciding the status of a day in exactly one place, in a defined order of precedence: approved leave outranks a missing punch; an official holiday outranks a weekend rule; an approved hourly permission reduces a shortfall before any deduction is considered. Then every screen reads that decision instead of forming its own.

Decide the edges in advance

Policies fail at the edges, and the edges are predictable enough to decide in advance rather than case by case.

• Someone with no shift assigned. Treat them as absent, as present, or as needing attention - but decide, because the default will otherwise be whatever the code happens to do.

• A punch in with no punch out. A missing exit is not a zero-hour day; it is an incomplete record and belongs in front of a supervisor.

• A shift that crosses midnight. The hours belong to the day the shift started, or you will split a night into two half days.

• Early departure versus late arrival. Many businesses treat these differently, and if yours does, the rule has to say so rather than leaving it to whoever reviews the sheet.

Overtime is a policy question wearing a technical costume

Hours beyond a shift are not automatically overtime. Overtime usually requires that the work was needed, approved, and beyond the scheduled end - and a system that pays every extra minute will pay for a person who simply forgot to clock out.

The clean shape is that overtime is calculated by one rule everywhere, from approved time only, with a threshold below which nothing accrues. Different rates for weekdays, rest days and holidays are fine; four different calculations in four screens are not.

Trust the record, verify the capture

Where staff record their own attendance on a phone, the question of whether a punch happened where it claims is real. The useful answer is that the server decides, not the device: location is checked against the registered site, the device is enrolled, and the evidence collected with the punch is kept so a disputed day can be reviewed rather than argued.

And when the system cannot tell - a phone with no signal, a location it cannot verify - record that it could not tell. A three-valued answer, with "unknown" as a real state, is far more useful than a confident guess that later turns out to be wrong.

Publish the rule

The single highest-value step is also the cheapest: write the policy down in language an employee can read, and make it reachable from the place they see their own attendance. Most disputes are not about the rule being unfair. They are about the rule being invisible.