Skip to content

Compliance

From circular to closed action, department by department.

Load a regulation, break it into obligations, route it to the departments it touches and track every gap to closure.

Module structure verified in the application, 18 Sep 2026.

The pipeline

One regulation, six steps, nothing re-keyed.

Each step hands a record to the next. Select a step to see what it holds and what it passes on.

01

Regulatory Register

Add a regulation or bulk-import a set of them. Every entry is versioned and can be reported on.

On the record

  • Issuing body
  • Document type
  • Status
  • Effective date
  • In-compliance share

Hands on

A versioned regulation, ready to be routed.

01 / 06

On the foundation

Obligations point at controls you already hold.

Compliance does not keep its own copy of the control library. It maps obligations onto the controls in Governance, so a control that satisfies three regulations is one record, not three.

Governance

  • ObligationControlEvery obligation maps onto the control library in Governance.
  • ObligationRiskObligations carry through to the risks the control answers.
  • GapActionA gap raises an action plan and a task, with an owner and a date.

Recorded in the product

Regulatory Watch

Regulator feeds arrive as a change feed. Opening an item shows the requirement deltas read out of it and the policies and controls each one touches.Sample organisation

And the two views people actually open.

Frameworks we cover

  • My Compliance WorkA personal view of assessments, obligations and overdue actions.
  • Regulatory WatchPreviewRegulator feeds turned into a triage queue with the policies and controls each change touches.Feeds on the preview screenRBISEBIIRDAICERT-InMeitYEDPBMAS

Bring us a circular. We will show you the closure.

The demo walks one real regulation from the register through applicability, assessment and action to the evidence behind it.