Help · How it works

Attendance across offices in different timezones

Which day a check-in belongs to when your offices disagree about what day it is, and how to read one report across all of them.

In LiteEntry each location keeps its own timezone, and a check-in belongs to the business day at the place it happened — never the reader’s day. A scan in Singapore lands on Singapore’s Tuesday even if you are reading the report on Monday evening in London.

This sounds obvious and is the thing most attendance software gets wrong, because it is only visible for a few hours a day.

Why it matters more than it looks

With an office in Dubai and one in London, there are five hours of every day when the two disagree about the date. A system that stamps rows with the server’s date puts a Dubai morning on the previous day for anybody who looks from London — and the error is invisible most of the time, which is what makes it expensive. You find it at month end, in the rows that matter.

LiteEntry decides the business day when the row is written, from the location’s own timezone, and never recalculates it afterwards. Somebody moving country does not rewrite their history.

Reading it from one place

The timezone toggle switches between Site time and My time. It changes the clock and never the date: First In 09:12 may be shown in Dubai’s clock or yours, and the row stays on Dubai’s Tuesday either way. The column header tells you which you are looking at.

Live shows every location side by side, each with its own local time and its own count, so an office that has gone home reads differently from one that has not opened.

Attendance filters by location, and the CSV carries a Timezone column next to the times it qualifies rather than gluing an offset onto the value — so a spreadsheet still parses 09:12 as a time.

Setting up a second office

Add another location with its own timezone, put a screen by its door, and that is the whole of it. Each location keeps its own checks too: a geofence in one city has nothing to do with the rules in another, and one office can require the office network while another does not.

Nothing is shipped, nobody travels, and the fourth office takes the same five minutes as the first — done by whoever is already standing in it.

For seeing all your offices side by side, right now, with each one on its own clock: who is in the office.

Overnight shifts

A shift starting Monday evening and ending Tuesday morning is one row on Monday, with the check-out shown as 05:00 +1 and the full duration counted. It is filed under the day the shift began, the way a rota reads it.

The events themselves keep their own dates — the check-out really did happen on Tuesday, and the Events view says so. It is the session that follows the shift, so a night crew reads as people who worked a night rather than as two half-empty days.

Still stuck? Try the demo — most questions here are quicker to answer by pressing the thing than by reading about it.