Agree who is responsible for your website launch

What this means for your practice

Use one launch checklist showing who decides the site is ready, which checks are complete and who can restore the previous arrangement if needed. Agree who can pause the launch when an important task fails.

A practical example

For example, if online bookings do not open correctly just before launch, everyone should know who makes the decision to pause. Ask the suppliers to rehearse that discussion against the test site. Also agree who checks the public website immediately after the change. A good launch feels coordinated because responsibilities are clear, rather than depending on whoever happens to see an urgent message first.

Keep supplier contact details available outside the website itself. If something important fails during the switch, the team should not have to search the affected site to find help. Agree the immediate checks and named contacts before launch so the response can be calm and specific.

Make this improvement work

Name the person who decides the launch can proceed and the people who verify its important dependencies. The checklist should distinguish completed evidence from somebody's intention to check later. Agree who can pause the release if a booking or enquiry route fails and who handles communication to the team. Ask the supplier to rehearse a failed handover on the private test site, including the route back to the previous arrangement where appropriate. Keep any work created during testing identifiable and controlled. This gives the practice a clear decision process when a problem occurs instead of a last-minute debate about whether somebody else has already approved launch.

How to check the result

Review outstanding work that could prevent a safe, useful launch.