Skip to content
Overflow Sites Discuss a partnership

Agency website project discussion

Agency Website Handoff and One-Round Review

Prepare approved content, page lists, and decisions so the agency and production partner can complete one focused revision within agreed scope.

Start with a complete handoff

A useful handoff explains what the client expects and what the starter-site scope includes. List up to five standard pages, the purpose of each page, the approved text and images, business details, contact destination, and any required calls to action. Identify the current approved version of every asset so the production partner does not have to guess which file or comment takes precedence.

Name one agency contact who can answer questions and one client decision-maker who can approve content and changes. The agency owns the client relationship and should consolidate feedback before sending it onward. If access is needed for the project, arrange it through a secure method and grant only the minimum required permission. Keep passwords and private client data out of ordinary email briefs.

Review against the agreed scope

Before the project begins, confirm the page list and requirements against the standard offer: curated template customization, mobile-responsive build, contact form, basic SEO setup, SSL, backups, uptime monitoring, and one focused revision round. Record anything outside that scope, including e-commerce, memberships, custom applications, brand identity, copywriting, photography, complex booking systems, or premium software licenses. Those items are quoted separately rather than assumed to be included.

When the initial site is ready for review, compare it with the approved content, page list, and agreed project direction. Check that the pages are present, links and contact destination are correct, and the supplied information is represented accurately. Collect the client’s focused revision notes in a single list. Distinguish a correction within the agreed work from a new page or expanded feature that needs a separate discussion.

The user’s contract and the project agreement determine approval, client communication, and acceptance. Do not treat a handoff checklist as a substitute for those terms. For a more detailed example, see the agency handoff brief and project QA checklist.

For the review round, keep one dated list of requested corrections and the page or section each item refers to. Ask the client to prioritize when feedback conflicts, then have the agency confirm which notes are within the focused revision and which represent a new request. Record the response so the same item is not sent back as a new change later. The handoff should also identify any dependency the client must complete, such as approving a contact destination or providing missing text.

Close the loop

After the revision round, summarize what changed and flag any request that remains outside the confirmed scope. Confirm who owns client communication, who handles future content changes, and which hosting responsibilities were agreed. Keeping that record helps prevent a later request from being mistaken for an included revision.

If you have a prospective project, discuss its handoff and scope with Overflow Sites before making a delivery or timing promise to the client.

Discuss a project with us.

Share the scope and workflow you have in mind. We can discuss whether it is a fit before deciding next steps.

Discuss a Project Handoff