Soft2Bet sets out activity-based model for responsible gambling monitoring
Operator-level baselines and combined activity signals drive flagging and review prioritisation.

Key Takeaways
- Soft2Bet published its activity-based responsible gambling monitoring framework on 13 October 2026.
- The company uses an individual baseline per account to make deviations contextual rather than applying universal thresholds.
- Multiple operator-derived signals—intensity, frequency, variability and deposit changes—are interpreted together to set review priority.
- Automation is used for flagging and prioritisation but not for making final assessments; human review remains required.
Soft2Bet published a detailed framework on 13 October 2026 explaining how it converts changes in player activity into review priorities for responsible gambling monitoring. The company treats each account’s history as an individual baseline, detects deviations across multiple signals and keeps detection and final review as separate stages in the workflow.
Individual baselines as the starting point for responsible gambling monitoring
Soft2Bet builds a reference point for each account from that player’s usual history and recent activity. Current sessions, deposits and stakes are compared against this individual baseline rather than against a single universal threshold. The vendor argues identical raw figures can carry different significance across two accounts because of differing underlying patterns, so the baseline makes any deviation contextual.
The elements Soft2Bet highlights for forming an individual baseline include:
individual markers that define a typical account profile
intensity, meaning typical stake sizes or session expenditure
frequency, covering deposit cadence and session count
variability, the normal spread of behaviour over time
Soft2Bet is explicit that the baseline is not a rigid boundary between “usual” and “unusual.” The baseline’s role is to reveal change relative to the account’s own history. Detecting a deviation creates a signal; it does not on its own determine a final assessment.
Activity signals and how they are grouped for monitoring
Soft2Bet treats signals as a set to be interpreted in context rather than as discrete checklist items. Operator-derived data feeds into categories that include gambling intensity, frequency, variability and deposit-related changes. Time-based indicators such as session length and playing hours are used to identify shifts in timing and session duration.
The framework also incorporates account-context indicators: changes to responsible gambling controls and a player’s reactions to prior contact. Those items are recorded and viewed alongside behavioural signals rather than given predetermined weight.
Soft2Bet says several signals often co-occur and that co-occurrence can raise the priority of a case. A change in session pattern alone might be immaterial, but when combined with increased frequency or a spike in stake size the deviation becomes more noticeable under their model.
From signals to meaningful patterns: strength, repetition and combination
Signal significance is determined by strength, frequency and repetition. A single weak or one-off deviation is treated as limited in significance if it genuinely falls outside the account’s usual range. Recurring patterns point to a stable change. Multiple indicators that coincide provide a fuller account context for human reviewers.
Even so, Soft2Bet accepts a single pronounced or unusual indicator can be sufficient to trigger further review if account context warrants it. That balance creates a connection in the model between signal interpretation and review priority rather than a rigid severity category.
How monitoring supports review prioritisation in practice
Soft2Bet sets out a three-step operational chain for turning a detected activity change into a review decision:
gather relevant evidence around the activity change
compare the evidence against the account’s individual baseline
determine whether the case merits further human attention
Automation supports monitoring, automated flagging and prioritisation. Automation reduces the number of cases requiring human intervention by surfacing those with the strongest or most persistent deviations. Automation does not deliver a diagnosis; it elevates cases for human assessment and preserves the separation between detection and interpretation.
The model requires a shared player record where relevant activity, changes to controls and prior contacts can be collected. Where that information is available, the combined record forms the evidence context reviewers use to set review priority.
Preserving the boundary between detection and assessment
Soft2Bet’s model emphasises that unusual action is a prompt for contextual assessment rather than proof of harm. Detection creates grounds for review, evidence forms the context and review determines the next steps. The company keeps the operational review and specialist assessment separate: a flagged case leads to further data-gathering and human interpretation, not an automatic judgement.
That boundary is practical. It ensures monitoring focuses on building a meaningful context before any decision about interventions is made, and it limits automated systems to triage and prioritisation rather than final determinations.
Implications for operators and suppliers
For licence-holding operators, the model presumes access to rich operator-derived data and a shared player record that links activity signals with control changes and prior contact history. Vendors supplying monitoring, analytics or CRM systems will be expected to support:
creation of individual baseline profiles for each account
multi-signal correlation and time-based analytics
automation for flagging and prioritisation while preserving human review workflows
Operators that implement this approach will need to ensure their data pipelines capture deposit frequency, stake data, session timing and record control changes and outreach responses. The practical outcome is fewer automated actions and more targeted human reviews based on contextual evidence.
Where this sits in the compliance toolkit
Soft2Bet positions its framework as a decision-support model for responsible gambling monitoring: it converts activity change into review priority, not into final assessments. The approach preserves human judgement, relies on account-specific baselines and treats signals in combination rather than in isolation. That is the company’s prescription for turning operator data into reviewable cases without automated diagnoses.
Frequently Asked Questions
What is Soft2Bet’s core method for detecting risky behaviour?
Soft2Bet compares current activity against an individual baseline for each account to detect deviations. The baseline is built from a player’s history and recent activity and covers markers such as intensity, frequency and variability, so identical figures can mean different things for different accounts.
Do multiple signals need to appear before a case is flagged?
No, a single pronounced or unusual indicator can be enough to trigger further review if account context warrants it. Soft2Bet evaluates strength, frequency and repetition, and combines signals when they co-occur to increase review priority.
What role does automation play in Soft2Bet’s monitoring model?
Automation supports monitoring, flagging and prioritisation but does not make final assessments. Automated processes reduce the caseload for humans by surfacing the strongest or most persistent deviations, after which human reviewers gather evidence and interpret the situation.
Tags
About the author

Marcus Webb
Industry Deals Correspondent
Marcus Webb covers the deal flow of the gambling industry — operator strategy, M&A, market entries, and product launches from sportsbook rebrands to full platform migrations. The reports name the companies, valuations, and jurisdictions exactly as disclosed and separate the announcement from its market impact. When a group consolidates a brand or a challenger launches into a new state, Marcus Webb explains who gains, who pays, and what closes next quarter.
More from Marcus Webb








