Legal reasoning workflows
- Seeking
- Complex legal workflows and attorney work product
- Format
- Documents + structured metadata
- Geography
- US
For Acquisition Partners
SourceX helps you source relevant company records, agree licensing terms and coordinate preparation and delivery through one relationship.
01 / Example data request
Candidate suppliers
02 / How sourcing works
We look for businesses in the supported countries that hold the data you described. Nothing is contracted until a supplier agrees.
We check the data and the supplier's licensing permissions.
Pricing and allowed uses are agreed in a license.
We coordinate delivery and payment.
We handle future purchases and the supplier relationship.
Supported countries: U.S., Canada, EU, UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, UAE, Saudi Arabia.
See what leading AI developers build, browse Acquisition Partners by industry or search licensing terms.
Find guides on task demonstrations, procedures, objects, inspection, maintenance, warehouse, manufacturing and procurement. Browse all
03 / Example demand
Illustrative examples of the kinds of datasets businesses in the U.S., Canada, the EU, the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia hold. These are categories we source, not inventory already under contract.
04 / Rights and use
We coordinate dataset-specific licensing terms, so each dataset arrives with documented rights and a license that defines what you can do with it.
Sourcing starts from your requirements: domain, volume, language, format and timing. Nothing is licensed outside the scope you agree.
Each dataset follows a dataset-specific preparation specification, agreed before delivery.
Where the records came from and the supplier's licensing permissions are documented before a license is signed.
We coordinate dataset-specific licensing terms that set allowed uses, duration and restrictions.
Format, quality checks and delivery method are agreed for each dataset.
Personal details are removed before delivery, and the privacy processing applied is documented for each dataset.
Evaluating this data for procurement?
Diligence packets are prepared per dataset. Rights, privacy processing and quality differ between datasets.
Request dataset diligenceAcquisition Partner guides to sourcing and licensing AI data →
Describe the failure as a business task, then name the context, actions and outcomes that records of that task must contain, and give each one its own field in the request form. A symptom such as the agent mishandles refunds gives the Find step nothing to look for; a task with named systems and outcome labels does.
The request form already has a place for each part. Choosing Workflow datasets opens a workflow specification: business task, workflow type, input or context required, desired action trajectory, required outcome labels and evaluation criteria. Volume, format, geography, language, historical timeframe, licensing and de-identification follow for every request. Datasets are sourced on request rather than held in stock, and sourcing starts from what you write in those fields.
Deciding which failure deserves data, and whether more examples can fix it at all, comes first, and our guide to post-training task selection covers that protocol. The worksheet below picks up where it ends, using an illustrative support agent that grants refunds outside policy.
| Part of the failure write-up | Request form field | Illustrative entry | Why a supplier can act on it |
|---|---|---|---|
| The task the model gets wrong | Business task; workflow type | Decide refund requests against the written refund policy; case resolution | It names work a company does daily and records in its tools |
| What the model saw at the time | Input / context required | Ticket thread, order history and the policy version in force on the ticket date | It lists the records every case must carry |
| What a correct handler did | Desired action trajectory | Check order status, apply the policy rule, then approve, refund in part or escalate | The steps appear in a help desk's case history |
| How each case ended | Required outcome labels | Refund issued, refused or escalated, and whether the customer reopened the case | Outcomes the source system already stores need no new labeling |
| How you will judge fit | Evaluation criteria | Every case links the thread, the decision and the policy clause applied | It can be checked on delivered records, not only on a trained model |
| How much and from where | Volume; historical timeframe; language; source systems | 50,000 or more cases, 2021 to present, English, Zendesk and Shopify | A supplier can confirm it holds enough history before anything is agreed |
| Rights and privacy | Licensing requirements; de-identification requirements | Training and evaluation use; customer names, emails and addresses removed | Permissions and privacy processing can be checked against a stated use |
A success test is a check you can run on the delivered records themselves, such as coverage, linkage and label presence, kept apart from the model result you hope the data will produce. The first can be agreed and checked; the second depends on your own training and evaluation, and no dataset can promise it.
Anthropic's engineering guide to agent evaluations defines a task as a test with defined inputs and success criteria, and says a grader's checks should be clear from the task description so that a result never turns on an ambiguous spec. Hold a data request to the same rule: if two reviewers could read your criterion and disagree about whether a record passes, rewrite it. Format, quality checks and delivery method are agreed for each dataset, so a criterion already in the request gives that agreement a concrete starting point.
The same terms make feedback usable after delivery. This page describes no separate feedback process; the Manage step covers future purchases and the supplier relationship. If a dataset misses the test, or a gap appears once you train, report it against the field or criterion it breaks, for example outcome labels missing for escalated cases in 2022. That turns it into a revised specification for the next request without sharing your model, prompts or evaluation set, and our buyer feedback taxonomy shows how to classify such reports.
Two illustrative requests show the difference between a test and a hope:
Because records can match your specification exactly and still not be licensable for your use, while records with clear permissions can still miss the task; evidence for one says nothing about the other. The Assess step on this page names both checks: the data, and the supplier's licensing permissions.
Public datasets show how far the two can drift apart. The Data Provenance Initiative's 2023 audit of widely used AI training data collections reported frequent miscategorization of licenses on popular dataset hosting sites, with license omission above 70% and error rates above 50%. A clean schema said nothing about permission.
Treat an open item on either track as a no until it is closed, and never let a strong result on one track carry the other. Nothing is contracted until a supplier agrees. On the rights track that means the supplier has accepted the scope and terms and put its signature on the agreement before a single record goes to SourceX; on your side, pricing and allowed uses are agreed in a license. The table below sets the two tracks side by side.
| Point of review | Technical fit | Rights fit |
|---|---|---|
| Question | Do the records hold the task, context and outcomes you specified? | May these records be licensed for the uses you need? |
| Evidence | A sample prepared like the full set, checked against your evaluation criteria | Where the records came from and the supplier's licensing permissions, documented before a license is signed |
| Typical open item | A field, period or outcome label missing from part of the scope | A system, customer contract or record type whose terms are not yet confirmed |
| Ways to close it | Narrow the scope to what the records hold, or look for another source | Document the permission, or leave out the records it does not cover |
| Who decides | You decide whether a narrowed scope still serves the task | The supplier decides what it agrees to license; pricing and allowed uses are agreed in a license |
That it was drawn from the same scope you would license and prepared the same way, with the selection rule, the exclusions and its limits written down. A sample of the best cases shows the best cases, not the dataset.
SourceX's guide to selecting a representative sample says a good sample spans different years, teams and outcomes, failures as well as successes, is prepared exactly like the full set, and is selected by SourceX from data delivered under the supplier's signed agreement. Neither this page nor that guide sets out a statistical sampling protocol, and the candidate suppliers and fit scores in the example request near the top of this page are illustrations, not inventory or validated samples. For a seeded random draw you can run yourself, see our sample representativeness audit.
Representative needs an object. For high-risk AI systems, Article 10(3) of the EU AI Act (Regulation (EU) 2024/1689) requires training, validation and testing data sets to be relevant, sufficiently representative and, to the best extent possible, free of errors and complete in view of the intended purpose. Outside that scope the question still helps: representative of what, for which use. Ask for five items with any sample:
Checklist · 5 items
0 of 5 ticked. Tick each item as you go.
One thing each, with its limits stated. This page commits to six kinds of per-dataset evidence, and diligence packets are prepared per dataset because rights, privacy processing and quality differ between datasets. No sample packet is published here, so ask for the packet for the dataset you are evaluating with the Request dataset diligence button above.
Datasheets for Datasets, a 2018 proposal by Timnit Gebru and coauthors, asks that every dataset come with a document covering its motivation, composition, collection process, preprocessing, uses, distribution and maintenance, written for the people who use a dataset as well as those who build it. Its questions are a quick way to spot what a packet leaves out. The table below maps each commitment on this page to what its document should prove and what it cannot.
| Commitment on this page | What the document should prove | What it does not prove |
|---|---|---|
| You control the scope | Which records, systems and date ranges are included, matched to the scope you agreed | That the records are useful for your task |
| Preparation to specification | The dataset-specific preparation specification and the checks run against it | That the specification was the right one for your model |
| Provenance and rights documentation | Where the records came from and the supplier's licensing permissions, documented before a license is signed | Anything about quality or coverage |
| Permitted uses | The allowed uses, duration and restrictions set in the dataset's licensing terms | That a use not named there is allowed |
| Delivery standards | The agreed format, quality checks and delivery method | That no rows were lost before export; ask for counts against the source system |
| Privacy processing | That personal details were removed, and which processing was applied | That re-identification is impossible; no method rules it out |
Request data
Share the domain, volume, language, format, timing and licensing requirements.