Planned work on a server, the services that pause with it, and the people who should know in advance.
The admin plans to update the file server on Saturday from 10 to 12. The work runs until 3. AverDesk records both: the announced window and the actual one. The next plan is based on how long it really took, not on hope.
Before announcing, the admin opens the file server and sees what sits on top of it: the shared drive, the accounting program that saves its files there, and the two departments that use both. Those are the people to warn. They get the message on Friday, not on Saturday when their phones light up. (The impact is traced through recorded dependencies: host, service instance, service, product.)
While the window is open, the file server and everything on it get an orange ring on the map and a maintenance mark in the status view. The night-shift engineer tells a planned pause from an outage at a glance, and nobody opens a ticket for work that was scheduled.
Notifications go out in the app, by email or to Telegram. They can be set for the whole platform, a subscription, an organization, a team or one person, so a team lead sees their team’s work and the accountant hears only about the file server. Repeated identical alerts are muted: one message per problem, not one per minute.
Record one maintenance window (the time the work is planned for) and see who it touches. Free for one operator, no card.
