Every tile on the Policy Checks dashboard carries the current window plus up to three earlier windows of the same length. Read Pass Rate and Critical & Blocker across those windows first. A pass rate that is falling while violation counts climb is a different problem from one that is falling because coverage just widened onto databases nobody had checked before.

So check the two coverage figures in the same pass. See Measure governance effectiveness.

The Policy Checks dashboard filters by Check and by Severity, so you can isolate a single rule and see every operation it flagged in the window.

Note: Check and Severity filter the operations list only. The tiles above the list keep describing the set without them, so they will not move as you narrow. The tiles also do not rank checks by how often they fail, which is why isolating a rule and reading its operations is the way to find the one generating the most work.

The Check picker is built from the checks that have actually recorded a violation in your workspace, so it is empty until a policy check reports one. It does not require the governance capability to be set up.

Each operation in the list carries a Severity column of five pills, in a fixed order of Info, Minor, Major, Critical, and Blocker, each with the count of violations at that severity. Scanning the column down a filtered list is the fastest way to see whether one rule is producing a steady trickle of low-severity findings or occasional blockers.

Note: The pills are counts rather than an outcome. A row of zeros shown as muted outlines means the operation ran checks and found nothing, while a dash means the operation carries no policy check report at all. Those are different states and only the second one is a gap.

Open any operation from the filtered list to reach its details page. Findings groups the same results two ways, and which one you want depends on the question.

A rule that fires constantly at low severity across every team is usually miscalibrated rather than widely violated. A rule that fires rarely but at blocker severity is doing its job. Recalibrating is a governance change, so make it in Browse the policy catalog, and record what you expect to happen so the next window tells you whether it worked.