Redemption process design: stages and deadlines
Redemption process design turns a token's promised buy-back or wind-down mechanic into a working procedure. It fixes who may ask for redemption, what they submit, who checks the request, and when assets actually move. Get the stages fixed before launch. Changing them once holders start redeeming creates disputes, and in some structures there is a point after which the terms for that cycle cannot be revised at all.
What this covers
Redemption process design is an operational exercise, not a drafting exercise. It sits downstream of the token's economic terms and upstream of settlement. The output is a short internal policy plus a set of forms, checks and a timeline that staff can follow without asking the same question twice. A weak design shows up months later, usually on the day the first holder actually asks for their money back.
The design work usually touches four areas: who is eligible to redeem, what triggers a redemption window, how a request is verified, and how the settlement leg is executed. Each area needs its own owner, even on a small team.
Stages, documents and typical timing
| Stage | What gets produced or checked | Typical timing |
|---|---|---|
| Drafting | Redemption policy, eligibility criteria, trigger conditions | 1–2 weeks |
| Internal approval | Board or governing body sign-off, updated offering document reference | A few days to a week |
| Operational build | Identity checks, custody instructions, settlement rails | 2–4 weeks |
| Holder-facing disclosure | Notice text, request form, contact channel | Before the window opens |
| Live window | Intake, verification, execution of accepted requests | Defined window, often 5–10 business days |
| Cut-off | Confirmation that no further terms change for that cycle | Fixed date, set in advance |
These figures describe common practice, not a fixed rule. A structure with several classes of token holder, or with assets held across more than one custodian, tends to sit at the longer end of each range.
What to do
- Name an owner. One person runs the design end to end, even where several teams contribute.
- Map the trigger. Decide what event opens a redemption window: a holder request, a wind-down event, or a fixed calendar date.
- Draft the policy. Set eligibility, the documents a holder must submit, and the verification steps that follow.
- Build the settlement path. Agree how assets or funds move, in what order, and who signs off each leg.
- Fix the cut-off. Set the moment after which terms for that specific cycle cannot change.
- Run a dry test. Process one internal request before opening the window to holders.
Who decides
The issuer's board or equivalent governing body approves the redemption policy before it goes live. A named redemption officer, or the compliance function acting in that role, handles day-to-day decisions on individual requests. Disputes about a specific request are usually resolved inside this internal chain first, before any external forum becomes relevant. Where a supervisory authority is involved in the wider project, its role in redemption is normally limited to reviewing that the process matches what was disclosed to holders, not to approving each request.
Scenarios
If the token is redeemable on demand at any time, then the window concept matters less than a stable verification queue. Design the intake and checking steps to handle a steady flow, rather than a single cut-off date.
If the token has a fixed maturity or a planned wind-down date, then the cut-off usually sits close to that date. Requests filed after the cut-off are refused, and the policy should say this in plain terms before the window opens.
If holders are already submitting requests and the eligibility criteria are still being finalised, then freeze the criteria immediately. Changing eligibility after the first request lands is the most common source of later disputes.
Limits of this page
This page covers process design. It does not set the legal basis for a specific redemption obligation, and it does not cover tax treatment of a redemption payment.
Where a redemption stalls because a filing date does not line up with what the register shows, a Document report when dates do not match the register takes a factual, register-first approach to that specific problem.
Before committing redemption design to a particular market, a Jurisdiction report before entering a market answers the market-entry question this page does not.
Where the counterparty on the other side of a redemption is based in Hong Kong, a Counterparty in Hong Kong check answers a separate, factual question about that party.
Verified
Reviewed as of 10 March 2025. This page reflects standard issuer redemption practice rather than a single statutory text; where a national filing or authorisation applies to a specific structure, that sits outside this page's scope. For how our scope is defined more broadly, see About the firm and its scope in detail.
Related reading
If the redemption design requires changes to the offering document itself, see Update of the offering document step by step for that separate procedure.
FAQ
How long does redemption process design take in practice?
A single-token, single-jurisdiction design usually takes four to six weeks from drafting to a tested live window. Multiple token classes, multiple custodians, or several jurisdictions extend this. The bottleneck is almost always the operational build stage, not the drafting.
Which documents are needed to start?
Start with an internal mandate naming the owner, a description of the trigger event, a draft eligibility list, and a first-cut settlement instruction. Everything else in the policy is built around these four items.
What happens if the other side does not respond?
The policy should set a response window for the holder and a separate escalation path for internal teams. If a holder does not respond within the stated window, the request lapses under the policy's own terms. If an internal team misses its step, the redemption officer escalates rather than letting the request sit unresolved.
Next step
If a regulator shift happens partway through the design work, see When the regulator changes during the project in detail for how to keep the timeline intact. Send us the structure and we reply within minutes during business hours; a fee quote follows within one business day.