Managing Client Revisions in Bricks: A Step-by-Step Workflow
The most reliable way to manage client revisions on a Bricks build is to run each round as a tight loop: collect all feedback in one place on the live page, action it inside the Bricks builder, then get an explicit “approved” before moving on. Revisions spiral when feedback is scattered, vague, or never formally closed — not because the work is hard. A repeatable loop fixes that.
Here’s the workflow.
Why revision rounds spiral out of control
On most Bricks projects, the build is the easy part. Revisions are where margin disappears:
- Feedback trickles in over days, in five different channels, so you never know if a round is “complete.”
- Comments are positional and vague (“make the hero bigger”), so you spend time interpreting instead of building.
- Nothing is formally signed off, so “round 2” quietly becomes round 5, and scope creep is invisible until you’ve eaten the hours.
The fix isn’t working faster — it’s running revisions as a defined, repeatable process.
A repeatable revision loop for Bricks
1. Set the rules before round one
Tell the client up front how feedback works: “You’ll get a link, leave all your comments directly on the page, and I’ll action them in one batch. We’ll do up to two rounds; extra rounds are billed.” Setting the number of included rounds is the single biggest defence against scope creep.
2. Collect all feedback in one place, on the live page
Send one review link and have the client leave every comment pinned to the actual element — not in email, not over a call. On-page, element-level feedback removes interpretation work and keeps a round contained. (Here’s how to collect client feedback in Bricks without email threads.)
3. Wait for the round to be “complete”
Don’t react comment-by-comment — that’s how one round becomes ten. Ask the client to add all their notes, then tell you it’s ready. Now you have a finite, reviewable list.
4. Action the batch inside the builder
Work through the feedback where you actually build. With Reviso, every pinned comment shows up inside the Bricks builder, so you resolve items without tab-switching, and mark each one done as you go. Threaded replies let you ask a quick clarifying question on a specific comment instead of restarting an email chain.
5. Close the round with an explicit sign-off
When you’ve actioned the batch, send it back for one look and ask the client to approve. An explicit approval (ideally timestamped) is what turns “is this done?” into a clear yes — and gives you a record if scope is ever disputed. Reviso generates a timestamped PDF approval certificate when the client signs off.
6. Repeat — but count the rounds
Each loop is the same: collect → complete → action → approve. Because every round is defined and signed off, you can see exactly when you’ve hit the included limit and have a clean, documented basis to bill for more.
How Reviso supports this loop
Reviso is built for exactly this cycle on Bricks sites: a no-login link for collecting pinned feedback, comments that surface inside the builder for actioning, threaded replies for clarification, a “reviewed” state per item, and a PDF sign-off to close each round. The core flow is free on WordPress.org — try the live demo to see a full round end-to-end.
FAQ
How many revision rounds should I include for a client website?
Most agencies include two rounds in the base scope and bill for additional rounds. The important part isn’t the exact number — it’s defining it up front and closing each round with an explicit sign-off so extra rounds are visible and billable.
How do I stop client revisions from creeping out of scope?
Define the number of included rounds before you start, collect each round’s feedback in one batch (not trickled over days), and require an explicit approval to close each round. A timestamped sign-off makes scope creep visible instead of silent.
What’s the best way to collect revision feedback on a Bricks site?
Use on-page, element-level comments via a no-login review link, so the client points at exactly what they mean and you action a single, finite list. Tools like Reviso surface that feedback inside the Bricks builder where you work.
Can I track which revisions are done?
Yes — give each comment a status. Reviso lets you mark comments resolved/reviewed and shows the round’s progress, so both you and the client can see what’s actioned and what’s outstanding.
See a full revision round in action — try the Reviso demo → or compare it to other feedback tools.