Analyze capabilities

The analyze family answers “where do we stand?” across a regulation you’ve adopted. Each capability reads your stored questionnaire, citations, and evidence and returns a structured card a reviewer can act on.

Gap Analysis Database-derived

Delivers — the requirements that are unanswered or lack documented coverage, so you know where the work is. How — questionnaire completion and stored obligation coverage. Read it as — workflow and documented-coverage gaps; not a legal finding of non-compliance.

Evidence Strength Heuristic

Delivers — how well each answer is backed by traceable evidence. How — answer completeness plus traceable passage-and-location evidence checks. Read it as — traceability is checked; semantic sufficiency and operating effectiveness still require human review.

Examiner Simulation Heuristic

Delivers — the questions an examiner is likely to ask first, drawn from your weakest answers. How — questions generated from unanswered, uncited, or brief questionnaire responses. Read it as — a predictive readiness aid; not an examiner opinion or enforcement forecast.

Compliance Posture Database-derived

Delivers — an at-a-glance readiness score across a regulation. How — questionnaire completion and stored gap counts. Read it as — operational readiness, not certified legal compliance.

Policy Coverage Database-derived

Delivers — which obligations your internal policies actually cover, with the citation. How — stored internal citations requiring a supporting passage and section/page for “Covered” status. Read it as — a candidate mapping; human review must confirm semantic coverage and implementation.

Evidence Checklist Database-derived

Delivers — a per-requirement checklist of what’s present vs missing. How — presence checks for responses, citations, policies, and evidence documents. Read it as — presence, not substantive adequacy or authenticity.

Cross-Reg Overlap Database-derived

Delivers — where obligations are shared across the regulations you’ve adopted, so you answer once. How — shared canonical obligation identifiers across adopted regulations. Read it as — a high-level overlap map; article-level equivalence requires document-grounded comparison.

Conflicting Obligations Heuristic

Delivers — requirements that pull in different directions across regulations. How — stored obligation and requirement-value conflict detection. Read it as — potential conflicts that require review against the authoritative regulatory text.

Regulation Summary Database-derived

Delivers — a quick overview of an adopted regulation and where you stand on it. How — adopted regulation metadata and stored questionnaire state. Read it as — an overview only; consult the retrieved primary text for provision-level legal analysis.