What supports this guide’s conclusions?

A sound conclusion rests on a clear written condition, a careful reading of what that condition means, and a recommendation that follows from it. Those are separate steps: a promotion’s stated requirement is not the same as an interpretation of that requirement, and neither automatically becomes a promise about your result.

A conclusion should begin with an explicit rule, term or feature that can be identified in the subject being assessed. The next step is to explain its practical meaning for you without adding a benefit, restriction or outcome that is not stated.

The recommendation then follows from that interpretation. For example, a condition may describe eligibility, a wagering requirement or a withdrawal process; the conclusion should explain how that affects a player’s decision. You can read the bonus discussion for a practical example of separating a written offer from its interpretation.

Research means examining written conditions, product information and provisions. Testing means observing what happens during an actual action, such as completing a transaction.

These activities answer different questions. Written material explains the stated process and terms; an observed transaction shows how that process worked in one instance. The withdrawal discussion explains the distinction in the context of sending money out.

Give the most weight to a conclusion when it is relevant to your question, tied to the conditions that apply, and clear about when those conditions were in force. A conclusion should guide a decision, not replace your judgement.

• Relevance: It addresses the feature or task you care about.
• Applicable conditions: It uses the rules that govern that feature.
• Timing: It reflects the terms connected to the decision.
• Individual outcomes: One result does not become a general promise.

The about page provides more context about the publication and its role as an independent guide.