About this tool
A maintenance window has to cover more than the planned command execution. It also needs room for pre-checks, validation, troubleshooting and rollback if the change does not behave as expected.
This calculator compares the full scheduled window with the planned work duration and shows how much time remains as buffer. That can help reviewers spot changes that have no realistic backout margin.
How to use it
- Enter the maintenance start and end times.
- Enter the estimated planned work duration in minutes.
- Calculate and review the remaining window before approving or executing the change.
Example: four-hour window with three hours of work
A 00:00–04:00 window contains 240 minutes. If planned work is 180 minutes, 60 minutes remain for validation, troubleshooting and rollback.
Engineering notes
- Build rollback decision points into the MOP rather than waiting until the end of the window to decide whether to back out.
- When multiple teams share a window, include dependencies and handoff time in the planned duration.
Frequently asked questions
How much rollback time should I reserve?
There is no universal number. It should reflect the complexity and worst credible recovery path for the specific change.
Should pre-checks count against the window?
If they occur after the approved start time, yes. Anything that consumes the maintenance period reduces the remaining buffer.
Can I use this for overnight changes?
Yes. Enter the correct dates so a window that crosses midnight is calculated properly.