Build a defensible process for documenting suitability, explaining risk, and distinguishing advisory guidance from technical implementation services.
Good compliance is not a pile of jargon. It is a clear record of what was discussed, why it was suitable, what the risks were, and where the advisor stopped.
Why Bitcoin was considered, what role it plays, and what risks were reviewed should all be visible in the client record.
The client file should clearly distinguish allocation guidance from technical implementation, custody setup, or legal/tax advice.
If a specialist is involved, document why, when, and for which responsibilities so there is no ambiguity later.
Use this to identify the minimum documentation set the file should contain before implementation moves ahead.
Choose your inputs and generate tailored guidance.
Advisor responsibility: Own suitability, disclosures, rationale, and the written line between advisory work and specialist implementation.
Specialist responsibility: Provide technical scope, implementation notes, and operational documentation relevant to custody or execution — without replacing the advisor’s fiduciary file.
Advisors own the client record. Specialists document their technical lane.
This module is designed to stay practical and verifiable. Use these reference points when you adapt the material for client-facing use.
Test your understanding of the key concepts from this module.