guide
Build a broker evidence file that another reader can reproduce
A document-control workflow for recording claims, preserving source versions and keeping unresolved regulatory or contract mismatches visible.
By Betsafe Reviews Editorial Team ·
Updated Oct 5, 2026
- Source
- Finding
- Open question
A useful evidence file is not a folder of logos and screenshots. It connects each material statement to a source, an account scope and an observation date, so another reviewer can follow the same path. Betsafe Reviews uses this document-oriented approach to distinguish what a record establishes from what an editor still needs to ask.
01 — Give the file a precise subject
Name the proposed contracting entity, product, jurisdiction and client category on the first page. Keep the marketing brand in its own field. 'Brand X is regulated' is too broad to test; 'the agreement names Example Markets Ltd for a UK retail CFD account' is an intelligible claim. Example Markets is a fictional name here, used only to demonstrate the file structure.
02 — Create a claim ledger
| Claim ID | Statement | Evidence required | Open question |
|---|---|---|---|
| E-01 | The offer names a particular legal company | Applicable agreement or onboarding disclosure | Does the application change entity by residence? |
| R-01 | The company has a specified current authorisation | Regulator's live record and relevant activity | Does the permission cover this product? |
| F-01 | A withdrawal route has a stated fee | Same-entity method schedule | Whose fee, in which currency, and with what exception? |
| P-01 | A protection applies | Applicable rule or contract and eligibility conditions | Does client classification change the result? |
The ledger makes gaps visible without converting them into conclusions. If R-01 is unresolved, write that the independent authorisation check is incomplete. Do not mark the company unregulated merely because the researcher could not read the register. Conversely, a provider's statement can be accurately recorded without presenting it as independent confirmation.
03 — Record document control information
For each item retain the exact URL, publisher, document title, visible version or effective date, date accessed and the relevant section. An access date and a document date answer different questions. A PDF read today may contain old terms; a recently crawled search result does not make those terms current. Where the issuer replaces a file at the same URL, retain a permitted copy or checksum with the dated research note so the change can be identified.
04 — Keep product document sets separate
Vantage's UK hub explicitly distinguishes legal documents by account entity. CMC's UK document hub also separates product/platform document sets. These are practical reasons to label a downloaded agreement before using it: the nearest PDF on a familiar domain is not necessarily the applicable contract. An institutional agreement, an old promotion and a retail client agreement answer different questions.
05 — Log a contradiction without choosing a winner
Suppose an account FAQ says 'requests processed next day', while a contract reserves a longer review period. Record both statements and their scope. Ask whether one describes ordinary processing and the other an exception, whether they name the same entity, and whether either document is superseded. Until that is resolved, the defensible finding is that a single unconditional deadline is not established. Do not silently remove the less convenient source.
06 — Separate record verification from protection eligibility
The FCA explains that its Firm Checker cannot decide an individual compensation or complaint outcome. Even a successful firm match therefore leaves a separate eligibility question. In the evidence ledger, connect any protection statement to its own conditions rather than adding a broad 'protected' label to every product under the brand.
07 — Make the handoff reviewable
Close the file with three lists: supported statements, attributed provider disclosures and unresolved questions. State whether any live-account or support testing took place; a documentary file normally cannot establish operational performance. Include the exact article revision reviewed, so later copy changes cannot inherit approval merely because they concern the same broker.
A reproducible file can support a bounded editorial profile even when some secondary facts remain unknown. Material entity or regulatory mismatches must stay visible and can prevent publication; the ledger explains why without inventing a numerical trust score. Read withdrawal terms as a sequence
Article sources
| Document | Publisher |
|---|---|
| FCA Firm Checker ↗ | Financial Conduct Authority |
| UK legal documents ↗ | Vantage |
| Legal documentation ↗ | CMC Markets |