Brand compliance & template regression
Catch off-brand color, swapped logos, and missing disclosures by diffing a document against an approved baseline — so unintended changes are caught before a run, not after.
Runs on PDF · compares against an approved baseline you set in the workspace.
Every finding maps to a named rule and a baseline reference, so a result is reproducible and defensible. The compliance modules run in a workspace — the free analyzer parses structure only.
Frequently asked questions
What is brand / template regression?
It compares a new version of a document against an approved baseline and reports what changed — a moved or swapped logo, an off-brand color, a missing disclosure, an added or dropped page — so unintended changes are caught before a run, not after.
How is color conformance measured?
With ΔE2000, the perceptual color-distance metric, against your approved brand palette — so “close enough” versus “off-brand” is objective and reproducible rather than eyeballed. The check covers vector colors by default; image-derived colors are an opt-in, advisory add-on, and a placed raster left outside the active scope is reported as not-evaluable rather than passed clean.
What about legal disclosures?
The module checks that required disclosure text is present, placed where the baseline expects it, and unmodified — and reports a disclosure it cannot evaluate rather than guessing.
Does it need a baseline?
Yes. Brand checks compare against an approved baseline you set in the workspace; an expired baseline is flagged so you are never comparing against a stale template.
Are brand findings blocking?
Several brand signals are advisory (≤ warn) by design, so a borderline match flags for human review rather than hard-failing a run.