# Access switch replacement — fictional example

Generated: 2026-10-07T01:47:21.084Z
Status: working plan; requires local review and approval.

## Change record
Owner: Change owner
Reviewer: Peer reviewer
Scope: Replace a lab access switch. Inventory every connected service before adapting this example.
Window: 2026-10-15 22:00 (UTC+00:00) to 2026-10-16 00:00 (UTC+00:00)
Planned implementation finish: 2026-10-15 22:55 (UTC+00:00)
Latest planned rollback start: 2026-10-15 23:20 (UTC+00:00)
Rollback reserve: 25 min; recovery verification buffer: 15 min.
Remaining time before rollback cutoff: 25 min.

## Review items
- No missing fields detected. This is not an approval or a safety certification.

## Implementation sequence

1. Record baseline and confirm rollback access
   Owner: Change owner | 15 min | 2026-10-15 22:00 (UTC+00:00) to 2026-10-15 22:15 (UTC+00:00)
   Verify: Baseline saved; tested console or independent management path available.

2. Execute the approved replacement procedure
   Owner: Change owner | 25 min | 2026-10-15 22:15 (UTC+00:00) to 2026-10-15 22:40 (UTC+00:00)
   Verify: Match physical patching and approved device configuration.

3. Validate affected services and record evidence
   Owner: Service tester | 15 min | 2026-10-15 22:40 (UTC+00:00) to 2026-10-15 22:55 (UTC+00:00)
   Verify: Compare each expected result to the recorded baseline.

## Rollback
Triggers: Start rollback if the required service checks fail, management access cannot be restored, or the planned rollback cutoff is reached without acceptance.
Procedure: Use the separately reviewed device-specific restore procedure. Preserve the previous device/configuration and a verified physical patch map. Reconnect the original path, then repeat the service checks.

## Evidence

### Management access
Baseline: Lab example: independent console path confirmed before work.
Pass criterion: Approved administrator can reach the intended management endpoint.
Observed: Not recorded
Status: pending

### Service owner acceptance
Baseline: Lab example: application test passes on the original path.
Pass criterion: Repeat the same application transaction successfully after the change.
Observed: Not recorded
Status: pending

### Uplink and error counters
Baseline: Record current link state and counter timestamp; values not provided in this example.
Pass criterion: Expected links and forwarding state restored; assess counter changes over the agreed interval.
Observed: Not recorded
Status: pending

## Communications and handoff
Before: confirm approval, named test contacts, console access and stop authority. During: log deviations and timestamps. After: notify the service owner, record the observed result and hand off unresolved items.

Planning aid only. Durations are estimates. Verify device-specific actions against current vendor documentation and your approved procedures.