Planning a tokenisation pilot: rights, records and redemption

A tokenisation pilot should demonstrate how an asset moves through a complete operating process: issuance, transfer, servicing and exit. Start by defining the right being represented and who is responsible at each step, then test whether the shared ledger improves the process.

Block Consult3 min read
In this article
Figure · Tokenisation

Choose one asset and one measurable problem

Pick a narrow asset class and a specific operational problem. That could be repeated reconciliation between administrators, a slow transfer process or poor visibility of settlement status. Record the current processing time, manual handoffs and exceptions so the pilot has a baseline.

Keep the participant group and transaction scope small enough to observe end to end. For a receivables pilot, the aim might be to reconcile a defined set of claims between an issuer and an administrator. That is a testable objective; a promise to make every asset liquid is not a useful acceptance criterion.

Describe the holder's right in plain language

Write down what holding the token is intended to represent, who owes the relevant obligation, how that obligation can be enforced and what happens if the issuer or a service provider fails. Have qualified counsel assess the proposed rights, eligibility, disclosures and transfer arrangements for the chosen asset and jurisdictions before involving participants.

Keep this description alongside the technical specification. The BIS and CPMI report announcement on tokenisation identifies governance, legal frameworks, custody and operational risks as important considerations. The token contract is one part of that wider arrangement.

  • Right: what the holder can claim and from whom.
  • Record: which register is authoritative and how it relates to the ledger.
  • Transfer: who may receive the token and which checks apply.
  • Servicing: who updates asset information, handles payments and resolves discrepancies.
  • Exit: when and how a holder can redeem, transfer or otherwise end the position under the agreed terms.

Reconcile issuance and redemption with the underlying records

Map every token state to a business event and a responsible operator. Before issuance, someone verifies the underlying record and approves the amount. After issuance, another check confirms that the ledger and the authoritative register agree. Define how duplicates, corrections and pending transactions appear in that reconciliation.

Plan redemption with the same detail. Separate the request, eligibility check, settlement instruction and final confirmation. Specify when a token is locked or retired and how an interrupted settlement is resolved. The sequence depends on the legal and settlement design, so test the agreed sequence rather than assuming an on-chain transaction completes every obligation.

Test the limits of access and liquidity

Define who can approve issuance, change permissions, pause supported operations and recover access after a lost key. Have the operators practise those procedures. They need to understand who can authorise recovery, what evidence is required and which steps to follow before they can use the contract's recovery feature.

Keep transferability, secondary trading and redemption separate in the participant materials. A transferable token still needs a willing buyer for a sale, while redemption depends on the arrangement's terms and resources. The FSB's 2024 tokenisation report identifies liquidity and maturity mismatches and operational fragilities among the relevant vulnerabilities.

For the pilot, test what happens when a transfer is rejected, a settlement service is unavailable or several participants request exit together. Describe what the team can actually do in those cases. Our introduction to real-world asset tokenisation provides the broader context.

Decide whether the pilot justifies expansion

Compare the completed process against the baseline: reconciliation effort, end-to-end time, unresolved exceptions and cost per completed transaction. Include the additional work created by keys, permissions, infrastructure and multiple service providers. Compare the same workflow with a conventional shared database where that is a viable alternative.

The decision record should explain which benefit was demonstrated, which dependencies remain and what must be resolved before adding assets or participants. Feed those findings into project due diligence. Use the pilot evidence to decide whether to expand, revise the design or stop.

Frequently asked questions

Does tokenisation guarantee liquidity?
No. Transfer capability does not guarantee buyers or a functioning secondary market. Redemption is a separate process governed by the arrangement's terms, available resources and underlying asset characteristics.
What should the first tokenisation pilot prove?
It should show whether a defined operating process improves, while the represented rights, records and responsibilities remain clear. Measure the full lifecycle, including exceptions and exit, against the existing process.
Should the team select a blockchain first?
Define the asset, participants, intended rights and operational requirements first. Those requirements then inform the choice of ledger, settlement method, custody arrangements and access model.
Contact

Let's build something durable.

Tell us about your project. We reply within two business days.

EssentialAs needed
We use storage to keep portal sign-in secure, verify invitations and remember that you’ve seen this notice. Security controls also help protect the site.
Your preferences and toolsWhen you use them
Your browser can save your chosen theme, chat conversation in this tab, simulator model and workspace preferences. You can clear this data in your browser settings.
Analytics and advertisingNot used
We don’t use Google Analytics, advertising pixels or cross-site tracking. We use Search Console to see how the site appears in Google Search; it adds no tracking script to this site.

Acknowledging this notice does not give consent to tracking. We will ask for your consent before adding optional tracking.

Cookie policyPrivacy policy