> For the complete documentation index, see [llms.txt](https://docs.dapta.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dapta.ai/dcal/calendars-and-availability/time-zones.md).

# Time zones

How dCal handles time zones: your own time zone, the time zone of each schedule, the guest's own time zone on the booking page, and what happens when clocks change for daylight saving time.

dCal works with three time zones: yours, the one of each schedule, and your guest's, which the booking page reads from their browser. Knowing which one applies where saves you from offering 9:00 when you meant 9:00 somewhere else.

***

## Which time zone counts where

| What                                       | Time zone used                                                                                                                                       |
| ------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------- |
| The hours your booking links offer         | The time zone of the schedule the event uses.                                                                                                        |
| The booking page, when a guest opens it    | The guest's own time zone, from their browser. The event panel still names the schedule's zone as the host's time. The guest can switch to any zone. |
| The time a guest books                     | The time zone on the guest's screen when they book. It is saved with the booking.                                                                    |
| Your guest's emails and manage page        | The time zone saved with the booking.                                                                                                                |
| Your **Bookings** list and your own emails | Your own time zone, from **Settings**.                                                                                                               |
| A team page (the list of a team's events)  | The team's time zone, shown after **Times in**.                                                                                                      |
| A team event's booking page                | The guest's own time zone. The event panel names the team's time zone as the host's time.                                                            |

The key point: your open times follow the **schedule's** time zone, not the one in your settings. Changing your own time zone does not move your schedules.

***

## Set your own time zone

**Step 1:** Open **Settings** in the left menu. You land on **General**.

**Step 2:** Pick your zone in **Timezone**. The list holds every time zone with its GMT offset; type a city to find yours. Click **Save**. You see **Saved.**

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-e82da18f4e237b59240eb6e60809e01c64488c04%2Fdcal-time-zones-01-settings-timezone.png?alt=media" alt="The Timezone field of Settings > General set to America/Bogota, GMT-5, boxed, with the Save button below"><figcaption><p>Your own time zone sets how dCal shows times to you.</p></figcaption></figure>

You do not have to set it at first: the first time you open the dashboard, dCal takes your browser's time zone and also moves your first schedule to it. After that, dCal never changes a time zone you chose.

> **💡 Tip:** If you move to another time zone for good, change it in two places: your own **Timezone** here, and the **Timezone** of each schedule on the **Availability** page.

***

## Set a schedule's time zone

Each schedule has its own **Timezone**, at the top of the schedule editor on the **Availability** page. All its weekly hours and date overrides are read in that zone. A new schedule starts in your browser's time zone. See [Set your hours](https://docs.dapta.ai/dcal/calendars-and-availability/set-your-hours.md).

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-60d2b045d6bcdaaea98cf970a0c7101ce764b020%2Fdcal-time-zones-02-schedule-timezone.png?alt=media" alt="The Timezone picker of a schedule, open, with the Search timezone box boxed and a list of zones with their GMT offsets, America/Bogota highlighted"><figcaption><p>Search the list by city. Each zone shows its current GMT offset.</p></figcaption></figure>

This is how one person can keep hours in two places: one schedule in `America/Bogota` for clients in Colombia and one in `Europe/Madrid` for clients in Spain, each linked to its own events.

***

If a personal event uses **Custom hours for this event**, its **Time zone** in **General** > **Availability** sets the zone of those weekly hours. It does not change your profile or any saved schedule. See [Custom hours for one event](https://docs.dapta.ai/dcal/calendars-and-availability/set-your-hours.md#custom-hours-for-one-event).

***

## What your guests see

**Your guest's booking page opens in their own time zone**, the one their browser reports. The days, the times, the details step and the confirmation all follow it, so a guest in Madrid reads Madrid times without doing anything. The event panel still shows the zone of the schedule the event uses, with the words **the host's time** (for example `America/Bogota, the host's time`), so the guest knows where you are.

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-66e5693d8bc5e9c727a38e2529678f29b71db3a5%2Fdcal-time-zones-03-host-time.png?alt=media" alt="The event panel of the Intro call booking page with Jane Doe, 30 min, Online meeting and the boxed line America/Bogota, the host&#x27;s time"><figcaption><p>The event panel names your time zone. The times themselves open in the guest's zone.</p></figcaption></figure>

This works the same everywhere guests book: your event pages, team event pages, one-off invite links and booking pages embedded on a website.

**If the browser gives no usable time zone**, the page opens in your time zone instead: that happens when the browser reports UTC or a zone the page cannot use. The time zone control always shows a zone.

**Your guest can switch to any zone.** Next to the times, the time zone control shows the zone in use and its GMT offset. Clicking it opens a list with:

* **Showing times in**: the zone in use now.
* **Your time zone**: the zone the guest's device is set to, shown only when the page is in another zone, for example after the guest picked a different one.
* **All time zones**: every zone, with a search box.

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-0336aafeb4290c541871eb48543e6aa56296d6e1%2Fdcal-time-zones-04-guest-picker.png?alt=media" alt="The time zone list of a booking page opened from a browser in Madrid, with Europe/Madrid under Showing times in and the All time zones list below it"><figcaption><p>A guest in Madrid sees Madrid times from the start, and can still pick any zone.</p></figcaption></figure>

Once the guest picks a zone, the page keeps it for the rest of the visit; the choice is not remembered between visits. It regroups the days and times at once, without reloading. The zone on the guest's screen when they book is saved with the booking: their emails and their manage page use it, and so does the event dCal writes to your calendar.

> **💡 Tip:** If a guest says the times look wrong, ask them to open the time zone control next to the times and pick their zone. The line **the host's time** in the event panel tells them which zone is yours.

**12-hour or 24-hour.** The guest can switch between **12h** and **24h**. English pages start in 12-hour time, Spanish pages in 24-hour time. The choice is not remembered between visits.

**Team pages.** The list of a team's events shows **Times in** and the team's time zone, set when the team was created. A team event's booking page opens in the guest's own time zone like any other, and its event panel names the team's zone as the host's time. See [Your team page](https://docs.dapta.ai/dcal/teams/team-page.md).

***

## Daylight saving time

Your hours are clock times in the schedule's time zone. When that zone changes its clocks, 09:00 stays 09:00 on the local clock: dCal works out the right moment for every date.

* If the schedule's zone does not use daylight saving time, nothing changes for you.
* If your guest's zone changes its clocks on a different date than yours (or not at all), the times they see shift for those weeks. Your hours on your own clock stay the same.
* On the night clocks go forward, a time that does not exist that day is moved forward. On the night clocks go back, a time that happens twice uses the first one.

***

## Related

* [Set your hours](https://docs.dapta.ai/dcal/calendars-and-availability/set-your-hours.md)
* [How open times are calculated](https://docs.dapta.ai/dcal/calendars-and-availability/how-open-times-work.md)
* [Your name and time zone](https://docs.dapta.ai/dcal/account/general-settings.md)
* [What your guests see](https://docs.dapta.ai/dcal/what-guests-see.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.dapta.ai/dcal/calendars-and-availability/time-zones.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
