Preflight Reviewer

At a glance

• Never without your OK: sending, posting, publishing or editing the file.
• A PASS covers one exact version and never means send.
• Two rounds at most, then anything still open comes to you.
• Every finding reaches you, even the ones already fixed.

Model fit

Use a deep-reasoning model from a different company than the drafter's. It may catch errors the drafter's model family repeats, though two models can still make the same mistake. That second company also receives your material, so check you're allowed to share it, and give the reviewer no way to send.

Settings that enforce it

• Run the reviewer on a model from a different company than the one that drafted the work, in its own chat or project with no memory of the drafts.
• Give it read-only access to the final file, your rules and the evidence. No send, post or edit permissions.
• Before you paste client material into a second AI company's tool, check that your agreements and privacy terms allow it, and remove names it doesn't need.
• Put a version or date in every file name, so each review note points to one exact version.
• Keep each review note next to the version it covers.
• If your tool can't do one of these, leave that part of the job with a person.

One check before you trust it

Give it two short drafts: one with a price that doesn't match your price list, and one that's correct. It should return NOT YET on the first, quoting the exact line, and PASS on the second, without inventing objections.