
Your website is finished: what to collect from the contractor before closing the project
Access, instructions and an update process help your team manage the site after launch.
Read storyCheck the whole journey from the form to an employee’s reply, not just the success message.

A visitor fills in a form and sees “Thank you.” The website’s flow is complete, but the business’s work has only begun. If the enquiry disappears into an inbox or has no owner, the quality of the page cannot rescue it.
Submit a message from a phone using a recognisable test name. Check where the data arrives, who receives a notification and whether the originating page is visible. Do not stop at a technical delivery status: open the record in the place where an employee will handle it.
Then test a failure scenario. What does the visitor see when the service is temporarily unavailable? Is the entered text preserved? Is there another way to contact you? Do not display success before the server has actually accepted the enquiry.
Give each enquiry type an owner: sales, support or the editorial team. Agree what happens during holidays and outside working hours. Publish a precise response-time promise only when the team can actually keep it.
Make notifications actionable: a link to the enquiry, its subject and the responsible team. Copying everyone may create a feeling of oversight, but it does not assign a person to respond.
Once a week, compare accepted forms with handled enquiries. Investigate specific gaps: incorrect routing, an unavailable employee or an unclear request. Improving the process sometimes requires one handover rule rather than rebuilding the entire website.