Contents:

• Overview
• Configuring Weighting on a Count-Based Pool
• Setting Weights for Pool Members
• How Weighted Distribution Is Calculated
• Weighting Example
• How Weighting Interacts with Credits and Calibration
• Default and Edge Case Weights
• How Ties Are Resolved
• Summary

 

Overview

By default, count-based round robin pools are unweighted and will pick whoever has the fewest meetings.

If you enable weighting in the pool, this changes the math so that instead of comparing raw meeting counts, the system compares each rep's meetings adjusted for their target share. A rep who's supposed to get twice the volume of meetings needs to accumulate roughly twice as many actual meetings before they are considered "caught up" to a rep with a smaller weight.

A weight is a number assigned to a pool member that represents the share of meetings that member should receive relative to the rest of the pool. Weights are set per user, at the pool level, so the same person can carry different weights in different pools.

Weighting applies only to pools where weighting is enabled. In a pool without weighting, all members are treated as having an equal share and meetings are distributed by Net Meetings alone. For definitions of Net Meetings, Calibration, and Credits, see LeanData BookIt - Meeting Credits and Calibration for Count-Based Pools.

Use Cases:

• Ramp New Team Members: Assign a lower weight to a rep who is still ramping so they receive a smaller share of meetings while remaining in the pool.
• Reflect Part-Time and Split Roles: Give reps who split their time across territories or responsibilities a share that matches their actual capacity.
• Prioritize Capacity: Give reps with more availability a larger share of the pool's meetings without creating a separate pool for them.
• Pause a Member Without Removing Them: Set a weight of 0 to take a member out of rotation temporarily while keeping them in the pool.

 

Configuring Weighting on a Count-Based Pool

To enable weighting for a pool, navigate to the LeanData App > BookIt > Round Robin > Pools and select the pool you would like to weight.

Click Edit Members, then toggle on Weighted Distribution in the upper right.

 

Setting Weights for Pool Members

Use the sliders or enter numerical values to adjust the weighting distribution for each member of the pool.

Weights are relative to each other rather than absolute. When every member has an explicit weight, a pool with weights of 100 and 50 produces the same distribution as a pool with weights of 2 and 1, because what matters is each member's share of the total. Keep the default weight of 50 in mind when some members are left unweighted, since those members are counted as 50 rather than scaling with the values you enter.

Changing a weight affects only how future meetings are distributed. It does not reset or recalculate Net Meeting counts from before the change, and counts continue to reset on the schedule configured for the pool.

 

How Weighted Distribution Is Calculated

LeanData first calculates a weight percentage for each pool member:

weight percentage = the member's weight / the sum of all member weights in the pool

Selection then compares an adjusted count rather than Net Meetings:

adjusted count = Net Meetings / the member's weight percentage

The pool member with the lowest adjusted count receives the next meeting.

Dividing by the weight percentage is what produces the proportional split. A member with a smaller share has their Net Meetings inflated more, so they reach a higher adjusted count after fewer meetings and are deprioritized sooner. A member with a larger share can receive more meetings before their adjusted count catches up.

 

Weighting Example

Consider a pool with two members:

• Alice, weight of 100.
• Bob, weight of 50.

The total weight is 150, so Alice's weight percentage is 66.7 percent and Bob's is 33.3 percent. Starting from zero meetings, the first three meetings are distributed as follows:

Meeting	Alice adjusted count	Bob adjusted count	Receives the meeting
1	0.0	0.0	Alice, by tie-breaking order
2	1.5	0.0	Bob
3	1.5	3.0	Alice

After three meetings, Alice has two and Bob has one, which matches their 100 to 50 weight ratio. Over time the pool converges on distributing meetings proportionally to each member's weight rather than equally.

 

How Weighting Interacts with Credits and Calibration

Weighting does not replace Calibration or Credits. It applies on top of them.

Net Meetings are calculated first, as Calibration plus Scheduled Meetings minus Credits. The weight percentage is applied to that result to produce the adjusted count. Because the division happens last, a Credit moves a higher-weight member's adjusted count less than it moves a lower-weight member's adjusted count.

Calibration works the same way. Increasing a member's Calibration raises their Net Meetings and therefore their adjusted count, which deprioritizes them, and decreasing it has the opposite effect.

Adjusting pool weighting does not reset counts before the scheduled reset date. It changes only how future meetings are distributed and does not affect past assignments or counts. For more on Calibration, Credits, and reset dates, see LeanData BookIt - Meeting Credits and Calibration for Count-Based Pools.

 

Default and Edge Case Weights

• Members without an explicit weight use a weight of 50. Leaving a weight unset does not exclude a member or give them a zero share.
• A weight of 0 effectively pauses a member. Their adjusted count is treated as infinite, so they are never selected in the normal flow. This is a supported way to take someone out of rotation without removing them from the pool and losing their counts.
• Weights are relative to the pool. Adding or removing a member changes the total weight and therefore every other member's weight percentage, even if their own weight value does not change.

 

How Ties Are Resolved

When two or more pool members are equally next up for a meeting, LeanData resolves the tie in this order:

1. Lowest count. The member with the lowest count receives the meeting. In a weighted pool, this comparison uses the adjusted count rather than Net Meetings.
2. Longest since last meeting. If members are still tied, the member who has gone the longest without receiving a meeting is selected. A member who has never received a meeting is treated as the longest.
3. Higher weight. If weighting is configured and members are still tied, the member with the higher weight is selected.
4. Consistent internal fallback. If members are tied on all of the above, LeanData applies a fixed internal rule that will resolve the tie the same way every time. This guarantees the outcome is deterministic rather than random.

Weighting therefore affects distribution in two places. It changes the count comparison that drives day to day assignment, and it acts as a tiebreaker when adjusted counts land exactly equal.

 

Summary

Weighted distribution lets you distribute meetings across a Count-Based Round Robin Pool in proportion to a share you define for each member, rather than evenly. Weights are set per user at the pool level, unset members default to 50, and a weight of 0 pauses a member without removing them from the pool.

For additional assistance please submit a ticket to LeanData Support.