DPO Radio

A compliance officer running a multi-framework programme spends a disproportionate share of their week on three tasks. The first is walking control coverage against a specific framework (ISO 27001 Annex A, SOC 2 Trust Services Criteria, PDPL requirement set). The others are triaging conflicts where two installed frameworks point in different directions, and assembling dossier filings or maturity-assessment exports for an upcoming review. Each task requires fluency in the framework text plus fluency in the organisation's actual control library.
The Compliance Specialist persona is tuned for that work. Each conversation tells it which frameworks your organisation has installed, and it reads assessments and other records through its search tools, within the permissions of the person asking. Its tool affinity is biased toward regulatory search, framework conflict detection, and the compliance-lane workflow pack — coverage walkthroughs, gap analyses, control mappings.
The Compliance Specialist's citation discipline is the same as every other persona: no legal conclusion without an inline citation naming the framework and the specific requirement. The off-topic refusal block redirects compliance-adjacent questions that drift outside the specialist's scope back to the Generalist or to a more appropriate specialist.
The Compliance Specialist's prompt names every framework your organisation has installed — for example PDPL, GDPR, ePrivacy, Cybersecurity Law, ISO 27001, SOC 2, DORA, NIS2 or sector overlays, where you have installed them. It carries the names, not the text: the specialist may cite a framework only when its regulatory search returned that text in the same turn. Cross-framework reasoning is the specialist's default mode of operation.
The specialist reaches for regulatory search and framework conflict detection first. The compliance-lane workflow pack — ISO 27001 Annex A Control Coverage, SOC 2 Trust Services Criteria Evidence Map, RoPA Hygiene Auto-Fix against the 4-framework registry, compliance rule auto-mapping — sits one click away.
The specialist walks a control library against installed packs and surfaces per-requirement coverage. The output is a structured task list for evidence collection, never an autonomous commit. The compliance officer reviews per row and accepts the mapping.
The specialist runs gap analyses against the framework requirement set and returns a per-gap finding with the source citation. Each gap carries a suggested remediation routed through the appropriate workflow (remediation plan generator, policy gap detection, etc.).
The specialist surfaces conflicts between installed packs and walks the country compliance manager or the legal counsel through the side-by-side framework positions. Acknowledgement, assignment, and resolution all happen through the in-product Cross-Framework Conflicts surface.
A question about contract redline or vendor risk acceptance triggers a redirect to the Legal Counsel or Risk Analyst persona. A question outside the compliance, legal, privacy, risk, or audit scope triggers the standard refusal block.



Every legal conclusion the Compliance Specialist makes ships with an inline citation naming the framework and the specific requirement. When grounding is unavailable the specialist says so explicitly.

Every workflow run through the specialist produces a structured draft, not an autonomous commit. The compliance officer reviews per field, accepts what is right, rejects what is not. Both the accepted draft and the rejections are in the audit trail.

The persona prompt is reviewable on request. It ships in the runtime persona pack and is identical on every tier — no tier offers a tenant-level override, so the specialist's citation discipline and refusal block cannot be edited away.

The Compliance Specialist's English and Vietnamese playbooks cover incident triage, AI inventories, policy and programme reviews. Open AI governance workflows or management system workflows from the appropriate record to turn a question into reviewable work.
Ready to see an ISO 27001 Annex A coverage walkthrough produced in three minutes with citations per control? Request a personalised demo.


Run the ISO 27001 Annex A Control Coverage workflow and the SOC 2 Trust Services Criteria Evidence Map through the Compliance Specialist persona for 30 days against your installed packs.

Talk to our team about which framework programmes the specialist should be tuned for first in your environment.
Framework cross-walks, gap analyses against installed regulatory packs, control mapping into the organisation's control library, and cross-framework conflict triage. The specialist is also the default voice for ISO 27001 Annex A coverage and SOC 2 Trust Services Criteria evidence walkthroughs.
Yes. Each conversation tells it every framework your organisation has installed for use — PDPL, GDPR, ePrivacy, Cybersecurity Law, ISO 27001, SOC 2, DORA, NIS2, sector overlays or AI Law, where you have installed them. An overlay you installed for reference only is left out. The specialist cites a framework only when its regulatory search returned that text in the same turn. Cross-framework reasoning is its default mode of operation.
No. Every workflow run through the specialist produces a structured draft, never an autonomous commit. The compliance officer reviews per row and accepts the mapping.
A question about contract redline, vendor risk, or audit walkthrough triggers a redirect to the Legal Counsel, Risk Analyst, or Auditor's Eye persona. A question outside the compliance scope entirely triggers the standard off-topic refusal block.
No. The Compliance Specialist's prompt ships in its runtime persona pack and is identical on Light, Standard, and Enterprise — no tier offers a tenant-level override. The prompt is reviewable on request, and what it picks up per conversation is your own context: the user's locale and role, the organisation's tier, and the regulatory packs your organisation has installed.