A network outage, failed server, compromised account or inaccessible business system can stop work quickly. The quality of the response depends less on panic and more on having clear priorities, authorised contacts and reliable technical information.
Protect people, evidence and data
Do not repeatedly restart, delete suspicious messages or make uncontrolled configuration changes. Record what happened, when it started and which users or systems are affected.
Use one escalation route
Nominate an incident lead and a single route into IT support. Multiple people contacting different suppliers can create conflicting changes and slow diagnosis.
Define the business priority
Explain which process is blocked, how many people are affected and whether there is a safety, contractual, financial or data-protection concern. Technical severity and business impact are not always the same.
Communicate without speculation
Give employees short, factual updates and a clear workaround if one exists. Avoid announcing a cause before it is confirmed.
Review after recovery
Once service is restored, identify the root cause, gaps in monitoring or resilience, and the actions needed to prevent recurrence.
Explore backup and business continuity or book a free IT health and risk review.