🎯 Problem Statement (Context for Remote Workers)

For remote employees who frequently travel or relocate across different timezones, the current Automatic Tracking Schedule requires constant manual adjustment.

✨ Proposed Enhancement: Timezone Lock

It would be extremely beneficial to have the option to specify and lock the schedule to a fixed Timezone, regardless of the user's current geographical location.

💡 Specific Use Case

Context: I work remotely for a company based in Colombia. My work hours are defined according to Colombian Time (COT).

Current Pain Point: Every time I travel or change my current device's timezone, I have to manually calculate and adjust the tracking schedule to match the equivalent office hours in Colombia.

Expected Feature: If I could set Colombian Time (COT) as the default timezone for the Automatic Tracking Schedule, the schedule would automatically start and stop tracking at the correct local hours in Colombia, regardless of my current location.

🚀 Benefit

This feature would eliminate the need for manual recalculation and adjustment, significantly improving the reliability and consistency of automatic time tracking for globally distributed teams and frequent travelers.