Compliance Alert Density(5.7.10)

Alert density normalizes compliance alerts by activity volume — it is the share of a project-week's active issues that raised at least one alert, so a busy project with 10 flagged issues is treated differently from a quiet project with the same 10. This metric makes it possible to compare compliance health fairly across projects of different sizes and to track whether alert rates are improving over time.

For stakeholder reporting, alert density is more meaningful than absolute alert counts — it measures compliance per unit of work rather than total failures.

What you can conclude

• A rising alert density (more flagged issues per 100 active issues) indicates that flagged issues are growing relative to team activity.
• A falling alert density indicates genuine compliance improvement — the team is completing more work cleanly.
• A stable but elevated alert density indicates a known, persistent share of flagged issues that has not yet been addressed.

How this chart works

Weekly table showing compliance alert density per project: the number of distinct issues that raised at least one alert that week — a status moved backward out of a done status, a skip from a not-started status straight to done, or personal data in the summary — per 100 issues active that week, with week-over-week delta and a status label: stable / watch / elevated / alert. An issue raising several alerts, or the same alert on several edits, counts once, so the density never exceeds 100 and reads as the share of the week's issues a reviewer would want to look at. Use the date and project filters to scope the reporting period.

The week in progress is shown at its value so far. Because the week is not yet complete, it is marked as still in progress and does not enter the trend comparison.