An ISP cutover checklist should connect the carrier’s work to the systems that depend on it at your location. Before the visit, confirm the circuit handoff, equipment, access, technical contacts and approved recovery decision. After the change, record the agreed network and business-system checks separately.
This guide helps an internal IT or MSP project owner prepare the onsite assignment. The technical owner and carrier must set the actual configuration, change sequence, test criteria and recovery steps for the site.
An ISP cutover is the planned transition from one internet service arrangement to another. The carrier’s service activation, onsite connection work and checks of the site’s dependent systems may be separate work packages with different responsible people.
Who is responsible for each part of an ISP cutover?
A carrier may confirm its service while the site still needs physical connections, equipment work or application checks. Put the boundaries in the work request so each person knows which result they are responsible for.
- Carrier: confirm the service handoff, appointment, circuit reference and support route for the agreed work.
- Customer or MSP technical owner: approve the design and change steps, provide authorized configuration work and decide whether to proceed, recover or accept the result.
- Onsite technician: carry out the agreed physical work, relay observations and perform the approved checks with the technical owner.
- Site contact: arrange access to the required rooms and make the agreed staff or devices available for checks.
Name an alternate contact for each dependency that could stop the visit. If support must be available live, confirm that appointment before the technician travels.
What should an ISP cutover checklist include?
Reconfirm the current state shortly before the appointment. An incident may already be resolved or the carrier’s plan may have changed since the original dispatch request.
- Match the current carrier order and instructions to the intended site and circuit.
- Confirm where the service terminates and whether the agreed connection path reaches the equipment location.
- Check that the correct equipment, permitted access, materials and instructions are available.
- Agree the service window, affected systems and communications to the site.
- Confirm who can authorize the start, a change to scope, a pause or recovery.
- Identify the approved recovery plan and the point at which the decision must be made.
Use the site readiness checklist to assign unresolved dependencies. A proposed connection path should remain unconfirmed until the agreed tracing or site check has established it.
What should be tested after an ISP change?
Prepare a validation list based on the actual systems at the location. Include only checks that are applicable, authorized and safe for the assigned personnel. The system owner should arrange any specialist checks for emergency calling, security or other controlled systems.
| Layer | Result to agree and record | Reviewer |
|---|---|---|
| Carrier handoff | Carrier confirms the agreed service state and any open carrier issue. | Carrier and technical owner |
| Physical connections | The assigned equipment and connections match the approved work, with exceptions recorded. | Onsite technician and remote engineer |
| Network and application checks | The technical owner records the selected checks and results against the site requirements. | Customer or MSP engineer |
| Business devices | Authorized users or system owners check the relevant computers, printers, phones, cameras or access systems. | Named system or site representative |
A successful connection on one computer does not establish that every dependent system works. Mark a check as not performed when its reviewer or required access is unavailable, then assign the next action.
What if support is unavailable or recovery is needed?
If the intended support contact cannot be reached, use the agreed escalation route and record the dependency. Do not improvise a configuration or recovery sequence outside the authorized work.
If the technical owner decides to recover the prior arrangement, record the decision, what was restored and what was actually checked afterward. If the original problem was already resolved before arrival, record that finding and the release instruction rather than reporting a cutover or rollback that did not occur.
Hand over the final state
The onsite completion record should identify the work performed, carrier status, observed checks, items not tested and the person responsible for each open action. Keep the service’s observed state separate from customer acceptance.
For a wider equipment deployment, read the network installation planning guide. ALL I.T. coordinates and carries out agreed onsite network work alongside your technical team and carrier, with the assignment defined around the site.
If the connection change affects meeting rooms, include the agreed meeting workflow in validation. The conference-room acceptance checklist helps define those checks.
About this guide
Published by ALL I.T. and updated November 15, 2026. This guide draws on a targeted review of onsite ticket notes and project correspondence to identify practical planning and handoff questions. Examples are illustrative; they are not a performance benchmark or a universal technical procedure. The system owner sets the checks and acceptance criteria for each assignment.
Learn about Ilya Elbert, ALL I.T.’s CEO, or contact ALL I.T. about the work described.
