List every dependency beside the balance
For a fictional portfolio, create rows for each custody location. Add columns for legal entity, authentication method, who controls the keys, withdrawal network, destination wallet or bank route, and jurisdiction.
Do not fill unknown fields with guesses. Mark them unknown and treat the uncertainty itself as a risk item.
Stress three different failures
Run a login failure, a withdrawal suspension and a network outage. For each one, record which assets are inaccessible, which alternatives are genuinely available and which alternatives merely look available because they have not been tested.
Identify concentration that price charts cannot show
If 80% of the portfolio depends on one login or one venue, that is a concentration risk even if the assets themselves are different. If several venues ultimately rely on the same banking route for PHP cash-out, record that shared dependency too.
Completion check
The worksheet passes when you can point to every balance and answer: who controls access, what route is required to move it, what could stop that route and what contingency has actually been verified.
*Cryptocurrency and virtual asset transactions are highly volatile and irreversible, may result in significant losses, and do not guarantee returns; customers should trade only after understanding the risks involved.
