Maintenance Web app

Explain the interruption and find new information.

5 checks · 2 content groups

Checklist contents

Review progress

Information and structure

Compare information and presentation in context of use.

Clearly state that the product cannot be usedState the scope of the disruption and its known cause in easy-to-understand terms.Don't give a firm reopening time when you only have an estimate.Example “Estimated recovery in about 30 minutes. Last update: 10:15.”Indicates time or progressState the estimate if any and keep the update date clear.Use a time zone and update date; If you don't know when it will be restored, say you don't have an estimate yet instead of making an unfounded appointment.There is independent monitoringThe status page link remains active while the product is offline.The status page should use independent infrastructure or remain accessible during an incident; check the link when the app is not working.

Actions and status

Try the operation, change the status and continue working.

Maintain support in case of urgent needIndicates the receiving channel and information to send.If the channel is still active during the interruption; does not lead users to a form within the main section under maintenance.Give it another try on purposeKeep familiar identities and shortcuts, avoid endless unresponsive loading.Retry only if the user is proactive or has a clear delay; holds the task address to return to after the service restores.

Progress is saved automatically in this browser.

GUIDANCE

How to review

Clearly state that the product cannot be used

Don't give a firm reopening time when you only have an estimate.

EXAMPLES

Usage examples

Clearly state that the product cannot be used

“Estimated recovery in about 30 minutes. Last update: 10:15.”

Maintenance Web app

Information and structure

Actions and status

How to review

Clearly state that the product cannot be used

Usage examples

Clearly state that the product cannot be used

Find a checklist

No checklists found