diff --git a/content/en/service_management/status_pages/_index.md b/content/en/service_management/status_pages/_index.md
index 32a7fe3ef39a6..0984704b6e7f3 100644
--- a/content/en/service_management/status_pages/_index.md
+++ b/content/en/service_management/status_pages/_index.md
@@ -22,12 +22,13 @@ further_reading:
 
 {{< img src="service_management/status_pages/shopist_status_page.png" alt="Example status page showing service components with their current status and recent incident updates" style="width:100%;" >}}
 
-Status Pages is part of Datadog's Incident Response suite, alongside On-Call and Incident Management. It lets your team proactively communicate **service availability** and **incidents** with customers or internal stakeholders through a shareable web page.
+Status Pages is part of Datadog's Incident Response suite, alongside On-Call and Incident Management. It lets your team proactively communicate **service availability**, **degradation**, and **planned maintenance** with customers or internal stakeholders through a shareable web page.
 
 Use Status Pages to:
 
 * Share the availability of critical systems and features
-* Communicate service disruptions clearly during incidents
+* Communicate service disruptions clearly during service degradations
+* Announce scheduled maintenance and planned downtime in advance
 * Reduce inbound support volume with proactive email notifications
 
 ## Configure permissions
@@ -57,7 +58,7 @@ To create, update, or publish Status Pages, you must have `status_pages_settings
     </tr>
     <tr>
       <td style="white-space: nowrap;">Status Pages Notice Write<br><code style="white-space: nowrap;">status_pages_incident_write</code></td>
-      <td>Publish and update Incidents.</td>
+      <td>Publish and update Notices for degradations and maintenance windows.</td>
       <td>Datadog Admin Role</td>
     </tr>
   </tbody>
@@ -130,6 +131,28 @@ After a notice is published, the notice:
 
 You can post **updates** over time to keep users informed, and then mark the notice as **Resolved**.
 
+## Schedule maintenance windows
+<!-- Image placeholder
+{{< img src="#" alt="Status page showing a scheduled maintenance window for upcoming infrastructure work" style="width:100%;" >}}-->
+
+Maintenance windows allow you to proactively communicate planned downtime or service impact before it happens. Unlike [notices](#add-a-notice) which are used for unplanned incidents, maintenance windows are scheduled in advance for infrastructure upgrades, system maintenance, database migrations, and other planned work. Proactively communicate scheduled downtime so you can keep your customers informed and lessen the load on your support team.
+
+### Publish a maintenance window
+
+1. From a status page, click **Public Notice** to open the maintenance window modal.
+1. Under **Notice type**, select the "Scheduled Maintenance" tab and provide:
+   | Field | Description |
+   | ---- | ---- |
+   | **Title** | Clear description of the maintenance activity <br>*Example: Database infrastructure upgrade* |
+   | **Maintenance window** | Scheduled time range for the maintenance window, including start and end times |
+   | **Messages** | Set the messages that you want to automatically publish for each status update |
+   | **Components impacted** | One or more components that is affected during maintenance |
+   | **Impact** | Default impact per component during a maintenance window. If an incident occurs during maintenance, components can transition to: <br>- Degraded Performance <br>- Partial Outage <br>- Major Outage |
+   | **Notify Subscribers** | Toggle to notify subscribers in advance and for each automatic update|
+1. Click **Review Notice** and click **Publish Notice**.
+
+After scheduling, the maintenance window appears on the status page under "Upcoming Maintenance" with the scheduled time range. When the window begins, component status automatically updates to "Undergoing Maintenance" and returns to "Operational" when it ends (unless manually overridden). You can edit the messages, post updates if plans change, reschedule the window, or cancel it if no longer needed.
+
 ## Email subscriptions
 
 Email subscriptions on status pages are **double opt-in**: users must confirm their email address before they are added as subscribers. After entering an email to subscribe, a confirmation email is sent, and the subscription is only activated after the user clicks the confirmation link.