Model Performance looks at the Revit model itself — not the drawings that come out of it.
If Project Review is for the team producing the set, Model Performance is for whoever is responsible for the model staying healthy.
How this differs from Project Review
Project Review reviews your drawing set and consults the model to resolve anything unclear. It will not tell you your model is messy.
Model Performance is where model quality lives — warnings, counts, and the elements causing them.
Two different questions, two different surfaces, usually two different people.
What you see
Warnings grouped by type, with counts. Rather than a flat list of hundreds of warnings, you see which kinds of problem your model has and how much of each.
The Revit element ID behind each one. Copy it, paste it into Revit, and go straight to the element. This is the part that turns a report into something you can act on.
Trends over time, so you can see whether things are getting better or worse as the project runs.
Not every warning resolves to an element you can jump to. Some are conditions rather than objects.
Who this is for
BIM managers, mostly, and whoever at your firm owns model standards.
The work of finding this by hand — opening the warnings dialog, working out which warnings matter, tracking down the elements — is real and repetitive. This is that work, done for you, kept current.
Related
Live model health vs. a point-in-time snapshot — why linked models update and uploaded ones do not
How a review actually runs: the drawing set first, the model second — why Project Review does not audit the model
Frequently Asked Questions
Q: How is this different from Project Review?
A: Project Review checks your drawing set — the deliverable — and consults the model only to resolve what the drawings leave unclear. Model Performance checks the model itself. Different questions, and usually different people.
Q: Can I get from a warning to the element causing it?
A: Usually. Each warning carries the Revit element ID — copy it, paste it into Revit, and go straight there. Not every warning resolves to an element; some are conditions rather than objects.
Q: Do the numbers update as we work?
A: For a linked model, yes — someone syncs to central, you refresh, the numbers move. For an uploaded model it is a snapshot from the moment of upload. See Live model health vs. a point-in-time snapshot.
Q: Why not just use Revit's own warnings dialog?
A: You can, and BIM managers do. What this adds is grouping by type with counts, the element IDs alongside them, and a trend over time rather than a snapshot you have to interpret each time you open it.
Q: Does this need a Forma-linked model?
A: No, but it is much more useful with one. An uploaded model gives you accurate numbers for that file at that moment; a linked model gives you numbers that keep up with the work.