Why it matters
Scheduled maintenance matters because teams need a precise shared meaning for planned work communicated in advance on a status page. Vague language turns incidents into arguments about words instead of fixes.
When everyone uses the same definition, alerts, status updates, and post-incident reviews stay aligned.
How it works
In practice, planned work communicated in advance on a status page shows up as a concrete signal you can measure or communicate. Operators define what good looks like, watch for deviations, and record what happened when expectations break.
The useful version of scheduled maintenance is operational: it changes who gets notified, what customers see, or which metric a team reviews after an incident.
Practical example
Imagine a team operating around database upgrade window Sunday 02:00 UTC. When observed behavior stops matching the definition of scheduled maintenance, the team treats that change as a reliability event with a clear owner and next step.
Common misconception
Maintenance is secret so customers are not worried
That reading usually collapses distinct ideas into one slogan. Keep scheduled maintenance tied to observable behavior so the definition stays useful under pressure.
How Fajita handles this
Announce maintenance early. See create maintenance.