Menu
Browse
Best casinos
August’26Bonuses
Reviews
Slots
Free spins
Free spins by type
0$No-deposit FS Free
$+Deposit FS
↑No-wagering FS Best
🎁Free spins on signup
Popular slots
SBSweet Bonanza FS
SBStarburst FS
Guides
News
›On this page
Top 10 ranking
›Compare casinos
›How we rank
›Payment methods
›FAQ
›Editorial team
›★ See top bonus →
Showing offers for your region
Nathalie built the model behind the SlotsGamblers composite score and audits it herself. Every rank is downstream of the whole desk — Claire's RTP, Marc's payouts, Kevin's bonus EV, Andrew's RG flags — and if a casino's position moves, it moved through her code first. She'd rather a score arrive a day late than arrive wrong.
Every SlotsGamblers casino review carries one composite number. Nathalie built the system that produces it, and this is the short version of how it works — the longer write-up of how the desk tests lives in the methodology section of our About page.
The model takes the desk's 64-point reviewer checklist — licensing, games, bonuses, payments, responsible gambling — and folds every answer into a single weighted figure. Nothing enters unlabelled: each input carries the name of the desk that produced it, so a wrong number can always be traced back to its source before it reaches a published review.
Each of the five checklist categories carries its own weighting rather than an even split, because a licensing failure or a live RG issue matters more than a slow-loading game filter, and the weightings aren't fixed forever — they're the thing the quarterly audit exists to test. Before any figure is folded in, Nathalie checks it against the format the source desk actually reports in: Claire's RTP and volatility numbers arrive per-game, Marc's payout timings arrive per-method, Kevin's bonus EV arrives per-offer, so the model has to normalise all of it onto the same scale before the weighting can mean anything. A single missing input doesn't get quietly zeroed — the casino's checklist stays incomplete on her side until the desk in question fills the gap, which is usually the actual bottleneck between a review being written and a score being published.
The methodology write-up on our About page shows how the desk tests, end to end; what it doesn't show is how often a number gets sent back before it ever reaches that stage. A payout timing that's inconsistent with the same method on a different casino, a bonus EV that assumes a wagering requirement the operator's terms page doesn't actually state, an RTP figure quoted from a different game variant than the one Claire tested — these are the everyday snags, and catching them before publication is most of what "auditing the model" means day to day, more than any single formula change.
Nathalie joined SlotsGamblers in March 2026 as the Data & Methodology Auditor, brought on once the desk was fully staffed and generating enough figures across licensing, games, bonuses, payments and RG that the ratings needed a formal model instead of a spreadsheet. She came to the desk from a data-analysis background, where the job was the same underneath: take numbers from several sources, check that they agree, and be honest when they don't. She's French-Canadian, based in Canada, and her job is downstream of everyone else's — Claire's RTP figures, Marc's payout timings, Kevin's bonus EV maths and Andrew's RG flags all feed into her model, and she's the one who chases a desk when their numbers don't line up before a score goes anywhere near a review.
In practice that means she doesn't wait for a finished review to check her inputs — she pulls the raw figures straight from each desk's own notes as they're logged, so a discrepancy surfaces while the reviewer still remembers the context, not weeks later when the page is already close to publishing. The first few months on the desk were mostly building the checklist-to-score pipeline itself: turning 64 separate yes/no and graded answers into one number that a reader can trust without having to read the underlying 64 lines herself. That meant deciding, category by category, what should move a score a little and what should be able to move it a lot — a licence irregularity or an active RG complaint can cap a score outright, while a slower-than-average payout on one method nudges it.
She also owns the ongoing check on her own work: she's set a quarterly cadence for auditing the model against the operator-complaint dataset the site has built since it launched in September 2025, checking that a high score still tracks a low complaint rate and adjusting the weighting when it drifts. She's honest that the dataset is still young — under a year of complaint records — so those weightings are provisional and get revisited every audit rather than treated as settled; the first quarterly audit ran in June 2026, and it confirmed the model was broadly tracking complaints correctly but flagged that payment-speed inputs were carrying slightly more weight than the complaint data actually justified, a note she's carrying into the next audit rather than changing on a single quarter's evidence. Nothing she publishes counts as final — David still gives every review the last sign-off, but he doesn't get a score to sign off until Nathalie's model has run.
The part of the job she talks about least, but that eats the most of her week, is the chasing itself: pinging Marc for a payout timing that hasn't landed yet, or asking Kevin to re-check a wagering figure that looks off against the operator's own terms page. It's rarely dramatic — most gaps close within a day once the right desk knows about them — but she's built the habit of never filling a blank cell in the checklist with an assumption, even a reasonable one, because a guessed number is exactly the kind of thing that survives quietly in a model until an audit catches it months later. When a figure genuinely can't be sourced in time, the checklist stays marked incomplete rather than the model inventing a placeholder, and the review waits.
Nathalie's rule — no figure enters the composite score until it can be traced back to the desk that produced it, and no rank ships until the model has been checked against it. She keeps the working log deliberately dull: a source, a date, a number, nothing dressed up — it's the log she reaches for first whenever a reader or a colleague asks why a casino sits where it does.
Her model only works because every desk feeds it real, sourced figures — game testing, bonus maths, payout runs, compliance flags and fact-checking all land with her before a score reaches David's sign-off. None of the six people below report to her, and she doesn't edit their copy — her job is narrower and, in a way, harder to shortcut: take what each of them has already verified and turn it into one honest number, then be able to explain exactly why that number is what it is.
Recent work
A running log of the model changes, audits and checklist updates Nathalie has made as Data & Methodology Auditor — newest first. New work is added automatically as it happens.
Reviewed the Wild Panda Slot US: RTP, Free Play & Where to Play page prior to publication.
Reviewed the Wild Panda Slot UK: RTP, Free Play & Where to Play page prior to publication.
Reviewed the Cleopatra Slot Review UK — RTP, Free Spins & Demo page prior to publication.
Reviewed the White Rabbit Megaways Slot Review UK — RTP & Feature Drop page prior to publication.
Reviewed the Mega Joker Slot Review UK — 99% RTP & Supermeter Guide page prior to publication.
Reviewed the 50 Lions Slot Review US — RTP, Free Play & Wins page prior to publication.
Reviewed the More Chilli Pokie Review Australia: RTP, Free Spins & True Value page prior to publication.
Reviewed the Where's the Gold Slot Review US — RTP & Where to Play page prior to publication.
Reviewed the More Chilli Slot Review US: RTP, Free Games & Where to Play page prior to publication.
Reviewed the Where's the Gold Pokie Review NZ — RTP & Availability page prior to publication.
Reviewed the 5 Dragons Pokie Review Australia: 243 Ways, RTP & Where to Play page prior to publication.
No entries match .
Every rank change since April runs through Nathalie's composite model — laid out on the methodology write-up on our About page — is checked against the operator-complaint dataset and only ships after David's sign-off. Spotted an error in a review? Email [email protected] and it goes on the public log — including a note on whether the fix changed the score, since that's the part readers actually want to know.