Review obligations and their sources

A document is the starting point. To use it in daily compliance work, you also need to understand the requirement it contains, the circumstances in which it matters and the operational work connected to it. The repository brings those elements into a structure you can examine.

Obligation records sit alongside their source references and links to controls or reporting requirements. This lets you move between the underlying material and its place in your firm’s regulatory picture without treating a document title as a complete answer.

The distinction matters: a source explains the regulatory basis, an obligation describes a requirement, applicability considers its relevance to the firm, and a control describes related work. These are connected layers, not interchangeable conclusions.

When you begin with an obligation, return to the linked material to examine its wording and context. Then follow the operational links to understand which controls or reporting requirements need consideration.

When you begin with a control or reporting item, work in the other direction. Inspect the underlying requirement and the company facts relevant to it. This helps you explain why the work is on the agenda, rather than relying on a checklist without its supporting rationale.

Check the scope, dates, conditions and available source references before relying on a record. A requirement may need to be read alongside other material, and an available reference does not mean every interpretation has already been resolved.

For example, when preparing an internal review, begin with the relevant obligations, examine their sources and identify the linked controls. Keep any missing references or unresolved interpretation questions visible for follow-up. The repository supports that investigation; professional judgement remains part of it.