Skip to main content
Structured data fields are by definition an abstraction of legal language. When in doubt, use citations, the AI chat, and the actual contract text to validate the structured data against your own interpretation.

​
Overview

The Dates extraction captures explicit dates from the contract, identifies term durations, and calculates when rights periods end. This multi-phase process transforms complex contractual timing into structured, actionable data.

​
Extraction Focus

This extraction is designed to capture dates and durations that affect when music exploitation rights begin and end. Understanding what is and isn’t in scope helps you interpret the extracted data correctly.
The extraction focuses on the primary exploitation of musical IP (compositions, masters, recordings) by the parties to the agreement. Ancillary rights, third-party rights, and administrative processes are not extracted as calculable terms.

​
What Gets Extracted

​
Explicit Dates

Specific dates stated in the contract:
Date TypeDescriptionNotes
Agreement DateWhen the contract was made/datedOnly ONE per contract
Effective DateWhen terms take effectOnly with explicit “effective as of” language
Signature DateWhen parties signedCan be per-signatory or general
Start DateWhen a term beginsMust reference a specific date value
End DateWhen a term endsOnly for rights or agreement terms
Release DateWhen a work was/will be releasedMust be explicitly stated with a date
Start and end dates are only extracted when explicitly stated in the contract. Dates that would be inferred from other dates (e.g., “commences on signature” when no signature date is provided) are not extracted.

​
Term Durations

Periods expressed as durations rather than specific dates:
Term TypeDescription
RightsPeriod during which exploitation rights are granted (e.g., “10 years from delivery”)
AgreementOverall contract term, when separate from rights period
AdministrationPeriod of administration control (publishing/neighbouring rights)
CollectionPost-rights period for collecting royalties (publishing agreements)
RetentionPeriod after term ends before rights revert
ExtensionOptional periods that extend base terms (each option is separate)
NoticeRequired notice period to terminate and revert rights
Each term includes:
  • Value and unit: e.g., “5 years”, “18 months”, “perpetual”
  • Description: Context from the contract
  • Condition: Only when start/end depends on an uncertain event (recoupment, option exercise)
  • Identifier: Specific catalog or work name (not generic period names)

​
Calculated End Dates

The system calculates when rights periods end based on extracted dates and durations:
End TypeDescription
FixedSingle definitive end date (no variations/options)
EarliestSoonest the term could end (no extensions exercised)
LatestLatest the term could end (all extensions exercised)
Each calculated date includes:
  • Date: The calculated end date (YYYY-MM-DD)
  • Type: rights, agreement, administration, collection, or retention
  • Estimated: True if using proxy dates (e.g., release date instead of delivery date)
  • Linked assets: Recording and/or composition IDs this date applies to

​
Perpetual Terms

Terms with “perpetual”, “in perpetuity”, “life of copyright”, or similar language have no calculated end date. These are captured as term durations but do not produce end date calculations.

​
Missing Dates

When a calculation requires a date that isn’t available, it’s listed as missing:
FieldDescription
NameShort name for the missing date (e.g., “Delivery Date”)
DescriptionWhy it’s needed and what calculation it affects
Missing dates only appear when the contract explicitly references a specific date type that isn’t provided. The system does not speculate about what dates “might” be needed.

​
Reading Dates Data

​
Understanding Calculated End Dates

When interpreting calculated end dates:
  1. Fixed dates mean there are no optional extensions - this is the definitive end
  2. Earliest/Latest pairs mean extensions exist - earliest assumes no options exercised, latest assumes all options exercised
  3. Estimated dates use proxy dates (e.g., release date when delivery date is unavailable) - verify against actual dates when available
  4. Per-asset dates (showing linked recordings/compositions) mean each asset has its own timeline based on its release date

​
Date Hierarchy

The extraction follows a clear hierarchy: 
Contract Document
│
├── Explicit Dates (stated in contract)
│   ├── Agreement Date, Effective Date
│   ├── Signature Dates
│   ├── Start/End Dates (explicit)
│   └── Release Dates
│
├── Term Durations (periods stated in contract)
│   ├── Rights, Agreement, Administration
│   ├── Collection, Retention
│   ├── Extensions (each option separate)
│   └── Notice periods
│
├── Calculated End Dates (computed)
│   ├── Fixed OR Earliest/Latest
│   └── Linked to assets
│
└── Missing Dates (needed for calculations)

​
Editing Dates

Click the edit icon to:
  • Add missing dates (delivery dates, release dates, etc.)
  • Correct date values
  • Modify term durations
  • Update term descriptions and conditions
Adding missing dates triggers recalculation of end dates, giving you accurate reversion timelines.

​
See Also

Categorized Dates

View reversion dates organized by unique asset, date, and territory combinations. Optimized for tracking reversions, timeline views, and exports.