Maintenance Messages: 9 Scheduled Maintenance Templates to Copy

Maintenance messages tell employees when scheduled maintenance will take a system offline, what they will lose access to and when it will be back. Most IT teams send one email and hope for the best, then field tickets from people who never read it. The scheduled maintenance templates on this page cover the full cycle, from advance notice to completion, including a dedicated system maintenance message and short versions for desktop alerts, tickers and lock screens. For the wider framework these messages sit within, see our emergency alert system guide.

What is a maintenance message?

A maintenance message is a planned notice that tells employees which system will be unavailable or degraded, when the work starts and ends, what they need to do beforehand and who to contact. It is sent before, during and after scheduled maintenance, so that planned downtime does not feel like an unexpected outage.

Scheduled maintenance is different from an incident. You choose the date, you know the impact in advance and you can tell people in good time. That makes poor communication harder to excuse: if staff lose unsaved work or turn up for a shift to find a system offline, the failure was in the message, not the maintenance. If the problem is unplanned, use our major incident communication templates instead.

What should a scheduled maintenance message include?

A good scheduled maintenance message names the system, gives the start and end time with the time zone, describes the impact in plain terms, states any action people must take first, and says who to contact and when the next update will follow. Put the date, time and impact in the first line.

• System: the name employees know it by, not the server name. Say "the HR portal", not "HRAPP02".
• Window: the day, date, start time, end time and time zone. "Saturday 14 November, 20:00 to 23:00 GMT" leaves no room for doubt.
• Impact: what people will not be able to do, such as log in, submit expenses or access shared drives, and whether the system is fully offline or only slower.
• Action: anything to do beforehand: save work, log out, download files or use a workaround.
• Audience: which sites, teams or users are affected, so everyone else can ignore it.
• Contact: the service desk number or channel to use during the window.
• Sender: a recognised team name, so the message is trusted and not mistaken for phishing.

Avoid relying on the word "maintenance" alone. The GOV.UK Design System guidance on service unavailable pages advises against vague words such as "maintenance" or "improvements" and recommends stating the day, date and time the service will be available again. The same rule works inside an organisation: impact and time matter more to employees than the reason.

Scheduled maintenance message templates to copy

Replace everything in [square brackets]. The templates follow a scheduled maintenance window from start to finish. Each has a suggested channel; where a message is short enough for a desktop ticker or SMS, a short version is included.

1. Advance notice email

Send to affected users about a week before work on a business-critical system, or one to two days before routine work.

2. System maintenance message

A short, all-purpose notice for any system: post it on the intranet or status page, send it as an all-staff message, or adapt it for the channels below.

Ticker or SMS version:

3. Lock screen or wallpaper notice

Schedule to run on affected devices for the week before the window, so the message is seen without anyone opening an email.

4. Reminder desktop alert (day before)

Send to affected users 24 hours before the window. Use a standard pop-up, not a full-screen alert.

Ticker or SMS version:

5. Login page or app banner

Display on the login page or as a banner inside the application from a few days before until the work is complete.

6. Maintenance starting now

Send to affected users 10 to 30 minutes before the work begins.

Ticker or SMS version:

7. Maintenance overrunning

Send before the announced end time, not after it, as soon as you know the work will take longer.

Ticker or SMS version:

8. Maintenance cancelled or rescheduled

Send to everyone who received the original notice, on the same channels.

9. Maintenance complete

Send as soon as the system is confirmed working, on the channels you used for the reminder.

Ticker or SMS version:

How far in advance should you send scheduled maintenance messages?

Give about a week of notice for maintenance on business-critical systems and one to two days for routine work, then remind people the day before and again shortly before the window opens. Send a completion message as soon as the system is confirmed working, and an overrun message before the promised end time.

This follows the guidance from network monitoring vendor Paessler on announcing scheduled maintenance, which recommends at least a week for critical systems, one or two days for smaller routine work, and more reminders as the impact grows. Publish your notice policy so employees know what to expect, and stick to it.

Which channel should each maintenance message use?

Use email for the advance notice, a lock screen or banner for the days leading up to the window, and a desktop alert or ticker for the reminder and the start. Send the overrun and completion messages on the same channels as the reminder. Avoid relying on any channel that the maintenance itself takes offline.

Be careful when the maintenance affects the channel itself. If you are upgrading the mail server, do not rely on email to announce that it is back. Our article on communicating when the outage is the channel covers this in more detail.

Scheduled maintenance or major incident: which templates do you need?

Use maintenance message templates when the work is scheduled and you control the timing. Use incident templates when a service fails without warning. Scheduled maintenance needs advance notice and reminders; an incident needs immediate alerts and regular updates. If scheduled work fails or overruns badly, treat it as an incident from that point.

Many IT teams keep both sets ready and switch between them. A maintenance window that runs hours over the planned end time, or that breaks a dependent system, is no longer planned: move to the major incident communication templates and your incident process. For safety events such as evacuations or site closures, use our emergency alert templates.

Sending maintenance messages with Heed

The templates above only work if people see them. Heed is an all-in-one internal communication platform that reaches employees across desktop, mobile and digital signage, so a maintenance notice does not depend on an inbox. You can send pop-up or full-screen desktop alerts, run a scrolling desktop ticker that can repeat until read, and schedule a corporate lock screen campaign to go live and expire on set dates ahead of a window.

Messages can be targeted by department, location or role through Active Directory and SAML groups, so only affected users are told. Acknowledgement tracking gives named, timestamped confirmation of who has read each alert, and alerts can be triggered from tools such as ServiceNow and Jira, or via API and webhooks. Heed is ISO 27001 certified and available on premises or in a regional cloud. To see how this fits a wider IT communication process, visit our major incident management solution. Want to see a maintenance notice as a live desktop alert? Book a demo.