Shared, Local and Must-Drop Jackpots: What the Pool Actually Commits To
A jackpot counter is not a prize fund the operator has set aside. It is a seed plus a contribution rate, accumulating across whichever pool the operator has joined, and the rules of that pool decide everything that matters about it — including whether a 'drops before' line is a commitment or a description.
On this page
What has to be disclosed, and where
RTS 9 of the remote gambling and software technical standards covers progressive jackpot systems, with the stated aim of ensuring they operate fairly. Requirement 9A is short: "An explanation of the jackpot rules must be clearly available to the customer before they commit to gamble."
The implementation guidance is where the substance is, and it lists what that explanation has to cover:
- How the jackpot is funded, including the start-up seed and any ceiling values.
- The return to player percentage, under RTS 3C, either as one combined game-and-jackpot figure or broken down into base game and jackpot components.
- Who is eligible to win, and the respective theoretical return to player for a player who is not eligible.
- How prizes are determined and awarded, including how simultaneous triggers are handled.
- The current jackpot value, updated as frequently as is practicable, particularly after the amount has been reset following a win.
- Where a jackpot is capped at a ceiling value, how subsequent player contributions are handled.
Requirement 9B adds that jackpot systems must be configured and operated with adequate fairness and security, with strict access and logging controls over configuration and over changes made to live jackpots.
Two lines in that guidance answer most of the questions players actually have.
Eligibility, and the stake that buys it
The guidance states that where a customer contributes to a jackpot pool, that customer should be eligible to win the jackpot while they are playing that game — and that the chance of winning should increase in correlation with the amount contributed.
That is the honest form of the "you must bet max to win the jackpot" folklore. A player contributing to the pool is to be eligible; a larger contribution is to carry a larger chance. Where a game has an eligibility condition at all, the rules must say so, and they must also state the theoretical return for a player who does not meet it — because a player outside the jackpot is playing a materially different game from one inside it, at a lower effective return.
Why the same title shows a different number on two sites
Because it is a different pool. A progressive can be run as a network pool shared across many operators, or as a local pool confined to one site, and a title can be deployed either way. A shared pool grows faster because more play feeds it; a local pool grows more slowly and resets to its own seed. Neither is more generous per spin — the contribution rate and the seed, both of which RTS 9A requires to be disclosed, are what determine the arithmetic.
The figure on the counter is therefore not a comparison between operators. It is a statement about how much play has gone into that particular pool since it last reset.
Must-drop conditions
A jackpot described as dropping before a date, a time or an amount is operating under a condition written into its own rules. The route to understanding it is the same route as everything else here: RTS 9A requires the explanation of the jackpot rules, including how prizes are determined and awarded, to be clearly available before the player commits.
What a must-drop condition does not do is improve the value of an individual spin as the deadline approaches. The condition describes when the pool must be awarded; it says nothing about which player receives it, and a pool that is close to its ceiling or its deadline carries no better chance for the next spin than it did the day before. A larger pool is a larger prize, not a shorter odds.
When a jackpot game is withdrawn
This is the scenario nobody thinks about until it happens, and the standards address it directly. Where a jackpot is decommissioned while player contributions sit in the pool, the guidance names the acceptable approaches: waiting for the next award, transferring the contributions to a similar pool, or returning the remaining contributions as a one-off event with adequate customer disclosure. On an award, the winning customer is to be notified immediately and other participants informed of the reset value.
So a withdrawn game does not simply absorb the accumulated contributions, and the operator does not have a free choice about what to do with them.
8 of 17
8 of 17
13 of 17
5 of 17
Counted across the 17 licensed sites in our own pool.
Frequently asked questions
Does betting the maximum improve the chance of winning a progressive jackpot?
The implementation guidance for RTS 9B states that the chance of winning should increase in correlation with the amount contributed, and that a customer who contributes to a pool should be eligible to win while playing that game. Whether a particular game has an eligibility threshold, and how the chance scales, is in that game's jackpot rules, which RTS 9A requires to be clearly available before play.
What happens to the pool if the game is removed?
The guidance sets out acceptable methods for a decommissioned jackpot that holds player contributions: waiting for the next award, transferring the contributions to similar pools, or returning the remaining contributions as a one-off event with adequate customer disclosure.
Is a must-drop jackpot guaranteed to pay by the stated time?
The condition is part of the game's published jackpot rules rather than a schedule the operator publishes separately, and those rules are what state how and when the prize is determined and awarded. The condition concerns the award of the pool; it does not identify a recipient in advance and does not change the chance attaching to any individual game cycle.