{"id":11966,"date":"2017-09-06T10:04:44","date_gmt":"2017-09-06T10:04:44","guid":{"rendered":"https:\/\/www.process.st\/templates\/scheduled-maintenance-notification\/"},"modified":"2024-02-28T20:45:07","modified_gmt":"2024-02-28T20:45:07","slug":"scheduled-maintenance-notification","status":"publish","type":"post","link":"https:\/\/www.process.st\/templates\/scheduled-maintenance-notification\/","title":{"rendered":"Scheduled Maintenance Notification"},"content":{"rendered":"
\n

Introduction: <\/h2>\n
\n
\n <\/a>
\n <\/figure>\n<\/p><\/div>\n
\n

No matter what kinds of systems you have in your organization or installed for your clients, scheduled maintenance is unavoidable. The best thing you can do to help is ensure everyone that will be affected is notified ahead of time.<\/p>\n

The purpose of this process is to generate a report for notifying departments of scheduled maintenance.<\/p>\n

See an example of the report below:<\/p>\n<\/p><\/div>\n

\n
\n <\/a>
\n <\/figure>\n<\/p><\/div>\n
\n

It's also useful as a reminder of how to format scheduled maintenance notifications, and a way to easily train new staff.<\/p>\n

(For an automated way to notify users of maintenance, it might be possible to feed the software's status page to a Slack channel using Zapier<\/a>.)<\/em><\/em><\/p>\n<\/p><\/div>\n<\/section>\n

\n

Identify the affected products, servers, systems, etc. <\/h2>\n
\n
\n
\n
\n <\/a>
\n <\/figure>\n<\/p><\/div>\n<\/section>\n
\n

Identify affected departments <\/h2>\n
\n

Edit the form fields below to reflect the departments in your organization.<\/p>\n<\/p><\/div>\n

\n
\n