What to accept at website design handover

Agree on the delivery checklist at the start. Approving a design, completing development and launching the site are separate milestones with different owners and evidence.

Review the system

• Check all agreed templates and reading order.
• Review reusable components and mobile behaviour.
• Include focus, loading, disabled, empty and error states.
• Document asset formats and usage conditions.

Test long titles, missing images, multiple downloads and translated content. Ideal homepage layouts alone cannot establish whether the system supports the business.

Explain behaviour at handover

Provide editable files and the agreed component, prototype, asset and documentation package. Explain navigation, language switching, validation, overflow and reduced-motion behaviour. Confirm ownership and licences rather than assuming the commission includes source code or transferable third-party rights.

Verify the implemented tasks

Download a real document, follow an article to a service, and submit a clearly marked test inquiry on mobile. Check that notifications reach their owner. Review metadata, canonical URLs, sitemaps and migration alongside visual implementation.

Track closure

For each issue, record the URL, device, reproduction steps, expected result, owner and status. Prioritize blocked tasks and inaccurate facts. Have a named reviewer confirm fixes and retain the final asset inventory.