What is Maintenance & Outage Planning?

What is maintenance and outage planning?

Maintenance and outage planning is the IT operations practice of scheduling planned work on systems and services into agreed windows, assessing its impact and communicating it so disruption to users is minimized.

It sits inside change enablement. ITIL 4 gives that practice the purpose of maximizing the number of successful service and product changes by making sure risks have been assessed, authorizing changes to proceed and managing the change schedule. A maintenance window is a pre-agreed slot in that schedule; a planned outage is a known loss of service inside a window; an unplanned outage is an incident. The stakes are not small. Uptime Institute's Annual Outage Analysis 2025 found that 54% of operators' most recent significant outage cost more than $100,000, 20% cost more than $1 million, and human error plays a part in two-thirds to three-quarters of all outages, with failure to follow procedures up ten points on the year before.

Why it matters

• Announced downtime is tolerated; surprise downtime is not. The same hour of patching reads as a plan or as an incident depending on whether users were told.
• Windows protect the business calendar. Month-end close, campaign launches and trading hours are known in advance and can be kept clear.
• It is the record. A planned outage with an approved window, an impact assessment and a post-review is evidence for auditors and for the next service review.

How does maintenance and outage planning work?

1. Publish the windows. Agree standing maintenance windows per service with the business, and record the blackout periods when nothing may change.
2. Raise the request. Each piece of planned work enters the change schedule with its scope, duration, rollback plan and the services it touches.
3. Assess the impact. Use the dependency map to find every downstream service and user group, and check the window against other scheduled work.
4. Authorize. Standard maintenance is pre-approved; anything novel or high-risk goes through the change authority.
5. Communicate. Notify affected users when the work is authorized, again shortly before it starts, at the start, and when service is restored.
6. Execute and review. Run the work, confirm restoration, and record what happened so the next window is better planned.

Planned, emergency or unplanned?

Related terms

• Change management in ITSM
• Release management
• Dependency mapping in IT operations
• Incident management
• SLA and OLA governance
• CMDB

In SmartSuite

SmartSuite IT Operations Management keeps changes, maintenance windows and operational activities in one shared maintenance calendar, captures planned and unplanned outages with structured workflows for response, communication and follow-up, and maps systems, services and dependencies so the impact of a window is visible before it is approved.

Frequently asked questions

What is a maintenance window?

A maintenance window is a recurring or one-off period agreed with the business during which planned work on a service may take place and some disruption is accepted. It is published in the change schedule, chosen for low usage, and used to decide whether a given change can be pre-approved or needs a specific authorization.

Does a planned outage count against the SLA?

That depends on the agreement. Many service level agreements exclude agreed maintenance windows from availability calculations, provided the work stays inside the window and users were notified as the agreement requires. Work that overruns the window, or a window that was never agreed, usually counts as downtime, so the contract wording and the schedule should match.

How far ahead should users be told?

ITIL sets no fixed notice period; the right lead time follows the service's user base and the agreement. A working rule is to announce when the change is authorized, remind shortly before the window opens, post at the start and confirm at restoration. Emergency maintenance follows the same sequence with the notice compressed.