> 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/set-your-hours.md).

# Set your hours

Set the hours your booking links offer in dCal: create schedules with weekly hours, split a day into several ranges, change the hours of one date with a date override, choose each schedule's time zone

Your hours live in **schedules** on the **Availability** page. A schedule is a set of weekly hours, plus any dates where the hours are different, in one time zone. Personal events can follow your working hours, use a saved schedule or have custom weekly hours of their own, so you can keep different hours for different kinds of meetings.

You start with one schedule already made, so your booking links have hours from day one. This page shows you how to change it, add more and link them to your events.

***

## Your schedules

**Step 1:** Go to [app.dcal.ai](https://app.dcal.ai) and open **Availability** in the left menu. Each schedule is listed with its name and time zone, an **Edit** button and a **Delete** button.

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-7e53ff26450e7405f82cc38ed6fe97ecf1e05ab5%2Fdcal-set-your-hours-01-schedules-list.png?alt=media" alt="The Availability page listing two schedules, Working hours and Afternoons, each in America/Bogota with Edit and Delete buttons, and the New schedule button boxed"><figcaption><p>Your schedules, oldest first. The one at the top is your default.</p></figcaption></figure>

Every account starts with a schedule called **Working hours**: Monday to Friday, 09:00 to 17:00, in your time zone.

> **💡 Tip:** Your **default schedule** is the one at the top of the list, your oldest schedule. Events set to **My working hours** follow it. dCal does not let you pick another schedule as the default, so to change the hours most of your events use, edit that schedule.

***

**Step 2:** Click **Edit** on a schedule to change it, or click **New schedule** to add one. A new schedule is named **New schedule**, uses your browser's time zone, starts with Monday to Friday, 09:00 to 17:00, and opens right away.

***

## Edit a schedule

**Step 1:** Click the name at the top of the editor and type a name you will recognize, for example `Afternoons` or `Clinic hours`.

**Step 2:** Choose the **Timezone** these hours are in. Type a city in the search box to find it, for example `Bogota` or `New York`. Every time in this schedule is read in this time zone. See [Time zones](https://docs.dapta.ai/dcal/calendars-and-availability/time-zones.md).

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-17544389ec2435e95a33c0f0690c84ee0f55cf71%2Fdcal-set-your-hours-02-schedule-editor.png?alt=media" alt="The Working hours schedule in the editor, with the Timezone field set to America/Bogota and Weekly hours where Monday has two ranges, 09:00 AM to 12:00 PM and 02:00 PM to 06:00 PM, and the + Add a range button boxed"><figcaption><p>Name, time zone and weekly hours. Monday has a lunch break: two ranges on the same day.</p></figcaption></figure>

***

**Step 3:** Under **Weekly hours**, tick the days you take meetings. A ticked day starts with 09:00 to 17:00; change the start and end times as you need. A day you leave unticked reads **Unavailable**.

**Step 4:** To split a day, click **+ Add a range** on that day and set the second range, for example 09:00 to 12:00 and 14:00 to 18:00 for a lunch break. Remove a range with the icon at its end (**Remove range**).

You pick each time from a list in 15-minute steps, and the editor shows it in 12-hour format, for example 09:00 AM. Each range must end after it starts, and the ranges of one day cannot overlap. dCal tells you under the day if something is off, and does not save until it is fixed.

***

**Step 5:** To change the hours of one specific date, go to **Date overrides** and click **+ Add date override**. Pick the date and set the hours for that day.

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-cebec3d272f1b02aa953a4d893632aab4f59692e%2Fdcal-set-your-hours-03-date-override.png?alt=media" alt="The Date overrides section with one date, 30/10/2026, and a range from 10:00 AM to 01:00 PM, and the + Add date override button boxed"><figcaption><p>An override replaces the weekly hours for that specific date.</p></figcaption></figure>

* An override replaces the weekly hours of that date completely. A Friday override with 10:00 to 13:00 means only 10:00 to 13:00 that Friday.
* For two ranges on the same date, add a second override with the same date.
* Each override needs a date. A row without a date is not saved.

***

**Step 6:** Click **Save availability**. You see **Availability saved.** Saving replaces all the hours and overrides of the schedule at once with what is on screen.

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-af1afcf43e6ade37e2cb8d3ebe7a07f4c17e9a9f%2Fdcal-set-your-hours-04-save.png?alt=media" alt="The Afternoons schedule in the editor with the Save availability button boxed and the confirmation Availability saved. at the bottom right"><figcaption><p>Nothing changes on your booking pages until you save.</p></figcaption></figure>

***

## Take a day off

A date override always has at least one range of hours, so it cannot mark a whole day as unavailable. To block a full day, use your connected calendar instead: add a timed event that covers your hours that day (not an all-day event), shown as busy, to a calendar with **Check for conflicts** on. dCal then offers no times that day. See [Connect your calendar](https://docs.dapta.ai/dcal/calendars-and-availability/connect-a-calendar.md) and, for why all-day events are different, [How open times are calculated](https://docs.dapta.ai/dcal/calendars-and-availability/how-open-times-work.md#all-day-events).

***

## Choose the schedule an event uses

**Step 1:** Open **Events** and click **Edit** on the event.

**Step 2:** In **General** > **Availability**, find **Bookable hours**. Keep **My working hours** to follow your default schedule, or choose **A saved schedule** and pick a schedule under **Availability schedule**. Click **Save changes**.

The booking page of that event then offers times from that schedule, shown to each guest in their own time zone.

> **⚠️ Note:** Team events use each host's own default schedule. **Custom hours for this event** is unavailable for team events. To change when a teammate can be booked on team events, edit their default schedule. See [Round-robin, collective and fixed hosts](https://docs.dapta.ai/dcal/teams/scheduling-methods.md).

***

## Custom hours for one event

Choose this when one personal event needs different weekly hours and you do not want another shared schedule.

**Step 1:** In the event's **General** tab, under **Availability** > **Bookable hours**, choose **Custom hours for this event**. The first time you choose it, dCal copies your working hours as a starting point, without their date overrides.

**Step 2:** Set the **Time zone** for these hours. On each row, pick **Days**, then the start and end times. You can choose one day, **Weekdays**, **Weekends** or **Every day**. Use **Add hours** for another range and the remove button to drop one.

**Step 3:** Click **Save changes**. Keep at least one range; each range must end after it starts, and rows cannot overlap on the same day. If a field needs attention, the error summary takes you to it.

These hours belong only to this event and are not added to **Availability**. Your connected calendars still block busy times. To use date overrides, choose **My working hours** or **A saved schedule** instead. See [Length, location and timing](https://docs.dapta.ai/dcal/events/event-settings.md).

***

## Delete a schedule

Click **Delete** on the list or in the editor. dCal asks **Delete this schedule?** and reminds you that events using it fall back to your default availability. Confirm, and you see **Schedule deleted.**

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-4568870cbb49bca86ecd42d5ba7d68ef7e23a87a%2Fdcal-set-your-hours-06-delete.png?alt=media" alt="The Delete this schedule? confirmation dialog for Afternoons with the Cancel and Delete buttons, Delete boxed"><figcaption><p>Events that used the schedule switch to <strong>My working hours</strong>.</p></figcaption></figure>

* Events that used the deleted schedule switch to **My working hours**.
* If you delete your default schedule, the next oldest schedule becomes the default.
* If you delete your only schedule, dCal creates a new **Working hours** schedule (Monday to Friday, 09:00 to 17:00) the next time you open the dashboard, so your booking links never go without hours. To change your hours, edit the schedule rather than deleting it.

***

## Related

* [Time zones](https://docs.dapta.ai/dcal/calendars-and-availability/time-zones.md)
* [How open times are calculated](https://docs.dapta.ai/dcal/calendars-and-availability/how-open-times-work.md)
* [Connect your calendar](https://docs.dapta.ai/dcal/calendars-and-availability/connect-a-calendar.md)
* [Length, location and timing](https://docs.dapta.ai/dcal/events/event-settings.md)
* [Create an event](https://docs.dapta.ai/dcal/events/create-an-event.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/set-your-hours.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.
