Schedule: Acceptance criteria
Starting point only. Have counsel align this schedule with the license and the escrow instructions before signing.
Agreement: [name and date of the data license]
Dataset: [name, as described in the data card version and date]
Delivery method: [how files are transferred]
1. Definitions
- Delivery: the files listed in the checksum manifest supplied by the Seller.
- Record: [the unit the price is based on, for example one conversation].
- Direct identifier: [list the identifier classes in scope, for example personal names, email addresses, phone numbers, account numbers, postal addresses].
- Duplicate: [exact match on the full record after whitespace and case are normalized, or other rule].
- Review period: [number] business days from the date the Buyer receives the Delivery and the manifest.
- Cure period: [number] business days from the date the Seller receives a rejection notice.
2. Who runs the checks
- Checks are run by: [Buyer, escrow holder or named reviewer].
- Results are reported in writing to: [names and addresses for notices].
- Tools and versions: [list the validator, scanner and scripts both parties have agreed].
3. Checks
| No. | Check | Criterion | Method | Blocks acceptance |
|---|---|---|---|---|
| 1 | File integrity | Every file matches the manifest | Recompute SHA-256 for each file and compare | Yes |
| 2 | Format | Files are UTF-8 JSONL, one object per line | Parse every line with the agreed validator | Yes |
| 3 | Schema | Every record has the required fields and types in Annex A | Validate against the agreed schema | Yes |
| 4 | Volume | At least [number] Records | Count Records as defined above | [Yes or price adjustment] |
| 5 | Time span | Records dated from [date] to [date], with at least [number] per year | Minimum, maximum and yearly counts of the record date field | [Yes or price adjustment] |
| 6 | Completeness | Empty values in [fields] do not exceed [rate] | Fill rate per required field | [Yes or price adjustment] |
| 7 | Duplicates | Duplicates do not exceed [rate] | Hash normalized records and count repeats | [Yes or price adjustment] |
| 8 | De-identification scan | No structured Direct identifiers | Run the agreed pattern scanner on the full Delivery | Yes |
| 9 | De-identification review | No Direct identifiers in the sample | Manual review of the sample in section 4 | Yes |
| 10 | Secrets | No credentials, keys or tokens | Run the agreed secrets scanner | Yes |
4. Sampling plan
- Sample size: [number] Records.
- Selection: random, using seed [value], so either party can draw the same sample.
- Stratification: [by source system, year and record type, in proportion to volume].
- Pass rule: [no Direct identifiers in the sample].
5. Acceptance and rejection
- The Buyer accepts by written notice once all blocking checks pass.
- The Buyer rejects by written notice within the Review period. The notice names each failed check and attaches the evidence.
- If the Buyer gives neither notice within the Review period, the Delivery is deemed accepted.
- On acceptance or deemed acceptance, release follows the escrow instructions.
6. Cure
- After a rejection notice, the Seller may correct and redeliver within the Cure period, with a new manifest.
- The Review period restarts for the corrected files only.
- The Seller has [number] cure attempts.
- If the Delivery still fails a blocking check after the final attempt, the Buyer may terminate, funds are returned under the escrow instructions, and the Buyer deletes all copies of the Delivery and confirms deletion in writing.
7. Price adjustment
[Where a non-blocking check falls short, state the adjustment. For example: if the Record count is below the criterion in check 4, the fee is reduced in proportion to the shortfall.]
Annex A: Schema
| Field | Type | Required | May be empty |
|---|---|---|---|
| [field] | [type] | [yes or no] | [yes or no] |