BIG DAWG BILLIARDS
September 8, 2026
FOR IMMEDIATE RELEASE
Regarding: Session 3, 2026 — Monday, Tuesday & Wednesday Race Grid Leagues
Per my commitment to monitor and re-evaluate the Posting Caps, here are the revised Posting Caps for the remainder of 2026 Session 3:
| Night | Old Cap (Aug) | New Cap | Change | Why |
|---|---|---|---|---|
| Monday | 25 | 25 | No change | Calmest night; one flagged team, one real overpost all season |
| Tuesday | 25 | 27 | +2 | Four of six rosters were too tight without more room |
| Wednesday | 25 | 27 | +2 | Most active growth of any night; our highest-skill player was nearly unplayable at 25 |
Per that same commitment, and consistent with the procedure I followed at the beginning of the year, I will retroactively adjust all matches already played this session to reflect these caps by Sunday, September 13th, 2026.
Here’s how we got to these numbers — the original math, what we watched for, the modeling behind it, and the real match data that confirmed it.
Where We Started
When we set the caps at the beginning of 2026 for Session 1, the process was meant to be math-based from the start: evaluate each team’s mean skill level, average that across every team in the league, and divide by the number of matches to be played to arrive at the cap for that night. By the end of Session 2, though, watching the league system in action made it clear there was some real imbalance. A few things drove it: the unplanned departure of some players to other league systems; uneven growth from recruiting and from players’ own preferences about which team they’ll play for, which can limit a league operator’s ability to redistribute players to restore balance; and, underneath both of those, the lack of a fully vetted, math-based model that removes bias and preference from the equation and incorporates skill growth with real data instead of judgment calls.
Maintaining competitive balance across the league systems is one of the League Operator’s primary responsibilities (although one that never makes us very popular), and the Posting Cap is one of the tools available to help achieve that. That includes the gap between teams that can recruit higher-skill players and those that, for whatever reason, can’t, but it also covers roster stacking — when players take the position that they’ll only play if they can play alongside a particular teammate or team, the cap gives us another lever to keep that from concentrating too much skill on one roster. That kind of imbalance can have a real effect on team morale even as players compete, learn, and grow, and on how competitive a team is able to be.
Heading into Session 3, we ran that same math-based process again: look at each team’s five most-active players from last season, average their skill levels across the whole league, and multiply by five (the number of matches in a weekly meet). All three nights landed on the same number — 25 — down from 27 (Monday/Wednesday) and 28 (Tuesday) the season before, mostly because of roster turnover: some teams didn’t come back, others reshuffled, and the players actually getting fielded skewed a bit lower than the season before.
This time, though, we deliberately left growth out of the math again at the start — not an oversight, but a test: we wanted to see just how stringent the new cap would be on balance across the different leagues without it.
What the test showed: on the more growth-oriented nights, leaving growth out of the math made the cap too restrictive. That drove two changes. First, it meant acting faster than originally planned to get these revisions in place. Second, and more important long-term — growth needs to become a truly math-based part of the process itself, not a follow-up correction: going forward, every cap-setting cycle will run the full analysis, growth included, from the start.
What We Watched For
Over the next couple of weeks we kept an eye on the actual rosters as they settled in, and a few things stood out. Some teams picked up new players — including a few family sign-ups joining together on one Wednesday roster. A handful of players who were quiet last season started showing up more. And we included historical skill-level change data to determine specifically how growth played a role in evolving the aggregate skill level across the league system as a whole and within individual leagues — a clear pattern emerged: promotions have been outpacing demotions leaguewide by roughly 1.7 to 1, and that growth has NOT been spread evenly.
| Night | Promotions (12 mo) | Demotions (12 mo) | Read |
|---|---|---|---|
| Monday | 15 | 7 | Calmest of the three nights |
| Tuesday | 21 | 7 | Solid upward drift, concentrated on a couple of rosters |
| Wednesday | 26 | 11 | More promotions than the other two nights combined |
The Math: A 50,000 Foot View
Here’s the part that took the most work: for every team, we didn’t just look at their average skill level — we looked at every possible 5-player lineup a team could field from its actual roster, and checked which of those lineups would stay legal at a cap of 25, 26, 27, or 28. That gave us two things for every team: how flexible their overall roster is at each cap (how many different legal lineups they could put together), and — for teams with a clear standout, skill level 8 or higher — how often that player could actually be fielded at all without the team having to bench their four weakest players just to make room.
The standout players told the real story. A few of our highest-skill, actively-playing players were seriously boxed in at the current cap of 25:
| Player / Team | Skill Level | Legal Lineups at Cap 25 | What That Means |
|---|---|---|---|
| Jeff Acito, The Pocket Lintz | 10 | ~10% | Almost never fieldable without benching the team’s weakest four |
| Anthony Sullivan, Raising Gordizona | 8 | ~67% | Comfortable already — one reason Monday didn’t need to move |
| Bryan Chinn, Pho Cue | 8 | ~81% | Already fine, but part of a Wednesday-wide pattern |
That last point matters: it wasn’t just about single standout players. We also checked which nights had clusters of rising talent bunched onto the same rosters — a few teams with two or three players all sitting at skill level 7, one promotion away from turning into a much stronger lineup than the cap was built for. Tuesday’s Nice Rack and Wednesday’s Rack Havoc stood out here: both have multiple players on the cusp, and both would have gotten meaningfully more cramped under the old cap once those players leveled up.
Tuesday’s case for 27 isn’t about one team — it’s about roster strength across the whole night. Two of Tuesday’s six teams (Hot Shots, High I Cues) are flexible at any cap we tested, small or thin enough on high-skill players that the cap barely touches them. The other four — Straight Shooters, Hold My Pocket, Nice Rack, and Christopher Chalk’n — are the opposite story: all four were meaningfully constrained at 25 (58%-72% of legal lineups), still tight at a cap of 26 (70%-82%), and only reached a comfortable range (82%-90%) at 27. Three of those four also carry active skill-7 players one promotion away from skill 8; once those promotions land, a cap of 26 tightens further — Nice Rack down to 50% of legal lineups, Straight Shooters to 63%, Hold My Pocket to 75% — while 27 keeps all three workable (75%-83%). Tellingly, these are the same four teams that actually overposted this season at the current cap of 25 — the model, the growth outlook, and the real results all agree on which rosters needed the room.
One correction along the way: a couple of our highest-skill players on paper — including one of Monday’s two skill-9/8 players — turned out to barely play in the league at all despite being on a roster. Once we set those two aside and focused on who’s actually getting fielded, Monday’s picture looked a lot healthier than the raw skill numbers alone suggested. That’s a big part of why Monday held at 25 while the other two nights moved.
Checking It Against Real Matches
Modeling is only as good as its confirmation, so before finalizing anything we pulled this season’s actual match data at the current cap of 25 — every instance, leaguewide, where a team posted a total skill level over the cap.
| Night | Teams Overposting | Total Instances | Spread | Match to the Model? |
|---|---|---|---|---|
| Monday | 1 team | 1 | Single outlier | Yes — the one flagged team |
| Tuesday | 4 teams | 4 | Spread across roster | Yes — the same four teams |
| Wednesday | 3 teams | 3 | Spread across roster | Yes — includes Pocket Lintz & Rack Havoc |
Monday had exactly one overposting instance all season, and it landed on the one team our model flagged as the night’s hottest roster. Tuesday and Wednesday each had overposting spread across three to four different teams — not a single fluke, but a pattern showing up on multiple rosters, on the same teams the growth analysis and skill-history trend already called out. Three completely different ways of looking at the problem — the lineup math, the two-and-a-half years of skill-change history, and this season’s actual results — all pointed at the same teams and the same conclusion.
Where We Landed
Monday stays at 25, Tuesday and Wednesday move to 27 — each for the reasons laid out above, and each independently confirmed by the lineup math, the skill-history trend, and this season’s real match data. Going forward, growth is built into the standing process rather than something we correct for mid-session, which is exactly the fix Session 2’s imbalance called for.
None of this is meant to be the last word. Nice Rack on Tuesday and Rack Havoc on Wednesday both still have skill-7 players close to their next promotion, and Raising Gordizona on Monday has real momentum even though Monday’s cap isn’t moving this time — all three are worth watching as the season continues. For now, this is the number that fits where each league actually is.