---
title: "Time zone abbreviations list for scheduling"
url: https://meet.barq.dev/glossary/time-zone-abbreviations
updated: 2026-11-17
author: "Hammad Ali"
---

# Time zone abbreviations list for scheduling

> **Short answer:** Time zone abbreviations are short labels, such as EST or EDT, used beside local clock times; their meaning depends on the intended location and sometimes the season. They aren't a complete scheduling address: New York uses UTC-05:00 in January 2026 and UTC-04:00 in July, so include a city and meeting date.


## Which time zone abbreviations appear in this list?

This time zone abbreviations list pairs labels returned for named locations with offsets on two stated dates. New York's EST and EDT differ by one hour; Chicago also changes its label and offset between these winter and summer examples. Use the [British Summer Time definition](https://meet.barq.dev/glossary/bst-british-summer-time) when a London appointment is one hour away from the conversion you expected.


Use the date too.



**Named locations and their calculated winter and summer clock labels**

| Feature | Named zone | 15 January 2026 | 15 July 2026 |
| --- | --- | --- | --- |
| New York | America/New_York | EST, UTC-05:00 | EDT, UTC-04:00 |
| Chicago | America/Chicago | CST, UTC-06:00 | CDT, UTC-05:00 |
| London | Europe/London | GMT, UTC+00:00 | UTC+01:00 |
| Kolkata | Asia/Kolkata | UTC+05:30 | UTC+05:30 |
| Shanghai | Asia/Shanghai | UTC+08:00 | UTC+08:00 |

Source: [Luxon calculations using named IANA zones; January and July dates are example inputs, not transition dates. Checked 17 November 2026.](https://www.iana.org/time-zones) (November 17, 2026)


Method: offsets and the displayed US abbreviations were computed with Luxon for noon on each date. [IANA's time-zone database](https://www.iana.org/time-zones) supplies the named-zone model; its [release notes](https://data.iana.org/time-zones/tzdb/NEWS), as of 17 November 2026, describe rule updates. This is a short scheduling reference, not an exhaustive abbreviation dictionary.


## Why can time zone abbreviations cause booking mistakes?

An abbreviation can leave the intended location unclear, and a seasonal label can be wrong for the date you're discussing. Writing EST beside a July New York appointment applies the winter offset to a city using its summer offset on that date.


The hour matters.


For 15 July 2026, 14:00 in America/New_York converts to 18:00 UTC. Treating 14:00 as the fixed EST offset instead produces 19:00 UTC, one hour later. Both calculations can be internally consistent while only one matches the sender's intended New York appointment.


The [EST and EDT explanation](https://meet.barq.dev/glossary/est-vs-edt) works through that distinction. If someone supplies only a label, ask for a city before proposing a time; don't guess what their acronym means.


## How do I write a time that someone can check?

Write the date, local clock time and location together, then include the named zone when the appointment crosses regions. For example, use 15 July 2026 at 14:00 New York time, America/New_York, and check the recipient's local equivalent for that same instant.


Be explicit once.


1. Confirm which city's clock controls the appointment.
2. Convert the actual date using that named zone.
3. Read the recipient's date as well as the hour.
4. Send one invitation after both people agree.


An offset answers how far a clock sits from UTC at that instant. A named zone supplies the location's rules over time. [Working hours overlap](https://meet.barq.dev/glossary/working-hours-overlap) answers the next question: whether the converted time is within both people's working day.


## How does Barq Meet handle guest time zones?

Barq Meet shows guests a time-zone selector, so they can inspect offered appointments in their intended local zone instead of interpreting an abbreviation in your email. We base offered hours on the host's availability schedule and its named zone.


We let guests change the display zone without changing the underlying slot. We still check the selected Google calendars at submission, because a readable time label doesn't mean a previously displayed slot remains available. Check before you share.


This remains one host's schedule; it doesn't calculate collective availability for a team. The [scheduling terminology index](https://meet.barq.dev/glossary/scheduling-glossary) explains related booking concepts. Review [what an account includes](https://meet.barq.dev/pricing), or [offer dated appointments through a booking page](https://meet.barq.dev/app/sign-in).

## Frequently asked questions

### Is a UTC offset enough for an appointment next summer?

An offset fixes a relationship to UTC, but it doesn't describe future clock changes in a location. For an appointment next summer, send the date and a named zone, then calculate that date's offset instead of carrying today's difference forward.

### Should I write ET instead of EST in an email?

ET can avoid choosing the wrong seasonal suffix, but include the city and date as well. A phrase such as New York time on 15 July makes your intended location clearer, while a booking link lets the guest inspect their local equivalent.

### What should I ask when a message only says IST?

Ask for the city, the meeting date and the sender's intended clock time. Don't select a location on their behalf or accept the first result in a converter; confirm those inputs before you send an invitation. Ask which city and date the sender means, instead of choosing an offset from an abbreviation that several different regions use.

## Related pages

- [EST vs EDT: what's the difference?](https://meet.barq.dev/glossary/est-vs-edt)
- [Scheduling glossary: booking and calendar terms explained](https://meet.barq.dev/glossary/scheduling-glossary)
- [What is working hours overlap?](https://meet.barq.dev/glossary/working-hours-overlap)
- [What is BST (British Summer Time)?](https://meet.barq.dev/glossary/bst-british-summer-time)

[Create your free booking link](https://meet.barq.dev/app/sign-in)
