Track a corrected announcement without losing the original
A correction should lead to a field-by-field impact review, not deletion of the original announcement. Save the original, the correction, and any replacement file separately. Then identify what changed and which research claims depend on those fields.
Use the issuer’s actual correction on HKEXnews or CNINFO, as appropriate to the market. An official search result is a discovery route; the correction’s text establishes its stated scope. The ledger below is a suggested research record rather than an exchange-mandated format.
Read the relationship before the changed wording
Locate the original announcement named by the correction. Compare title, publication date, issuer, and subject. A similar title does not prove that a later file replaces the earlier one. Record whether the issuer says it corrects, supplements, replaces, or clarifies specific content.
Next, identify each changed item. Preserve old wording, new wording, and a locator for both. If a replacement PDF is supplied, keep its identity and compare the relevant section. If the correction does not clearly state whether other material changes, leave that point unresolved rather than claiming a complete document review.
Hypothetical correction ledger
Suppose fictional Stonebridge Machinery issues a notice correcting a project’s expected date and adding a condition. The details below are invented.
| Item | Earlier statement | Corrected statement | Research impact |
|---|---|---|---|
| Expected milestone | Month A | Month B | Update event follow-up date |
| Condition | Not captured in earlier note | Approval required | Narrow the claim |
| Counterparty | Same in inspected passages | Same in inspected passages | Retain, with scope note |
| Historical memo | Written before correction | No retroactive edit | Attach later revision record |
Do not interpret the changed date as proof of a project failure or deliberate misstatement. The source establishes the correction and its content. Reasons and consequences need their own evidence. Your immediate task is to make the research record accurate.
Update claims by dependency
Search for the original document identifier in your notes. A copied quote, an event timeline, and a review reminder may all depend on the changed date. Update each affected object and leave a revision note. Claims that do not depend on the correction can remain, but record that the scope check was performed.
Keep a historical view when the note’s purpose is to reconstruct what was disclosed at an earlier cutoff. Add a visible later-update line instead of rewriting the earlier text as though the correction had always been known. A current view and a historical view can coexist when clearly labeled.
Verification and limits
Reopen the original and corrected sources. Confirm that your new wording preserves every relevant qualification. Then follow the changed field into the research objects that use it. The correction review is complete when the dependency list has an action or explicit unresolved status for each affected object.
This workflow does not guarantee that every discrepancy has been found. If only the named correction items were reviewed, say so. Nor does the word “supplement” tell you whether all prior statements remain suitable for every research question. Read the actual relationship and preserve uncertainty where it remains.
Frequent errors include overwriting the original PDF, using a corrected file with an old publication citation, and changing a sentence without updating the associated review trigger. Another is treating any later file as a correction. A progress notice may add a new event rather than alter the earlier disclosure. Classify the relationship before changing the record.
A final record check
After processing a correction, inspect reminders and exports created from the old information. These secondary objects often retain a changed date after the main note has been fixed. Mark the scope of this dependency check. If an exported packet cannot be recalled, retain a revision notice in the current archive instead of claiming that every distributed copy was updated.
FAQ
Should a correction count as a new event?
It is a new source publication. Whether it represents a new business event depends on the content. Link it to the original research object before deciding.
Can I keep quoting an unchanged passage from the original?
You can if the scope review supports that use. Record the correction relationship and avoid implying that the original is the only relevant version.