Every practice that uses AI on client work already reviews it. The forums agree on that: "I don't trust a single AI tool we use... without a human in the loop" (a personal injury lawyer on r/LawFirm), and a fractional CMO is told to "keep yourself on the review" (r/marketing, July 2026). What differs is whether the review is a habit or a step the work cannot skip.
What a review step needs
- One reviewer, named before the work starts. If nobody owns the approval, it happens when someone remembers.
- The whole deliverable, not message by message. Approving each sentence as it streams past is not review; reading the finished document, deck or page is.
- A handoff, not just an output. What was done, the decisions made, the concerns and what it cost. The concerns are where review time pays off.
- A way to send it back with context. "Request changes" should carry your note and the thread, so the next draft fixes the problem instead of starting over.
- Nothing leaves without it. Sending, posting and publishing should be things a person does after approving, not things an agent does on its own.
How to run it by hand
A shared folder with "draft" and "approved" subfolders, a checklist in the doc header, and a rule that only one person moves files into "approved". It works until volume grows, then drafts skip the folder.
How Afarin builds it in
In Afarin each card has a person as its approver. An agent hands the work back to the card's review column with a handoff, and the card reaches Done only when that person approves it. Request changes and the agent reruns with the whole thread. In each connected app an agent acts only with the access you give it: leave your email at read, and sending stays yours. When you approve shipped work, the card moves to Done and the Wiki updates.
Make the concerns easy to find
Ask for concerns first in every handoff. A draft that says the Wiki has no wait-time figure, so the page does not promise one saves you the one check that matters.