Rights Agreements
Part of Sponsorship rights management
Building a register of contracted sponsorship assets
Turn a sponsorship agreement into a working asset register with agreement references, owners, dates, permissions and delivery evidence.
Build the register from the signed sponsorship agreement, its schedules and authorised amendments. Give each row an agreement reference. Use one row for each asset, restriction or permission needing its own owner, date or check, and keep proposals awaiting agreement separate from a contracted right.
Decide what deserves its own row
A programme credit, venue sign, organiser post, staffed space and permission to use a property mark may share a package name. Record them separately: each can have a different producer, deadline and proof.
For a recurring promise, create a row for each issue, fixture or other occurrence that can be delivered or missed independently.
Show both parties' tasks where they affect delivery. The sponsor may owe artwork by a deadline while the organiser owes a placement. Supplying the file does not complete the organiser's promise.
Use fields that answer working questions
Field / What to enter
- Item ID and source
- Stable identifier, agreement version and clause or schedule reference.
- Entitlement
- Contract wording plus a plain-language task description.
- Scope
- Asset, format, position, property, channel or place as relevant.
- Dates
- Submission, approval and delivery windows, or the permission period.
- Responsibility
- Supplier, approver, delivery party and contact.
- Dependency
- Third-party consent or another condition still to be confirmed.
- Verification
- Evidence suited to this particular item.
- Current state
- A dated status and the next action where needed.
These are suggested fields. Preserve the contractual wording. If it is too broad to schedule, ask the authorised parties to settle its meaning rather than silently narrowing it in the register.
Keep different rights distinct
A placement row describes what the property must publish or provide. A usage-permission row describes what a named party may do with an asset. An exclusivity row describes a restriction on competing activity.
Link related rows, but do not merge them. A delivered event sign does not establish permission for the sponsor to use the event logo in its own advertisement.
A hypothetical festival package could therefore have separate rows for an entrance sign, one organiser post and approved sponsor use of the festival name. Moving the post would not automatically move the other two rights.
Control changes
Keep the signed documents with identifiable versions or dates. Record a requested change as proposed until authorised.
When a right changes, retain its original reference and identify the amendment, revised item and effective date. Make the current instruction easy to identify so an old creative brief is not mistaken for approval.
Before activity starts, filter for unclear dates, missing permissions and rows without a defined check. During delivery, review items due soon.
At close-out, link each row to its evidence and accepted changes; leave unsupported items open. The register then shows what was contracted and what happened, without claiming that anyone noticed the assets.
