A token described as backed by a real-world asset needs more than an attractive asset description. The review must connect the ledger entry to a defined claim, identify the parties responsible for honoring it, and explain what the holder can do when the arrangement works or fails. Those connections are the substance of RWA due diligence.

Use the RWA screening criteria to establish the asset category and available evidence. Then examine the entire arrangement below. The objective is a reviewable account of documents, responsibilities, and unresolved dependencies, with no assumption that a token's technical transferability settles the quality of its underlying claim.

1. Write the claim in one precise sentence

Begin with a sentence in this form: “The documents describe this token as representing [specified interest] in [specified asset or obligation], provided by [named entity], under [identified terms].” Fill every bracket from evidence. If a bracket cannot be completed, the missing element becomes a screening issue.

The BIS and CPMI report on tokenisation describes digital representations of traditional assets on programmable platforms and discusses tokens representing claims on real or financial assets. It also explains that familiar financial infrastructure risks remain relevant to token arrangements. The practical implication for this review is to investigate the underlying asset, the participating entities, and the platform together.

Ask whether the documents describe a direct interest in an asset, a claim against an issuer, an interest in a pooled vehicle, or another arrangement. Preserve the exact description rather than replacing it with a more reassuring label. Terms such as “backed,” “secured,” and “redeemable” should each lead to a specific supporting provision and an explanation of its scope.

2. Map the parties and their responsibilities

Create a list of entities responsible for issuance, holding the underlying asset, maintaining records, valuing assets, processing payments, and handling redemption. Identify the organization behind each role, its relationship to the issuer, and the documents supporting that assignment. If one organization performs several roles, make that overlap visible.

For each handoff, record what information or action must pass between parties. Who instructs the custodian? Who updates the token supply after a redemption? Who reports a discrepancy? Who can correct a mistaken record? A role chart without these handoffs can look complete while leaving the operating process unexplained.

Then describe what authority is actually evidenced. A name on a website does not by itself establish an executed custody agreement, and a project announcement does not establish that a named party accepts the stated responsibility. Request the relevant confirmation or document. When access is limited, mark the responsibility unverified rather than implying that it has been checked.

3. Reconcile tokens, underlying assets, and other obligations

Choose an observation date and compare the token record with the underlying asset record for that same period. Document the supply definition, the unit of account, the assets included, and any stated conversion ratio. If reporting dates differ, show the difference explicitly and identify the intervening events that require reconciliation.

Consider a fictional arrangement with 1,000 underlying units and 1,250 tokens, each described as representing one underlying unit. That comparison creates a question, not an automatic finding of misconduct. Investigate pending issuance, reporting timing, conversion terms, or an incorrect interpretation of the documents. Leave the mismatch open until the explanation reconciles both records.

Ask what else may have a claim on the same assets. Review the available disclosures for borrowing, pledges, expenses, or other obligations relevant to the proposed backing. Record whether a report addresses asset existence, ownership, restrictions, liabilities, or only a narrower measurement. The label attached to a report should not expand the work it actually describes.

Preserve the evidence date and the next expected update. A record can be accurate for its stated date while being too old for the decision under review. Write down the event that would require a refresh, such as new issuance, an asset substitution, a material payment, or a change in the reported custodian.

Keep the asset description consistent across records

Compare the identifiers and scope used in the terms, custody material, valuation report, and token description. Check whether they refer to the same pool, period, asset category, and issuing entity. A shared brand name is insufficient when several arrangements operate under it. Give each supporting document a reference in the review so the connection can be followed without guessing.

For a changing pool, ask how additions and removals are authorized and recorded. Identify what evidence would explain a substitution between reporting dates and whether holders receive an updated description. For a claim on a specific item, ask how that item is distinguished from similar items. These are alternative review questions, not assumptions that either structure is in use. The key is consistency: the asset described to holders should be traceable through the records used to support the claim, with differences explained by the responsible party.

4. Walk through redemption from request to receipt

Describe redemption as a sequence of actions. Identify who may request it, the minimum amount, accepted submission method, required account status, applicable fees, and the asset or currency delivered. Separate documented processing targets from guaranteed obligations, and identify any conditions under which the process may be deferred or suspended.

Follow a hypothetical request through every step: submission, eligibility review, valuation, token handling, asset sale if relevant, payment instruction, and final receipt. At each stage, name the responsible party and the evidence that would show completion. If tokens are surrendered before payment, identify what the documents say about the holder's position during that interval.

Run the same walkthrough for an exception. What happens if the request is incomplete, the underlying market is closed, the receiving account rejects payment, or the processor becomes unavailable? An exception procedure should explain ownership of the problem and the route to resolution. “Contact support” is an incomplete description when no responsible entity or process is identified.

Keep secondary-market trading separate from redemption. The existence of a trading venue does not answer who can redeem directly or on what terms. A screening note should describe each potential exit route independently and state which participants can use it.

5. Examine valuation and the route of any cash flow

Record how the arrangement values the underlying asset and how that valuation enters token pricing or redemption. Identify the valuation date, methodology, responsible party, and circumstances that permit adjustment. Where estimates are used, preserve the assumptions and the source of uncertainty rather than displaying the result as a directly observed cash amount.

If the token is described as paying income, trace the payment from its underlying source to the holder. List the stated deductions, reserves, service charges, conversion steps, and distribution conditions. Distinguish accrued amounts from cash received. Ask who bears an interruption, a delayed payment, or a cost that exceeds the original estimate.

A useful hypothetical worksheet starts with the documented gross inflow and then subtracts each identified charge once. It ends with the amount available for distribution and the conditions required to distribute it. Any missing input remains blank with an explanation; an optimistic assumption should not quietly complete the calculation.

6. Test failures across the entire arrangement

Build short scenarios around an issuer interruption, a custody dispute, a record mismatch, a platform outage, and an unavailable payment channel. For each, identify the affected obligation, the evidence needed to understand it, and the documented recovery process. Do not assign a recovery amount when the available material cannot support one.

Questions about enforceability, priority, or treatment when an entity fails may depend on the actual structure and applicable law. Keep those questions precise and direct them to qualified review when they matter to the proposed use. Technical visibility of a token should not close a question about an external claim.

The Web3 dependency review is useful for identifying which platform components must remain available. Add the named custodians, issuers, valuation providers, and payment channels to a portfolio exposure map so that repeated reliance on the same party becomes visible across multiple tokens.

Conclusion: require a continuous chain of evidence

A useful RWA screening record connects the token to a defined claim, that claim to responsible parties, and those parties to an observable operating process. Finish with a short list of supported findings, unresolved questions, and the documents or events that would change the conclusion. A complete ledger record is one part of the review; the quality of the arrangement depends on the connections surrounding it.