Keeping a Rights Log for Every Asset

A rights log is one of the easiest ways to protect your work. It gives your team a clear, searchable record of what each file can be used for—and what it cannot.

What to record

• Asset name and source URL
• Who owns the content
• Permission basis (license, contract, direct written approval)
• Attribution requirements
• Restrictions (commercial use, region, expiration date)
• Date imported into your project

How to store it

Start simple: a text file in each project folder or a shared spreadsheet for teams. The key is consistency. Every new asset gets a row or note before it enters your timeline.

When to review

Review your log before publishing, before client handoff, and before repurposing older content in new campaigns. Rights can change over time, so a quick review prevents accidental misuse.

Not legal advice. If rights are unclear, pause publication and request written confirmation.