On this page
Published: September 8, 2026
A fixed label such as "GMT-5" can become wrong when clocks change. A city name alone may also confuse people who do not identify with the suggested location. The brief needs rules for identity, display, and conversion.
State what the choice controls
Explain whether the zone affects appointments, reports, deadlines, notifications, or the whole account. Say where it is stored and whether users can override an organization default. Keep the original instant and chosen zone distinct in the data model.
Use recognizable labels
Present a searchable city or region label with the current offset as supporting information. Avoid abbreviations that have more than one meaning. If the browser suggests a default, let the person review and change it.
Put dates beside converted times
When people compare locations, show the date as well as the hour. A conversion can cross midnight or a calendar boundary. Clarify which zone a deadline or historical record uses, especially when its offset differs from today's.
Test the difficult moments
- Dates before and after seasonal clock changes.
- Zones with half-hour or quarter-hour offsets.
- Users who travel or change device settings.
- Ambiguous, skipped, and repeated local times.
- Search by city, region, and common wording.
- Keyboard operation, zoom, and long translated labels.
Use a maintained time-zone data source approved by the engineering owner. Record the data version and fixtures used in acceptance. The design team should not hard-code a permanent offset into labels or conversion rules.
Further reading
Related Articles
Use this brief with the related planning and acceptance guidance linked above.
Ready to plan your next step?
Contact WebsiteDesignOutsource.com
Turn the guidance into a reviewable handoff
Record the owner, input, acceptance condition, evidence, and escalation point before production begins. That small contract makes the work easier to inspect and approve.
Plan a website production handoff