This case belongs to assess procurement approvals and exception workflows, which sets four exception types side by side. This page takes a different supplier substitution and walks it step by step.
What went wrong
Illustrative and fictional. A 520-person manufacturer of industrial pumps buys a fluoroelastomer compound for the shaft seals in its largest pump line. In March, the compound's maker announces it will stop producing that grade in 60 days. The pump maker has open orders for nine weeks of production and no second approved source.
The engineering specification lists ten requirements for the compound. Purchasing finds three alternatives. Lab results show the best one meets nine of the ten: its compression set at the highest rated temperature is slightly outside the limit. Every other property, including chemical resistance, passes.
The choice is uncomfortable: stop the line, or accept a substitute with a known, bounded weakness while a fully compliant source is qualified.
Who decided what, step by step
| Step | Decision | Who decided | Record that captured it | Usual system |
|---|---|---|---|---|
| 1. Notice | Treat the discontinuation as a supply risk | Purchasing manager | Supplier notice and risk entry | Email, supplier portal |
| 2. Search | Request quotes from three alternative sources | Purchasing manager | Requests for quote and three quotes | Source-to-pay suite |
| 3. Test | Test samples against all ten requirements | Quality engineer | Certificates of analysis and lab report | QMS, lab system |
| 4. Exception | Substitute fails one requirement; seek a deviation | Engineering manager | Deviation request with the gap stated | QMS |
| 5. Limits | Approve for 120 days, high-temperature models excluded, extra seal test per lot | Engineering and quality directors | Signed deviation with expiry and conditions | QMS |
| 6. Notice to customers | Inform customers whose contracts require change notice | Sales operations | Change notices and replies | CRM, email |
| 7. Receiving | Accept lots under the deviation number | Receiving and quality inspection | Receipts and inspection results citing the deviation | ERP, QMS |
| 8. Closure | Qualify a compliant source; close the deviation early, at day 95 | Quality director | Closure note and new approved supplier entry | QMS, source-to-pay suite |
Step 5 is the heart of the case. The approval did not say "use the substitute"; it said where, for how long, and under what extra check. Those conditions turn a one-line exception into a decision someone can evaluate.
Why this sequence is useful evidence
Formal acceptance of a known nonconformance is a recognized kind of decision, not an informal shortcut. Government purchasing rules show the same structure: under FAR 46.407, a U.S. contracting officer may accept nonconforming supplies when it serves the Government's interest, such as for economy or urgency, after concurrence from the activity responsible for the technical requirements, with a price reduction or other consideration when the nonconformance is critical or major. A manufacturer's deviation follows a similar pattern: a stated gap, a technical owner's agreement, limits and a record.
For an AI agent, the value lies in the parts a routine purchase never shows:
- The initial problem is specific: one requirement out of ten, at one condition.
- The authorized action is bounded: an expiry date, excluded models and an added test.
- The checked result is measurable: lots inspected under the deviation number, and an early closure once a compliant source passed.
Public descriptions of agent data point the same way. Appen's agentic AI page, checked on October 18, 2026, lists failure-mode taxonomies and golden trajectories among its agent data services, and micro1 announced on 2026-10-09 a commitment to spend $1 billion over 12 months acquiring enterprise operational data. That is a company announcement, not evidence the money has been spent, and neither source says any given company's deviations will be bought. They show the kind of material being described: decisions with their reasons and results.
Why records of real work matter to agents in general is covered in AI agents need work data.
Where the trail usually breaks
The same case can survive or fail on small details. Three are common:
- The deviation number is missing from receiving. If receipts and inspection results do not cite the deviation, nobody can show which lots it covered. This is the single most damaging gap.
- The conditions are in email. The QMS shows "approved" while the expiry date and excluded models sit in an email thread that may not be retained.
- Closure is never recorded. The deviation simply lapses, so the outcome, early closure with a qualified source, is invisible.
Ask the procurement or quality director about each at metadata level: does the deviation number appear on receipts, where are conditions written, and is closure recorded? Never ask to see a deviation, a lab report or a quote.
How to recognize similar cases at a client
The pump maker's case has a shape that appears across manufacturing, distribution and construction supply. Listen for these signals in an ordinary conversation:
| Signal you hear | What it suggests |
|---|---|
| "We had to qualify a second source quickly" | A substitution under time pressure, likely with test data |
| "Quality signed a deviation" or "we ran it under a concession" | A recorded exception with conditions |
| "We added an inspection step for those lots" | Lot-level evidence linked to the decision |
| "Allocation" or "end of life" notices from suppliers | Recurring substitutions over years |
| "The customer had to approve the change" | Customer change notices, with confidentiality terms |
Companies that hear these phrases often run a quality management system and a source-to-pay suite or ERP, and keep deviation logs for years. The manufacturing quality workflows guide and the data type pages for procurement and vendor workflows and quality assurance workflows cover the surrounding records. The sector view is on the manufacturing industry page.
Who decides about licensing: the procurement or quality director knows where the records are; the CEO can authorize a licensing discussion, often with the COO or CFO preparing the case. Supplier quotes and certificates may be covered by supplier confidentiality terms, and customer change notices by customer contracts. What stays unknown until SourceX reviews it: export capability of the QMS and source-to-pay suite, which records are restricted, and whether any buyer wants this record type.
The company also needs 50+ full-time employees at peak (contractors excluded), documented operating history, rights to license and an authorized contact. 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.
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.
If a manufacturer you advise records deviations with conditions and ties them to the lots they covered, register as a partner, check the company against who qualifies and read the terms before introducing the executive who can authorize the discussion.