> 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/teams/scheduling-methods.md).

# Round-robin, collective and fixed hosts

Choose how dCal assigns team bookings: round-robin, collective or fixed round-robin. Which times guests see, how priority and weight pick the host or how Equal distribution shares bookings evenly, and

Every team event has a scheduling method. It decides which times guests can pick and who takes the meeting. This page shows how to create a team event, how to set its hosts, and exactly how dCal picks the host for each booking.

***

## Create a team event

**Step 1:** Click **Teams** in the left menu, then **Manage** on the team. Under **Team events**, click **New team event**. Only workspace owners and admins can create team events.

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-35cc22471d9534e397b77b97c4c987868e455ea4%2Fdcal-scheduling-methods-01-new-team-event.png?alt=media" alt="The Team events section of the Acme Sales page with Sales demo and Discovery call, both Round-robin, and the New team event button boxed"><figcaption><p>Team events are created from the team's own page.</p></figcaption></figure>

You can also start from **Events** in the left menu: under **Team events**, each team has its own **New event for** button, for example **New event for Acme Sales**.

**Step 2:** Fill in the event as you would any other event: title, slug, length, location, booking questions and timing. See [Create an event](https://docs.dapta.ai/dcal/events/create-an-event.md) and [Length, location and timing](https://docs.dapta.ai/dcal/events/event-settings.md).

The **Location** you choose applies to every host of the team event. When you choose **Online meeting**, the hint under it says where each booking's meeting link comes from, depending on the method you pick in step 3:

* **Round-robin:** "This location applies to every host. Each booking’s meeting link comes from the calendar where the assigned host receives new events."
* **Collective** and **Fixed round-robin:** the link comes from the calendar where one of the booking's hosts receives new events.

A host receives new events when one of their connected calendars has **Add new events here** on, in **Calendars**. When hosts are missing one, the editor shows a warning, for example "Bookings assigned to Jane Doe won’t get a meeting link." Each host sets their own calendar, in **Calendars**. The warning never blocks you: the event saves and takes bookings, but those bookings get no meeting link.

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-126218347700e3a093cc818177c2502eb7da8acf%2Fdcal-scheduling-methods-05-team-location.png?alt=media" alt="The Location block of a team event set to Online meeting, with the hint This location applies to every host and where each booking&#x27;s meeting link comes from, and below it the warning Bookings assigned to Jane Doe won&#x27;t get a meeting link"><figcaption><p>On a team event, one location serves every host. The hint tells you where the meeting link comes from, and the warning names a host whose bookings would get no link.</p></figcaption></figure>

When the editor warns depends on the method:

| Method                | The editor warns when                                                                                                                                                                      |
| --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Round-robin**       | Any host has no calendar set to receive new events. It names each of them.                                                                                                                 |
| **Collective**        | No host has one.                                                                                                                                                                           |
| **Fixed round-robin** | No fixed host has one and a rotating host has none. It names those rotating hosts. With no host ticked **Fixed** it warns as round-robin does; with every host ticked, as collective does. |

***

**Step 3:** Under **Scheduling method**, choose **Round-robin**, **Collective** or **Fixed round-robin**. A short hint under the list explains the method you picked. New team events start on **Round-robin**.

With **Round-robin**, a **Distribution** list appears right under the method. It decides how bookings are shared among the hosts:

| Option                                  | The hint under it reads                                                                                                                          |
| --------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Maximize availability** (the default) | "Offer every time any host is free; the booking goes by priority, then by load."                                                                 |
| **Equal distribution**                  | "Share this event's bookings evenly: a host 3 or more bookings ahead is not offered until the others catch up. Priority and weight don't apply." |

Every round-robin event starts on **Maximize availability**, the events you created before included. **Collective** and **Fixed round-robin** have no **Distribution** list. How each option picks the host is explained in [How dCal picks the host](#how-dcal-picks-the-host).

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-00b9cbb1b18dfc0cfd4de1ef530dc456a5160291%2Fdcal-scheduling-methods-02-method-select.png?alt=media" alt="The Scheduling method list open in the team event editor, showing Round-robin (selected), Collective and Fixed round-robin"><figcaption><p>Pick the method. Once the list closes, the hint under it explains your choice.</p></figcaption></figure>

***

**Step 4:** Set up the hosts. The **Hosts** list shows every member of the team: you do not pick hosts, every team member is one. The editor says so under **Hosts**, for example "Every member of Acme Sales hosts this event once you save it." Owners and admins also get the link **Add or remove members on the team page, then save this event.**, which opens the team's page.

* **Round-robin:** pick a **Priority** level and set a **Weight** for each host (see [How dCal picks the host](#how-dcal-picks-the-host)). With **Equal distribution**, these controls are hidden, because priority and weight do not apply. Their values are kept and come back if you switch to **Maximize availability**.
* **Fixed round-robin:** pick a **Priority** level and set a **Weight**, and tick **Fixed** next to each host who must attend every booking. Hovering the box reads **Always on every booking**.
* **Collective:** the list shows names only. Everyone attends.

**Priority** has five levels: **Lowest**, **Low**, **Medium**, **High** and **Highest**. Every host starts at **Medium**. The hint under **Hosts** sums up the rule: "Each booking goes to the free host with the highest priority; weight shares bookings among hosts at the same level."

Here a host is free when their own working hours cover the whole meeting and, at that time, they have no other dCal booking and no busy time on their connected calendar. A teammate who was invited but has not joined yet has no working hours in your workspace, so round-robin never assigns them a booking, and neither does it assign a host whose working hours do not cover the time.

The editor names the hosts who are not ready yet, in a box above the host list:

* **No working hours:** "No bookings yet, there are no working hours for:" followed by their names. On a **Collective** event it starts with "No times are offered yet." Hours are set when a person first signs in, and they can change them in **Availability**.
* **No calendar connected:** "No calendar connected for:" followed by their names. dCal does not check their busy times elsewhere, and writes nothing to a calendar of their own, until they connect one in **Calendars**.

The box is only a warning: the event saves and takes bookings either way. It disappears once every host is ready.

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-37e00845f8c2e179c5d3d08bb04af3485ce250da%2Fdcal-scheduling-methods-03-hosts-priority-weight.png?alt=media" alt="The Scheduling method set to Round-robin with its hint, and below it the Hosts section, with the line Every member of Acme Sales hosts this event once you save it, the priority hint, and Jane Doe at Priority Medium and Weight 100, the Priority control boxed in red"><figcaption><p>Round-robin: every host starts at <strong>Medium</strong> priority and weight 100.</p></figcaption></figure>

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-b738b6b541eee4dcf2209cd1c843c722dcc7e011%2Fdcal-scheduling-methods-04-hosts-fixed.png?alt=media" alt="The same editor with Scheduling method set to Fixed round-robin and the hint A fixed host always attends, plus one rotating host; in Hosts, Jane Doe has Priority Medium, Weight 100 and Fixed ticked, with the Fixed column boxed in red"><figcaption><p>Fixed round-robin: tick <strong>Fixed</strong> for the hosts who join every booking.</p></figcaption></figure>

**Step 5:** Click **Create event** (or **Save changes** on an event you are editing). The event appears under **Team events** on the team's page, and on the **Events** page under **Team events**, grouped by team.

> **⚠️ Note:** A team event takes its hosts from the team when you save it. After you add or remove a team member, open each of the team's events and click **Save changes**, so the host list matches the team.

***

## The three methods compared

|                                                                                      | **Round-robin**                                                                                                                          | **Collective**                                                | **Fixed round-robin**                                                                       |
| ------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------- | ------------------------------------------------------------------------------------------- |
| **Times guests see**                                                                 | Any time at least one host is free in their own working hours (with **Equal distribution**, a host 3 or more bookings ahead is left out) | Only times when every host is free in their own working hours | Times when every fixed host and at least one other host are free in their own working hours |
| **Who attends**                                                                      | One host                                                                                                                                 | Every host                                                    | Every fixed host, plus one rotating host                                                    |
| **Settings per host**                                                                | **Priority**, **Weight** (none with **Equal distribution**)                                                                              | None                                                          | **Priority**, **Weight**, **Fixed**                                                         |
| **Organizer** (whose calendar creates the meeting link, when it receives new events) | The host who was picked                                                                                                                  | One of the hosts, rotated fairly                              | One of the fixed hosts, picked by priority, then by fewest bookings for their weight        |
| **Host emails go to**                                                                | The host who was picked                                                                                                                  | Every host                                                    | Every host on the booking                                                                   |
| **Good for**                                                                         | Sales or support teams sharing incoming meetings                                                                                         | Panel interviews, meetings that need everyone                 | A lead who joins every call with one teammate from a rotation                               |

Two edge cases for **Fixed round-robin**:

* With no host ticked **Fixed**, it works exactly like round-robin.
* With every host ticked **Fixed**, it works exactly like collective.

***

## How dCal picks the host

When a guest books a time, dCal checks each host again at that moment (their other dCal bookings and, if connected, their calendar) and keeps only the hosts who are free then and whose own working hours cover the whole meeting. For round-robin with **Maximize availability**, and for the rotating seat in fixed round-robin, it then picks one of them:

1. **Highest priority first.** The free host with the highest **Priority** level gets the booking. Everyone starts at **Medium**. Set a host to **High** or **Highest** to send them bookings first whenever they are free, or to **Low** or **Lowest** so they get bookings only when the hosts above them are busy.
2. **Then the lightest load, by weight.** Among free hosts at the same priority level, dCal picks the one with the fewest bookings compared with their **Weight**. Weight starts at 100. A host with weight 200 takes about twice as many bookings as a host with weight 100.
3. **Then whoever waited longest.** If it is still a tie, the host whose most recent booking is the oldest gets it. A host who has never been booked counts as the one who waited longest.

A priority set through the API can be a number outside the five levels. The editor then shows it as **Custom** with the number, for example **Custom (5)**, and keeps it until you pick a level. It ranks as that number: 5 ranks above **Highest**.

> **⚠️ Note:** The booking count behind the weight includes all of a host's confirmed bookings in dCal, on any event, past and future, not only this team event. A host who is busy with personal bookings receives fewer team bookings.

### Equal distribution

On a round-robin event set to **Equal distribution**, dCal shares this event's bookings evenly instead:

1. **It counts each host's bookings of this event.** Confirmed bookings of this event count, past and future, including those a host attended while the event was collective or fixed round-robin. Bookings of other events do not count.
2. **It holds back hosts who are ahead.** A host with 3 or more bookings more than the least-booked host offers no times until the others catch up. At 2 ahead, they are still offered. Hosts who cannot offer times, such as a teammate with no working hours yet, are left out of this count, so they never hold the team back.
3. **It picks the free host with the fewest bookings of this event.** If two hosts tie, the one whose most recent booking is the oldest gets it. Priority and weight do not take part.

Guests see only the times that a host who is not held back can take, so the page can show fewer times than your hosts' full availability. Guests are never told which option the event uses. When guests book at the same moment, each pick uses the latest counts, so they do not all land on the same host. If the picked host lost that time meanwhile, the guest sees **That time was just taken.** and picks another.

For **Collective** and **Fixed round-robin**, every required host must still be free when the guest books. If one of them is no longer free, the booking does not go through and the guest picks another time.

An AI agent you connect to dCal can also find a team's open times and book with the team, and dCal assigns the hosts with these same rules. See [MCP tools reference](https://docs.dapta.ai/dcal/developers/mcp-tools.md).

***

## Where each host's times come from

* **Their default schedule.** Each host's availability comes from their own default schedule on the **Availability** page. The event's **Bookable hours** controls do not replace each team host's own hours. To change when a host can take team bookings, edit that host's default schedule. See [Set your hours](https://docs.dapta.ai/dcal/calendars-and-availability/set-your-hours.md).
* **Their connected calendar.** Busy times on each host's connected calendar block team times, using that host's own calendar settings. Team events do not have the **Calendars for this event** section that personal events have.
* **Their other dCal bookings.** A host who already has a dCal booking at that time is not free.
* **The event's own settings.** Length, minimum notice, buffers and slot interval apply to every host.

> **💡 Tip:** If a host's calendar cannot be read at the moment, dCal offers no times from that host rather than risk a double booking. On a collective event, or when that host is a fixed host, the event shows no times at all until the calendar can be read again. Keep every host's calendar connection healthy on the **Calendars** page. See [How open times are calculated](https://docs.dapta.ai/dcal/calendars-and-availability/how-open-times-work.md).

***

## After a guest books

* **Always confirmed.** Team bookings are confirmed the moment the guest books. The **Requires confirmation** box appears in the team event editor, but it does not apply to team events. If you need to approve each request first, use a personal event. See [Require confirmation](https://docs.dapta.ai/dcal/events/require-confirmation.md).
* **Emails.** The guest gets the usual guest emails. The host emails (new booking, reminders, reschedules and cancellations) go to every host assigned to the booking: the one picked host for round-robin, every host on the booking for collective and fixed round-robin. See [Who gets which email](https://docs.dapta.ai/dcal/emails/who-gets-which-email.md).
* **Calendar.** The meeting is added to the calendar of every assigned host who has a connected calendar. When the event is an online meeting, dCal creates one meeting link, on the calendar where the organizer receives new events (or, if the organizer has none, where another host of the booking does), and puts that same link on the other hosts' events. When a calendar notifies the guest at all, only the organizer's event does, never one per host. See [Who gets which email](https://docs.dapta.ai/dcal/emails/who-gets-which-email.md#the-calendar-invite). A booking with no such calendar among its hosts gets no meeting link; the editor warns you about this (see [step 2](#create-a-team-event)).
* **Rescheduling.** When the guest reschedules, the same hosts keep the booking. dCal only offers new times when every assigned host is free, and it never hands a round-robin booking to a different host. See [Reschedule and cancel](https://docs.dapta.ai/dcal/bookings/reschedule-and-cancel.md).

## Related

* [Create a team](https://docs.dapta.ai/dcal/teams/create-a-team.md): add the people who become hosts.
* [Your team page](https://docs.dapta.ai/dcal/teams/team-page.md): the public page and links guests book from.
* [Set your hours](https://docs.dapta.ai/dcal/calendars-and-availability/set-your-hours.md): each host's default schedule.
* [Who gets which email](https://docs.dapta.ai/dcal/emails/who-gets-which-email.md): the full email list.


---

# 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/teams/scheduling-methods.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.
