Update of the offering document: stages and deadlines
Updating an offering document means revising the whitepaper published before or during a token offer, then republishing it once internal review and any required notification are complete. Stages run from identifying a material change to republication. A live offer creates a point of no return, where withdrawal rights or a temporary pause may apply.
What triggers an update
An update becomes necessary when the original document no longer describes the offer accurately. Common triggers include a change to the price or the token cap, a correction to a risk factor, a change in the issuing entity's details, or new information a reasonable investor would want before deciding. The duty to keep the document accurate runs for as long as the offer stays open, not only at launch.
Some triggers are internal, such as a governance decision to extend the offer window. Others come from outside, such as a market event that changes the risk profile of the underlying asset. Either way, the obligation to update sits with the issuer, not with the distributor or the trading venue.
What changes for the issuer once an update starts
Once a trigger is confirmed, the offer enters a review cycle. The issuer cannot treat the change as a private matter between drafting teams. Depending on how material the change is, the update can affect the subscription timeline. It may create a withdrawal window for existing investors, or require a short pause in new subscriptions until the revised text is public.
The practical risk is timing. An issuer who republishes too late keeps investors bound to an inaccurate document. An issuer who republishes without proper internal sign-off risks having to redo the cycle. Neither failure is cosmetic — both extend the overall timeline of the offer.
Stages of the update
| Stage | Who acts | Typical output |
|---|---|---|
| Trigger identification | Compliance function | Logged change description and date |
| Drafting the revision | Legal counsel | Marked-up text against the original document |
| Internal approval | Management body | Signed change log |
| Notification | Compliance officer | Confirmation of submission to the competent authority |
| Republication | Issuer | Updated document at the same access point as the original |
| Monitoring | Compliance function | Record of investor withdrawal requests, if any |
Each stage produces a document. Missing paperwork at any stage is the most common reason an update takes longer than the issuer expected.
Steps to run the update
- Compliance logs the trigger and the date it was identified.
- Legal counsel drafts the revised sections and marks every change against the original text.
- The management body reviews the draft and signs off on the change log.
- The compliance officer submits the notification through the required channel and keeps proof of submission.
- The issuer republishes the updated document at the same access point as the original, without breaking the existing link.
- Compliance monitors investor reaction and logs any withdrawal request received during the applicable window.
Who reviews and decides
The management body that approved the original offer approves the update. It does not delegate this to a single officer, because the sign-off record is what a supervisor will ask for later. Where the change is material, the competent authority for the offer reviews the notification and may raise questions before the update takes effect. Where the change is corrective only, the internal sign-off is usually the final step.
The forum for a dispute about an update, should one arise, is the same forum that would hear a dispute about the original offer. An update does not open a new procedural track; it continues the existing one.
Point of no return and other forks
If the offer has not opened to investors yet, the issuer updates the document freely and republishes before opening. There is no investor-facing deadline at this stage.
If the offer is live and the change is material, investors who already subscribed may gain a short window to withdraw before their subscription becomes final. Once that window closes, the subscription is locked — this is the point of no return referred to in the title of this page.
If the change is corrective only, such as fixing a typo or a formatting error, the simplified path applies: internal sign-off, republication, no formal notification cycle, no withdrawal window.
What this page does not cover
This page does not verify who actually sits behind a distributor before it is onboarded to place the updated document with investors. That check runs through a separate report: Counterparty report before onboarding a distributor.
This page does not confirm whether a scanned signature or approval document submitted as part of the sign-off record was genuinely generated rather than altered. That question sits with a dedicated report: Document report when a scan looks generated.
This page does not assess what happens to an ongoing update if the issuing entity itself relocates mid-process. That scenario is covered separately in Jurisdiction report before moving an entity.
This page does not map who ultimately owns the entity behind the offer once the update is republished. For that, see Ownership structure in Czechia and its limits.
Related publications
The same offer often has a cross-border dimension that follows its own timeline. See Cross-border offer assessment step by step for how that assessment runs alongside an update.
Verified
This page was last reviewed on 10 March 2025. It describes the procedure as we see it applied across the projects we support. It does not cite a specific article, regulation, or national act, because a procedural page of this kind answers how the process runs, not what to cite. The reasoning behind our reports, including how they are compiled and checked, is explained by the people who write them: The people behind the reports in detail.
FAQ
How long does an update of the offering document take in practice?
The timeline depends on how material the change is and on the authority's review queue. A corrective update can move within days. A change to core offer terms usually takes longer, because it triggers internal approval, notification, and a possible withdrawal window if the offer is live.
Which documents are needed to start?
The issuer needs the original offering document, a description of the trigger and its date, a marked-up draft showing every change, a signed internal approval record, and proof of notification once it is submitted. Without the marked-up comparison, reviewers cannot confirm what actually changed.
What happens if the authority does not respond after notification?
Silence is not the same as a block. The issuer keeps a dated record of the submission and proceeds once the applicable internal waiting period has passed, unless the authority has asked a specific question in the meantime. Continued silence does not by itself stop republication.
If a change of this kind coincides with a change of your supervising authority itself, the sequence is different: When the regulator changes during the project explained.