Configure round robin scheduling

Short answer: Balance bookings fairly across an available team. Begin with “Choose eligible hosts and define the availability each contributes.” and verify the result through the public participant path.

Before you change the setup

Identify the exact organizer, event type, public link, and time zone involved before editing anything. Save the current behavior or take a screenshot so the test has a reliable before-and-after comparison.

How to complete this task

Choose eligible hosts and define the availability each contributes.Start with the intended outcome and the record that controls it.
Select a distribution rule and decide how existing ownership behaves.Review every related setting before saving so one rule does not mask another.
Test equal availability, no availability, and an absent team member.Keep private data and guest-facing information clearly separated.
Review assignment outcomes instead of assuming equal booking counts.Complete the same path an external participant will use.

Verify the participant result

Run one successful case and one edge case. Confirm the public title, local time, available choices, duration, location, confirmation, calendar file, and private management path as applicable. Then check the organizer view and any email delivery record. A saved setting is not proof that the scheduling lifecycle worked.

Troubleshoot configure round robin scheduling

These are the failures reported most often for this specific task, with the cause that explains each one.

One host receives most bookings.

Distribution follows availability. A host who publishes more open hours will absorb more meetings regardless of the rule — compare contributed availability before changing the algorithm.

A host on leave is still being booked.

Their availability was not removed. Round robin distributes among eligible hosts; eligibility has to be withdrawn explicitly.

No times appear when several hosts are eligible.

Check whether the rule requires all hosts rather than any host. That is collective scheduling, and it produces far narrower availability.

Related Meetin.gs help

Return to the Meetin.gs Help Center for the adjacent configuration guide, or send the exact event code and expected result when the documented checks do not explain the behavior.

Configure round robin scheduling acceptance checklist

Use the following evidence map while completing this specific task. It ties each action to an observable result so another person can repeat the setup or diagnose it without guessing.

1. Choose eligible hosts and define the availability each contributes.

Write down the intended result, the organizer or account that owns it, and the exact event type or public link in scope. This prevents a correct change from being applied to the wrong record.

2. Select a distribution rule and decide how existing ownership behaves.

Inspect the related rules and dependencies before saving. Record the previous value and the new value, including the time zone, provider account, or team owner when one controls the outcome.

3. Test equal availability, no availability, and an absent team member.

Review what an invitee can see and what remains private. Keep only the context needed to complete the meeting task, and make the fallback understandable when information is missing.

4. Review assignment outcomes instead of assuming equal booking counts.

Complete this step from a signed-out participant session. Preserve the resulting URL or event code, displayed state, message, calendar output, and any provider response needed to prove the task worked.

Evidence type	What to record
Controlling input	The account, event type, setting, public link, and time zone used in the test.
Participant result	The exact choices, context, confirmation, or error visible while signed out.
Lifecycle result	What changes after confirmation, finalization, cancellation, reschedule, or retry.
Failure boundary	The missing permission, unavailable dependency, invalid input, or conflicting rule that prevents success.
Owner	The person responsible for correcting the setting, provider connection, content, or customer communication.

Evidence type

What to record

Controlling input

The account, event type, setting, public link, and time zone used in the test.

Participant result

The exact choices, context, confirmation, or error visible while signed out.

Lifecycle result

What changes after confirmation, finalization, cancellation, reschedule, or retry.

Failure boundary

The missing permission, unavailable dependency, invalid input, or conflicting rule that prevents success.

Owner

The person responsible for correcting the setting, provider connection, content, or customer communication.

RELATED CAPABILITY

Team scheduling

Support collective hosts, pooled availability, group sessions, and fair round-robin distribution. This page explains team scheduling requirements. Confirm production availability before depending on this capability.

Review scope

Configure round robin scheduling: frequently asked questions

Short answers to the questions organizers ask most about configure round robin scheduling.

How does round-robin scheduling assign meetings?

It offers the combined availability of eligible hosts and assigns each booking to one of them according to a distribution rule such as equal share, availability, or priority.

Why does one host get more meetings?

Because they publish more open hours. Distribution follows availability, so compare contributed hours before concluding the rule is unfair.

What happens when a host is on leave?

Remove their availability or their eligibility. Round robin keeps assigning to anyone still eligible, so absence has to be expressed explicitly.

Should round robin override account ownership?

No. Check ownership first and route known accounts to their existing owner; use round robin only for genuinely unassigned demand.