Buyer decision tool
Rights, consent, handling and hand-offs are usually assumed rather than written down, and the gap only surfaces once material is moving. This checklist produces a provenance schedule for the statement of work, with a named owner against every decision.
Use it: Before collection, onboarding or data transfer begins.
Proof scale
300+ languages 1,000+ brands served since 2015 across AI data, translation, localization, media, and interpretation.When to use this
This is an operational scoping aid, not legal advice. Use it to make permitted use, consent responsibilities and every hand-off visible in the SOW.
What it produces
The checklist
Every question below is on the page as text. Use the link on any row to send a colleague straight to that one question.
| Ask this | A useful answer is specific about | What the answer actually tells you |
|---|---|---|
| What use of the material is actually permitted? # | The intended use, any limits on reuse or derivative material, and who must confirm a use that falls outside the stated purpose. | Whether the planned work fits the permission you have, or needs a separate decision. |
| Who owns each privacy, consent, metadata and quality decision? # | One named side for every activity, written into the SOW rather than left in an assumption. | Whether a sensitive responsibility has a real owner. |
| What contributor information is needed, and why? # | Eligibility, the consent record, the minimum metadata needed, and who may access it. | Whether recruitment can begin without collecting unnecessary or unsupported information. |
| Who may configure or operate the capture setup? # | The permitted operator, device boundary, and any restriction on passive capture or outward-facing equipment. | Whether the collection setup matches the agreed privacy boundary. |
| How does material move from collection to delivery? # | Each sender and receiver, the permitted transfer method, and the record kept at every hand-off. | Whether the chain of custody can be followed without reconstructing it later. |
| What happens when an item fails a handling or consent condition? # | Whether it is stopped, flagged, returned, or escalated, and who can make that decision. | Whether exceptions have a safe route or will be improvised during delivery. |
| What will prove the source and treatment of an item later? # | The provenance record that stays with the item or batch as it moves through the work. | Whether the buyer can explain where the material came from and what happened to it. |
How to fill it in
Work down the first column with the supplier in the room. A row is only answered when the middle column is specific — a yes that is not specific about anything is the thing this tool exists to catch. Write the unresolved rows down; those are the ones worth a call.
What counts as evidence
A named owner, a document you can open, a sample produced under the instructions you will actually use, or a test whose result changes the decision. A capability statement, an organisation-wide headcount, or a claim about a different assignment does not answer these rows.
The document
The PDF needs no sign-in and is free to forward or quote. The working document is there if you would rather copy the checklist into your own process. If either will not open for you, tell us and we will fix it the same day.
Where this fits
The guide explains what to look for; this checklist is what you take into the conversation. Both are published in full.
A procurement framework for ISO evidence, role-based access, secure file handling, AI/MT policy, supplier controls, audit trails, and closeout evidence.
Read the guideStuck on a row?