> ## Documentation Index
> Fetch the complete documentation index at: https://docs.scaling.cloud/llms.txt
> Use this file to discover all available pages before exploring further.

# Schedule a Maintenance Window

> Announce planned work on your public status page — set the time window, write a customer-facing notice, pick affected components, and manage it through to completion.

This guide walks you through announcing planned work on your [public status page](/concepts/status-pages): scheduling a maintenance window, writing the customer-facing notice, and driving it through its lifecycle. For the underlying model — states, the markdown body, how windows affect the banner — see [Scheduled maintenance](/concepts/scheduled-maintenance).

<Frame caption="Scheduling a maintenance window in the dashboard">
  <img src="https://mintcdn.com/scalingcloud/5-FlXcH6ySIwHzG0/images/placeholder.svg?fit=max&auto=format&n=5-FlXcH6ySIwHzG0&q=85&s=18ab9c45531fe92b117df1f9652cb357" alt="Schedule maintenance form" width="1200" height="675" data-path="images/placeholder.svg" />
</Frame>

## Prerequisites

* A [status page](/guides/publish-status-page). The window appears on it whether or not the page is published, but customers only see it once the page is live.
* The [components](/concepts/components) the work affects, in your catalog.
* A signed-in scaling.cloud account in the organization.

## Schedule a window

<Steps>
  <Step title="Open status page settings">
    Go to **Settings → Status Page** in the scaling.cloud dashboard and find the **Scheduled maintenance** section.
  </Step>

  <Step title="Click “Schedule maintenance”">
    This opens the maintenance form.
  </Step>

  <Step title="Write the notice">
    * **Title** — a short summary customers will read, e.g. `Database engine upgrade`.
    * **Details** — the body of the notice. **Markdown is supported** and it's shown publicly, so link to a tracking issue or list the expected impact. Headings, bold/italic, lists, and links all render; anything unsafe is stripped automatically.
  </Step>

  <Step title="Set the time window">
    Pick a **Starts at** and **Ends at** in your local time. The end must be after the start.

    <Tip>
      You don't have to be online when the window starts. At the start time, the page automatically shows the maintenance as **In Progress** — see [the note on going live by the clock](/concepts/scheduled-maintenance#the-lifecycle).
    </Tip>
  </Step>

  <Step title="Select affected components">
    Tick the components the work touches. While the window is active, each shows as **maintenance** on the page (unless an incident or override is already worse on that component), and the overall banner reads **Under maintenance**.
  </Step>

  <Step title="Schedule it">
    Click **Schedule**. The window appears in the list as **Scheduled**, and — once your page is published — in the **Scheduled Maintenance** section of the public page as **Upcoming**.
  </Step>
</Steps>

## Manage the window

Each window in the list shows its state and offers the actions valid for that state:

| State                         | Available actions                  |
| ----------------------------- | ---------------------------------- |
| **Scheduled**                 | **Edit**, **Start**, **Cancel**    |
| **In progress**               | **Edit**, **Complete**, **Cancel** |
| **Completed** / **Cancelled** | None — terminal                    |

* **Edit** — change the title, body, time window, or affected components. Allowed while the window is `scheduled` or `in_progress`; terminal windows can't be edited.
* **Start** — mark the work as begun (moves to **In progress**).
* **Complete** — mark the work as finished (moves to **Completed**). It stays on the public page for **48 hours**, then drops off.
* **Cancel** — call the work off. A cancelled window is **removed from the public page immediately** and never shown again.

<Note>
  **Start** and **Complete** are about your own workflow and timing — the public page already reflects the window by its clock times. Use them to mark reality and (in future) to time customer notifications precisely.
</Note>

## Verify it

Open your status page in an incognito window (no account needed) and confirm:

* The window appears in the **Scheduled Maintenance** section with the right state (**Upcoming** before the start, **In Progress** during).
* The body renders as you intended — links work, lists are formatted.
* During the window, the affected components show **maintenance** and the banner reads **Under maintenance** (unless a real incident outranks it).

## Next steps

* [Scheduled maintenance](/concepts/scheduled-maintenance) — the full model: lifecycle, public states, banner behaviour, and the JSON feed shape.
* [Connect a custom domain](/guides/connect-custom-domain) so the page is served at `status.example.com`.