What blocks approval
Read the "Approved when" list to see exactly which people and requirements still stand between a version and Approved.
An asset is never marked Approved by hand. Brightproof keeps a list of every requirement for the current version and derives the status from that list. The same list is shown wherever the status appears, so nobody has to reconstruct "what is left" from separate tabs. For the model as a whole, start with How approval works.
The "Approved when" list
Open the asset and select the Decisions tab. The top of the tab shows Approved when, followed by every requirement and its state:
- Approvers — one row per required approver on the current version, under a heading that states the approval policy. A named final approver's row reads Waits for others until it is their turn. A reviewer inherited from the project is marked via project. Each row is Awaiting, Approved, Not applicable, or Changes requested. Not applicable satisfies the slot without counting as an approval; at least one approver must still approve. A withdrawn decision shows as Awaiting again.
- Guest sign-off — one row per required guest link. It is satisfied when at least one person on that link approves and nobody's latest decision requests changes. Only the creative team sees the link's label and who decided; reviewers see the gate as Guest sign-off.
- Required checks — one row per required checklist item on this version. Optional items are not listed here; they never affect the status.
Below those, Also reviewing, for feedback only lists reviewers with the feedback-only role. They show Reviewing or Review complete and never count toward the status.
The summary beside the heading counts what remains. When it reads Every requirement is met, the asset is Approved.
Reading the status badge
Hover or focus the status badge in the asset header to see only the requirements that still block approval; select it to open the full list without leaving the viewer. The review queue and asset list show the same information as a short Waiting on … line beneath each status, naming outstanding approvers and counting guest sign-offs and checks.
How the status is decided
- If any required approver or any required guest link has requested changes, the asset is Changes requested. No approval elsewhere overrides that; the round reopens only with a new version or when that request is withdrawn.
- Otherwise, if at least one approver is assigned, the approval policy is met, and no other requirement is outstanding, the asset is Approved.
- Otherwise it stays In review.
A required checklist item that is Not started or Failed holds the asset at In review even after every approver has approved. It does not move the asset to Changes requested, because a check is the creative team's work, not a reviewer's verdict.
Your own slot
If you are an assigned reviewer, your row in the list is your slot for this version. It appears in Awaiting you until it is answered — by your own decision, by Mark review complete if you review for feedback only, or by an owner recording an override on your behalf. Reminders go only to required approvers whose slot is still awaiting.