Where the duty ends
An operator protection duty is bounded, and pretending otherwise is how it gets blamed for things it cannot do. It covers the play it can see, on the account it holds, for as long as the account is open. It does not follow a player to another operator, it cannot force treatment, and it is not the body that polices the licence. Knowing where the boundary sits is what tells a player which organisation can actually help with what.
- who can act
- 5 bodies
- accounts the operator sees
- 1 of 40,000
- patterns split across accounts
- 72
- regulator action
- not a protection response
- support routes
- outside the operator
- review records kept
- 4,000
Read the signals
Five comparisons the account already supports, run continuously rather than after a complaint. 6,000 flags in the sample, 96.0% of them relative to the account own history.
Choose a response
Nothing, a message, a limit or a break, or a restriction - one of four, graded by how much it takes from the player. 960 of 4,000 reviews in the sample changed access.
Write it down
Signals, crossing dates, rule version, path, response and outcome - one record per review, including the 1,600 that ended with nothing done.
Take the appeal
A route outside the desk that decided. 480 appeals in the sample, 176 of them upheld, which is 36.7% - high enough that the route does real work.
A protection duty is bounded by what the operator can see: its own accounts, its own play data, for as long as the account is open. It cannot read play at another operator, force treatment or police its own licence. So the operator handles the account, the regulator handles the licence, the support charities handle help, the bank handles payments and a clinician handles health - and no single one of them does another job.
One account is one account
The clearest edge of the duty is that the operator sees one account. A player with accounts at four operators produces four partial pictures, and a pattern that is spread across them is invisible to each one. Sample H is this desk attempt to put a number on the gap: of the 360 accounts in the sample that should have met a trigger and did not, 72 (20.0%) were missed because the pattern was split across two accounts, neither of which reached the rule alone.
That is not a defect an operator can fix, and it is the honest reason a protection duty cannot be described as a safety net. It is a rule set reading what it holds. A player whose play spans several operators has, in a real sense, play that no single protection rule is written to see.
Who does what
| Body | What it handles | What it cannot do |
|---|---|---|
| The operator | the account: signals, reviews, limits, breaks, restrictions and the record | see the player other accounts, or order treatment |
| The regulator | the licence: whether the operator is meeting its conditions at all | take an individual decision about one account |
| A support charity | help for the player and the people around them, free and confidential | change an account, a limit or a break |
| The bank | payments: blocks, declines and disputes over money that moved | read gambling patterns for protection |
| A clinician | health: assessment, treatment and support | act on an account at all |
The middle row is the one most often misdirected. A regulator does not decide a single account, so a complaint to one about a limit will usually be routed back to the operator appeal route first. The regulator matter is whether the operator had a policy and followed it - which is exactly what the record on the record page is for.
A worked map of one situation
Consider a player whose spending has risen over a month and who has just been placed on a seven-day break they do not agree with. Four things are in play at once, and each has a different owner. Separating them is what turns a confusing week into a set of concrete steps.
- The account: ask the operator for the record - the rule, the signals and their dates - and use the appeal route it named.
- The money: check any pending withdrawal with the operator first, then the bank if a payment is stuck; the break is not a payments matter.
- The licence question: if the operator will not say which rule it applied or keeps no record, that is a matter for the regulator, not for the appeal.
- The player: support routes are independent of all of the above and do not require an appeal to have failed first.
- The future: a declared affordability band is the one input the account holder controls, and updating it changes what the rule reads next time.
- 2,400 contacts in the sample carried a named route to respond; that route is step one.
- 176 of 480 appeals were upheld, so step one is worth taking even on a decision that looks final.
- 360 of 36,000 accounts went unreviewed, 72 of them because the pattern was split across accounts - step four matters whether or not any rule ever reads the player.