Listing preparation: documents to prepare
Listing preparation is the stage where a token issuer assembles the file a trading venue needs before it opens a review. The file covers the token's legal status, the issuer's structure, the disclosure document, and proof that holders can be reached. Missing one piece stops the review before it starts, regardless of how strong the rest of the file is.
What the stage actually covers
A trading venue does not review a token on its own. It reviews the issuer, the token, and the process that connects the two. Preparation means building three parcels of paper before a venue's compliance team opens the file: proof of who the issuer is, proof of what the token does, and proof that holders can be reached if something changes.
Each parcel answers a separate question. The venue asks who is accountable, what rights the token carries, and how a dispute or a technical incident would reach the holder base. A file that answers only one of these three stalls at intake.
Documents to prepare
| Document | Purpose | Typically prepared by |
|---|---|---|
| Issuer identification file | Confirms legal form, registered address, and the beneficial ownership chain | Issuer's corporate team |
| Token description and rights summary | Sets out what the token represents and what it does not represent | Issuer with outside counsel |
| Disclosure document | Explains risks, technology, and the issuer's obligations to holders | Issuer with outside counsel |
| Holder communication plan | Shows the channel and timing used for notices, incidents, and changes | Issuer's operations team |
| Custody and control statement | Confirms who holds the keys and how access is split | Issuer's technical lead |
| Screening summary | Confirms the screening process applied to counterparties and large holders | Compliance function |
A venue rarely asks for all six documents on day one. It asks for the first three, then requests the remainder once the file passes an initial read.
What changes once the file is submitted
Submission starts a clock the issuer cannot pause. A venue's compliance team reviews the file against its own checklist, not against the issuer's timeline. Once a question comes back from the venue, the issuer has a fixed window to answer; a missed window resets the queue position rather than the whole file.
This is the point of no return in the title of this page: after submission, the issuer no longer controls the pace, only the quality of each answer it sends back.
What to do
- Assign one internal owner for the file. A file with two owners tends to produce contradictory answers to the same question.
- Draft the issuer identification file and the token description first; the venue reads these before anything else.
- Have outside counsel check the disclosure document against the venue's own template, not against a generic model.
- Confirm the holder communication plan names a channel that already exists and has been tested, not one planned for launch day.
- Send the file to a partner for review before submission; a second read catches gaps a single team misses.
Who decides and how long it takes
The trading venue's listing or admissions committee makes the decision, not the issuer's counterparty and not the issuer's own board. The committee works from the file and from its own risk screening; it does not negotiate document by document.
Timing depends on how many rounds of questions the file generates. A file that answers the venue's checklist in full at first submission moves through fewer rounds than a file assembled in stages. The issuer controls the number of rounds far more than it controls the calendar.
Two scenarios
- If the token has already traded on another venue, keep the prior disclosure document on hand: the new venue will ask why the terms differ, if they do.
- If the issuer is a newly formed entity with no trading history, expect the identification file to receive closer reading than the token description.
- If holders are spread across several jurisdictions, the communication plan needs a channel that reaches all of them at once, not one built for a single market.
What this page does not cover
This page describes the file to assemble and the order to assemble it in. It does not set out a venue's internal scoring, and it does not predict how many rounds a specific file will need. It also does not cover the separate procedure for talking to existing holders once a listing is live; that sits in a linked page below.
Sources and limits
This description reflects how trading venues structure intake in practice, drawn from process observation rather than a published checklist any single venue has confirmed.
Where a counterparty in the chain is Polish, our Counterparty in Poland report sets out what a public register can confirm and what it cannot.
Where a document in the file originates in Denmark, Document in Denmark and its limits covers the same question for that register.
Where a counterparty or venue sits in the United Kingdom, Jurisdiction in United Kingdom and its limits covers what that jurisdiction's registers show.
Checked: 3 March 2025. This page does not cite specific legislation; where a legal question turns on a specific provision, raise it with a partner directly rather than relying on this summary.
Related reading
Once the listing file is in and a venue is live, the next procedural question is usually how holders are told about changes. That sequence is covered separately: Holder communication procedure step by step.
FAQ
How long does listing preparation take in practice?
It depends on how many rounds of questions the file generates rather than on a fixed calendar. A file that is complete at first submission moves faster than one built in stages, and a venue does not commit to a fixed review period in advance.
Which documents are needed to start?
A venue typically wants the issuer identification file and the token description first. The disclosure document, the holder communication plan, and the custody statement follow once the initial file passes a first read.
What happens if the other side does not respond?
If a venue does not respond within its own stated window, the issuer's position in the review queue is not protected automatically. Following up through the assigned contact point, rather than resubmitting the file, is the usual next step.