Meet Claire Wilson, our slots & games reviewer.

Claire's remit is narrow on purpose: game verification. When David built the founding desk in September 2025, she came on as one of the first two specialists, alongside Andrew, to own the side of the review that no spreadsheet can fake — does the game exist, does it play the way it's described, and does its RTP match the studio's own published figure. Her working knowledge is provider-deep rather than casino-wide: the studios she checks against source most — Pragmatic Play, NetEnt, Play'n GO and Hacksaw Gaming on the slots side, Evolution on live-dealer — are the ones whose published RTP and release data she reconciles game by game, title by title, rather than trusting a provider's own summary sheet to be current.

She runs the games desk directly, and it's a desk, not a solo act. The rule the desk holds to is that every slot listed on SlotsGamblers is opened and played before it earns a place — by Claire or by a games-desk tester reporting to her, never pulled straight from a provider's catalogue and republished as fact. That distinction matters more than it sounds: an operator's lobby feed and a provider's own release list frequently disagree, and the gap is usually where a stale RTP figure or a quietly retired title is hiding. Claire personally handles the calls that decide a rating: RTP-versus-source reconciliation, white-label spotting, and any figure that's disputed on replay. A dispute isn't rare — a game can post a different session RTP on a second run for reasons that have nothing to do with the published theoretical figure, and part of her job is knowing which variance is normal volatility noise and which is a listing worth re-opening.

Live-dealer studios get the same treatment — she keeps a running coverage map of which rooms are actually live, hosted by whom, and under which licence, because a studio's branding on the lobby tile doesn't always match who's dealing the cards behind it. Findings go to David for final casino sign-off, and her RTP data feeds directly into Nathalie's scoring model — if a game's numbers move the site's rating, they moved through Claire's desk first. That link between the games desk and the scoring model is deliberate: Nathalie's composite score treats RTP accuracy as one of its heavier-weighted inputs, so an unverified figure from Claire's side would distort every operator's rating downstream of it, not just the one review it appeared in.

Based in Leeds, she covers slot libraries across GB, CA and US operators, which in practice means the same provider's game can show up under three different licensing regimes with three different published RTP tables — a detail that gets missed when a review is written from a single market's lobby. Every RTP claim she publishes has already been through Helen's fact-check against the provider's own source, and she won't sign off a library audit on a replay that doesn't match the first pass — if a number looks off, the game gets opened again before it goes anywhere near a review. On a typical audit pass she'll re-open a handful of titles a second or third time before she's satisfied a figure is stable enough to publish, and any title that still won't settle gets held out of the review rather than listed with a caveat.

Volatility is the part of the audit that's easiest to state wrong from a provider's one-line summary, and it's where Claire spends time most reviewers skip. A studio's own classification — low, medium, high — is a starting point, not an answer; two titles both marked "high volatility" by the same provider can play very differently in practice, one paying in frequent mid-size hits and the other sitting dry through long stretches before a large bonus round. She notes the actual hit frequency and swing she observes in play alongside the provider's stated figure, so a review isn't just repeating a marketing label back to the reader. That distinction feeds directly into how a title gets described in a casino review — "high volatility" on its own tells a player almost nothing about what a session will actually feel like, and a review that stops at the label is repeating marketing copy rather than describing the game.

The desk doesn't work in isolation from the rest of the site. When Kevin is modelling a welcome offer's expected value, the wagering requirement's effective difficulty depends partly on which games count toward it and at what contribution rate — so Claire's library data on volatility and RTP feeds his bonus maths as much as it feeds Nathalie's scoring model. And when Andrew's compliance checks turn up a licensing question tied to a specific game studio, it's Claire's provider map that tells him whether the badge on the lobby tile matches who's actually licensed to operate it. None of this is formal handoff documentation — it's the same small desk checking each other's work, day to day, because the site's numbers only hold together if they agree with each other.

The GB, CA and US split isn't cosmetic either. A game cleared for the UK market under a UKGC-licensed operator's RTP disclosure requirements isn't automatically the same build running on a Curaçao-licensed skin serving Canadian or US players — sometimes it's an older version of the same title, sometimes the RTP genuinely differs by region because the operator has configured a different volatility profile. Claire treats each market's lobby as its own audit rather than assuming a UK finding transfers cleanly to a US-facing operator, which is slower than auditing once and republishing three times, but it's the only way the RTP figure on a US-facing review is actually the figure that US-facing lobby is running.

A new studio entering an operator's lobby gets a different, slower pass than an established one. With Pragmatic Play or NetEnt, Claire is largely reconciling against a track record — the studio's published RTP figures for its back catalogue have already been checked repeatedly, so a new release from them is mostly a matter of confirming the specific title matches its own spec sheet. A studio she hasn't audited before gets treated with more suspicion by default: she checks whether it holds its own licence or is operating under someone else's umbrella, whether its published RTP figures are even publicly available in the first place, and whether the titles it's supplying actually run its own engine or a licensed third-party framework wearing its badge. Several "new" studios that have shown up in operator lobbies over the past year turned out, on inspection, to be a licensing or distribution arrangement rather than an independent developer — which changes how the review credits the game, even when nothing about how it plays is misleading.

She also keeps half an eye on what happens to a title after it's first listed. A provider can quietly revise a game's RTP configuration post-launch — sometimes disclosed in a changelog, sometimes not — and an operator's lobby doesn't always flag when the version running has changed. Part of the games-desk audit routine is re-opening titles the site has listed before, not just new ones, on a rolling basis, precisely because "verified once" isn't the same guarantee as "verified as of today." A review that hasn't been revisited in months is treated as due for a re-check rather than assumed still accurate.

None of this is meant to read as adversarial toward providers or operators — most published RTP figures Claire checks turn out to match what's actually running, and most lobbies are honest about what they carry. The point of the desk is that "most" isn't good enough for a rating a reader is using to decide where to play real money. The audit exists for the minority of cases where a figure has drifted, a title is mislabelled, or a game simply isn't there — and finding those before publication is the entire reason the games desk exists as a separate role from the review itself, rather than a step folded into David's own write-up.