Terminology GuideEvent Model Language

Regulatory Universal Timeline Glossary

Use one vocabulary for the merged timeline, the delivery calendar, and governance reporting.

Shared terms reduce ambiguity when legal, security, product, and audit teams read the same timeline snapshot.

This glossary is tuned to the actual universal timeline implementation and the operating model around it. It defines the core viewer terms as well as the program terms needed when events move from the timeline into owned delivery work.

Viewer and data model terms

These terms describe how the merged timeline is built and how users should interpret what they see on screen.

Use them when explaining the timeline itself, not when describing internal remediation work.

  • Source timeline: one local timeline dataset merged into the universal viewer
  • Source label: the framework label shown after normalization from source key or regulation identifier
  • Category chip: a filter chip representing a namespaced category inside one source timeline
  • Milestone event: an event marked as a milestone in the underlying data model
  • Ranged event: an event that includes both a start date and an end date
  • Event detail: the title, article context, summary, and source link shown when an event is opened

Planning and delivery terms

These terms describe how external dates become internal work.

Use them in program boards, governance packs, and delivery reviews.

  • Internal milestone ladder: your ordered set of analysis, design, implementation, assurance, and closure dates built from one external event
  • Collision window: a period where multiple source timelines create pressure on the same owners or dependencies
  • Dependency blocker: an unresolved issue that prevents an internal milestone from closing
  • Control owner: the role accountable for implementation quality and evidence readiness
  • Escalation trigger: a predefined threshold that forces management review or re-prioritization

Evidence and reporting terms

These terms matter when you export or audit the timeline driven program.

They help separate a useful visual snapshot from the evidence record behind it.

  • Export snapshot: the PNG image generated from the current viewer state
  • Evidence package: the set of artifacts that proves an internal milestone or external obligation has been met
  • Evidence freshness: the maximum accepted age for a supporting artifact
  • Reuse register: the external record that documents when one artifact supports more than one obligation
  • Version note: the date and change explanation attached to a shared export or calendar update

Interpretation and governance terms

These terms govern how the timeline should and should not be used.

They are essential for keeping planning useful without overstating legal certainty.

  • Scope assumption: a documented interpretation about entities, products, or services considered in scope
  • Residual regulatory risk: the remaining compliance risk after controls and delivery actions are complete
  • Non-reusable obligation: a requirement that cannot be fully covered by a shared control or evidence package
  • Decision log: the record of governance approvals, exceptions, and changed priorities linked to the timeline
  • Planning tool: the correct role of the universal timeline, which is coordination and prioritization rather than legal determination authority
Recommended next step

Use Regulatory Universal Timeline Glossary as a cited research workflow

Research Copilot can take Regulatory Universal Timeline Glossary from getting cited answers and faster research on this topic to a reusable workflow inside Sorena. Teams working on Regulatory Universal Timeline can keep owners, evidence, and next steps aligned without copying this guide into separate documents.

Primary sources

EUR-Lex portal

Legal terminology and milestone context for EU source timelines.

UK legislation

Legislative terminology source for UK timelines in the merged view.

Related guides