The audit stops being a two-week project

The problem

Every audit is a two-week project, and the non-conformities come from the gaps.

A chemical distributor lives on its credentials. The quality management system, the sector's responsible distribution scheme and the specific requirements of large customers are not paperwork: they are the license to sell to them. And the evidence that supports them is scattered. The cleaning on a shift log. The analysis on the lab sheet. The certificate in an email. The signature in a filing cabinet. None of it grouped by batch or by period. That is why every audit is a project: someone spends a week or two gathering what exists, and the non-conformities come out precisely from the gaps left uncovered. A non-conformity gets raised not because the process was bad, but because it could not be demonstrated.

• A chemical distributor lives on its credentials: the quality management system, the sector's Responsible Distribution program, the food-grade or high-purity requirements of large customers. They are not paperwork; they are the license to sell to them.
• The evidence that supports them is scattered: the cleaning on a shift log, the analysis on the lab sheet, the COA in an email, the signature in a filing cabinet. None of it is grouped by batch or by period.
• So someone spends a week or two before every audit gathering what exists. At two or three audits a year, that is a month of the quality team on reconstruction.
• And the non-conformities are raised precisely from the gaps: not because the process was bad, but because it could not be demonstrated.

How it fits the IRIS system

Edge and Connect capture at the moment of the event; Agents organizes by standard.

Edge + Agents.

Every product changeover, batch release and shipment leaves its evidence closed the instant it happens: photos of the critical points, measurements, decisions, signatures. Agents does not create evidence after the fact; it indexes what already exists against whichever scheme is asking, and it finds the missing photo while there is still time to take it. The quality team stops being archivists for two weeks a year and goes back to being quality.

• Every product changeover, batch release and shipment automatically generates its evidence: photos of the critical points, measurements, decisions and signatures.
• Agents groups that evidence by batch, by period and by certifying standard.
• It finds the gaps before the auditor does: it flags that a changeover has no photo of a critical point while there is still time to resolve it.
• It publishes the downloadable pack for the period, accessible to the auditor from the web with no plant involvement.

See the full IRIS architecture →

Before and after

Today's audit preparation versus the permanent pack

Aspect	Today	With iLEAN Agents
Preparation per audit	1-2 weeks of the quality team	Hours of review
Changeover evidence	A signed checklist on a shift log	Photos of every critical point, by batch
Batch release evidence	The lab sheet and an email	COA, validation and signature, linked
Gap in the evidence	Found by the auditor	Flagged the day it occurs
Same evidence, another scheme	Reconstructed again	Re-indexed
The auditor's access	A conference room and a filing cabinet	A web view scoped to the period

from 1-2 weeks of reconstruction per audit to zero · from documentary gaps discovered by the auditor to gaps found and closed in the moment · from evidence spread across four systems to one pack per period.

Impact estimate

Impact estimate — to be validated with your numbers.

The block below is an estimate to be validated against your plant's actual data. We put it forward so the committee has an order of magnitude; we refine it during the assessment.

• Estimated payback 6-12 months, depending on audits per year.
• One to two weeks of quality staff released per audit, multiplied by the quality system, the sector program and every large customer with audit rights, which at a distributor with several large accounts adds up to more than a month a year.
• Continuous protection of the credentials that enable sales to large customers, because a gap is closed the day it appears, not discovered on the auditor's day.
• And a customer audit stops being a risk to the account and becomes a link sent the week before.

continuous protection of the credentials that enable sales to large customers, and one to two weeks of quality staff released per audit. Estimated payback of 6 to 12 months depending on audits per year. *Estimate to validate.*

And the fair question from the production manager

“Isn't this just another document manager?” — the difference is direction. A document manager stores what somebody decides to upload, after the fact, and inherits the same gaps. Here the evidence is generated by the event itself, and mapping it to a clause of a standard or a customer requirement is an anchored task, where the best models drop below 1.5% error [1], with the quality manager reviewing the pack before it is published to the auditor.

^[1] OpenAI paper "Why Language Models Hallucinate", 2025 — on the reliability of AI in anchored tasks.