guide
How to date a broker contract without confusing download time and legal scope
Build a document record that separates retrieval date, printed version, contracting entity, product and unresolved conflicts.
By Betsafe Reviews Editorial Team ·
Updated Oct 5, 2026
- Document date
- Entity and product
- Limits
A PDF downloaded today is not necessarily a contract issued today. Equally, an older printed date does not by itself prove that a document has been withdrawn. A verification record needs both the date of inspection and the document’s own version information, together with evidence of where it was linked. This guide describes our documentary workflow; it does not interpret an individual contract or decide which terms legally govern a dispute.
Make the document identifiable
Start at the provider’s relevant regional legal hub and record its URL. Note the exact company named inside the document, the product it covers and the client category if specified. A group brand in the file name is less precise than the contracting entity in the body. Save the document title and visible version or effective date as separate fields. If no version is visible, record ‘not stated’ instead of borrowing the webpage’s last-updated label.
| Research field | Example of what belongs there |
|---|---|
| Checked on | When the researcher inspected the source |
| Document version | The date or version printed in the document |
| Linked from | The regional legal hub that supplied the link |
| Scope | Named entity, product and client category |
| Open question | Conflicting schedule, missing appendix or uncertain applicability |
Do not merge neighbouring agreements
IG’s UK agreement hub distinguishes CFDs, spread betting and other services. CMC’s UK legal material separates product and platform arrangements. Those divisions are evidence that the reader needs the right document, not permission to assemble favourable clauses from several agreements. A protection described for one client category cannot be assumed for another. A cash-investing fee table also cannot fill a missing forex-CFD charge merely because it carries the same brand.
Retain a trace when the source changes
Suppose a research note checked on 5 October records a document printed in March. A later check finds a new version. The useful record retains the earlier observation, adds the later source and identifies which claims changed. Silently replacing the old text destroys the explanation for a previous conclusion. For stored files, a cryptographic digest can distinguish exact bytes; it cannot establish that the file is genuine, applicable or legally superior to another document.
When a URL serves a different file later, the URL alone is no longer enough to reproduce the earlier review. Record the new retrieval and printed dates. Keep personal account documents out of public citations, and do not publish account numbers or identity evidence as proof of research. Public research sources and a reader’s private agreement have different handling requirements.
Handle a conflict as a question with an owner
If an operational FAQ says one thing and a contract reserves a broader right, quote the scope of each in your own concise notes. Do not decide that the friendlier statement automatically wins. Identify the unresolved point: perhaps a route-specific fee, an introduced-client schedule or a particular platform agreement. Seek clarification through the verified company contact and retain the written response with its date. Legal priority in an individual dispute may need qualified advice; a research checklist cannot determine it.
A file is complete enough for a qualified profile when its supported claims and remaining limits can be traced, not when every empty field has been filled. Documentary checking does not measure actual service performance or eliminate the financial risks of leveraged trading. See the CMC UK evidence record
Article sources
| Document | Publisher |
|---|---|
| UK customer-agreement hub ↗ | IG |
| UK CFD legal-document hub ↗ | CMC Markets |