On this page5
A manager reviewing finished work with a team member
Client review ai work counts when the client can inspect the deliverable and their approval enters the verification process. Give clients a reviewable diff, define what they are approving, and route their response into Verify.
What you’ll learn
- What clients need to inspect before approval
- How client approval enters Verify
- How to handle changes after a review
- What to keep in the review record
What does client review AI work include?
A client cannot make a useful approval from a finished-looking result alone. They need to see what changed, what the work is meant to satisfy, and where any concern applies. That context makes client review ai work part of delivery rather than a request for a general thumbs-up.
Present the deliverable as a reviewable diff, with old versus new. Brainis shows each deliverable as a reviewable diff, with inline threads and Verify findings on exact lines, before it counts as done. See how Verify supports review.
Give the client the acceptance criteria that apply to this piece of work. Keep them concrete enough to assess: what must be present, what must be correct, and what would mean the work needs revision. Brainis can turn your acceptance criteria into Verify checks. A guide to defining done for AI work can help you write those criteria.
Keep review of the deliverable separate from approval to proceed. A client may confirm that a change meets the brief without authorizing the next step, or approve moving forward while raising a concern about one part. State which decision you need from them, so their response has a clear meaning.
How does client approval enter Verify?
Client approval works best when it enters the same verification flow as the work, rather than sitting in a separate email or message thread. In Brainis, external client review uses the same PR-review component in the client portal, and client approval becomes a Verify input.
Before review starts, tell the client what they are approving and how that response will be used. Approval can be an input to verification, but it is not the same thing as the verification decision. Keep the two outcomes distinct: the client gives their response, and Verify evaluates the work against the agreed criteria.
Important: State what the client is approving, and make clear how that approval will be used in Verify.
Your acceptance criteria should describe the conditions the work must meet. Brainis turns your criteria into Verify checks; you can author them once, compose them into libraries, and enforce them by domain. That gives the review a defined basis, rather than leaving the client and delivery team to judge against different expectations.
For each criterion, make it clear what evidence would satisfy it and where the client can inspect that evidence. If the client raises a concern, keep it connected to the relevant part of the diff. The Verify page describes how client review fits into that process.
What happens when the client requests a change?
Treat a requested change as work to assess, not as a vague note to remember. Attach it to the relevant part of the diff, and clarify whether it changes an acceptance criterion or asks for something beyond the agreed scope. That distinction helps the team respond without quietly changing what approval means.
If the team accepts the request, assign an owner to make the revision. Keep the request and its status connected to the work, so the client and team can see what changed in response. Then present the revised work against the same criteria, unless both sides have agreed to change them.
Tip: When work changes after review, ask the client to review the changed version rather than relying on the earlier approval.
Example: A small fictional design studio sends a revised booking page to a client. The client asks for clearer cancellation terms on the payment screen. The studio assigns the change to its page owner, updates the diff, and returns that revision for review against the existing clarity and accuracy criteria. The earlier response remains part of the record, but it does not stand in for approval of the changed page.
A review of one revision does not settle whether a later revision meets the same conditions. Brainis shows the verified seal only on the exact revision Verify checked. If work changes, it shows “verified at rev N, changed since” rather than a stale seal. For a broader view of separating creation from checking, read why the agent should not grade its own work.
A quality review meeting around a table of printed pages
What should the review record preserve?
The record needs to show which revision went to the client, what response they gave, and what Verify checked. Without that, a team may remember that approval happened but lose the context needed to know what the approval covered.
Keep the client’s comments and requested changes attached to the relevant work. Record whether a request was accepted, deferred, or declined, and identify who owns any accepted revision. This gives the team a path from review feedback to the resulting change without treating every comment as an agreed requirement.
Also preserve Verify’s findings against the acceptance criteria. Brainis presents reviewable diffs with Verify findings on exact lines, so the team can inspect what each finding concerns. Keep the client’s approval visible as a separate input, rather than presenting it as proof that every criterion passed.
The revision matters. Brainis’s verified seal applies only to the exact revision Verify checked; when the work changes, the display says “verified at rev N, changed since.” That distinction helps the record show which work was checked and prevents a previous review from appearing to cover later edits. Review the Verify product page for this workflow.
How do you add client review to your next delivery?
Start with one deliverable that already goes to a client. Write down its acceptance criteria before asking for approval. Make the criteria specific to the work, so both the client and the team can tell what a pass or a requested change means.
Prepare a reviewable diff and show the client where to comment. Set the route for their response, and name the owner who will assess and carry out any accepted changes. Decide how the revised work will return to the client and what must be checked again.
Then confirm that Verify evaluates the agreed criteria before anyone calls the work done. In Brainis, client approval can enter Verify as an input, while acceptance criteria become checks for the work. Keep the approval and the verification result distinct in your delivery process.
After that delivery, look at the record. Can you identify the revision the client reviewed, the response they gave, the requested changes, and the findings against the criteria? If not, tighten the handoff before applying it to more work. The guide to defining done for AI work offers a starting point for setting those criteria.
The aim is not to add a sign-off step for its own sake. It is to make clear what the client saw, what they approved, and what the team checked. That is the point where client review ai work becomes a usable part of delivery.
Brainis Team
Notes on running a company with Brainis, from the people building it and running on it.