Round-robin assignment
How BunnyCal picks a host, how weighting works, and how to keep distribution even.
A round-robin event type spreads bookings across several hosts. A guest sees the combined availability of everyone on the team and never chooses a person — the host is assigned when they pick a time.
How a host is chosen
Assignment happens per slot, at the moment the guest confirms:
- Eligibility. Hosts who aren’t free for the full duration (plus buffers) at that exact time are excluded. Being unavailable never costs a host their turn.
- Load. Of those remaining, the host with the fewest bookings of this event type in the balancing window — a rolling 7 days by default.
- Recency. Ties break toward whoever was assigned longest ago.
Because eligibility is evaluated before load, a host on holiday doesn’t accumulate a backlog of skipped turns that all land the day they return.
A plain rotating pointer counts offers rather than meetings, so hosts in awkward timezones get skipped repeatedly while keeping their queue position. See Round-robin that actually balances.
Weighting
Each member has a weight, defaulting to 1.0. A host at 0.5 receives roughly
half the bookings of a host at 1.0:
| Host | Weight | Share of 20 bookings |
|---|---|---|
| Priya | 1.0 | 8 |
| Marco | 1.0 | 8 |
| Dana | 0.5 | 4 |
Set weights on the team’s Members tab. Changes apply to future assignments only — meetings already booked are never reassigned.
Set a weight to 0 to keep someone on the team, and on the page as an optional
host, without putting them in the rotation.
Fixed hosts
A round-robin event can also have one fixed host who attends every meeting, alongside the rotating one — a manager sitting in on every intro call, for instance. Availability then becomes the intersection of the fixed host and at least one rotating host, which is narrower than a pure round-robin.
Reassignment
Hosts can hand a booking to a teammate from the booking’s detail view. The guest is notified and the calendar event moves. This is a manual action on a specific booking; BunnyCal never reassigns automatically after the fact.
Keeping distribution honest
The Distribution panel on the team page shows bookings per host over the last 30 days. If it looks lopsided when weights are equal, the usual causes are:
- Mismatched availability. A host with 12 open hours a week will lose to one with 30, because they’re eligible for fewer slots. Compare schedules first.
- Timezone skew. If most guests book mornings in one region, hosts elsewhere are structurally less eligible. Widening one schedule usually fixes it.
- Calendar noise. A host whose personal calendar is a conflict source and is full of all-day events will rarely be eligible. See Connecting calendars.