Asset Licence Register / Licence audit checklist

Due diligence

The 10-step asset licence audit

Publisher agreements make you warrant that everything you ship is properly licensed - usually with an indemnity behind it - and acquirers now ask for asset inventories in due diligence. Run this audit before they do.

Why this audit happens to you eventually

Three contract mechanisms turn sloppy asset records into personal pain: warranties (you promise the content is cleanly licensed), indemnities (you pay if the promise breaks), and due-diligence questionnaires (they ask you to prove it before signing, increasingly including AI-content disclosure). The studio that can answer in an afternoon looks fundable; the one that needs three weeks looks like risk.

The checklist

  1. Inventory every third-party asset in the shipping build: models, textures, tools, audio, fonts, stock. The forgotten categories are audio and fonts - start there.
  2. Record the source and licence type for each - not "Unity store" but "Unity Asset Store, Single Entity"; not "Fab" but "Fab Standard, Professional tier".
  3. Match entities. For every Single Entity licence: is the shipping product the purchasing entity's? Client work needs Multi Entity or equivalent.
  4. Count seats. For per-seat tools (Unity Extension Assets and friends): seats purchased vs people using. Fix shortfalls now - it is a cheap upgrade today.
  5. Check attribution debts. CC BY content, OFL fonts with credit requests, stock with credit lines - is every required credit actually in the credits screen, in the required form?
  6. Attach proof of purchase: order IDs, invoices, claim records. An entitlement you cannot evidence is a question you cannot close.
  7. Verify the purchasing accounts. Assets bought on personal accounts are a transfer conversation to have before the deal, not during it.
  8. Flag editorial and restricted content. Editorial-only licences in a commercial build, revenue-capped tiers a grown studio has outrun, stock used beyond its cap.
  9. Note AI-relevant provenance. Steam asks about AI content; publishers and acquirers increasingly ask which assets are AI-generated and under what terms. Record it per asset while you still remember.
  10. Export the manifest. One document, grouped by source: asset, licence, order ref, usage, credits. That IS the due-diligence answer.
The trick is not doing this audit - it is never needing to. Thirty seconds of recording when an asset enters the project beats a forensic weekend three years later, when the artist who bought it has left and the marketplace has changed its terms twice.

Asset Licence Register is this checklist as software: the register enforces steps 1-2 and 6-9 as fields, computes 3-5 as automatic flags, and step 10 is the Export manifest button.

FAQ

Do publishers really check?

The demand usually arrives as contract language (warranties, indemnities) plus an inventory request during due diligence - and platforms add their own provenance questions. When it arrives it has a deadline attached; the audit is much cheaper as maintenance than as a fire drill.

What counts as proof of purchase?

An order ID or invoice from the marketplace, tied to an account your studio controls, plus (for claim-based content like pre-2025 Megascans) the claim record. A screenshot with a visible date and account beats nothing.

How do AI-generated assets fit in?

Track them like any other third-party input: what tool, under what terms, in which parts of the product. Steam requires AI-content disclosure per title, and acquirers increasingly request an AI asset inventory in diligence.

Stop tracking licences in a spreadsheet

Asset Licence Register flags entity and seat traps as you type and exports the due-diligence manifest in one click. Free, local-first, no sign-up.

Open the free tool →

Keep reading