Compliance evidence pack
Show what was active at the time.
Not what the settings say today. Not what somebody remembers. Not what the sales brochure promised.
Beaver's Live Evidence Pack creates a dated export showing which compliance controls were active during a period.
Controls leave evidence.
A sanitised, genuine export goes here. We will not publish a prettier made-up version first. Ask for the real one in a demo.
Why the date matters
Current state is not historical evidence.
Systems change. Settings change. People change them. Compliance Packs change. Operating requirements evolve. A screenshot taken today does not tell you what the platform was doing three months ago.
The useful question is: what controls were active when the event happened? The Evidence Pack is designed to answer that for a defined period.
When matters.
Two kinds of evidence
State tells you what was true. Audit tells you how it changed.
-
Evidence Pack
Live
What controls were active during the period? A dated export, different from a policy, a static settings screenshot, an internal checklist or a marketing claim.
-
Audit trail
Live
Who changed sensitive state, why, and what changed? Actor, reason, before and after for activity touching money, entries or marketing.
Locked controls
The control has a source. The source should be traceable.
Compliance Packs can impose minimum control levels an operator cannot loosen, and the Operator Console explains which pack imposed a locked floor and why. That creates an evidence chain.
- Compliance Pack
- Control floor
- Operator configuration
- Active control
- Audit history
- Dated evidence pack
Questions it helps answer
Instead of "I think it was".
-
Question 1
What spending controls were active?
Instead of "I think the cap was £500 at the time", inspect the dated platform evidence. If the setting later changed, the audit trail adds the history.
-
Question 2
Was this protection configured when the customer entered?
The relevant question is the effective platform state during the period under review, not today's settings.
-
Question 3
Which Compliance Pack imposed this setting?
The console already explains locked floors. Whether the export carries that linkage is something we will show from the real sample, not promise in advance.
Different question, different evidence
The evidence pack is not the draw verifier.
Public draw verification: can somebody reproduce the winner from the published draw evidence?
Compliance Evidence Pack: which Beaver controls were active during a defined operating period?
Audit trail: which sensitive changes happened and who made them?
Together they form a stronger evidence story.
Who it is for
Evidence for review. Not a certificate.
- Operators: retain evidence of platform state.
- Compliance teams: review controls and changes.
- Commercial partners: understand how the operator has configured the platform.
- Auditors and advisers: inspect system evidence alongside wider business evidence.
The pack is evidence an auditor could inspect. It is not itself an audit opinion.
Evidence for review. Not a certificate from Beaver saying everything is fine.
What it does not prove
Evidence of platform state is exactly that. Evidence of platform state.
An Evidence Pack does not prove:
- all applicable laws were identified
- the operator complied with obligations outside Beaver
- every advertisement was accurate
- every manual process was followed
- every employee behaved correctly
- the operator is regulator approved
A registry control for audit retention exists but is switch only, so we do not claim configurable retention. The actual retention policy will be published in the Trust Centre.
A retention setting that does nothing is not a retention policy.
Sample pack
See a real Beaver evidence pack.
We will publish a sanitised, genuine export here, in the format the system actually generates. We will not build a prettier fictional version first.
Until it is here, ask for one in a demo and we will walk you through it.
The proof does not need a mascot.
A sanitised, genuine export goes here. We will not publish a prettier made-up version first. Ask for the real one in a demo.
Questions
Asked and answered
What is a Beaver Compliance Evidence Pack?
A Live dated export showing which platform controls were active during a defined period.
Is it the same as an audit log?
No. The Evidence Pack describes active controls during a period. Beaver's sensitive write audit trail records actor, reason, before and after for relevant changes.
Does an Evidence Pack prove my business is legally compliant?
No. It provides evidence about Beaver platform state. It is not a legal opinion and does not prove that activity outside the platform complied with every requirement.
Can I see a sample?
Yes, in a demo. We will publish a sanitised genuine export on this page rather than a fictional marketing example.
Can the audit retention period be configured?
A retention control exists in the registry but is switch only, so we do not present configurable retention as working today.
See the evidence
Ask what was active. Get a dated answer.
Then ask us how the controls got there.