Build a shared facts log
Record detection time, affected systems, observable customer impact, containment actions and unresolved questions. Distinguish a confirmed event from a working technical hypothesis. Assign an owner to each fact and preserve versions. The response team needs a common source of information across time zones; a circulating presentation with untracked edits is not sufficient. Never publish technical detail that could compromise containment.
Separate response workstreams
Technical containment, legally required notifications, customer assistance, employee instructions and market disclosure have different owners and dependencies. Specialists determine the obligations and deadlines that apply. Communications should make these workstreams visible in one coordination table, including who can approve a statement when a decision-maker is unavailable. ENISA's incident-awareness resources help frame preparation without replacing national authority guidance.
Answer the customer's immediate problem
A European factory customer may need to know whether to disconnect a service, use a workaround or await a technical instruction. Give only actions validated by the response team. If impact is unknown, say what is being investigated and when the next update is expected. Do not announce 'no evidence of compromise' as though it conclusively proves that no compromise occurred.
Coordinate the listed-company narrative
The company secretary, legal team and investor relations must assess the implications for Hong Kong disclosure. Do not let a local spokesperson speculate about financial loss, attribution or the scale of the incident. Equally, do not leave customers without operational information while waiting for a general corporate message. Prepare differentiated communications with consistent facts and a documented approval sequence.
Plan the handover between continents
Name incident communications leads for European and Hong Kong working hours. Each handover should list new evidence, communications sent, open questions, next update times and decisions awaiting approval. Rehearse a scenario in which the chief executive is unavailable and inaccurate media claims are spreading. The test should expose approval bottlenecks and translation ambiguity before an actual incident.
Review credibility after containment
Once specialists approve the account, explain what happened, who was affected, what support was provided and which corrective actions can be disclosed. Avoid declaring the matter closed before recovery and customer follow-up are complete. Useful outputs include an incident communications playbook, stakeholder templates, a simulation and an after-action report. Belief System coordinates the communications dimension alongside the appointed technical and legal response teams.
Sources and reference points
Reference sources checked on 9 October 2026. The proposed methods and hypothetical situations are Belief System analyses. Your advisers determine the rules applicable to your project.
Continue your preparation
- Launching an AI business in Europe: what should a Hong Kong-listed company prove?
- European cloud buyers and a Hong Kong parent: how to explain data governance credibly
- Acquiring a European technology company: explain ownership without losing the operating story
Discuss your European expansion
Public affairs · Media relations · Reputation & crisis management · GEO & AI visibility