Control
A specific, testable action an organisation performs to meet an obligation, with an owner, a frequency, a test and evidence on every run.
Overview
Good controls are precise: who does what, how often, against which data, with what pass condition. Each run produces evidence that the control operated.
Controls can be preventive, detective or corrective, and manual or automated.
It connects most directly to Obligation, Audit evidence, Evidence package and Control test.
Example
C-RED-03: redeem MWUSD at par within two business days. Owner: Treasury. Runs on every redemption request.
Check the official sources below for legal scope, applicable dates and exceptions. This entry is an explanatory reference, not legal advice.
Why it matters
Controls are where compliance actually happens. Everything else is a description of it.
Who it affects
Every regulated organisation.
Where it sits
Ten linked steps connect where you operate to the proof that you complied.
- 01Jurisdiction
- 02Industry
- 03Activity
- 04Authority
- 05Regulation
- 06Requirement
- 07Guidance
- 08Control
- 09Evidence
- 10Enforcement
Connections
The terms most closely tied to Control. Select one to open it.
What to do about it
- 1Define the owner, frequency, data and pass condition.
- 2Automate the test on source data where you can.
- 3Capture evidence on every run, including exceptions.
- 4Review exceptions and failures and record the decision.
From requirement to evidence.
Controls in Regulation Layer run on streaming data where possible and seal an evidence pack on every run. Each one is a pip on the dial.
Request early access →