Systems and records
How to represent a creative asset whose approved license has expired
By SourceX Editorial · Reviewed by Noah Loul ·
10 sections
Short answer
Represent an expired license by keeping the original approval unchanged, storing each rights layer as a dated window with its source document, boundary rule and time zone, and computing the asset's status for a stated as-of date. A media usage rights expiry dataset turns those records into tasks: for this version, use and date, which layer binds, what status applies and what must happen to live placements.
License terms
Media usage rights expiry
Key takeaways
- Approval belongs to a version on a date; expiry is a time condition on rights. Store both and never overwrite one with the other.
- Record how every end date was produced: stated, derived from a duration, or counted from an event such as first filming day.
- Keep the boundary rule and time zone with each window, because boundary days and zone mismatches are where status calls go wrong.
- Use a closed status vocabulary so reviewers and models can be scored on exact agreement and the binding layer they cite.
- Route records whose end date depends on missing documents to a rights reviewer instead of guessing.
How do you represent a creative asset whose approved license has expired?
Keep the approval exactly as it was given, store each rights layer as a dated window with the document that sets it, and compute the asset's status for a stated as-of date instead of overwriting a single status field. An approval says someone accepted a version of the asset for a use on a given day. A license window says when that use is permitted. Expiry is the moment the second stops covering the first, and it should never erase the record of the first.
That separation is what makes a media usage rights expiry dataset useful. A training or evaluation task built from it asks a model or a reviewer a question with a correct, checkable answer: on this date, for this requested use of this version, what is the asset's status, which rights layer decides it, and what must happen to placements already live. The same asset can be asked about on several dates and give several different answers, all correct.
Teams that flip a DAM field from Approved to Expired and move on lose the evidence for both states. Six months later nobody can show that a placement was legitimate when it ran, or explain why a renewed version is fine while the original cut is not.
Why an Approved badge and an Expired badge answer different questions
Approval is a workflow decision about a version; expiry is a time condition attached to rights, and a DAM can show both on the same asset at once. Adobe's documentation for Experience Manager Assets 6.5 lists Expired alongside Published, Approved and Rejected as states an asset can display, and shows approval and expiry statuses in separate columns of the list view.
The same page shows how much behavior an expiry date carries in a real system. Adobe describes asset expiration as a way to enforce license requirements: the published asset is unpublished when it expires, and a user without administrator permissions cannot edit, copy, move, publish or download it. It also notes two details that matter for a dataset. The expiration date is displayed differently for users in different time zones, and a compound asset that references an expired subasset is only shown as expired after the next scheduler run detects it.
Two other kinds of expiry are easy to confuse with a license end. The schema.org expires property describes the date content is no longer useful or available, which is a publisher's statement about relevance, not a rights term. Copyright duration is a third clock entirely: the U.S. Copyright Office explains that a work created on or after January 1, 1978 is generally protected for the author's life plus 70 years. A license can end decades before the copyright does, and the end of a license never means the work is free to use. Your records should name which of the three clocks a date belongs to.
Where does the end date come from: stated, derived or triggered by an event?
Record how each end date was produced, because many are not written on the license at all. Some are stated outright. Some are derived: the PLUS License Data Format defines optional license start and end dates in ISO 8601 form and notes that the end date may be calculated by adding the license duration to the start date. Some start counting only when an event happens.
Talent terms in advertising are the clearest example of an event clock. SAG-AFTRA's summary of its 2025 commercials contracts says the maximum period of use moved from 21 months, counted from first use or 13 weeks after the last production day, whichever came first, to 24 months starting 10 business days after on-camera principal photography begins. Two spots under different contract versions can therefore have end dates computed from different anchor events, and a dataset that stores only the resulting date cannot be checked.
Boundaries and time zones need the same care. The W3C ODRL vocabulary defines a dateTime constraint whose value is a date or date-time, strongly recommends time zone information, and distinguishes lt from lteq, which is the difference between a license that ends before a date and one that includes it. Store the boundary rule and the zone with every window; do not leave them to whoever reads the PDF next.
The dated usage rights and expiry evaluation task
Each task record asks one question: as of this date and time, may this version of the asset be used in this way, and what happens to existing uses? The fields below are the minimum a separate reviewer needs to rebuild the answer from evidence. Fill every field from a system of record, such as the DAM, the contract repository or the talent payment system, and mark missing values explicitly rather than guessing.
Use the record three ways: as an evaluation item for a rights assistant, as a supervised example of the reasoning a rights desk applies, and as an audit trail for your own team. The version stamp on the task (v1, dated 2026-10-18 here) should change whenever you add a field or a status.
| Field | What it holds | Typical source | Validation check |
|---|---|---|---|
| task_id and as_of | Unique id; evaluation date-time with time zone | Generated at build | as_of has an explicit zone; no two tasks share id |
| asset_ref | Asset id plus exact version or rendition | DAM version history | Version exists on as_of; renditions listed separately |
| requested_use | Action, media, channel, territory and whether it is a new placement or a continuing one | Request ticket or media plan | Every dimension filled from a controlled list |
| rights_layers | One entry per license, release, music cue or embedded element, each with document reference | Contract repository, release files | Every layer links a document; no free-text-only layer |
| window_per_layer | Start, end, end_basis (stated, derived, event) and anchor event if any | License terms, production calendar | Derived ends recompute from start plus duration |
| boundary_and_zone | Inclusive or exclusive end; zone the contract uses | License wording | Present for every window; mismatch with as_of zone flagged |
| post_expiry_duty | What must happen to live uses: remove, stop new placements only, archive allowed | License or release clause | Quoted clause reference, or marked unknown |
| approval_record | Approver role, date and version approved, kept unchanged | Workflow tool or DAM review task | Approved version equals asset_ref version or task fails |
| expected_status and action | One status from the fixed vocabulary plus required action | Rights reviewer | Status cites the binding layer by id |
| review_trail | Reviewer role, date, and any second-review disagreement | Build log | Two-person agreement on a sample before release |
A fixed status vocabulary keeps expiry decisions comparable
Give expected_status a closed list so two reviewers, or a reviewer and a model, can be scored on exact agreement. Free-text answers such as 'probably fine until spring' cannot be checked. The list below separates the cases a rights desk actually treats differently; adjust names to your contracts, but keep the distinctions.
| Status | Condition on the as_of date | What may be delivered or reused |
|---|---|---|
| active | Every layer's window covers as_of for the requested use | New and continuing uses as requested |
| expiring_in_notice_period | Earliest binding end falls within the team's notice period | Use allowed; renewal or replacement task opened |
| not_yet_active | A layer starts after as_of | Nothing yet; schedule launch after the start |
| expired_no_new_use | A binding layer ended; the clause allows existing placements to run out | No new placements; existing ones follow the clause |
| expired_takedown_required | A binding layer ended and the clause requires removal | Remove live uses; record removal evidence |
| renewal_pending_unsigned | A renewal was agreed in principle but not executed | Treat as expired until the signed document is linked |
| perpetual_with_conditions | No end date, but other constraints (territory, media) still apply | Uses inside the remaining constraints |
| end_unknown | No document states or lets you derive an end | Route to a rights reviewer; exclude from scoring |
Which approval, rights condition or revision changes the answer over time?
Three kinds of change move an expiry answer, and each needs its own dated record. The first is a revision. A recut that removes a performer can drop the talent layer and extend the usable life of the new version, while the old version stays bound to the old end date. Approvals belong to versions, so the approval_record check fails whenever the approved version and the evaluated version differ.
The second is composition. A campaign page, a video with licensed music or a layout with stock photos inherits the earliest binding end among its parts. Adobe's description of compound assets that reference expired subassets is a reminder that systems may detect this late, on the next scheduled check, so the dataset should compute it rather than copy the DAM flag.
The third is a change to the rights themselves: a signed renewal, an amendment that narrows territory, or a new signal about machine use. IPTC Photo Metadata 2023.1 added a Data Mining property so rights holders can state whether images may be used for AI training, and IPTC notes that regional law may override the value chosen. Treat that field as one more dated layer with its own source, not as a replacement for the license.
Worked example (illustrative): one product video asked about on four dates
This example is illustrative and does not describe a real client, campaign or asset. A 30-second product video, version 2, has three layers: a footage license with a stated 12-month window, a performer term anchored to the first day of filming with a 24-month maximum period of use, and a music license with a 6-month window that requires removal of live uses at expiry. Version 3 replaces the music with a track the company commissioned and owns. The requested use is paid social video in one territory.
The point of the example is the shape of the answers, not the specific durations. The same asset yields four correct and different statuses, each traced to one layer.
| as_of (illustrative) | Version | Binding layer | Expected status | Required action |
|---|---|---|---|---|
| Month 2 after launch | v2 | Music, ends month 6 | active | None |
| Month 5 after launch | v2 | Music, ends month 6 | expiring_in_notice_period | Open renewal or recut task |
| Month 7 after launch | v2 | Music, ended month 6, removal clause | expired_takedown_required | Remove live v2 placements and log removal |
| Month 7 after launch | v3 | Footage, ends month 12 | active | New placements allowed for v3 only |
| Month 13 after launch | v3 | Footage, ended month 12 | expired_no_new_use | Stop new placements; follow clause for live ones |
A record that should fail validation, and the exception it hides
The most common broken record overwrites the approval. In the illustrative case, someone changes version 2's status from Approved to Expired in month 7 and deletes the reviewer's note. The task now fails two checks: approval_record no longer matches the version that ran, and nothing shows that placements in months 1 to 6 were covered. Rebuild it from the review history or drop it.
The exception is a renewal that looks signed but is not. A renewal agreed by email in month 5, with the countersigned copy never filed, should be scored as renewal_pending_unsigned until the executed document is linked. A model trained on records that treat the email as a renewal learns to extend rights on intent alone, which is exactly the behavior a rights desk cannot accept.
Score evaluated systems on exact status, on whether they cite the right binding layer, and separately on boundary-day and time-zone tasks, where errors cluster. Report how many tasks were routed out as end_unknown so readers can see what the score does not cover.
Which expiry records belong with a rights reviewer instead of in the dataset?
Route a record out when the end date depends on facts the archive does not hold. Typical cases are licenses that reference a separate schedule nobody can find, talent terms whose anchor event (first use, first filming day) was never recorded, renewals negotiated by phone, and assets whose embedded elements were never broken out into layers.
A rights reviewer, ideally with the creative operations lead who knows how approvals were really given, should decide whether a gap can be repaired from other records. A missing version number can often be recovered from DAM history; a missing license cannot. Contract interpretation, especially of post-expiry clauses and termination wording, is a question for counsel on the specific documents, not for a schema.
Licensing a rights history is not licensing the media in it
Your team's dated rights decisions and the media they describe usually have different owners. Footage, photos and music often belong to studios, photographers, stock libraries and labels, and an expired license is a reason to keep that media out of any outside use. The decision records your staff created, such as requests, rights layers, approvals, status calls and removal logs, are more often yours, subject to client confidentiality and personal data about performers.
Decision trails like these can go through SourceX's sourcing, rights review, contracting, preparation, delivery and payment as a licensed AI dataset. A creative operations team would begin with a short assessment that requires no uploads, approve the scope and sign before anything is delivered, and in most cases keep third-party media out of that scope or refer to it by id only.
Frequently asked questions
Should an expired asset be deleted from the DAM?
Not as a rule. The license may require removing live uses, but keeping the file and its history lets you prove that past placements were covered and supports renewal. Restrict access to it instead, the way DAM platforms such as Adobe Experience Manager block editing and download of expired assets for non-administrators.
Is a license end date the same as the schema.org expires property?
No. Schema.org defines expires as the date content is no longer useful or available, which is a publisher's statement about relevance or availability. A license end date is a contractual limit on use and needs its own field, document reference and boundary rule.
How should time zones be handled in expiry dates?
Store the zone the contract uses with every window and evaluate the as_of time in that zone. ODRL strongly recommends time zone information on date-time constraints, and DAM interfaces may display the same expiry differently to users in different zones, so a date without a zone is not checkable.
What if a renewal was agreed but not yet signed?
Treat the asset as expired for new uses until the executed renewal is linked to the record. Mark the task renewal_pending_unsigned so that the dataset teaches the difference between intent to renew and an actual grant.
Does an expired license mean the work is in the public domain?
No. Copyright duration runs on its own clock, generally the author's life plus 70 years for works created since 1978 according to the U.S. Copyright Office, so a license can lapse long before the copyright does. After a license ends you usually have fewer rights, not more.
Sources
- Adobe Experience Manager Assets 6.5 documentation describes asset expiration as enforcing license requirements: expired assets are unpublished, non-administrators cannot edit, copy, move, publish or download them, expiry display varies by time zone, and compound assets referencing expired subassets are flagged on the next scheduler run. Source
- Schema.org defines expires as the date content expires and is no longer useful or available, and license as a license document that applies to the content. Source
- The W3C ODRL vocabulary defines a dateTime constraint taking an xsd:date or xsd:dateTime, strongly recommends time zone information, and distinguishes lt/lteq operators; it also defines a delete action with constraints. Source
- The PLUS License Data Format defines optional license start and end dates in ISO 8601 and notes that the end date may be calculated by adding the license duration to the start date. Source
- SAG-AFTRA's summary of the 2025 commercials contracts says the maximum period of use moved from 21 months to 24 months starting 10 business days after the start of on-camera principal photography. Source
- IPTC Photo Metadata Standard 2023.1 added a Data Mining property for rights holders to signal whether images may be used for AI training, noting regional laws may override the value. Source
- The U.S. Copyright Office explains that works created on or after January 1, 1978 are generally protected for the author's life plus 70 years. Source
See if your company qualifies
A short company assessment. No data uploads are needed.