IT Outage Notification
The IT Outage Notification broadcasts what service is unavailable, who is affected, what to do now, and where to find verified resolution updates.
Every employee gets a seat — priced per employee in Communications & Intranet, quoted with this template ready.
Rolled out to every employee at AutoZone (125,000), PetSmart (50,000+), A.S. Watson and Raley's (20,000) — and at larger retailers we are not permitted to name.
Built for: Technology and SaaS · Retail and e-commerce · Healthcare operations · Financial services · Manufacturing
Overview
The IT Outage Notification template is a short employee broadcast for reporting that a system or service is unavailable or degraded. Its body puts the headline fact first, then captures the affected audience or locations, the date and time with time zone, one primary action, the current estimated resolution, and the official source for verified updates. A support contact gives recipients a clear next step when the status channel does not answer their question.
Use this template when an outage changes how employees work, transact, access records, support customers, or use an internal platform. It is suitable for an initial alert, a meaningful status change, or a restoration notice adapted to the same structure. Keep the message reusable by replacing bracketed fields rather than embedding tenant-specific names, dates, or unsupported promises.
Do not use it as a substitute for a detailed incident record, root-cause analysis, recovery runbook, or maintenance policy. Those materials belong in the appropriate operational system and can be linked from the broadcast if needed. For safety or security incidents, confirm whether a critical broadcast, acknowledgment, or a separate emergency communication is required before publishing. The default settings are non-critical, no acknowledgment, comments allowed, and reactions allowed, which fits ordinary service-status communication but should be reviewed for each event.
Standards & compliance context
- For safety-related outages, align the broadcast with OSHA and applicable emergency-notification expectations by stating the immediate hazard, required action, and authoritative follow-up channel.
- For mandatory operational, security, or compliance notices, enable acknowledgment tracking only when recipients must confirm they received or understood the instruction.
- Maintain a separate incident record for audit evidence, timelines, decisions, and technical details because this broadcast is a concise employee communication.
- Apply internal communications standards by stating what is happening, when it began, and what the audience must do in plain language.
- Use CERC principles by communicating quickly, accurately, and credibly, correcting estimates or impact statements when verified facts change.
General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.
How to use this template
- Clone the template and replace the bracketed fields with the affected service, current availability state, audience or locations, start time, and time zone.
- Confirm the primary action, approved workaround, current resolution estimate, official status channel, and support contact with the incident owner before publishing.
- Select the employee audience that needs to change behavior and keep the broadcast body focused on one call to action.
- Review the message for a first-sentence headline fact, plain language, a single update source, and an estimate clearly labeled as such, then send it through the approved channel.
- Monitor comments and the official status channel, publish a follow-up when impact or timing changes, and correct any inaccurate detail promptly.
- Close the communication with a restoration update or direct readers to the incident record for post-incident review without turning the broadcast into a long technical report.
Best practices
- Open with the service state and affected audience so recipients understand the impact before reading further.
- Include the date, time, and time zone for the outage start because employees may work across locations.
- Give one primary action, such as using an approved workaround or pausing affected transactions, rather than a list of competing instructions.
- Use “under investigation” when no reliable resolution estimate exists instead of publishing a speculative time.
- Link or name one official status channel and ensure it is updated consistently throughout the incident.
- Write in plain language at roughly an eighth-grade reading level and keep the broadcast body within a single-read length.
- Set is_critical to true only for an outage requiring immediate attention because routine critical alerts create alert fatigue.
- Enable acknowledgment only when the message contains a mandatory-read instruction, and use comments for questions that support staff can monitor.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What outages is this notification template designed for?
Use it for unavailable or degraded systems, applications, networks, platforms, and business services. It works when employees need to change behavior, use an approved workaround, or pause affected transactions. It is less suitable for a routine maintenance reminder or a detailed incident postmortem.
Who should publish an IT outage notification?
An authorized IT service desk, incident manager, communications lead, or system owner should publish the broadcast. The publisher should confirm the affected service, audience, start time, current status, and official update channel before sending. Keep the named contact or support route monitored after publication.
When should I send updates during an outage?
Send the initial announcement as soon as the outage and its audience are reasonably confirmed. Post updates when the status, workaround, impact, or estimated resolution changes, and close the broadcast when service is restored or a separate recovery notice is issued. Avoid repeating unchanged messages because unnecessary alerts can reduce attention to critical notices.
Should this outage notice be marked critical or require acknowledgment?
Leave both settings off for a standard service disruption unless the outage creates an immediate safety, security, regulatory, or business-continuity risk. Use critical status only when rapid attention is genuinely necessary. Require acknowledgment for a mandatory-read instruction, not for a casual status update or routine availability issue.
How do I customize the message without making it confusing?
Replace each bracketed field with the service name, current state, affected audience or locations, start time and time zone, one primary action, resolution estimate, official status channel, and monitored support contact. Keep the headline fact in the first sentence and use plain language. Do not add multiple competing calls to action or paste a long incident log into the broadcast.
Can this template connect to status pages or support workflows?
The template identifies where verified updates should appear, so you can insert your approved status page, internal channel, ticket queue, or IT support route. Configure integrations separately in your communications or incident-management tools. Confirm that recipients can access the linked channel before publishing.
What is a common mistake when sending an outage alert?
A frequent mistake is saying that a service is down without stating what employees must do. Another is publishing an unverified resolution time or directing people to several update sources. Use one primary call to action, label estimates as estimates, and update the same official channel as facts change.
How is this better than writing an outage message from scratch?
The reusable format prevents common omissions by prompting for the service, impact, start time, action, resolution estimate, update channel, and contact. It also keeps the body short enough for a single broadcast read. You still need to verify the incident facts and choose the correct audience before sending.
Related templates
Go deeper on the topic
-
Asynchronous communication is any exchange where the sender and receiver are not in the same moment — written messages, recorded video, shared docs, threaded...
-
Benefits administration ("ben admin") is the operational work of running employee benefits — health plans, retirement, life, disability, voluntary benefits —...
-
A boomerang employee is a former employee who returns to the company after working elsewhere — typically 18 months to 5 years later. The category was...
-
Change management is the structured discipline for moving people, processes, and organizations through transitions — new systems, new structures, new...
Ready to use this template?
Every employee gets a seat. Request pricing for Communications & Intranet and we quote into a workspace with IT Outage Notification ready.
Rolled out to every employee at AutoZone (125,000), PetSmart (50,000+), A.S. Watson and Raley's (20,000) — and at larger retailers we are not permitted to name.
