Update of the offering document: what the decision maker looks at
An update to the offering document becomes necessary once the facts it describes no longer match reality — a change in the token's rights, in the issuer's structure, or in how the token is actually used. The update is not a formality. It resets what investors are told and, in most cases, resets the clock on related disclosure duties. Where the update also touches distribution in more than one state, the Jurisdiction reports overview shows how coverage differs by state. This page sets out the stages, the documents, the timing, and the point after which withdrawal is no longer realistic.
What changes once the update is filed
Before filing, the existing offering document stays valid, and any ongoing offer continues on its original terms. Once the update is submitted through the applicable channel, three things change at once. The issuer becomes bound by the new version, not the old one. Any live offer that relies on the document must be paused or reconciled with the new text. Investors who acted on the earlier version may acquire a right to reconsider their position, depending on how material the change is judged to be.
This is the practical reason updates are rarely simple corrections. A change treated as minor by the issuer can be treated as material by the person deciding whether the update is adequate — and that gap in judgement is where most delay comes from.
What to do
- Identify the trigger. Write down, in one paragraph, what fact changed and why the existing document no longer reflects it. This paragraph becomes the core of the filing.
- Assign an internal owner. One person or committee signs off on the substance before anything leaves the building. Without a named owner, updates stall at the drafting stage.
- Draft the amended sections only. Rewriting the whole document invites new questions about parts that did not change. Mark what changed and leave the rest untouched.
- Reconcile with any live offer. Decide whether the current offer pauses, continues under the old terms until the update takes effect, or restarts under the new terms.
- Submit through the applicable channel and record the submission date. This date is the reference point for every timing question that follows.
- Track the review, do not assume silence means approval. An update that has not been queried is not the same as an update that has been accepted.
Working through these steps with an outside team rarely changes the sequence, but it does change how fast each step closes. Working with this team in detail describes how that division of labour is set up.
Who decides, and on what timeline
| Stage | Who decides | What is checked |
|---|---|---|
| Internal sign-off | Issuer's own governance body | Whether the change is accurately described and complete |
| Filing | Person or team responsible for the offer | Whether the amended document matches the template used for the original |
| Review | The body that received the original offering document | Whether the change is material, and whether disclosure to existing holders is adequate |
| Effect | Set by the reviewing body or by the issuer, depending on the type of change | Whether the offer can resume, and under which version |
The reviewing body does not check whether the change is a good idea. It checks whether the update is honest about what changed and whether that is enough for someone reading it to decide again, from scratch, whether to invest.
Forks
If the change concerns the token's classification rather than its commercial terms, the update usually needs a separate technical justification, not just a redrafted paragraph. If the change is triggered by a request from the reviewing body itself, rather than by the issuer noticing something internally, the timeline compresses and the review tends to be stricter. If the offer is already closed and no new investors are being sought, an update may still be required for holders already in place, even though no active sale is running.
The point of no return
Once the reviewing body has issued a substantive query on the filed update, withdrawing it cleanly is rarely possible. The query itself becomes part of the record, and a second, quieter filing on the same point invites more scrutiny, not less. The safer point to reconsider is before submission, while the update is still an internal draft.
What this page does not cover
This page describes the update procedure in general terms. It does not set out how a specific jurisdiction schedules its review, and it does not describe the internal drafting standards a particular authority applies to the amended text. Those questions sit with the counterparty or document layer of the file, not with the procedure itself.
Sources and limits
Where the trigger for the update is a change on the other side of the relationship — a renamed counterparty, a restructured entity — the underlying question is closer to a change-of-party issue than a disclosure issue. The Counterparty report when the counterparty changes name covers that decision separately.
Where the trigger is a document that was never properly signed off before the original offer went out, the timing question is different again. The Document report when an assignment is unsigned sets out how that deadline is calculated.
This page describes procedure only. It does not name a specific authority, cite a specific provision, or quote a specific deadline, because those details vary by state and change independently of the sequence described above.
Related publications
A related sequence, covering offers made across more than one state at once, is set out in Cross-border offer assessment step by step.
FAQ
How long does an update of the offering document take in practice?
The internal drafting and sign-off stage is usually the longer part. The review stage after filing depends entirely on how the reviewing body schedules its queue and on whether it raises questions.
Which documents are needed to start?
The original offering document, a written description of the triggering change, and the amended sections themselves. Supporting evidence for the change — technical, corporate, or factual — is assembled around those three.
What happens if the other side does not respond?
Silence from a reviewing body is not approval and is not a fixed deadline either. Where the review sits with a counterparty rather than an authority, the practical answer depends on what that party's own obligations are — a question the file, not this page, tracks.
Checked
Last checked on the date this page was published. This page describes a general procedure and does not rely on a specific statutory citation; where such citations matter to your file, they are tracked separately and updated on their own schedule.
If your case does not match the sequence above — most often because the token's classification itself is in question — A token is classified differently than expected token issuance sets out what changes in cost and timing when that happens.