Test whether the incoming supplier can run the service

What this means for your practice

Accept the handover through ordinary operating tasks, with the outgoing supplier available for agreed questions. Record work still dependent on that supplier before closing the transition.

How to review the arrangement

Ask the incoming team to complete a safe test change using the handover materials and approved access. Include a support or recovery scenario. Where do they need undocumented assistance? Record those dependencies before closing the handover so the first real incident does not become the first practical test.

Accept the handover through a safe demonstration

Agree a few tasks that represent what the incoming supplier will need to do. A routine content change, a support investigation and a recovery exercise can expose different gaps. Use an appropriate test setup and approved access so the demonstration does not put the live service at risk.

Ask the incoming team to work from the handover materials while the outgoing supplier remains available for agreed clarification. Note where instructions are missing, an account cannot be reached or a step depends on private knowledge. Turn those findings into specific handover items with responsible people. Check the relevant task again after the gap is addressed. The practice should receive a clear explanation of what has been demonstrated and what remains unresolved before closing the transition. This gives a stronger basis for acceptance than a presentation in which everyone recognises the system but nobody has yet operated it independently.

How to check the result

Count the agreed operating tasks the incoming team can complete without undocumented help from the previous supplier.