Imagine a customer has chosen a service but leaves the enquiry form unfinished. Replacing the site could still leave that customer with the same problem. Before asking for a redesign estimate, take the journey yourself on a phone. Write down the first step where you cannot tell what to do, what information is needed, or whether the request went through.

Repair a task that already has a home

If the page is easy to find, the platform is supported, and the team can edit it, isolate the failure. On our own website, for example, a visitor coming from a service page should not have to select that service again. Passing the choice into the form is a small change with a clear acceptance check: open the service, follow the link, and read the selected topic.

Give a repair a boundary. In our in-house enquiry project, the test is whether a visitor can choose a service and keep that choice through the form. For the error and success states, the W3C guide to form notifications explains how to make the next step clear.

Migrate when the publishing system is the constraint

A useful page may be hard to maintain because its editor is unsupported or its workflow requires a developer for every change. A migration can keep the content and addresses that visitors know while replacing the tools behind them.

Inventory the URLs, downloads, and forms first. Identify who owns each one. Before switching, ask an editor to publish a change, check the redirects from old addresses, and send a test enquiry to a controlled inbox. An attractive new page does not tell you whether any of those things work.

Rebuild when the job itself has changed

A brochure page can explain a service. It cannot, by itself, manage approvals between customers and staff. If the work now involves different roles, permissions, or business records, sketch the smallest complete workflow. Name who starts it, who decides, and what each person needs to see when it ends. Compare a website, an existing booking service and a custom application before commissioning software.

What to put in the brief

Bring the current URL, one task that fails, a real constraint such as an existing booking system, and the name of the person who will maintain the result. Ask for the smallest change that solves the problem, the reason for choosing it, and a test you can repeat before accepting delivery.