Requirement
A single, testable duty within an obligation, specific enough to be mapped to a control and evidenced.
Overview
Large obligations often break into several requirements, each with its own condition, deadline or threshold. Mapping at requirement level is what lets one control satisfy several regimes at once.
It connects most directly to Obligation, Control and Regulatory relationship chain.
Check the official sources below for legal scope, applicable dates and exceptions. This entry is an explanatory reference, not legal advice.
Why it matters
Requirements are the level at which coverage and gaps become visible.
Who it affects
Compliance teams mapping controls.
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 Requirement. 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.
Mapper breaks obligations into requirements and finds where one control can cover many.
Request early access →