Understanding how Timezones work in Track: Timer vs. Reports vs. Approvals
Our platform handles time differently in three key areas: the Timer page, the Reports page, and the Approvals page. Understanding the logic for each is essential for accurate time tracking and reporting.
Timezones can be complex, especially when managing a distributed team. Our platform handles time differently in three key areas: the Timer page, the Reports page, and the Approvals page. Understanding the logic for each is essential for accurate time tracking and reporting.
The Quick Guide: Timezones at a Glance
Here’s the most important takeaway for how time is displayed in each area:
The Quick Guide: Timezones at a Glance
Here’s the most important takeaway for how time is displayed in each area:
- On the Timer Page: Controlled by your computer/browser’s clock setting.
- On the Reports Page: Controlled by the time tracker’s “Reports Timezone” setting in their account.
- On the Approvals Page: Uses a locked-in timezone from the moment the timesheet is submitted.
On the Timer Page: Your Device’s Timezone
The Timer page, where you actively track your time, is the simplest. The times displayed here are based entirely on your device’s local time setting.
Your account settings have no effect on this page. The system simply mirrors the clock on your computer or browser.
Your account settings have no effect on this page. The system simply mirrors the clock on your computer or browser.
- Example: If your computer clock is set to New York time (EST), the Timer page will show times in EST, even if you are physically located in London and your account’s “Reports Timezone” is set to something different. Changing your computer’s clock will immediately change the time displayed on the Timer page (after a refresh).
In Reports: The “Reports Timezone” Setting
This is where your account settings become crucial. All time entries shown on the Reports page are governed by the “Reports Timezone” setting found in the user’s Account Settings.
This rule applies to everyone, whether you’re viewing your own report or an admin viewing a team member’s report. The viewer’s timezone settings are completely irrelevant.
This rule applies to everyone, whether you’re viewing your own report or an admin viewing a team member’s report. The viewer’s timezone settings are completely irrelevant.
- Example: You track time from 9:00 AM to 5:00 PM. Your “Reports Timezone” is set to Gulf Standard Time (GST). Your admin, whose own timezone is set to Pacific Time (PST), will see your entry in the report as 9:00 AM to 5:00 PM GST.
Important: The Impact of Changing Your Reports Timezone
Your “Reports Timezone” setting applies to all of your time entries, both past and future. If you change this setting, it will retroactively adjust how all your previous entries are displayed in reports. This can cause entries to shift to different days, significantly impacting historical data analysis.
In Approvals: A Locked-in Timezone
The Approvals section works differently to ensure that submitted and approved data remains constant and immutable.
When a user submits their timesheet for approval, the timezone for that period is permanently locked in. This creates a static, unchangeable record for payroll and auditing purposes.
When a user submits their timesheet for approval, the timezone for that period is permanently locked in. This creates a static, unchangeable record for payroll and auditing purposes.
Potential for Discrepancies
Because the approval timezone is locked, a discrepancy can occur if a user changes their “Reports Timezone” after submitting their timesheet.
- Scenario: You submit your timesheet for last week. On Monday, you change your “Reports Timezone” from Eastern Time to Pacific Time.
- Result: The Approvals page will still show your submitted hours based on the original Eastern Time. However, the Reports page for that same week will now show your hours based on Pacific Time, and the data may not match.
Other Account Settings
- Country Setting: You may see a “Country” setting in your profile. This does not affect timezone calculations, time tracking, or reporting in any way.