How to Write a Maintenance Notice

A maintenance notice should tell people whether they can work, when the interruption begins, and where to look for updates.

Put The Window Up Front

Wrivio account services will undergo planned maintenance on Saturday, 3 August, from 02:00 to 03:00 UTC.

Always include the date, start time, end time, and time zone. For a regional audience, add the local equivalent.

Describe User Impact

Be specific:

During the window, users may be unable to sign in or refresh cloud credit status. Rewrites in Local mode are not affected.

Do not say “some services may be intermittently unavailable” if you know which ones. Do not promise zero interruption unless that is genuinely assured.

Explain Preparation And Recovery

Tell users whether they need to save work, sign out, avoid a transaction, or do nothing:

No action is required. If you are already signed in, your session should remain active.

Then explain how completion will be communicated:

We will update the status page when maintenance is complete.

If the work could overrun, state the contingency and next update time.

Maintenance Notice Prompt

Rewrite this as a clear planned-maintenance notice. Lead with the affected service, date, start and end time, and time zone. Explain expected impact, required user action, unaffected functions, and the update channel. Preserve all technical facts and do not promise availability beyond the source.

Send an internal version to support teams before the public notice so responses are consistent. For unplanned events, use an incident report. For release communication after successful work, see release notes people read.

Try Wrivio’s rewrite workflow to make a technical maintenance draft clear for the people who use the service.