Key takeaways
- Your organization's timezone, set in Preferences, decides where each day starts and ends.
- Auto punch-out, break and meeting auto-close and day-wise reports are all calculated against local midnight.
- Set it once at the start so every report lines up with your working day.
Every attendance report has to answer a simple question: which day does this hour belong to? For a team spread across places, the answer depends on whose midnight you mean. TIMO360 uses one: your organization's. That single boundary is what makes distributed workforce attendance and remote team productivity analytics comparable from one person to the next.
Where it is set
The timezone is part of the organization's preferences, set by an administrator when the organization is created or later from the Preferences page, alongside the idle threshold.
What follows local midnight
Auto punch-out: a session still open past local midnight is closed automatically, and administrators receive an Employee auto punched out notification.
Breaks and meetings left open are closed at local midnight too.
Day-wise reports: each day's working, idle, break and meeting time is grouped by days that start and end in your timezone.
Why it matters for distributed teams
Because the day boundary is the organization's, an employee working from another region still appears on the same report day as their colleagues. There is no mix of personal days and company days to reconcile when you export a report for payroll or review.
A quick checklist
Choose the timezone that matches how your company defines its working day.
Set it before the first report you plan to rely on.
Tell employees which timezone the daily cut-off uses, so a late-night session is no surprise.
See attendance, alerts and data retention for where the timezone applies.