> ## Documentation Index
> Fetch the complete documentation index at: https://docs.royaltyport.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Categorized Dates

> Reversion dates organized by asset, date, and territory combinations

<Info>
  Categorized Fields are simplified views derived from [Structured Data](/projects/contracts/contract-details/structured-data/dates). For full detail including term durations, conditions, and calculated date explanations, see the [Dates](/projects/contracts/contract-details/structured-data/dates) structured data page.
</Info>

## Overview

Categorized Dates flatten the complex date structures in a contract into unique combinations of assets, dates, and territories. This creates clear reversion date records that are easy to track and export.

<Warning>
  Categorized Dates currently ONLY calculates reversion dates for **Spotify only**. Support for additional platforms is coming soon.
</Warning>

## What Gets Categorized

Each categorized date record represents a unique combination of:

| Field               | Description                                 |
| ------------------- | ------------------------------------------- |
| **Composition IDs** | Linked compositions (if applicable)         |
| **Recording IDs**   | Linked recordings (if applicable)           |
| **Date**            | The reversion/end date (YYYY-MM-DD format)  |
| **Territories**     | ISO territory codes where this date applies |

## How Dates Are Categorized

The categorization process:

1. Takes all calculated end dates from the structured data
2. Incorporates control area territories
3. Uses release dates from linked recordings/compositions
4. Creates unique records for each asset + date + territory combination

### Asset-Specific Dates

When contracts have per-asset terms (e.g., "rights revert 5 years after release"), the categorized view creates separate records for each asset:

| Recording | Date       | Territories |
| --------- | ---------- | ----------- |
| Track A   | 2028-03-15 | US, CA      |
| Track B   | 2028-07-22 | US, CA      |
| Track C   | 2029-01-10 | US, CA      |

### Territory-Specific Dates

When rights expire at different times in different territories:

| Recording | Date       | Territories |
| --------- | ---------- | ----------- |
| Album X   | 2028-01-01 | US          |
| Album X   | 2030-01-01 | GB, DE, FR  |
| Album X   | 2032-01-01 | JP          |

## Example

A contract with:

* 5-year term from release date
* 2 recordings released on different dates
* Worldwide rights

Would be categorized as:

| Recording IDs | Date       | Territories |
| ------------- | ---------- | ----------- |
| rec\_001      | 2028-06-15 | World       |
| rec\_002      | 2029-02-20 | World       |

<Note>
  The categorized view shows the computed reversion dates. For the underlying term durations, conditions, and calculation logic, see the full [Structured Data](/projects/contracts/contract-details/structured-data/dates).
</Note>