Manage obligations, evidence and compliance activity in one system
Consolidate compliance obligations from law, contracts and internal policy into a single register — linked to controls, evidence and corrective actions.
It is the module that holds every compliance obligation in one register. Obligations are extracted from regulations, contracts, internal policy and standards, then linked to the controls in operation and the evidence submitted by business units. The system tracks each obligation through six stages until it reaches compliance.
Who is it for?
Compliance and legal carry the main responsibility. Compliance officers in each unit submit evidence through a dedicated portal. Leadership and the board see consolidated compliance status. Internal audit reuses the same control library once the platform is linked.
What problems does it solve?
Three problems: obligations spread across many spreadsheets so nobody knows the total; no clarity on which obligations lack a matching control; and evidence submitted in one place and assessed in another, so there is no trace of who concluded what, and when.
How is it different from a spreadsheet?
The system separates compliance outcome from workload, distinguishes five result levels rather than pass or fail, prevents whoever submitted evidence from assessing it, and keeps a log of who, when and why for every change.
How is it rolled out?
The module runs on its own; the other two are not required. Initial data covers the applicable regulations, the existing control list and the org structure. When the organisation is ready, switch on linking to share the risk register and control library with the other two modules.
The business problem
When obligations are scattered, mistakes slip through
01
Nobody knows the total number of obligations
Obligations sit in spreadsheets across many departments. When the regulator asks, it takes days to pull together.
02
Obligations are not linked to controls
The organisation has control processes and legal obligations, but nobody can reconcile which obligation is missing a control.
03
Evidence cannot be traced
Attachments live in email. It is unclear who submitted, who assessed, and on what grounds the conclusion was reached.
04
Regulatory change goes unreviewed
A new regulation is issued, but there is no mechanism to identify which obligations are affected and which controls must change.
Compliance obligations
From the source regulation through to assessed evidence.
End-to-end process
Track obligations from requirement through to remediation
Input
Regulations, contracts, internal policy
Activity
Extract obligations · link controls · collect evidence
Control and approval
The assessor concludes, separate from the submitter
Output
Compliance status, gaps, period reports
Compliance check processfour steps, following ISO 190114 steps
1Plan
Annual programme, objectives, scope, criteria and team assignment.
2Perform
Collect evidence against the programme, record findings and severity.
3Report
Discuss with the unit, confirm findings, draft and issue the report.
4Monitor remediation
Track actions to closure and update compliance risk.
Product screens
See compliance activity managed in practice
Two representative screens illustrating the product interface. The figures shown are sample data.
Compliance overview
Screen 1
Two separate groups of measures: the compliance outcome of obligations in force, and the workload still to be done.
app.risktech.asia / compliance
Compliance
Overview
My tasks
Obligations
Controls
Regulations
Reviews
OverviewQ3/2026
Compliance status
Compliance results — not workload.
142
Obligations in force
89
Compliant
18
Partially compliant
12
Non-compliant
14
Insufficient evidence
Workload
Work to be done.
12
No controls
23
Evidence awaiting review
9
Open findings
4
Overdue actions
New regulatory changes
HIGH IMPACTAmended personal data protection rules — 8 obligations affected
Each obligation passes through six stages; compliance check campaigns run alongside them in the four steps of ISO 19011.
app.risktech.asia / compliance/lifecycle
Compliance
Overview
Reviews
REVIEW PROCESS
1 · Planning
2 · Fieldwork
3 · Reporting
4 · Remediation tracking
Compliance reviews3 in progress
Obligation lifecycle · 6 stages
1Identify obligations142
2Link controls125
3Assess evidence102
4Gaps found34
5Remediating22
6Compliant89
Code
Review
Stage
Status
CR-01
Personal data protection compliance review
2 · Fieldwork
Running
CR-02
Supplier file review
3 · Reporting
For approval
CR-03
Branch compliance review
4 · Monitoring
Remediation
Feature groups
Every role knows what needs doing
Consolidated obligation register
Compliance function
Extract obligations from four sources: law, contracts, internal policy, standards
Link obligations to controls so uncovered obligations surface by themselves
A reassessment cycle set per obligation
Evidence and assessment
Unit compliance officers
Units submit evidence through a dedicated portal with deadlines
Five result levels rather than pass or fail
Submitter and assessor are different people, enforced from assignment onward
Regulatory change
Legal
Compare regulation versions
Impact analysis against every obligation being tracked
Rank impact as high, medium or low
Findings and remediation
Compliance function
Findings carry severity, an owner and a deadline
Exceptions carry a validity period and an approver
Tracked through to closure
Concerns and training
HR, compliance
A channel for raising concerns plus an investigation process
Awareness training campaigns per period
Completion rates tracked by unit
AI assistant with citations
All roles
Points out obligations with no control and suggests existing ones
Every suggestion carries source citations
Approval is required; with AI off the system still runs in full
Who it fits
Who is it for and what do you need to prepare?
Who it fits
When to use it
Data to prepare
Enterprises with many sector obligations: finance, banking, insurance, healthcare, education
Ahead of a review period or a sector inspection
The list of applicable regulations
Groups with several member companies and legal entities
When consolidating compliance after a merger or branch expansion
Org structure and compliance owners
Organisations building a compliance management system to ISO 37301
When moving from spreadsheets to a system
The existing control list
Platform linking
Connect compliance with risk and internal audit
This module runs on its own. Once linking is on, all three share the risk register, control library and evidence store — see the platform architecture diagram.
RiskTech supports organisations operating to the standards below. This is not a certification claim for the software or for the organisations using it.
ISO 37301
Compliance management systems
ISO 19011
Guidelines for auditing management systems
Three lines of defence
Responsibility model
Frequently asked questions
Compliance management
Yes. Compliance management runs entirely independently of the other two, with its own obligation register, control library and permissions. When the organisation needs it, switching on linking is a configuration step.
The sample content references domestic regulations. The list of regulations applicable to a given organisation must be reviewed and approved by its legal function before going live.
The assessor must be a different person from the submitter. The system blocks one person from both submitting and concluding, starting at the assignment step.
Five: compliant, partially compliant, non-compliant, insufficient evidence, not yet assessed. Exceptions in force are tracked separately.
No. AI only offers suggestions with source citations; every change needs approval by an authorised person. With AI off, the system still runs the full process.
Details on storage infrastructure, backup and per-unit data partitioning are covered directly in the demo, together with technical documentation for your IT team.
See how RiskTech supports your compliance needs
A 30-minute demo following the role you hold. No data preparation needed beforehand. We respond within one business day.