A Client Handoff Checklist for Bricks Builder Agencies
A clean client handoff comes down to three things: the client has reviewed and formally approved the work, you’ve documented that approval, and you’ve handed over access and next steps in writing. Projects that drag on after “launch” almost always skipped one of those. Use the checklist below to close Bricks projects properly.
Why handoff is where projects leak time
The build is done, the site looks great — and then weeks of “one more tweak” follow because nothing formally ended the project. A defined handoff turns a fuzzy finish into a clear line: approved, documented, delivered.
The handoff checklist
1. Final review on the live pages
Walk the client through the finished pages on their real URLs and collect any last feedback pinned to the actual elements, not over a call. (Here’s how to collect that feedback in Bricks.)
2. Explicit, documented approval
Get a clear “approved” per page and keep a timestamped record. This is the single most important step — it’s what ends the revision phase and protects your scope. (More on client sign-off.)
3. Access & ownership handover
Hand over (in writing) admin logins, the hosting/domain details, and who owns what. Confirm the client can log in.
4. Training & documentation
A short Loom or doc on how to edit their key content in Bricks, plus where to get support.
5. Post-launch terms
State what’s included after launch (e.g. a 2-week snag window) and what’s billable, so “quick changes” don’t become unpaid scope.
6. Invoicing & next steps
Final invoice tied to the documented approval, and a clear note on care plans / retainers if you offer them.
Make approval the anchor of your handoff
Every item above hangs off one thing: a clear, recorded approval. With a Bricks-native tool like Reviso, the client approves each page and you get a timestamped PDF sign-off — so your handoff has a documented foundation instead of a verbal “looks good.”
FAQ
What should a website handoff include?
A final client review, an explicit and documented approval, access/ownership handover, training or documentation, post-launch terms, and final invoicing. The documented approval is the part most agencies skip.
How do I stop “quick changes” after handoff?
Define post-launch terms up front (e.g. a short snag window, then billable), and anchor the handoff to a documented per-page approval so the end of scope is unambiguous.
How do I document client approval on a Bricks site?
Capture an explicit approval with a timestamp. Reviso records a timestamped PDF approval certificate per page, which gives your handoff a clear paper trail.
Close your next Bricks project cleanly — try the Reviso demo → or install the free plugin.