None of those elements has to be deceptive to create pressure. Put together, however, they turn one sporting event into a queue of small decisions. The product is not only a market on the match. It is an interface competing to decide what the customer notices next.
One screen contains several clocks
A television or app stream, the event data feed, the trader’s market state and the customer’s device do not update at the same instant. That makes “live” a convenient label rather than a shared timestamp.
The British Gambling Commission’s remote technical standard for in-play betting requires operators to tell customers that broadcasts described as live may be delayed and that others may have more up-to-date information. It also requires disclosure where the operator deliberately builds a delay into an in-play bet. RTS 15 sets out those information requirements.
The notice matters, but placement matters too. A disclosure below the market explains the legal and technical condition. The moving price, coloured score event and enabled button still command immediate visual attention. Compliance text and interaction design can therefore send different signals at the same moment.
Our explainer on the live sports data pipeline follows the journey from venue collection to screen. Each hand-off can change latency and confidence. The interface receives the end of that chain, then asks the customer to act before the chain changes again.
The attention stack
A modern in-play product can combine several functions that once lived in separate places:
| Interface layer | Useful job | Attention pressure |
|---|---|---|
| Stream or match visualisation | Shows the event context | Makes leaving the betting screen feel like leaving the match |
| Score, clock and statistics | Compresses event information | Creates a continuous sequence of new cues |
| Moving markets and odds | Shows current availability and price | Turns change itself into a reason to look again |
| Cash-out control | Offers an exit price on an open position | Adds a second live decision after the original bet |
| Prompts and cross-sells | Points to another market or event | Replaces a natural pause with a new action |
The table does not say that every layer is harmful. A clear score and visible market state can reduce confusion. A cash-out option can let a customer close exposure. A suspension indicator can prevent a stale price being accepted.
The design question is cumulative: how many simultaneous cues are asking for action, and does the interface preserve enough context for a considered decision?
Suspension is a message, not dead time
When important play occurs, an operator may suspend a market while its data and trading systems catch up. The button becomes unavailable, but the screen often continues moving around it.
Our guide to sportsbook market suspension explains why a pause can be a risk control rather than a technical failure. In interface terms, suspension also creates a brief interruption. The product can use it to explain what is happening, or cover it with more markets, countdown-like animation and prompts.
That choice is revealing. A system designed around informed state shows that the price is unavailable and why the status may change. A system designed around uninterrupted action treats any pause as inventory to fill.
What the research can—and cannot—say
Research on in-play betting has repeatedly examined the relationship between fast, continuous product features and gambling harm. It does not support the claim that one interface control causes an individual to develop a gambling problem.
A 2019 scoping study reviewed the emerging literature on in-play sports betting and highlighted structural characteristics such as speed and the opportunity to make many bets during an event. The review in the International Journal of Mental Health and Addiction is useful for mapping the concern, while its authors also describe limitations in the evidence base.
A PLOS One study later considered features including live streaming, statistical displays, cash out, instant deposits and the ability to place concurrent bets. The 2022 paper examined associations between feature use and measures of emotional or cognitive dysregulation among sports bettors. It was not a controlled test of a single screen design.
A 2026 case-control study compared 85 higher-risk and 84 lower-risk sports bettors and reported differences in the use of live-betting features, including in-play betting, cash out and streaming. The Journal of Behavioral Addictions paper strengthens the case for examining the feature bundle, but it still reports associations. People already experiencing harm may use the features differently; product exposure and user vulnerability can also interact.
That distinction protects the reporting from two bad shortcuts. “The science proves this button is addictive” goes beyond the study design. “There is no causal proof, so design does not matter” ignores a consistent risk signal and the operator’s duty to monitor customer behaviour.
The interface sees behaviour the headline cannot
An operator can observe patterns that no generic warning can describe: sessions lengthening, deposits following losses, rapid changes in spend, repeated rejected deposits, movement across products and attempts to reverse or cancel withdrawals.
The Gambling Commission’s formal remote-customer-interaction guidance requires licensees to use a range of indicators to identify gambling harm and to act in a timely way. Requirement 1 of the guidance is deliberately broader than a list of interface events.
The implication for product teams is uncomfortable but useful. A feature cannot be judged only by aggregate engagement. The same event stream used to optimise the betting journey can identify when the journey should slow down, change or stop.
The Commission’s in-play betting guide also places in-play products inside the wider customer-monitoring framework. It does not prohibit live betting. It makes the speed and frequency of the interaction relevant to how operators assess risk.
What calmer live design would make visible
“Calm” need not mean dull or unusable. It means that important states retain priority over prompts. A defensible interface would:
keep the event, market period and settlement basis visible;
distinguish stream time from the betting system’s market state;
explain suspension without manufacturing a countdown;
show cash out as a changing offer, not a guaranteed right or fixed value;
preserve deposit limits and safer-gambling controls inside the live journey;
stop promotional prompts from competing with risk or account messages;
let the customer leave a market without immediately substituting another one.
These choices can be tested. Teams can measure comprehension of delayed streams, mistaken attempts on suspended markets, acknowledgement of changing cash-out values and whether risk interventions are actually read. “Time on screen” is not enough evidence that the screen works well.
The fastest part of live betting is not always the bet. It is the replacement of one decision with the next. A responsible interface gives the customer a stable account of what is happening before asking for another action. In a product built from moving signals, clarity has to hold still.
