The dashboard answers one question: where is my organisation out of compliance right now?
The PolicyCodex dashboard with stat tiles, violations by domain, and the violations table

​
The tiles

Open blocking

Unresolved violations of enforced MUST statements. Each of these is failing a check somewhere. This is the number to drive to zero.

Open warnings

Unresolved SHOULD-level findings. Advisory — nothing is blocked, but a rising number means a standard is being routinely ignored.

Enforced statements

How many requirements are currently blocking. The size of your active rulebook.

Architecture domains governed

How many domains have standards in force — your coverage across subject areas.

​
Open violations by domain

Blocking and warning counts per domain, on a shared scale. Read it for shape, not totals. One domain carrying every blocking violation usually means one of two things: a standard was promoted to enforced before the codebase was ready, or a single statement is over-broad and firing on everything. Both are fixable at the RFC, and both are cheaper to fix there than to grind out across every team.

​
The violations table

Every recorded violation, newest first: Because slugs are stable, this history stays coherent across RFC rewrites — a violation from six months ago still resolves to the statement it cited.

​
Recent activity

Below the table is a feed of recent governance activity — approvals, promotions, extractions.
The recent activity feed at the bottom of the dashboard
This is a readable view of the same events the audit trail records formally. Use the dashboard feed to keep half an eye on what’s changing; use Settings → Audit when you need the verifiable record.

​
Working the numbers

1

Blocking first

Open blocking violations are actively costing engineering time. Either fix the code or — if the standard is wrong — revise the RFC.
2

Look for concentration

A single statement producing most findings is a signal about the statement, not the teams.
3

Check coverage

A low violation count with only one repository reporting is not compliance. See Coverage.
4

Then promote

Once a domain’s warnings are manageable, that domain’s approved RFCs are ready for enforced.