Prepare a rights and readiness register
Updated 4 October 2026
The short answer
A simple rights register helps you answer buyer questions without overclaiming.
Use the readiness register
A login proves access to a system. It does not, by itself, establish permission to license everything inside it.
Make a rights and readiness register, one row per proposed collection:
Collection | Rights owner | Authority to approve | Supporting document | Third-party or client material | Prior grants | Identifying or restricted fields | Exclusions | Open question and owner
Use three working labels: confirmed for the proposed scope, needs review, excluded. A blank answer stays needs review. These are internal preparation labels, not a legal certification.
Separate company-owned records from client work, licensed third-party content and code dependencies. Note whether the proposed use matches the permission you hold. For personal or sensitive records, ask who will prepare them, how the preparation is checked and what happens to the raw version.
Troveo's public business-data explanation calls for disclosure of third-party material and prior grants, and preparation before delivery. Do not assume another buyer uses the same process or accepts the same records.
One unresolved collection does not require putting every other collection into the same scope. Define a narrower proposal and have the responsible person check it.
Keep this register inside your company. Do not put contracts, credentials, personal records or sample exports into an assessment or email reply.
Sources and limitations
Programme descriptions can change. The signed agreement controls the price, licensed scope and payment conditions. These worksheets help prepare questions and do not certify rights or promise a deal.
- Troveo business-data terms, checked 3 October 2026
Related guides
Review your relevant buyers
Use confirmed facts and keep restricted records outside your proposed scope.
Start a free assessment