# Plan a maintenance window overrun decision

Illustrative planning brief; no automatic product import.

Illustrative planning case: A migration estimate is 40 minutes, but the approved maintenance window lasts 45 minutes with no rollback reserve.

## Decision

Reserve explicit recovery time before beginning the migration.

## Owned work

- Measure trial duration
  - Owner role: Release investigator
  - Acceptance evidence: A representative rehearsal records migration and recovery times.
- Set stop point
  - Owner role: Migration engineer
  - Acceptance evidence: The latest safe abort time is calculated from recovery evidence.
- Review window fit
  - Owner role: Release reviewer
  - Acceptance evidence: The change proceeds only if both work and recovery fit.

## Workflow

1. Record migration, recovery and acceptance durations from a representative rehearsal.
2. Compare those durations with the approved window and set the latest evidence-based stop point.
3. Hold or revise the window if work and recovery cannot fit; review actual progress before the recovery reserve is consumed.

## Judgment

Do not begin when the agreed recovery margin is absent.


## Filled illustrative release coordination record

The synthetic rehearsal takes 38 minutes and recovery takes 12. A 45-minute window cannot contain both. The release is rescheduled into a 70-minute window with an abort review at minute 45. The estimate remains a trial observation, not a promise; unexpected stalls must trigger the recorded stop decision.
Decision: Reserve explicit recovery time before beginning the migration.
Review boundary: Do not begin when the agreed recovery margin is absent.
This example uses synthetic conditions. Replace its observations with project evidence and record any changed assumptions before adopting the plan.


## Working artifact

- Duration variance / Trial exceeds expected migration time / Review at checkpoint before reserve is consumed
- Recovery reserve / Twelve minutes required for reversal / Abort before remaining window becomes insufficient
- Service check / Migration ends but usability unverified / Use reserved time for acceptance checks


## Workflow questions

### Why reserve rollback time?

An abort at the end of the window still requires recovery work before service is usable.

### Can average duration define the stop point?

Use a reviewed allowance informed by variation and recovery trials, rather than the most convenient average.

## Product connection

Use the manual work brief to discuss task ownership, review evidence and next actions in TeamBoost. Release execution remains a separate project workflow; the download performs no deployment or import.

Confirm account availability before adopting this manual outline.


## Reserve recovery before starting work

Use project rehearsal evidence instead of treating a forty-minute estimate as a guarantee.

### Rehearsal

Bounded test: Measure migration, recovery and acceptance checks on a representative fixture.

Review condition: Record variability and the fixture limits.

### Window decision

Bounded test: Fit the work and recovery reserve within the approved window.

Review condition: Revise the plan when the evidence exceeds the available time.

### Live checkpoint

Bounded test: Compare actual progress with the agreed latest safe stop point.

Review condition: Stop before consuming the recovery reserve when the boundary requires it.