Coverage GuideCurrent Build Scope

What is included in the Regulatory Universal Timeline

Know exactly what the merged viewer includes today before you rely on it in planning or reporting.

Coverage is driven by local timeline files in the artifacts catalog. If a source timeline is not present there, it is not present here.

The current build auto-merges the maintained source-linked artifact timelines. That means the universal timeline is comprehensive only within that maintained source set. It is not a live crawler and it does not infer timelines for artifacts that do not ship with timeline data.

Current Regulatory Universal Timeline source coverage

As of the current build, the viewer merges 38 source-linked timelines and 1297 dated events. The source timelines currently span APAC, EU, LATAM, UK, and US artifacts.

The current merged source set includes the following local timeline datasets.

  • APAC: Australia Cyber Security Act and Singapore PDPA
  • LATAM: Brazil LGPD
  • UK: UK GDPR, UK Online Safety Act, and UK PSTI
  • US: CCPA and CPRA
  • EU: Accessibility Act, AI Act, Batteries Regulation, CRA, CSDDD, CSRD, Data Act, DDP, Deforestation Regulation, DMA, DORA, DSA, EED, eIDAS, EMC Directive, ePrivacy, ESPR DPP, ESPR, GDPR, GPSR, Green Claims, LVD, Machinery Regulation, MDR, MSR, NIS2, PPWR, RED, RoHS, and Taxonomy Regulation

What each event record can contain

The merged viewer uses a consistent event model. Every event has a date, category, title, summary, and milestone flag. Events can also include an end date, article reference, and source URL.

Those fields are what let the viewer support both quick visual scanning and deeper event inspection when a team needs traceability.

  • date: the event start or single day marker
  • endDate: optional end date for a transition or reporting window
  • category: the namespaced category used for filtering
  • title: the normalized event title shown in the merged view
  • article: optional article or context field shown with source label prefix
  • summary: short explanatory text used in event detail
  • url: optional source link for direct reference
  • milestone: boolean marker used to distinguish milestone style events

How labels are normalized in the merged view

The builder preserves source separation but normalizes some labels for readability. It gives explicit stable labels to selected frameworks such as EU DORA, EU NIS2, EU CRA, EU Data Act, and Australia.

Other source timelines use an uppercase label derived from the local source key. This is why some labels appear as formal framework names while others appear as stable source identifiers.

  • Categories are namespaced per source timeline before they are shown as filter chips
  • Event titles are prefixed with the source label unless they already begin with it
  • The article field is also prefixed with the source label to keep context visible in the merged detail panel
  • Closely related source timelines may appear separately if they are maintained as separate local datasets

Known operating limits

The universal timeline is a strong planning and coordination view, but it does not supersede legal analysis or program management tooling.

Teams should understand those limits before using the viewer as a formal control in governance routines.

  • The viewer does not determine whether a framework applies to your entity
  • The viewer does not assign owners, tasks, or evidence packages for you
  • The viewer supports PNG export, not CSV or ICS export in the shipped user flow
  • High impact dates should still be validated against the official source link or legal text before external commitment
Recommended next step

Use the Regulatory Universal Timeline as a cited planning workflow

Research Copilot can help teams move from Regulatory Universal Timeline coverage checks to cited scope, timing, owner, evidence, and next-step decisions without copying this guide into separate documents.

Research workflow
Open Research Copilot for the Regulatory Universal Timeline

Start from the Regulatory Universal Timeline and answer scope, timing, and interpretation questions with cited outputs.

Explore next step
Talk to Sorena
Talk through Regulatory Universal Timeline planning

Review timeline coverage, source evidence, planning gaps, and next implementation steps.

Explore next step

Primary sources

EUR-Lex portal

EUR-Lex is cited because EU source timelines in the merged Regulatory Universal Timeline point back to official EU legal texts and metadata.

"EUR-Lex portal"
UK legislation

Primary legal source portal for UK timelines in the current merged build.

"UK legislation"

Related guides

Compliance Calendar for Regulatory Universal Timelines
Build an internal compliance calendar from Regulatory Universal Timelines by converting external dates into owned milestones, lead times, collision windows, and evidence gates.
Regulatory Universal Timelines Export and Sharing Guide
Share Sorena AI Regulatory Universal Timeline correctly: browser generated PNG export, filter context, version notes, leadership reporting packs.
Evidence Reuse for Regulatory Universal Timeline
Use Sorena AI Regulatory Universal Timelines to spot framework overlap, reuse evidence across aligned obligations, and keep source-linked deadline decisions traceable.
Regulatory Universal Timeline Glossary
Glossary for Sorena AI Regulatory Universal Timeline covering source timelines, category chips, milestone events, ranged events, export snapshots.
How to Use Regulatory Universal Timelines
Step by step guide for using Sorena AI Regulatory Universal Timeline: source filters, category chips, event detail, zoom, minimap navigation.