Night shifts, time zones and late marks: attendance that matches real work
· 1 min read
How CRM Dost decides which day a punch belongs to when your team works across shifts and offices.
Attendance is easy when everyone works nine to six in one office. It gets harder with a night shift that ends the next morning, or a team spread across offices in different time zones. Getting the day wrong means wrong late marks, wrong absences, and wrong pay.
Each office keeps its own clock
Every office can have its own time zone, falling back to the company’s. The day a punch belongs to — and whether it was late — is worked out from the office’s clock, not the phone’s, so a wrong device setting cannot move someone’s day.
Shifts, including overnight ones
Turn on shifts and rosters, and each rostered day is judged against that person’s shift. For an overnight shift, a punch after midnight counts toward the day the shift started, so one night’s work never splits into two half days.
Late marks with a grace period
Lateness is measured against the start time plus a grace period, or against the start of the shift. If you want late marks to affect pay, an optional rule turns them into a deduction — by default, every three late marks cost half a day.
Full days, half days and absences
Hours worked decide how each day is counted: present, half day or absent, with thresholds you can change (eight and a half hours and four hours by default).
Closing the day
An optional day-end job can mark people absent who never checked in, and turn overtime into comp off. It waits until the day has ended in every office’s time zone, and runs each action once, so nobody is marked twice.
Set each office’s time zone before its first check-in. Everything else — late marks, reports, the day-end job — follows from it.