Skip to main content

Proof Iterations

The Proof Iterations card on the VR Dashboard tracks how many revision rounds a proof typically goes through before approval. This article covers how to read the card and what it means for your team.

This is a read-only metric tile that updates automatically as asset versions are uploaded.

What it measures​

Proof Iterations is the average number of versions created per asset group (i.e. per distinct asset, counting every re-upload as a new version) across your workspace.

How to read it​

  • The headline number is the average version count.
  • A warn marker appears once the average passes 3 versions, and critical past 5.
  • Below the number, a small bar chart breaks assets down by how many versions they needed — 1, 2, 3, 4, or 5+ — so you can see whether high iteration counts are widespread or driven by a few outliers.
  • The card needs at least 5 asset groups before it shows a value.

Why it matters​

A high average signals unclear briefs, misaligned expectations, or recurring feedback loops — all of which drive rework cost. It pairs naturally with First-Pass Approval Rate, which measures the flip side: how often a proof gets approved without any revisions at all.