Collective event scheduling

Short answer: Offer times when every required host can attend. Begin with “Add every host whose presence is required.” 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

Add every host whose presence is required.Start with the intended outcome and the record that controls it.
Confirm each host's conflict calendars and working hours.Review every related setting before saving so one rule does not mask another.
Inspect the combined availability for a realistic booking window.Keep private data and guest-facing information clearly separated.
Test what happens when one host declines or disconnects a calendar.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 collective event scheduling

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

Almost no times are available.

This is expected. Requiring three or more calendars to overlap shrinks availability sharply — reduce required hosts, widen the window, or make some attendees optional.

One host's calendar is not being considered.

Confirm that host is listed as required and that their conflict calendars are connected. A missing connection silently makes them look free.

A required host declined after confirmation.

Decide in advance whether the meeting proceeds or is rescheduled, and who communicates that. Panel interviews need this rule written down.

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.

Collective event 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. Add every host whose presence is required.

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. Confirm each host's conflict calendars and working hours.

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. Inspect the combined availability for a realistic booking window.

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. Test what happens when one host declines or disconnects a calendar.

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

Collective event scheduling: frequently asked questions

Short answers to the questions organizers ask most about collective event scheduling.

What is a collective event?

A meeting offered only where every required host is free at the same time — panel interviews, joint reviews, and multi-specialist calls.

Why is so little availability offered?

Requiring several calendars to overlap shrinks availability sharply, and that is the correct behavior. Reduce required hosts, widen the window, or make some attendees optional.

How is this different from round robin?

Round robin needs any one eligible host; a collective event needs all of them. The same host list produces very different availability under each rule.

What if a required host becomes unavailable?

Decide the rule before you publish: either the meeting proceeds without them or it is rescheduled. Name who communicates the change.