Skip to main content
OpsRoadmaps

Checklists / network-change-readiness

Network Change Readiness Checklist

Before a change to routing, filtering or topology: a tested back-out, an answer for losing your own access, a defined blast radius, and someone watching the paths rather than the devices.

8 steps · 7 required · last reviewed (next review 2027-03-20) · updated 2026-09-20

Related focus areas:NetOps

Sign in to run this checklist

Run this before any change to production network configuration. Network change has unusual blast radius — a single routing or filtering edit can disconnect a site — and unusually, the change can remove your ability to undo it.

The out-of-band access item is the one that turns a ten-minute mistake into a site visit.

  1. The change is written down, including the exact configuration to be applied

    required

    Changes composed at the console under time pressure are the ones that go wrong in ways nobody can reconstruct.

  2. A back-out has been written and is known to work on this device type

    required

    A back-out invented during the failure is not a back-out.

  3. Out-of-band access exists in case the change removes management connectivity

    required

    Locking yourself out of the device you are changing is a routine, foreseeable failure with an expensive recovery.

  4. The blast radius is understood: which services and sites are affected if this is wrong

    required

    Network dependencies are shared, so the people affected are usually not the people making the change.

  5. Current device configuration has been captured before the change

    required

    Diffing against the pre-change state is how you find what you actually altered.

  6. A maintenance window is agreed and the dependent teams have been told

    required

    Unannounced network change produces several teams debugging their own systems in parallel.

  7. Verification includes end-to-end path checks, not just device status

    required

    Every device can report healthy while the path between them is broken.

  8. The change has been validated against a model or lab first

    optional

    Modelling reachability before applying is how larger estates stop learning this the expensive way.

Run it against your real gaps

A checklist is most useful when you know which controls you are actually missing. A free OpsRoadmaps assessment scores your controls with explainable findings and builds a roadmap from the results.

Assess my stack

Checklists document self-reported practice. Items were last reviewed 2026-09-20 — adapt them to your own environment.