Cross-border offer assessment: stages and deadlines
A cross-border offer assessment checks whether a token offer prepared in one member state can proceed in another, and on what timeline. It runs in stages: internal readiness review, documentation package, notification to the host state, a waiting period, and a decision point after which withdrawal becomes difficult. Total duration depends on document quality and how quickly the host authority responds.
Practical consequence
The assessment sets the pace for everything downstream. Marketing, listing agreements and investor communications in the host state cannot start before the notification stage closes. Teams that treat the assessment as a formality tend to file incomplete packages, which restarts the clock rather than shortening it.
Once the package is submitted, there is a point of no return: withdrawing or materially amending the offer after that point usually means starting the process again in the host state, not just correcting a section.
Stages and typical timing
| Stage | What happens | Typical duration |
|---|---|---|
| Internal readiness review | Legal and compliance teams confirm the offer documents are complete and consistent across languages | 1–3 weeks |
| Documentation package | Final versions assembled for the home state file and the host state notification | 1–2 weeks |
| Notification to host state | Home state authority forwards the package to the host state regulator | Set by the authority, not the applicant |
| Waiting period | Host state reviews the package; questions may pause the clock | Depends on completeness and responsiveness |
| Decision point | Offer becomes enforceable in the host state or is returned for correction | End of the reviewable process |
The "typical duration" column reflects practice, not a fixed statutory count. A single missing annex can add weeks; a pre-cleared package rarely does.
What to do
- Assign one person as the file owner. Cross-border assessments fail more often from split ownership than from substance.
- Build the documentation package to the host state's expected format, not only the home state's.
- Send the package for internal sign-off before external submission; corrections after submission cost more time than corrections before.
- Track the notification date separately from the submission date — the waiting period runs from notification, not from when your team pressed send.
- Respond to any authority query within the window it sets, even with a partial answer, to avoid the file being treated as inactive.
- Flag the point of no return internally so marketing and business teams do not commit to dates that assume approval.
Who decides
The home state authority runs the first check and forwards the file. The host state authority decides whether the offer can proceed on its territory and on what conditions. Neither authority is bound by the applicant's proposed timeline; both work to their own internal review cycles.
If the process stalls and neither authority replies within a reasonable window, escalation inside your own organisation is often faster than escalation to the regulator. You can put the question to a partner before deciding whether to press the authority or wait.
Forks
If your offer only targets one member state, the cross-border stage does not apply — proceed under the home state process alone.
If the host state raises questions during the waiting period, the clock generally pauses until you respond; plan for this rather than treating the original estimate as fixed.
If you need to change the offer terms after notification, check whether the change is material. Minor corrections may be accepted; material changes usually require a fresh package.
Limit
This page describes the stages and the practical rhythm of a cross-border assessment. It does not state a fixed number of calendar days, because that number depends on the authority's own workload and on how complete your package is at first submission. It also does not cover what happens after the offer is live — that belongs to ongoing compliance, not to the assessment stage.
Sources and limits
Before naming a developer for the token build, confirm counterparty basics first — the counterparty report before appointing a developer is built for that step.
Before filing the assessment package with any office, a document-level check catches gaps a legal review can miss — see the document report before filing with an office.
When a deadline in your case depends on how a specific host authority behaves in practice rather than on a fixed rule, the jurisdiction report when a deadline depends on local practice maps that behaviour before you commit to a date.
This page was last reviewed in June 2025. It reflects the assessment procedure as followed in current practice and carries no statutory citations by design, since the underlying stages are procedural rather than defined by a single numbered provision.
Related publications
A related procedure worth reading alongside this one is the conflict of interest register step by step, which covers a check that often runs in parallel with the offer file.
FAQ
How long does cross-border offer assessment take in practice?
There is no single fixed period. A complete package that answers likely questions in advance tends to move through the waiting period faster than one that triggers follow-up requests. Build in weeks of buffer rather than committing to a specific launch date before notification closes.
Which documents are needed to start?
At minimum: the offer documentation itself, evidence of internal sign-off, and the notification file addressed to the host state format. Missing annexes are the most common reason a file is returned rather than reviewed.
What happens if the other side does not respond?
Silence from an authority does not mean approval. Keep a record of your submission date and any follow-up sent. If the window an authority itself set has passed without a reply, raise it through the appropriate contact point rather than assuming the file has cleared.