# Identify manufacturing quality workflows for data

Canonical: https://refer.sourcex.si/guides/how-to-identify-manufacturing-quality-workflows
Last updated: 2026-11-05

Identify valuable manufacturing quality workflows from companies in the U.S., Canada, the EU, the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia (outside the U.S., Canada and the EU, at least 70% of the data must be in English) by looking for original documentation like SOPs, QA records, and project histories from established businesses with an authorized sponsor. SourceX seeks material relevant to AI developer programs, not personal data or unowned content.

## Identifying Manufacturing Quality Workflows for Data Licensing

For referral partners, understanding what constitutes valuable data is key to identifying promising leads. Manufacturing quality workflows can leave years of proprietary operating records; whether a current SourceX program wants a company's records is decided in SourceX's review. This guide helps you recognize the characteristics of such data and the companies in the U.S., Canada, the EU, the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia (outside the U.S., Canada and the EU, at least 70% of the data must be in English) likely to possess it.

### What are Manufacturing Quality Workflows?

Manufacturing quality workflows encompass all documented processes, procedures, and records related to ensuring products meet specified standards. This can include:

*   Standard Operating Procedures (SOPs) for quality control.
*   Quality Assurance (QA) records and checklists.
*   Defect analysis reports and remediation processes.
*   Maintenance logs and predictive maintenance protocols.
*   Supply chain quality audits and vendor performance reviews.
*   Project histories detailing product development and quality gates.
*   Employee training materials related to quality standards.

These materials represent a company's internal knowledge and operational history, which, when structured and documented, can be valuable for training AI models to improve efficiency, predict failures, or optimize processes in other manufacturing contexts.

### Key Indicators of a Strong Opportunity

When evaluating a potential referral, look for companies in the U.S., Canada, the EU, the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia that exhibit the following traits regarding their quality workflows:

1.  **Operating Maturity:** SourceX looks for companies with 50 or more full-time employees at peak (contractors excluded) and several years of documented operating history. This suggests a mature, well-documented quality system. Check the general screening profile in [Who Qualifies](/who-qualifies).
2.  **Original Documentation:** The most valuable data consists of proprietary, original documentation the company created itself. This includes its own SOPs, internal knowledge bases, QA records, and project histories. Material that is generic, public, or copied is less likely to be valuable.
3.  **Rights to License:** The company must own the material or have clear rights to license it. This means the data isn't client-specific confidential information, employee personal data, or material that would breach third-party contracts. For instance, quality reports *about* the company's own products are valuable, but reports *for* a client (where the client owns the intellectual property) might not be.
4.  **CEO authorization:** The CEO authorizes a licensing discussion and signs for the company (in an owner-run company the owner is usually the CEO); a quality director or COO can sponsor the idea internally. Without the CEO's yes, even ideal data cannot be engaged. Remember, you do not need to export, upload, or describe confidential records yourself; the company controls what to share.
5.  **Relevance to AI Developer Demand:** While SourceX assesses specific AI developer program relevance during its review, you can initially consider if the company's quality data addresses common industry challenges like defect reduction, process optimization, or predictive maintenance. The [company fit checker](/tools/company-fit-checker) offers a preliminary, non-binding screening.

### What is Generally Not a Fit?

Conversely, certain types of data or company situations are typically *not* suitable for referral:

*   **Scraped or Third-Party Data:** Data not generated or owned by the company, such as publicly scraped information or client-owned material, is usually not eligible.
*   **One-Off Files Without Context:** Companies that only wish to license a single file without comprehensive documentation or contextual information are generally not a fit.
*   **Unapproved Introductions:** Making an introduction without the decision maker's prior knowledge or consent is unproductive and usually does not lead to a successful referral.
*   **Personal Consumer Data:** SourceX does not work with personal consumer data.

By focusing on these characteristics, you can identify manufacturers in eligible countries whose quality records may suit an introduction, increasing your chances of a successful referral and a potential reward. Review the full process in [How It Works](/how-it-works) for more details on the referral stages.

> Rewards on a referred company's first qualifying transaction are calculated as the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. A lead, meeting or signed agreement alone does not trigger payment. See the [program terms](/terms).

## What should a specialist advisor or plant operator know before referring a manufacturer for its deviation records?

A deviation log shows a plant departing from its own instructions and writing down why. That makes it a reason to ask questions, never proof of anything else. Before you refer the manufacturer, find out for each product family who ran the process, who owns the product and whose quality unit signed off, and put the answers on a manufacturer-owner referral brief built from conversation, not files. The CEO decides whether to talk. Rights, fit with a current SourceX program and buyer interest are settled only in SourceX's review.

## A deviation record in plain words

A deviation is a recorded departure from an approved instruction: a batch step done out of order, a mixer run outside its validated speed, a substitute raw material used under a temporary approval. It is not a failed product. Many deviations close with the batch released because the investigation found no effect on quality, and that judgment, with its author, is what the record keeps. Plants usually split planned deviations, approved in advance, from unplanned ones written up afterward.

In drug manufacturing the habit is a legal duty. Under 21 CFR 211.100(b), FDA's good manufacturing practice rule for finished pharmaceuticals, production and process control steps are documented as they are performed, and "Any deviation from the written procedures shall be recorded and justified." A drug plant that has run for ten years holds ten years of written justifications, each tied to a batch.

Two neighbors share the word. A nonconformance concerns product that missed a requirement and has its own [guide to nonconformance history](/guides/workflow-nonconformance-disposition); a clinical trial's protocol deviation is another industry's record, mapped in [protocol deviation records across systems](/guides/protocol-deviation-resolution-records-across-systems).

The record type settles little by itself. SourceX's [dataset page for manufacturing quality records](https://sourcex.si/datasets/manufacturing-quality-records) names inspection results, nonconformance reports, material review dispositions, corrective actions and 8D investigations, but not deviation logs, and SourceX has not published which deviation histories its current programs want.

## Two questions decide whose deviation it is: who ran the process, and who owns the product

Every deviation has a writer and an approver, and in contract manufacturing they can work for different companies. FDA's guidance on quality agreements for contract drug manufacturing says, in substance, that when a product owner uses a contract facility, the owner's quality unit is legally responsible for approving or rejecting what that facility makes, final release included, and that neither party can hand its good manufacturing practice duties to the other through the agreement. So a contract facility's deviation report can carry the product owner's sign-off.

European rules reach the same place from the other side. Chapter 7 of the EU good manufacturing practice guide states at paragraph 7.16: "All records related to the outsourced activities, e.g. manufacturing, analytical and distribution records, and reference samples, should be kept by, or be available to, the Contract Giver." The contract giver is the company that outsourced the work, so one deviation history can sit in two companies' files at once.

Neither text says who may license a copy. That turns on the agreements between the two companies, which counsel reads, and on SourceX's rights review. SourceX's dataset page draws the practical line: a contract manufacturer can license records about parts it makes for customers "Only within what its customer agreements allow", while records about its own processes, equipment and internal defects are usually easier to clear. The same split for drawings is covered in [who owns customer drawings at a contract manufacturer](/questions/who-owns-customer-drawings-contract-manufacturer).

| Position | Who wrote the deviation | Whose approval it carries | What a referral can describe | Left for counsel and SourceX |
|---|---|---|---|---|
| Makes its own products in its own plant | The company's staff | The company's quality unit | The whole history, with personal data flagged | Personal data and supplier documents inside the file |
| Makes products that clients own | The company's staff | Often the client's quality unit too | Its own lines in full; client lines as counts and shares | What each quality or supply agreement allows |
| Owns products that a contractor makes | The contractor's staff | The company's quality unit | Its own reviews and approvals, apart from the contractor's reports | Whether copies of the contractor's reports may be used |
| Took over a product line or plant | Depends on the year | Depends on the year | The years since the takeover | The transfer or purchase agreement's terms on records |

## The manufacturer-owner referral brief

One page, drafted with the head of quality and approved by the CEO before it goes anywhere. It is organized by product family, because ownership can change between families inside one plant, and it never contains a deviation report, a batch record, a screenshot or a login.

**Header.** Legal name, plant locations and the main language of the records; full-time headcount at its peak, contractors left out, with the year; the systems that hold deviations and the earliest year each covers; a rough yearly deviation count as a range, and the share classed as major.

**Ledger, one row per product family.** Who owns the product, which plant ran the process, whose quality unit approves its deviations, which agreement governs copies, and a status:

| Status | When it applies | What the brief says about that family |
|---|---|---|
| Describe | The company owns the product, ran the process and approved its own deviations | Systems, years and rough volume |
| Describe apart | A client owns the product, or a contractor wrote the reports | Counts and shares only, naming the agreement counsel must read |
| Hold | Years before a transfer, an agreement nobody can find, or an open recall, dispute or regulatory matter | That the years exist, and why they are held |
| Leave out | Any part already licensed for AI training | Only that it is excluded |

**Footer.** Earlier use first: among the points a supplier confirms, SourceX's how-it-works page lists that its data "hasn't been licensed for AI training before". Earlier contact next: section 3 of the [terms](/terms) says "A relationship includes any earlier lead, account or email correspondence between SourceX and the company, however it began", so a manufacturer SourceX already knew earns no partner credit. Then the internal sponsor and whether the CEO knows. Rights by family stay blank for SourceX.

## Three manufacturers through the brief (Illustrative)

Illustrative. The companies, years and counts are invented, and no outcome is implied.

| Case | Position | Deviation history | What the brief describes | What it holds back |
|---|---|---|---|---|
| A. Industrial adhesives maker, 240 full-time staff at peak | Makes its own products in its own plant | Electronic quality system since 2015; about 300 to 400 deviations a year | All three product families: Describe | Operator names in narratives and attached supplier certificates, both flagged |
| B. Contract manufacturer of tablets and capsules, 380 at peak | Makes client-owned products, plus one own-label line | Quality system since 2012; clients' quality units approve outcomes on their batches | Own-label line: Describe. Client lines: Describe apart, as shares of batches | Every client line until counsel reads the quality agreements |
| C. Topical products company, 160 at peak | Owned products a contractor made until 2021, then moved production in-house | Contractor-written reports for 2014 to 2021; its own quality system since 2021 | 2021 onward: Describe | 2014 to 2021: Hold, pending the ended supply agreement |

**A, original work.** The adhesives maker writes deviations against its own procedures and approves them itself, which is the original documentation the [who qualifies](/who-qualifies) screen looks for; a typical entry records a planned raw-material substitution, its trial batches and the decision to make it permanent. The log is still not clean: narratives name operators, and attached certificates are the supplier's documents. An owner who asks how such details are handled can read SourceX's [guide to quality assurance data](https://sourcex.si/data/quality-assurance), whose preparation steps include removing inspector and customer identifiers and protecting process trade secrets.

**B, mixed third-party content.** The manufacturer's staff write every deviation, yet on client batches the client's quality unit approves the outcome, and for EU clients the guide quoted above expects records of the outsourced work to be kept by or available to them. If the quality agreements allow nothing, the introduction can still rest on the own-label line, and SourceX judges whether that is enough.

**C, uncertain ownership.** The company owns the products and its own approvals, but another company's staff wrote the 2014 to 2021 reports, and whether the company's copies may be licensed depends on what the ended supply agreement says about records and confidentiality. Nobody contacts the former contractor; that conversation, if it ever happens, belongs to the company and its counsel.

## Finding who owns the product and who wrote the deviation

Four people answer four questions. The head of quality knows the systems, years and approval flows, and which deviations carry a client's signature. Commercial or supply-chain staff know which families are made for others, and under which agreements. Counsel reads those agreements. The CEO decides whether the company discusses licensing and signs for it; a quality director can sponsor the idea but cannot open that discussion. A similar map is drawn in [who can license nonconformance records](/questions/who-can-license-nonconformance-disposition-records).

Origin questions cluster around change: a line moved in from a contractor or out to one, a plant bought from another group. Each change draws a line across the ledger; [contract manufacturer records in an acquisition](/industries/contract-manufacturer-acquisition) covers the purchase case. When the plant belongs to a larger group, the USD 50,000 floor still applies only once, to the referred company's first qualifying transaction, and not again on a repeat, renewal or amendment. No published rule says whether a sister company's past dealings with SourceX, or another partner's earlier introduction of one, alters who receives credit; SourceX settles it while reviewing duplicates.

Fit comes before any of this. Section 1 of the terms sets the size floor at 50 or more full-time employees at peak; the screening page leaves contractors out of that count and asks for years of the company's own records, rights to license them and a CEO who wants the conversation. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English.

## Bounded questions for the head of quality, and what to turn down

Each question takes a system name, a year, a range, a share or a yes or no:

1. Which systems hold deviation records, and from which year does each start?
2. Roughly how many deviations does the plant open in a year, and what share is classed as major?
3. Which product families does the company own, and which does it make for clients?
4. On client batches, whose quality unit approves the outcome of a deviation?
5. Has any product line moved in from, or out to, another manufacturer, and in which year?
6. Has any of this history been licensed for AI training, or tied to a recall, a dispute or a regulatory action?
7. Has the company ever applied to SourceX, held an account with it or exchanged emails with it?

Decline an offered report, a screen share of the log or a quick export: the records stay with the company. Let the head of quality correct the brief and choose how it reaches the CEO; if the CEO wants a conversation, give the company your partner link so it applies itself. Your SourceX Channel Partner Agreement is signed before you submit anything (section 1). Under section 2 the credit goes to a single partner, whoever introduced the company validly before anyone else in the 90-day attribution window, and only once the company's own application is verified. Should a reward follow, SourceX pays it from its own funds and never trims the manufacturer's payout to cover it (section 4). If the head of quality is your only contact, see the [sponsor-or-CEO comparison](/compare/introduce-through-sponsor-or-directly-to-ceo).

## What the brief cannot tell you

- **Estimates age.** Counts and shares are one person's recollection on one date; date every answer.
- **A status is not a clearance.** "Describe" still leaves personal data, supplier documents and client confidentiality for review.
- **Regulated plants carry more rules** than the two cited here. SourceX's dataset page says complaint records that can contain patient information are reviewed separately and left out unless cleared.
- **No mandate feedback is public.** SourceX has not published which deviation histories its programs want, so the brief leaves fit blank.
- **Method.** Built on 2026-10-27 from the sources below. It does not measure how often client ownership or a past transfer narrows what a manufacturer licenses; comparing each ledger's statuses with the scope finally licensed would, and those figures are not yet published.

## Next step

> **Refer a company. No cap on rewards.** Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

When the ledger shows product families the manufacturer owns, made in its own plant and approved by its own quality unit, and its CEO has asked for the conversation, [register as a partner](/register), measure the company against [who qualifies](/who-qualifies) and read the [program terms](/terms) before you submit the introduction. Related: [root cause analysis records](/data-types/root-cause-analysis-records) and the [guides hub](/guides).

## Sources

- https://health.ec.europa.eu/system/files/2016-11/vol4-chap7_2012-06_en_0.pdf
- https://refer.sourcex.si/terms
- https://refer.sourcex.si/who-qualifies
- https://sourcex.si/data/quality-assurance
- https://sourcex.si/datasets/manufacturing-quality-records
- https://sourcex.si/how-it-works
- https://www.ecfr.gov/current/title-21/chapter-I/subchapter-C/part-211/subpart-F/section-211.100
- https://www.fda.gov/media/86193/download
