---
title: "What is an IANA time zone (tz database)?"
url: https://meet.barq.dev/glossary/iana-time-zone
updated: 2026-11-17
author: "Hammad Ali"
---

# What is an IANA time zone (tz database)?

> **Short answer:** An IANA time zone is a named identifier for local-clock rules in the time zone database, such as Europe/London or America/Los_Angeles. It lets software find the applicable UTC offset for a date. Europe/London uses zero offset in January 2026 and plus one hour in July, so the name carries more than one number.


## What information does an IANA time zone name provide?

An IANA [time zone](https://meet.barq.dev/glossary/time-zone) name identifies the rules software uses to interpret local dates and clock hours. The database is maintained as rules change; [IANA's time zone page](https://www.iana.org/time-zones) and [release notes](https://data.iana.org/time-zones/tzdb/NEWS) describe that maintenance, as of 17 November 2026.


The name isn't an offset. Europe/London points to rules that can give different UTC differences for different dates, instead of declaring that the clock always matches UTC.


For a schedule, this lets you say "offer 14:00 by London's local clock" without manually replacing a winter offset when the summer one applies. It doesn't remove the need to choose the appointment date.


The [UTC offset entry](https://meet.barq.dev/glossary/utc-offset) explains the number calculated from a named zone. Think of that number as a dated result, not the entire rule set.


## Why use Europe/London instead of GMT+0?

Use Europe/London when your intended availability follows London's local clock throughout the year. A fixed zero-offset instruction keeps matching UTC, which differs from London during the July example below even though both instructions match in January.


| Input | 15 January 2026 at 14:00 | 15 July 2026 at 14:00 |
| --- | --- | --- |
| Europe/London | 14:00 UTC | 13:00 UTC |
| Fixed UTC+00:00 | 14:00 UTC | 14:00 UTC |

Method: computed with Luxon for Europe/London and a fixed zero offset, using the two dates shown. The local meeting hour is held constant in both columns.


Choose what should stay constant. A distributed operation may deliberately follow UTC, while a consultation offered around a London working day should follow the local clock; those are different scheduling decisions.


## Can a named zone remove every daylight-saving ambiguity?

No. A named zone supplies the rules, but a local clock hour near a transition can still be missing or repeated. Check the actual appointment date and offset when a proposed time falls inside a clock-change interval.


Don't guess the occurrence. If two instants share a wall-clock label, the name of the place alone doesn't tell the recipient which occurrence you intended without more context.


Our [daylight saving definition](https://meet.barq.dev/glossary/daylight-saving-time) explains skipped and repeated hours. The [calendar terminology hub](https://meet.barq.dev/glossary/scheduling-glossary) places named zones alongside the other inputs an invitation needs.


Database freshness also matters. Published rule changes and the data available to a particular runtime aren't automatically identical, so a named identifier isn't a promise that every device has the latest political decision installed.


## How does Barq Meet use IANA zone rules?

Barq Meet uses a named zone on each availability schedule to interpret its working hours. We validate schedule zones through the time-zone library, so an arbitrary string doesn't become a usable schedule merely because it resembles a city name.


We keep the guest's chosen display zone separate from the host's schedule zone. We group available starts by the guest's local date, which can be the previous or following date compared with the host's clock.


Check dates on both sides of a transition. A January test alone won't show whether your intended local-hour arrangement still reads correctly in July for a guest elsewhere.


This explains individual appointment scheduling. Barq Meet doesn't offer recurring-series booking, so use a separate recurrence process if the requirement is a standing weekly meeting across future clock changes.


Review [the calendar and availability features](https://meet.barq.dev/pricing), then [create a schedule that follows your local clock](https://meet.barq.dev/app/sign-in) after choosing which named zone should govern the offered hours.

## Frequently asked questions

### Is an IANA zone the same as my computer's current offset?

No. Your current offset is a result for an instant, while a named zone supplies date-dependent rules. The two may agree today, but using the offset alone can lose the rules needed for a later appointment. Keep the named zone with the future appointment when the meeting follows a city's rules, instead of storing only today's offset.

### Can I invent a city-style identifier?

No. Use an identifier recognized by the time-zone database and the application. A plausible spelling doesn't establish a valid rule set, so pick the supported zone that corresponds to the location whose clock you intend to follow. Choose a recognized identifier from the zone list, then inspect a dated appointment to confirm it represents the place you intended.

### Will changing a zone setting reschedule existing meetings?

Don't assume that a display or availability setting moves appointments already made. Check the existing booking's actual time, and use its reschedule action if the intended meeting instant needs to change for both participants. Review existing invitations independently and contact attendees when their arrangements must change, instead of relying on a display preference to communicate a new time.

## Related pages

- [What is a UTC offset?](https://meet.barq.dev/glossary/utc-offset)
- [What is daylight saving time (for schedulers)?](https://meet.barq.dev/glossary/daylight-saving-time)
- [Scheduling glossary: booking and calendar terms explained](https://meet.barq.dev/glossary/scheduling-glossary)
- [What is a time zone (in scheduling)?](https://meet.barq.dev/glossary/time-zone)

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