Database rights audit: stages and deadlines
A database rights audit checks who actually owns the extraction and reuse rights in a database before a deal, a licence or a dispute. It maps provenance, tests each source against the collection agreement, and produces a gap list with a sign-off. Most audits run four to six weeks, longer where sources sit in more than one jurisdiction.
When the audit starts
The trigger is usually external: a buyer's due diligence request, a licensing negotiation, or a notice from a party claiming an overlapping right. Internally, the same review runs before a database is pledged, contributed to a joint venture, or used to train a model. Whoever raises the question first sets the clock running. The review does not wait for a formal complaint.
Stages
| Stage | What happens | Typical duration |
|---|---|---|
| Intake | Scope confirmed, source list requested, conflicts checked | 1–3 business days |
| Document collection | Contracts, extraction logs, contributor lists gathered | 1–2 weeks |
| Provenance mapping | Each source traced to its collection basis and any downstream licence | 1–2 weeks |
| Gap testing | Overlaps, missing consents and third-party claims flagged | 3–5 business days |
| Sign-off | Findings report issued, remediation steps agreed | 2–4 business days |
Stages overlap when the file is small and run in sequence when several jurisdictions or subcontractors are involved. A cross-border chain of suppliers changes this clock in a specific way, described in The outsourcing provider subcontracts abroad technology contract the d.
Documents needed to start
- The collection or scraping agreement, or the internal instruction that authorised collection
- Any licence-in or licence-out covering the same data
- Contributor and supplier list, with dates of onboarding
- Records of the investment made in obtaining, verifying or presenting the data
- Correspondence with any party already claiming a competing right
A missing document does not stop the audit. It moves into the gap list and shifts the timeline by the days needed to obtain a substitute or a written confirmation.
Who decides
Inside the audit, the reviewing partner decides what counts as sufficient evidence at each stage and signs off the gap list. Where the other side disputes a finding, the forum is whatever the underlying contract names: negotiation first, then the agreed court or arbitral body. Database rights are not registered anywhere, so the audit file itself becomes the record relied on later.
A comparable evidentiary cut-off, set before rather than after the fact, is described in The deadline that matters in this situation.
Branches
If the database was built entirely in-house with no external contributors, the audit shortens to document collection and gap testing. There is little to trace during provenance mapping.
If several contributors supplied raw data under different agreements, mapping proceeds contributor by contributor, and the timeline extends by roughly a week for each source with unclear terms.
If the other side raises a competing claim mid-audit, the sign-off stage pauses until that claim is withdrawn or formally answered.
Cost factors and timeline
What drives the fee is scope, not the audit label: how many source agreements exist, how many jurisdictions the data touched, whether a deadline is already running, and whether an opposing party is already involved. A single-source, single-jurisdiction file with no dispute costs a fraction of a multi-contributor cross-border one.
We answer within minutes during business hours and confirm the price within one working day of seeing the file.
Limit
This page covers the procedure, not the underlying question of whether a given database qualifies for protection at all. That assessment depends on facts the audit collects but does not itself resolve. It also does not cover valuation of the database for a transaction.
Verified and its transition
Reviewed for current practice. No specific statutory reference is cited on this page: the procedure described is internal and does not rest on a single provision. Where a database sits alongside a pledged asset, the evidencing timeline follows the pattern set out in Asset report before a right is pledged and its.
Where a dispute over the same data reaches a debtor already tracked in another file, the source structure for that file is described in Debtor in Lithuania in detail.
Related publications
A narrower version of the same check, applied one step earlier to a single training data set, is covered in Provenance review of a training data set ownership of.
FAQ
How long does database rights audit take in practice?
Four to six weeks for a single-jurisdiction file with a small number of sources. Multi-contributor or cross-border files run longer, mainly at the document collection and mapping stages.
Which documents are needed to start?
The collection agreement or internal instruction, any licence covering the data, a contributor list, and evidence of the investment made in obtaining or presenting the data.
What happens if the other side does not respond?
The sign-off stage records the outstanding item as unresolved and the file proceeds on the evidence already collected. A non-response does not stop the audit; it limits what the findings report can confirm.