Sourcing - primary sources first, secondary sources second
The desk prefers primary sources for every claim: regulator publications, court judgments, operator help pages, named news outlets and trade-body working papers. Secondary sources (industry publications, consumer reviews) are used for triangulation rather than as the sole basis of a claim. Self-reported claims by the desk itself are flagged as such and avoided where a primary source is available.
Cross-checking - one other source where possible
Each claim is cross-checked against at least one other source where possible. Where cross-checking is not possible - for example, an operator's internal withdrawal SLA - the desk flags the claim as "operator-published, desk has not independently verified". Reader-shared sources are treated under the same standard.
Writing style - adult readers, plain language
The desk writes for adult readers who already know what a rummy table is. The writing avoids jargon where plain language will do, and uses jargon only where the jargon is the technical term an adult reader needs to read elsewhere (a "drop point", a "playthrough multiplier", an "RNG certification"). The desk avoids promotional framing, AI-generated boilerplate, invented urgency and emotional hooks.
Review cadence - quarterly by default
Long-form pages are reviewed quarterly for currency. Reviewer checklists focus on three questions: is the source still live, is the claim still accurate, and is the framing still appropriate. Pages that fail any of the three are updated; the update is logged on the page with the date and the nature of the change.
Corrections - 14-day turnaround on reader reports
If a reader reports a factual error, the desk investigates within 14 days. If the report is correct, a correction is published on the affected page with the date and the nature of the change. Major corrections are also surfaced on the homepage score strip for at least 30 days. The desk does not retroactively rewrite older paragraphs to soften criticism; the original framing remains visible alongside the correction.
Affiliate relationships - disclosed at the point of use
The desk has affiliate relationships with some of the platforms it covers. The relationships are disclosed at the point of use - on the page that uses the affiliate link - in plain language, not buried in a footnote. Affiliate relationships do not affect editorial coverage: the desk does not accept payment in exchange for editorial content, and the desk does not allow operators to influence editorial copy.
Image policy - editorial photography only
The desk uses editorial photography generated by AI under a documented brief that emphasises natural exposure, recoverable highlights, smooth tonal gradients and realistic colour. The desk rejects images with blown highlights, solarised or posterised tones, false-colour casts, crushed shadows or anatomically impossible subjects. The desk does not use SVG illustrations or stock vectors as substitutes for editorial photography. Each image is inspected at full size before publication.
Limitations - what the desk will not publish
The desk will not publish: fabricated payout figures, unverifiable bonus amounts, operator helpline numbers that the desk has not verified, parent-company names that the desk has not confirmed, licence numbers that the desk has not verified against the regulator's register, or "guaranteed-win" claims unsupported by mathematics. The desk will not publish guest posts, paid placements without a clear "Sponsored" label, or AI-generated content without human editorial review.
Reader feedback
Reader feedback is the desk's most useful source of corrections and source material. The contact page has a route for general inquiries, corrections, source-sharing and responsible-play feedback. The desk aims to respond within seven business days.
The methodology in practice
Three short examples of the methodology in practice. First, when the desk writes a long-form page on a new topic, the lead writer assembles a primary-source dossier, the reviewer cross-checks the dossier against at least one independent reference, and the editor reads the page for voice. The cycle takes two to four weeks. Second, when the desk reviews an existing page on the quarterly cadence, the reviewer runs the same three checks (source still live, claim still accurate, framing still appropriate) and updates the page if any check fails. Third, when the desk receives a correction request, the editor investigates within 14 days and publishes the correction on the affected page if the request is correct.
What the methodology does not cover
The methodology covers the editorial process; it does not cover the technical infrastructure of the site (server, CDN, font delivery). The desk treats the technical infrastructure as an operational concern; the editorial desk's role is to describe the editorial process, not to manage the infrastructure.
The methodology and the policy
The methodology is the operational counterpart to the editorial policy. The policy describes the editorial standard; the methodology describes how the standard is put into practice. Readers who want a quick summary should read the editorial policy; readers who want the operational details should read this page.
How the methodology changes
The desk updates the methodology when the editorial process changes. The "Updated" line at the top of this page shows the most recent change. Material changes are also surfaced on the homepage score strip for at least 30 days.
Feedback on the methodology
Readers who want to share feedback on the methodology are welcome to do so through the contact form. The desk treats feedback on the methodology under the same standard as feedback on any other page.
Where the methodology is heading
Over the coming year, the desk plans to formalise the source dossier as a public artefact on the affected page; this will allow readers to verify the desk's sourcing at a glance. The change will be announced on the homepage when it launches.
The methodology in practice
Three short examples of the methodology in practice. First, when the desk writes a long-form page on a new topic, the lead writer assembles a primary-source dossier, the reviewer cross-checks the dossier against at least one independent reference, and the editor reads the page for voice. The cycle takes two to four weeks. Second, when the desk reviews an existing page on the quarterly cadence, the reviewer runs the same three checks (source still live, claim still accurate, framing still appropriate) and updates the page if any check fails. Third, when the desk receives a correction request, the editor investigates within 14 days and publishes the correction on the affected page if the request is correct.
What the methodology does not cover
The methodology covers the editorial process; it does not cover the technical infrastructure of the site (server, CDN, font delivery). The desk treats the technical infrastructure as an operational concern; the editorial desk's role is to describe the editorial process, not to manage the infrastructure.
The methodology and the policy
The methodology is the operational counterpart to the editorial policy. The policy describes the editorial standard; the methodology describes how the standard is put into practice. Readers who want a quick summary should read the editorial policy; readers who want the operational details should read this page.
How the methodology changes
The desk updates the methodology when the editorial process changes. The "Updated" line at the top of this page shows the most recent change. Material changes are also surfaced on the homepage score strip for at least 30 days.
Feedback on the methodology
Readers who want to share feedback on the methodology are welcome to do so through the contact form. The desk treats feedback on the methodology under the same standard as feedback on any other page.
The methodology in practice
Three short examples of the methodology in practice. First, when the desk writes a long-form page on a new topic, the lead writer assembles a primary-source dossier, the reviewer cross-checks the dossier against at least one independent reference, and the editor reads the page for voice. The cycle takes two to four weeks. Second, when the desk reviews an existing page on the quarterly cadence, the reviewer runs the same three checks (source still live, claim still accurate, framing still appropriate) and updates the page if any check fails. Third, when the desk receives a correction request, the editor investigates within 14 days and publishes the correction on the affected page if the request is correct.
What the methodology does not cover
The methodology covers the editorial process; it does not cover the technical infrastructure of the site (server, CDN, font delivery). The desk treats the technical infrastructure as an operational concern; the editorial desk's role is to describe the editorial process, not to manage the infrastructure.
How the methodology changes
The desk updates the methodology when the editorial process changes. The "Updated" line at the top of this page shows the most recent change. Material changes are also surfaced on the homepage score strip for at least 30 days.
Feedback on the methodology
Readers who want to share feedback on the methodology are welcome to do so through the contact form. The desk treats feedback on the methodology under the same standard as feedback on any other page.