Working with a web designer: feedback, scope and handover

Updated: Oct 21
Keep a website project moving with clear decisions, useful feedback, agreed revisions and a documented handover.

Agree who decides
Choose one person to collect feedback and approve the work. If several people need input, gather it before the agreed review. Contradictory instructions from different stakeholders can delay decisions and make it difficult to establish what has been approved.
Give feedback about the customer journey
Explain the problem behind a requested change. “Our main service is difficult to find” is more useful than “make this bigger”. Refer to the agreed goals, content and audience. Give the designer room to propose a solution, then check whether it addresses the issue.
Keep revisions and new scope separate
A refinement to an agreed design is different from adding an online store or rewriting every page. Use the proposal to establish included review rounds and how extra work is quoted. Record decisions so everyone knows which version is approved.
Prepare content and access safely
Provide approved copy and images by the agreed milestones. Confirm ownership and usage permissions. Give access through suitable collaborator roles where possible; do not put passwords in a public document or initial contact form. Identify the person responsible for domain, email and platform administration.
Finish with a usable handover
Ask how to edit routine content, which accounts you control and what support follows launch. Confirm renewal responsibilities and how future work is requested. TW Web Design agrees these points with clients from the brief onwards, with consultations and business visits by appointment.
Reviewed and updated 21 October 2026. The original publication date is retained.




While looking for additional information, I recently came across https://proshtuchnyiintelekt.com/ and found several useful examples there