Bet-Size Recaps Cut Deposit-Cap Reviews to 6 Minutes

Indian operators that switched from free-text responsible-gaming questionnaires to bet-size recap dashboards are reporting deposit-cap reviews completed in a median of 6 minutes, down from 31 minutes under the previous workflow. The figure comes from a six-month internal review across four licensed operators running on Indian-facing platforms, covering 14,820 deposit-limit review requests between January and June 2024. The mechanism is unglamorous: instead of asking a player to describe their gambling in prose, the review screen shows a compact table of their last 90 days of staking behaviour — median bet, 90th-percentile bet, session length, deposit-to-wager ratio — and the reviewer approves, adjusts, or escalates against fixed thresholds.

Why the questionnaire was the bottleneck

The pre-2024 standard for a deposit-cap review in most Indian-facing operations was a structured form: player's stated income band, stated monthly gambling budget, reason for the request, and a free-text field for "anything else we should know." That form generated three problems that compounded at the reviewer's desk.

First, self-reported income and self-reported budget rarely reconcile with actual deposit patterns. A player claiming a ₹15,000 monthly budget while depositing ₹40,000 across nine sessions in a fortnight forces the reviewer into an interrogation the player did not consent to and often cannot answer accurately. Second, free-text responses are unverifiable and inconsistent — "I want to slow down" and "personal reasons" sit in the same field but imply different risk levels. Third, and most expensively, the form captured almost nothing about actual play. A reviewer had to open a separate transaction ledger, cross-reference session logs, and mentally reconstruct behaviour before making a decision.

The 31-minute median was not a compliance failure so much as a data-plumbing failure. Reviewers were spending the bulk of that time assembling context, not exercising judgement.

The compliance cost of slow reviews

Under the self-exclusion and deposit-limit provisions that most Indian operators now apply voluntarily (and that several state regulators have begun to reference in licensing conditions), a deposit-cap request is meant to take effect promptly. A 31-minute median masks a long tail: the slowest decile of reviews in the pre-2024 dataset ran past 4 hours, and 2.3% exceeded 24 hours. During that window, players who had asked to be capped could continue depositing at their previous ceiling. That is a live regulatory exposure, and it is the reason the workflow change was funded.

What a bet-size recap actually contains

A bet-size recap is not a new data source. It is a re-presentation of data the operator already holds, compressed into a single screen that a reviewer can read in under 40 seconds.

A typical recap panel shows:

• Median bet, trailing 90 days — the central tendency, which resists distortion by a single large wager.
• 90th-percentile bet — the upper edge of normal play for that player, which is where stake escalation usually first appears.
• Largest single bet and its timestamp — useful for spotting one-off events (a cricket final, a festival promotion) versus a trend.
• Session length distribution — median and maximum, in minutes.
• Deposit-to-wager ratio — how much of deposited funds is actually staked, which separates genuine recreational play from deposit-and-withdraw churn.
• Requested cap versus trailing average deposit — the single most decision-relevant number on the screen.

Thresholds are set per operator but tend to converge. In the dataset reviewed, the most common escalation trigger was a requested cap more than three times the player's trailing 90-day median monthly deposit — a request that is either a genuine change in circumstances or a mis-set limit, and which warrants a human conversation rather than an automatic approval.

Why percentiles, not averages

Averages are the wrong instrument for betting behaviour because the distribution is heavily right-skewed. One ₹2 lakh wager on an IPL final can pull a ₹400 average to ₹9,000. The 90th percentile tells the reviewer what the player's busy day looks like without letting a single outlier define the profile. In the reviewed dataset, reviewers flagged 11% of cases using the 90th-percentile bet that would not have been flagged on average bet alone — a meaningful recall improvement on the exact population that matters.

The 6-minute review, step by step

The post-change workflow runs in four steps, and the timing data maps cleanly onto them.

1. Auto-population (0–10 seconds). The recap renders when the request enters the queue. No manual ledger pulls.
2. Threshold check (10–60 seconds). The system highlights any field breaching a configured threshold — cap-to-median ratio above 3.0, 90th-percentile bet up more than 40% quarter-on-quarter, session maximum above 180 minutes.
3. Reviewer decision (1–4 minutes). Approve, approve with a lower cap than requested, or escalate to a trained RG specialist. Escalation rate in the dataset was 8.7%.
4. Player communication (1–2 minutes). Templated confirmation with the effective timestamp and the recap's headline numbers attached.

The compression is almost entirely in steps 1 and 2. Decision time in step 3 fell only modestly, from a mean of 5.1 minutes to 4.2 — which is the correct outcome. Reviewer judgement should not be the thing you optimise away.

Where the 6 minutes breaks down

The median is 6 minutes. The 75th percentile is 11 minutes, and the 95th is 47. The tail is driven by three recurring causes: requests arriving outside specialist hours and queuing overnight; players with fewer than 30 days of account history, where a 90-day recap is mostly empty; and cases involving linked accounts or shared payment instruments, which require manual identity reconciliation before any behavioural read is meaningful.

The short-history problem is the most common and the least solved. A recap built on 12 days of play is not a behavioural profile; it is a sample too small to threshold against. Several operators in the review handled this by defaulting new-account requests to a fixed conservative cap rather than attempting a behavioural assessment — defensible, but it produces a different player experience for newcomers than for established accounts, and that asymmetry has not been tested against retention data.

What the timing number does and does not prove

A 6-minute median review is a workflow metric. It is not, on its own, evidence of better player protection. Three caveats belong in any honest reading.

Faster approval is not the same as correct approval. If thresholds are set too loosely, a 6-minute review simply rubber-stamps more requests. The dataset shows 8.7% escalation, which is plausible, but no operator in the review tracked post-review player behaviour — whether capped players actually stayed under the cap, whether they opened accounts elsewhere, whether their session lengths changed. Without that, the 6-minute figure measures operational efficiency and nothing more.

The recap privileges recent behaviour. Ninety days is a reasonable window for most players but misses the seasonal punter whose deposits spike for two months around a major tournament and flatten otherwise. A cap set against a 90-day median in a quiet period may be inappropriate three weeks later.

Self-reported context has not disappeared; it has moved. The free-text field is gone from the primary screen, but escalated cases still involve a conversation. Whether that conversation happens early enough to matter is an open question, and it is the one the timing data cannot answer.

The implication for operators is narrow and practical: the recap is a data-presentation fix, not a compliance fix, and it should be evaluated as such. The open question is whether the six-minute review, run at scale across a player base with genuinely heterogeneous behaviour, produces cap decisions that hold up when measured against what those players actually do over the following six months. No operator in this review has published that follow-up. Until one does, the 6-minute number is a claim about a queue, not about a player.