Compliance linter (Improve)
Automatically detect inconsistencies and gaps in your compliance file — like a grammar checker, but for Law 25.
What is the compliance linter?
The linter (Improve > Compliance linter) is a rules engine that continuously analyzes your compliance file and flags inconsistencies, missing fields, and risky configurations. It works like a grammar checker: it never forces you to do anything, but it draws your attention to what should probably be fixed. Example rules: a processing activity without a documented legal basis, a sub-processor without an attached DPA, a missing retention period, a cross-border transfer without a framing clause, a PIA that should have been triggered but was not.
Reading the results table
The linter table groups triggered rules by severity: "Blocking" (prevents approval), "Recommended" (to fix for full coverage), and "Informational" (best practice). Each row shows the triggered rule, the affected element (processing activity, actor, asset), the underlying risk, and a direct link to the screen to make the fix. You can filter by module, severity, or owner to distribute the work across the team.
Reading the results table
Fix or justify
For each alert, two actions are available. "Fix" opens the relevant record directly with the field to fill highlighted — one click, you enter the missing information, you save, and the alert disappears. "Justify" lets you declare that a rule does not apply to your context (for example: no DPA needed because the sub-processor is internal to the group). The justification is recorded in the audit trail and re-appears if the situation changes.
Automatic execution and quality score
The linter runs automatically on every change to a registry element (creation of a processing activity, addition of a sub-processor, modification of a measure). A global quality score, visible on the Compliance Health dashboard, aggregates the number of open alerts weighted by their severity. This score evolves in real time and is an excellent progress indicator for management.
Typical use cases
The linter is particularly useful (1) before an annual registry review — it identifies in seconds the gaps to fill; (2) after a bulk import of activities — it flags fields left empty by the import; (3) after a regulatory update — Conformaze adds new rules that may trigger alerts on already-approved activities. Make a habit of consulting the linter at least once a month.
Tip
Aim for "zero blocking alerts" and "fewer than 10 recommended alerts" to consider your file audit-ready. The linter replaces a manual review that would take several days.