Compliance
Turn regulatory and standards obligations into owned requirements, assess them with evidence, and see a compliance rate you can explain line by line.
What it does
Load the frameworks you are subject to as configurable libraries — you bring your own licensed content — then break each into requirements with an owner, review frequency and due date.
Mark what does not apply with a recorded justification, document gaps, map requirements to controls and attach evidence. The compliance percentage is calculated from assessed requirements with not-applicable items excluded, using a method you can configure.
Key capabilities
What works in the platform today, and what is on the roadmap.
- Available working in the current release
- Planned on the roadmap — not yet available
- Available
Frameworks and requirements
Maintain frameworks and their requirements with reference, owner, frequency and next due date.
- Available
Applicability with justification
Mark requirements not applicable, with a mandatory written justification.
- Available
Gap recording
Capture the gap and status for each requirement as it is assessed.
- Available
Evidence with SHA-256
Upload evidence files; each is fingerprinted so later tampering is detectable.
- Available
Requirement ↔ control mapping
Show which controls satisfy each requirement — and which requirements have none.
- Available
Configurable compliance %
Rate per framework and overall, excluding not-applicable requirements.
- Available
Compliance overview
A dashboard of status by framework with filters by unit and owner.
- Planned
Automated regulatory content feeds
Connectors that pull updated requirement text from external sources.
How it connects
Records are linked across modules, so the same fact is entered once and seen wherever it matters.
- Controls & RCSARequirements are satisfied by controls; control test results show whether they work.
- Policy ManagementPolicies translate requirements into internal rules with approved versions.
- AI IntelligenceThe rule engine flags gaps where a requirement has no linked control.
- Incidents & Corrective ActionsNon-compliance events are logged as incidents linked to the requirement concerned.
See Compliance with your own data
Book a guided walkthrough, or sign in to your workspace to explore the module.
Consulting: consulting@4each1.com · Projects & systems development: projects@4each1.com