Fine Print

Updated November 16, 2026

Advisory, blocking, and auto-approving checks

An advisory check tells a person what it found, and the person decides. A blocking check stops the work until someone fixes it or approves it. An auto-approving check approves the work by itself when the result is clear. Most products in the directory advise.

What is an advisory check?

An advisory check reports issues and changes nothing. Markup AI shows each issue to the writer, who applies the fix or dismisses it. IntelligenceBank sends each flag to a human reviewer. Rainbrand returns findings, and a Review does not edit the asset or approve it.

What is a blocking check?

A block stops the work at one step. The directory has three kinds:

  • A lock in a template. In Marq, users can change only the unlocked parts of a template.
  • A required approval. In Frontify, an admin can require approval before a user exports a publication from a template.
  • A gate in a pipeline. The GitHub Action of Markup AI can stop a merge, and a guardrail in Writer can block agent output.

What is an auto-approving check?

An auto-approving check decides with no person when the result is clear. Three products document this:

  • In Cloudinary, each rule can approve or reject an asset when the score is clear. An asset between the two thresholds goes to a person.
  • In Marq, admins can set a score threshold. Brand Guardian then approves content that meets the threshold.
  • In Bynder, an admin can turn on Auto-apply. The agent then writes its result to the asset without manual approval.

What do vendors say about automatic decisions?

The vendors that offer automatic decisions also warn about them. Bynder states that AI can make mistakes, and it tells customers to apply automated results only after careful consideration. Cloudinary tells customers to plan for human review where the stakes are high. Adobe tells users to double-check the suggested fixes of its Governance Agent.

How do you choose?

  • Use a lock when the layout repeats and the people who fill it in are not designers.
  • Use an advisory check when the work is new each time, and a person or an agent can fix it.
  • Use a required approval when a law, a client, or a contract needs a named person to sign.
  • Use automatic approval only for low-risk work. First compare its decisions with the decisions of your reviewers.

Who decides in each product?

Product Who decides
Adobe Suggests, then a person checks
Artwork Flow Marks errors for reviewers
Bynder Proposes, a person approves
Cloudinary People make the final call
Frontify Advises in chat
IntelligenceBank Advises, a person decides
Lytho Advises people
Markup AI Advises
Rainbrand Your team. A Review returns findings, not an approval.
Writer Advises
Filestage People decide
PageProof People decide
Ziflow People decide
Marq Brand Guardian advises. Users choose whether to make the changes that it suggests.
Templafy Templafy says that it prevents brand issues when a document is created. It says that most other tools flag issues afterward.
PerformLine The Pre-Publication Scanner gives a verdict, and human reviewers make the final decision.
Siteimprove Brand Consistency reports issues, and people decide. A user marks each issue occurrence as Open, Acknowledged, or Dismissed.