One-time or ongoing data licensing

Describe the delivery

A one-time data delivery has a defined cutoff: particular systems, files and dates. An ongoing supply adds records over time. Write down the archive cutoff date or update schedule before comparing payments. A proposal for last year's archive cannot be compared directly with a proposal that also requires next year's records.

List the work behind an update. Someone may need to export files, remove excluded records, check permissions and answer questions about missing periods. Ask who does that work and who pays if a delivery needs repair.

Keep three clocks separate

Repeated payment does not always mean repeated delivery. SuperAnnotate describes payment on delivery and each relicense. Turing's program describes revenue share from licensing a company record. Ask whether a proposed recurring payment comes from new work, renewed access or another license of the same material.

Price the obligations you can describe

Build two versions of the scope: a dated archive and that archive with specified updates. For each version, ask for payment triggers, acceptance checks and any minimum commitment. Leave future sales blank until you have a reasoned scenario; an invitation to earn recurring revenue is not a promised payment stream.

If new recordings are part of the deal, check the physical-work capture guide. Sieve's published program distinguishes that work from licensing an existing library.

Write the exit questions before signing

Ask how to stop future deliveries, what notice is required and what happens to already delivered data. Request separate answers for raw records, derived tasks, model use and downstream licenses. Do not assume ending a supply arrangement cancels rights already granted.

Use exclusivity and sublicensing to prepare those questions, then enter the competing scopes in the offer worksheet. Keep the written answer and its date with each proposal so a later revision does not silently change the comparison.