This guide is for specialists who sit close to a plant's deviation log without owning it: food safety and quality system consultants, preventive controls trainers, contract manufacturing operators and quality engineers who now advise. You know which exceptions get a real investigation and which get closed with a one-word note; the open question before a referral is whose permission each part of that history needs.
What a QA exception record is, in the words a plant uses
An exception is any moment when a product, a process or a check missed its standard: an out-of-specification test result, a failed line inspection, a positive environmental swab, a process step run outside its validated limits, a customer complaint that turns into an investigation. Each one leaves a small file behind. It usually opens with the trigger and a hold on the affected product, continues with the investigation and root cause, records what happened to the product (released, reworked, downgraded or destroyed), and closes with a corrective action and a check that it worked.
Regulation is one reason these files share such a consistent shape. In U.S. food plants covered by FDA's preventive controls rule, 21 CFR 117.150 requires corrective action procedures for when a preventive control is not properly implemented or turns out to be ineffective, and states that "All corrective actions (and, when appropriate, corrections) taken in accordance with this section must be documented in records." Quality systems in other sectors build the same habit by other routes. The result is a history in which every exception has a start, a reason and an outcome, the shape the QA workflow overview describes, and SourceX's screening page lists QA records among the original documentation it looks for.
The file type never settles rights, fit or demand
Knowing that a company keeps disciplined exception files tells you one thing: the records probably exist. It does not tell you who may license them, whether they are complete enough to be useful, or whether any current SourceX program wants them. Those are three separate questions, and only the first can be explored before an introduction, at metadata level and with the company's own people. Completeness and demand are judged in SourceX's review. A specialist who keeps the three apart avoids the most common slip in this field: calling a client's deviation log "valuable data" before anyone has asked whose it is.
The QA-history permission checklist
Ten checks, in the order an exception file is built. Each answer puts that part of the file into one of five states:
- Company decides. Its own people wrote it, about its own product, in its own system.
- Contract first. The company decides, but only after counsel reads a customer, supplier or manufacturing agreement.
- Someone else's content. Written or supplied by a customer, supplier, laboratory or outside consultant; listed separately for SourceX's rights review.
- Originals stay intact. A retention rule governs where and how long the originals are kept, and no conversation moves or alters them.
- Stop. A recall, a dispute or an earlier AI-training license puts that part, or the whole conversation, on hold or out.
| # | Stage of the file | Check | Answer that keeps it with the company | Answer that changes its state |
|---|---|---|---|---|
| 1 | Trigger | Did the company's own test, inspection or monitoring raise the exception? | Yes: company decides | A customer complaint or a customer's incoming inspection: that report is someone else's content |
| 2 | Specification | Was the missed requirement the company's own specification or recipe? | Yes: company decides | A customer's specification or drawing: contract first |
| 3 | Hold and release | Did company staff make and record the release decision? | Yes: company decides | A customer approved release of off-spec product: that approval is someone else's content |
| 4 | Investigation | Did the company's own quality team write the root-cause analysis? | Yes: company decides | An outside lab, consultant or former parent wrote it: someone else's content until counsel reads the engagement terms |
| 5 | Supplier link | Does the exception trace to a supplier's material? | No supplier involved | A supplier's corrective action response is attached: someone else's content |
| 6 | Corrective action | Did company staff define the fix and verify that it worked? | Yes: company decides | The fix answers a customer's audit finding: contract first |
| 7 | People | Do names, signatures or worker health details appear? | Business details only | Health or disciplinary detail: flagged for preparation, possibly excluded |
| 8 | Retention | Is the file inside a retention period set by regulation or contract? | Either answer: originals stay intact | Never suggest moving, trimming or deleting originals |
| 9 | Events | Is the exception tied to a recall, a regulatory action or a legal claim? | No | Yes: stop until counsel clears it |
| 10 | Earlier use | Has any of this been licensed for AI training before? | Never | Yes: stop; that material is out |
Check 8 earns a paragraph of its own, because specialists in regulated plants know these rules well. For food plants under the preventive controls rule, 21 CFR 117.315 requires the records it covers to be kept at the plant for at least two years after they were prepared, lets most of them sit offsite if they can be produced onsite within 24 hours, and counts electronic records reachable from the site as onsite. A rule like that tells the company how to keep its originals. It does not by itself decide whether copies may be licensed, and nothing in a referral conversation should touch the retained set.
Check 10 is not a review item. SourceX's suppliers confirm their data has not been licensed for AI training before, so earlier AI-training use takes that material out of any discussion.
A file whose investigation and corrective action (checks 4 and 6) come back as "company decides" carries the part most worth describing. Someone else's content does not end the conversation; it gets listed for the rights review. A single "stop" pauses everything until it clears.
Three exception histories through the checklist (Illustrative)
Illustrative. The three companies below are generic and their facts invented; nothing here implies an outcome.
| Check | A. Own-brand snack maker | B. Private-label co-packer | C. Former joint-venture plant |
|---|---|---|---|
| Own spec | Yes | No, retailers' specifications | Yes |
| Staff-written investigation | Yes | Yes | Partly, by the former partner's lab |
| No customer approvals inside | Yes | No, retailers approve off-spec releases | Yes |
| No supplier replies inside | No, ingredient suppliers' responses attached | No, packaging suppliers' responses attached | Yes |
| Originals stay put | Yes | Yes | Yes |
| Company-run system | Yes | Yes | Not for 2014 to 2022 |
| Next move | Introduce; list supplier replies apart | Contracts first: counsel reads the agreements | Hold the joint-venture years |
A. Original work. A 260-person snack maker sells its own brands from one plant. Its quality team has logged exceptions in a quality management system since 2016, roughly 1,400 a year by the quality manager's estimate, each with a hold decision, an investigation, a corrective action and a verification date. The specifications are its own. Some exceptions trace to ingredient lots, and the suppliers' corrective action responses are attached; those are described as a separate layer. The quality manager can explain the system, and the CEO, who wants a conversation, is the person introduced.
B. Mixed third-party content. A 180-person co-packer makes private-label products to retailers' specifications. Most of its exceptions are measured against those specifications, releasing off-spec product needs the retailer's written approval, and that approval sits in the same file, next to packaging suppliers' responses. Retailer audit findings drive many of its corrective actions. The co-manufacturing agreements decide what, if anything, of this history the company may license, so counsel reads them before any introduction. Its own sanitation and equipment deviations, written against its own procedures, may be the clearer part, and exploring that is the CEO's call.
C. An uncertain ownership case. A 140-person ingredient processor ran from 2014 to 2022 as a joint venture between two companies, until one partner bought out the other. During the joint-venture years the former partner's central laboratory ran testing and wrote investigations in a laboratory system it administered. Since 2022 the plant has kept its own records in its own system. The pre-2022 history waits until counsel reads the buyout agreement's records clause. The post-2022 history passes the checklist cleanly, and the CEO decides whether a conversation about that part is worth having now.
Tracing the owner and the origin of a QA history
Four people answer four different questions. The quality manager knows the systems, the years, who writes each part of a file and where customer and supplier documents sit. The food safety or regulatory lead knows which retention rules and customer audit obligations apply. Counsel reads the agreements behind checks 2, 3, 4 and 6. The CEO decides whether the company discusses licensing at all and signs for it; neither a quality manager's enthusiasm nor administrator rights to the quality system amounts to that decision.
Origin questions concentrate on the periods when someone else ran quality: a contract laboratory that wrote investigations, a former parent whose system the plant used, a consultant who drafted root-cause reports, a joint venture. Each of those periods is its own ownership question. The clean way to handle one is to name it, set it aside and let the clear years go forward.
The company has to fit the program before any of this matters. SourceX looks for at least 50 full-time employees at the company's peak, with contractors left out of the count, a documented operating history, rights to license what it holds 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.
Questions to bring, and the files you never ask for
A first conversation, through the quality manager or directly with the CEO, can stay inside six questions that need no document:
- Which system holds exception records, and from which year?
- Roughly how many exceptions does the company open in a year, and how many reach a full investigation?
- Whose specifications are most exceptions measured against: the company's own or customers'?
- Who writes the investigations: company staff, a contract laboratory, a consultant or a former parent?
- Are customer approvals, audit findings or supplier responses stored inside the same files?
- Has anything in this history been part of a recall, a regulatory action, a claim or an earlier AI-training license?
If someone offers a sample investigation "so you can see the quality", decline it. You never hold the client's records, and SourceX's screening page says an introduction the CEO has not been told about usually does not fit, so the CEO hears about the conversation before anyone describes the files in detail.
If you drafted any of those investigations yourself, say so early; your engagement terms decide who owns that work, and the company, not you, describes its records. The metadata-only opportunity map shows how to keep notes at that level, and who can license nonconformance records traces the sign-off path inside a discrete manufacturer.
Where the checklist falls short
- Answers are statements, not proof. Each one is what someone said on a date. SourceX's rights review and the company's counsel test them.
- Agreements differ. Co-manufacturing, supply and laboratory agreements vary widely; the checklist finds them and leaves the reading to counsel.
- Regulated sectors carry more rules. Food, pharmaceutical and device plants live under record rules beyond the two cited here, and the plant's regulatory lead knows which apply.
- Fit is not demand. A file that passes every check can still fall outside what SourceX's current programs need.
- No outcome figures exist yet. SourceX has not published how often QA exception histories lead to introductions or licenses. A specialist who wants a baseline can log each checklist run, its date, the states it produced and whether the CEO agreed to talk; 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 checklist shows an exception history whose investigations and fixes are the company's own work, and a CEO who wants to talk, register for a partner link, compare the company with who qualifies and read the program terms, including the Channel Partner Agreement you sign before submitting anything. Engineering firms have a parallel record in QA/QC peer review markups, a single case is traced step by step in a nonconformance disposition example, and more specialist guides sit in the guides hub.