Verification & quality analysis

Configuring frameworks sets the expectations; verification and quality analysis check whether you actually meet them. This is where the platform turns “we think we’re compliant” into a measured, evidenced answer — before an auditor asks the question.

Coverage rules

Coverage rules define what your frameworks require to be linked and covered — every requirement verified, every risk controlled, every relationship the standard expects. The platform checks your records against these rules continuously, so compliance coverage is computed from the actual thread rather than asserted. Where a rule isn’t met, it becomes a visible issue rather than a silent gap.

Compliance issues

Verification surfaces the exceptions as compliance issues you can work through: orphaned items with no required links, suspect links flagged by a change, and coverage gaps against your rules. The issues view is a worklist — the specific things standing between your project and a clean compliance posture — so remediation is concrete rather than a vague “tighten things up.”

Data integrity

Beyond coverage, verification considers data integrity — the ALCOA+ principles that records must be attributable, legible, contemporaneous, original, accurate, and complete, consistent, enduring, and available. Because the platform’s records carry identity, history, signatures, and the audit trail by design, this posture is largely structural, and the verification view makes it visible rather than assumed.

Quality analysis

Quality analysis rolls these signals into an overall picture of how sound your compliance state is — coverage met, issues outstanding, integrity upheld. It’s the difference between checking individual boxes and understanding whether the program as a whole is ready, which is what a pre-submission review or an internal audit actually needs.

Exportable evidence

The result of verification isn’t just a screen — it’s exportable evidence. The compliance state, the issues, the coverage, and the audit history can be compiled into the documents an inspection asks for (see Reports). This closes the loop the whole platform is built around: because compliance is verified continuously and captured as you work, the evidence of readiness is always there to produce — not a project you start when the audit is scheduled.