## TL;DR
A maintenance notice needs four lines: what is happening (in plain words), exactly when (with timezone), what the customer will experience (downtime, slowness, or nothing), and what they should do (usually nothing). Lead with the impact, not the technical details. "The dashboard will be unavailable for 30 minutes on Tuesday" beats three paragraphs about database migration.

## The query

```text
how to write a maintenance notice customers understand
```

## Use this when

- Scheduling planned maintenance
- Writing status page communications
- Notices confuse more than they inform
- Building the maintenance comms template

## Not for

- Unplanned incident communications
- Marketing emails
- Internal change notices
- API deprecation notices

## Steps

### 1. Lead with the customer impact

First sentence: what they will experience and when. "On Tuesday between 2 and 2:30am ET, the dashboard will be unavailable." Everything else is supporting detail.

Expected output: an impact-first opening line.

### 2. Give exact times with timezones

Date, start, end, and timezone. Better: include a link that converts to the reader's timezone. "Tuesday morning" is not a time.

Expected output: precise times with zone.

### 3. Say what they should do

Usually: nothing, or save your work beforehand, or avoid the affected feature during the window. If the answer is nothing, say "you do not need to do anything." Explicit inaction beats anxious guessing.

Expected output: a clear action or explicit no-action.

### 4. Explain the why in one sentence

"We are upgrading our database to keep things fast and reliable." One sentence. Customers accept maintenance they understand; they resent maintenance described in jargon.

Expected output: a one-sentence plain reason.

### 5. Send it twice and post it once

Email a week ahead, remind the day before, and keep it on the status page during the window. One notice is no notice; people miss emails.

Expected output: the notice in three places on schedule.

## Template: the notice

```text
Subject: Scheduled maintenance: [service] unavailable [date], [time range with zone]

On [day, date] between [start] and [end] ([timezone]), [service] will be [unavailable/slow/read-only].

What this means for you: [plain impact description].
What you should do: [nothing / save work before / avoid (feature) during the window].
Why: [one plain sentence].

We will post updates on [status page] during the window. Questions: reply here.
```

## Variant phrasings

### planned downtime announcement

Steps 1 through 3 plus the template.

### maintenance window email template

Full sequence. The double-send in step 5 matters.

### how to announce system maintenance

Steps 1 and 4. Impact first, one-sentence why.

## Why it works

Customers do not care about your infrastructure; they care about their Tuesday. Impact-first writing respects that, exact times prevent timezone confusion, and the explicit "do nothing" removes anxiety. The repetition schedule acknowledges that nobody reads every email.

## Edge cases

- The window slips: update the status page and send a correction immediately. Silence during a slipped window reads as an outage.
- No-downtime maintenance: say so upfront. "You will not notice anything" is the best notice.
- Recurring maintenance windows: establish the pattern (first Sunday monthly) so each notice is a reminder, not news.
- Enterprise customers: direct notice to their ops contacts in addition to the general announcement.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_outjP25s8uC5_7KpyrobRw