Plan domain-setting changes around all affected services

What this means for your practice

Record the settings to be changed, the intended result and the affected services. Agree checks and a route back to the previous arrangement, with an appropriately skilled owner reviewing the plan.

How to review the arrangement

Ask the supplier to explain the proposed change in business terms, identify affected services and record the relevant existing settings. Rehearse what happens if the move fails. Who can restore the prior arrangement, and how will the team check that the dependent services still work?

Agree the affected services before changing settings

Your supplier should identify the particular domain settings that need changing and explain which services depend on them. A website move may sit alongside email, booking addresses or verification arrangements managed by other providers. The practice's role is to confirm the services it relies on and the right contacts; a suitably skilled person should review and perform the technical work.

Ask for the relevant existing settings to be recorded, along with the intended changes and checks. Use a fictional failure to walk through the recovery decision: who can act, which prior arrangement is available and how the team knows it has been restored? Plan communication and timing around the effect on the practice. After the change, review all the affected services rather than only the homepage. Keep any inconsistent results visible while the supplier investigates, with a clear owner for confirming that the move has achieved the agreed outcome.

How to check the result

Track DNS changes completed with a reviewed record and successful post-change verification.