Content licensing rights inventory: know what can actually be offered

Inventory the asset, not just the article title

A licensable package may contain text, photographs, charts, illustrations, data, audio, video, embeds, trademarks, quotations, and contributor work with different permissions. One “owned” label at the article level can hide a photo licensed only for the publisher's site or a freelancer contract that does not cover sublicensing. Create one row per meaningful component and link the evidence supporting its status.

In the United States, the Copyright Office describes the owner's exclusive rights as including reproduction, derivative works, distribution, public performance, public display, and authorization of those acts. That is a useful checklist of possible scope, not a determination that a publisher owns every right in an asset. Start from contracts and provenance, and obtain qualified advice for the relevant jurisdiction and transaction.

• Record creator, creation date if known, source, ownership or permission basis, and evidence location.
• Separate media, territory, language, term, exclusivity, modification, and sublicensing.
• Mark privacy, publicity, confidentiality, embargo, and attribution constraints for review.

Use a rights state that can block the offer

Use operational states such as cleared for proposed scope, restricted, replacement required, permission requested, or unresolved. “Published before” is not a rights state. “Available online” is not permission. A link to a creator's page is provenance evidence, not necessarily a license. The inventory should be able to stop an asset from entering the delivery bundle.

Creative Commons advises that a person applying a CC license should own or control the copyright and that CC licenses are not revocable. If a publisher uses such a license, record the exact license, version, source URL, attribution elements, and any indicated modifications. Do not relabel third-party material under the publisher's license merely because it appears inside a larger page.

Work from the proposed bundle backward

The following example is hypothetical. A publisher considers licensing a twelve-article briefing archive to an institutional buyer. Eight articles contain only staff text and house graphics with linked ownership evidence. Two include contributor work whose agreements cover publication but do not clearly address the proposed reuse. Two use third-party photographs whose permissions do not include sublicensing.

The initial cleared bundle is eight, not twelve. The publisher can seek additional permissions, replace components, narrow the license to a text-only version, or offer only the eight cleared articles. It should not promise twelve and hope to cure the gap after signature. Any replacement creates a new version that needs its own manifest and quality review.

Attach the inventory to delivery and renewal

Turn cleared rows into a delivery manifest with stable asset IDs, file versions, permitted formats, required attribution, delivery date, and license end date. Store the buyer's accepted scope beside the manifest. If an asset is corrected, withdrawn, or replaced, record what changed and whether the buyer needs notice under the agreement.

Review expiring terms and proposed renewals against the same inventory. Exclusivity can conflict with another offer even when ownership is clear. A new translation, model-training use, print edition, or buyer sublicense is a new scope question, not an automatic extension. The inventory earns its keep by making “we have content” into a precise answer about what the publisher can presently deliver, under which evidence, and which questions remain unresolved.