Edict IQ logo
HomeRegulatory requirements

Regulatory requirements

Understand which regulatory requirements may matter.

A requirement only becomes actionable when its legal status, addressees, jurisdiction and effective conditions are understood. Start with the source—not a generic checklist.

Official sourcesTraceable analysisNo mandatory demo
SOURCE TO DECISION
01
Official sourceOriginal & legal status
02
Assess relevanceScope & activity
03
Make a decisionReview & evidence
Illustrative workflow · not a live product screenshot

THE CHALLENGE

Regulatory requirements are not one universal list

Two organisations in the same industry can face different duties. Regulatory texts must be read in context, and a summary must not collapse proposals, guidance and binding instruments into a single obligation.

01

Trace the legal basis

Examine the issuing body, publication and original instrument before using a requirement in an internal review.

02

Check organisational fit

Consider jurisdiction, regulated status, activities and the applicable framework. Context matters more than an unqualified keyword match.

03

Recognise open questions

Keep assumptions and unresolved applicability questions visible for specialist review.

FROM SOURCE TO REVIEW

A disciplined requirements review

Use the source-to-decision sequence to avoid premature or incomplete compliance conclusions.

  1. 01

    Find

    Identify the primary instrument, its issuer, status and related official guidance.

  2. 02

    Evaluate

    Understand who the provision addresses and what conditions could trigger an obligation.

  3. 03

    Review

    Compare the potential requirement with existing controls and retain the decision rationale.

Review the original first. Assess implications second. Final judgement remains with people.

Read our methodology

IN PRACTICE

For teams interpreting changing obligations

A defensible compliance workflow distinguishes the legal source from the organisation's own conclusion.

Check source coverage
Illustrative use case / 01

DORA and ICT providers

A service provider needs to distinguish its own duties from contractual expectations imposed by a regulated financial client.

Illustrative use case / 02

Regulatory advisers

An adviser reviews whether a new EU instrument changes the obligations of one client entity but not another.

TRUST THROUGH EVIDENCE

Every material claim needs a source.

Edict IQ distinguishes official publications from interpretation and possible consequences. Source status, coverage limitations and unresolved questions belong in the review—not hidden in the fine print.

The content is a framework for analysing requirements, not an exhaustive obligations catalogue or a legal opinion on any specific entity.

Browse official sources

FAQ

Frequently asked questions

Straightforward answers without pretending that one rule applies to every organisation.

How do I identify applicable regulatory requirements?

Start with the binding legal source, check jurisdiction, scope, regulated activities and effective dates, then document the organisation-specific conclusion.

Do all regulatory publications create requirements?

No. Consultations, policy statements and other materials differ in legal effect. The document's status must be checked first.

Can an AI summary decide applicability?

It can help organise evidence and questions, but final applicability decisions require human judgement and appropriate legal review.

EXPLORE EDICT IQ

See what changed. Understand what it means.

Start with available regulatory events and inspect the original sources. No mandatory product demo.