RegAlign + RiskAlign
Regulatory requirements and enterprise risks, side by side.
RegAlign® starts with regulatory requirements. RiskAlign® starts with objectives and enterprise risks. They meet at controls and evidence while each keeps its own records; decisions stay with the people responsible.
Obligations into evidence.
Start with regulatory requirements. See the controls and evidence linked to them.
- 1Regulatory change ingested
- 2Mapped to obligations
- 3Linked to controls
- 4Evidence captured & monitored
- 5Reported to the board
Risks into decisions.
Start with what could hurt the firm. End with appetite, controls and KRIs.
- 1Enterprise risk identified
- 2Inherent & residual scored
- 3Board appetite & limit set
- 4Controls & KRIs linked
- 5Scenarios stress-tested
Each product keeps its own control register. Where both are in place, an obligation in RegAlign and a risk in RiskAlign can be related to the same control. Information moves only through the defined exchange; the verified route today is a manual CSV exchange. There is no automatic shared live database.
RegAlign and RiskAlign are being prepared for release together first. Before a firm uses either product, we confirm that the features, jurisdiction, integrations and setup it needs have been tested for that use.
Use either product independently, or pair them.
| Capability | RegAlign only | RiskAlign only | Together |
|---|---|---|---|
| Regulatory change tracking | ✓ | — | ✓ |
| Obligations register | ✓ | — | ✓ |
| Enterprise risk register | — | ✓ | ✓ |
| Risk appetite & KRIs | — | ✓ | ✓ |
| Control register | ✓ | ✓ | Separate registers; references can move by defined CSV exchange |
| Board pack | Compliance pack | Risk pack | Separate packs per product |
| Audit trail | Per obligation | Per risk | Held separately in each product |