A single audit tells you how things are; the history tells you where you're heading. The project's History view gathers all audits and draws a trend from them - the shortest path to answering "is the analytics work paying off".
What you'll find in the History view
How to interpret the trend shapes
Steady growth - the fix cycle is working. Note which implementation batches produced the biggest jumps: that's knowledge about what weighs most in your case.
A sudden drop - almost always a regression after a site or configuration change. Open the report with the drop and compare it with the previous one: the new errors point to the culprit. The date of the drop is your best clue ("what did we deploy that week?").
A flat chart at a high level - the desired state; rescans act as monitoring.
A sawtooth (up-down-up) - a signal that fixes aren't durable: they vanish with subsequent deployments. Time to move the findings into the development team's documentation (e.g. a release checklist) instead of fixing the same thing a third time.
Practical uses of the history
Related articles: