How to calculate late marks and half-days fairly

Published 12 July 2026 · Merik team · 5 min read

Most attendance disputes aren't about the data — they're about the rule. When "late" and "half-day" aren't clearly defined, every case turns into a negotiation. Fix the rule once, and the disputes stop.

Define a grace period, in writing

Pick a grace window after the official start time (commonly 10–15 minutes) during which arrival still counts as on-time. Anything after that is late. The number matters less than applying it identically to everyone, every day.

Set a clear half-day threshold

A half-day is usually triggered one of two ways:

• Hours worked — fewer than half the required hours in the day.
• Arrival delay — later than a fixed threshold (e.g. more than 2–3 hours past start time).

Write down which rule you use and the exact numbers. Ambiguity is what creates disputes, not the policy itself.

A rule applied consistently feels fair even when it's strict. A rule applied inconsistently feels unfair even when it's lenient.

Decide how late marks turn into deductions

A common approach: allow a small number of late marks per month with no penalty, then convert every late mark beyond that into a half-day (or full-day) deduction. Whatever you choose, the calculation should run the same way every month — not be decided case by case at payroll time.

Connect it to payroll automatically

Once the rule is fixed, it should apply itself: attendance status feeds straight into the days-worked calculation that payroll uses, so no one has to manually total late marks and half-days before running pay. See from attendance to payroll for how that connection works.

How Merik handles it

Merik records entry and exit time for every employee and marks the day present, late, or half-day based on the rule you set — then carries that status straight into monthly payroll, so late marks and half-days are calculated the same way every time. See the features.

Create your workspace →

Or talk to us about your team →