Preflight Reviewer
Checks the final version against your rules before anything leaves. A PASS is never permission to send.
Two-reader release
A second AI reads the exact final version, you approve that version, and only then does it go out.
The ECHO line
An edit after review means another review, so the version you approve is the version that goes out.
The release path for anything an AI helped write. The drafter drafts, a reviewer on a different company's model checks the exact final version, the fixes go back to the drafter, and you approve that exact version before it's sent or published. A review PASS gets it ready for you and authorizes nothing.
TO BE TESTED — RESULTS WILL BE SHAREDFrom how we run our own AI agent teamSetup: about 30 minStandard5 of 5 free opens left
At a glance
- A PASS gets it ready for you; it never sends or publishes.
- Any edit after review means another review.
- Only the exact version you approved goes out.
Where the lines fall
AI may prepare
- The draft, the reviewer's findings with the exact line and a suggested fix, and the corrected version.
Only after a person says yes
- Sending or publishing the exact version that passed review.
- Releasing it with a must-fix still open.
Human reserved
- Resolving anything still open after two review rounds.
Stops when
A must-fix is still open after round two, the version changes after review, or the reviewer can't check a claim.
Takes over
The owner
Steps
Drafts the piece and puts a version or date in its name. Any drafting role can fill this step.
AIReviews the exact final version on a different company's model: must-fixes, suggestions, what it couldn't check.
AIMakes the fixes and saves a new version; the reviewer checks them in round two.
AIYou
Decide anything still open after round two.
YouYou
Approve the exact version: the text, where it's going and the date.
Your OKYou
Send or publish it, or let your tool release that approved version.
Your OK
Model fit
Best fit
- Everyday assistant
- Deep reasoning
Also fits
- Built into your business tools
Avoid
- Personal agent (acts for you)
Draft on your everyday assistant. Review on a deep-reasoning model from a different company than the drafter's; it may catch errors the drafter's model repeats, though two models can still share a mistake. That company also receives the material, so check you may share it. Sending and publishing stay with you.
Where it runs
- Social media and reviews
- Documents and files
- Quote or invoice tool
Risk
- Relationship
- Rights
Two-reader release · RL-WF-08
5 of 5 free opens left- ① Orientation
- ② Permission
- ③ Constraint ★
- ④ Invitation
The paste didn't load. Check your connection and try again.
These are samples. Fill in the [INSERT] blanks and adapt each one to your business.
A pasted role guides the agent. Your tool's settings are what stop an action.
Sample handoff note (fictional business)
Settings that enforce it
- Run the reviewer on a different company's model, in its own project with no access to the drafts or the chat history.
- Give the reviewer read-only access; it needs no send, post or edit rights.
- Turn on approval before anything sends or posts (often called "Review before sending", "Needs approval" or "Always ask").
- Put a version or date in every file name, and keep the review note with that version.
- If your tool can't do one of these, leave that part of the job with a person.
One check before you trust it
Get a PASS on a short post, then change one word and ask the run to publish it. It should stop, send the new version back for review, and publish nothing.
Want it set up in your own tools? Book a Working Session · $450Working Sessions run in English or Spanish.