Guide · website handoff
Website handoff approval checklist
A short process for agencies and freelancers who need a client to approve the deployed website version and understand what changed later.
Before sending the review link
- Confirm the pages are deployed at their final public URLs.
- Check desktop and mobile layouts at the same capture time.
- Record the URL, capture time, HTTP status and content hash.
- Remove private or logged-in pages from the review scope.
During client approval
- Send one review link tied to the captured version.
- Ask the client to approve each page or request a specific change.
- Keep the decision attached to the evidence version, not just an email thread.
After a later change
Run a new capture after the website changes. Carry approvals forward for pages whose evidence is unchanged. Ask for a new decision only on pages whose screenshots or content hash changed.
Useful rule: a changed Pricing page should not force a client to review an unchanged About page again.
What a good handoff record contains
- Named public URLs
- Desktop and mobile screenshots
- Capture timestamp and content hash
- Page-level approval status
- A clear note that the record is evidence of what was observed, not legal certification