The IATF audit and the customer audit, always ready

When the audit arrives, somebody spends days reconstructing evidence: first parts, lab records, color changeovers, batch-to-part-to-sequence traceability. Every gap is a potential non-conformity. With iLEAN, evidence is generated at source — photo, parameters, signature — and Agents organizes it by standard and period. The dossier is downloaded.

‹ See all 12 paint & assembly cases

Quality manager in an automotive paintshop downloading the IATF audit dossier generated by iLEAN Agents from the evidence captured at source by Edge and Connect
The problem

The evidence exists. The problem is that it is spread across paper, spreadsheets and systems that do not talk to each other.

No approved plant reaches an audit without evidence: the evidence is there. What is not there is it being together. And gathering it is manual work repeated every time, with the same uncomfortable result:

  • Days of preparation that produce nothing — the quality team stops doing quality to do archaeology: hunting for first parts, cross-referencing lab records, tracking down who signed which color changeover and when.
  • There is always some gap — not because the process failed, but because the record of that process lived on a paper filed badly or in a spreadsheet that got overwritten. And a documentary gap is a potential non-conformity even when the process was correct.
  • Cross-cutting traceability is the most expensive to reconstruct — linking a basecoat lot to the parts that came from it and to the sequence in which they were delivered means cross-referencing three systems by hand, and doing it backwards always costs more than having recorded it forwards.

And what is at stake is not a spreadsheet: it is approved supplier status, the asset the contract rests on.

How it fits the IRIS system

Evidence at source with Edge and Connect, a structured dossier with Agents.

The way to make audit preparation cost nothing is not to prepare it: to have every critical event generate its evidence at the moment it happens, with its photo, its parameters and its signature. That is what the IRIS layers already present in the other cases do; Agents only has to order it.

Edge captures the evidence of the critical events — 100% inspection and color changeover validation. Connect contributes the documentary and lab evidence. Agents structures it by certifying standard and period, and generates the downloadable dossier.

How the evidence pack is composed:

  • Edge — process evidence — every inspected part and every validated color changeover leaves its record with photo, classification, timestamp and owner. It is not a later report: it is the event itself.
  • Connect — documentary and lab evidence — startup sheets, delivery notes and receiving lots, viscosity, film thickness and delta E measurements enter already structured and tied to their corresponding batch.
  • Agents — organization by standard — the same evidence is presented according to what each framework asks for: IATF 16949, customer-specific requirements or the per-reference file. The data is not duplicated, the view is reordered.
  • Downloadable dossier by period — you choose the range and the standard and the pack is generated. What used to be days of work becomes a query.
  • Feeds PPAP with no extra work — the part approval file draws on already structured evidence instead of demanding a specific collection exercise every time a reference is approved.

See the full IRIS architecture →

Before and after

Audit prepared by hand vs. evidence pack generated at source

AspectManual reconstructionWith iLEAN Edge + Connect + Agents
Days of pre-audit preparation3-5 days of quality timeZero: it is downloaded
Source of the evidencePaper, spreadsheets and loose systemsThe event itself, in the moment
Documentary gapsThere is always at least oneEliminated: if the event happened, it is there
Batch ↔ part ↔ sequence traceabilityCross-referenced by hand, backwardsRecorded forwards
Adapting to each standardThe dossier is redoneSame evidence, different view
PPAP per referenceA specific collection exerciseFed with already structured evidence
Impact estimate

Impact estimate for your plant — to be validated with your own 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.

  • Tier 1 paint and assembly plant approved under IATF 16949, with additional customer audits and several days of preparation for each one.
  • Deployment resting on the Edge and Connect cases already running: they generate the evidence, Agents structures it by standard and period. First value expected within a few weeks of events being recorded.
  • Indicative payback of 6 to 12 months, depending on audit frequency and the number of people involved in preparing them today. Estimate to be validated.
  • What this case really protects is not time: it is the contract. Approved supplier status is the asset the customer relationship rests on, and documentary non-conformities are the most absurd way to put it at risk.
  • A side effect people appreciate: when evidence is always available, audits stop being an exceptional event that disrupts the plant for a week.

And the fair question from the quality manager

"Will an auditor accept a dossier assembled by AI?" — the auditor does not accept the dossier, they accept the evidence: the photo, the parameter, the signature and the date, which are the same ones that used to be scattered. Agents generates no new content: it orders existing evidence against a known standard, which is an anchored task — where the best models brought the error below 1.5% [1] — and every item in the pack is traceable back to its source. Nothing is presented without quality reviewing it.

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

Frequently asked questions

What people ask about the audit evidence pack

Does this work for IATF 16949 and also for customer audits?

Yes, and that is precisely why evidence is kept separate from its presentation. The evidence — the first part photo, the lab measurement, the color changeover signature, the batch traceability — is the same regardless of who asks for it. What changes is how it has to be ordered and what counts as sufficient proof in each framework. Agents keeps one source of evidence and several views: IATF 16949, customer-specific requirements or the per-reference file. Nothing is duplicated or redone, it is reordered.

Does the AI write the dossier? What if it makes something up?

It does not write evidence: it organizes it. Every element of the pack is a record that already existed — an image captured by Edge, a measurement poured in by Connect, a signature with its date and owner — and is traceable back to its source. That is the key point against the hallucination concern: there is no free generation of content, there is classification and ordering of existing documents against a known index. And before the dossier leaves the plant, quality reviews it, exactly as they would review one prepared by hand.

How much evidence has to accumulate before it is useful?

It depends on the period the audit covers, but the pack starts having value from the first month of recorded events. What matters is understanding that this case does not work alone: it rests on Edge and Connect already capturing evidence at source. That is why in the deployment sequence it usually comes after the inspection, color changeover, startup sheet and lab cases: once those are running, the evidence pack is practically a consequence. Before that, there is nothing structured to order.

What happens to evidence from before the deployment?

It stays where it is and is still provided the way it always was. The evidence pack does not rewrite the past and does not attempt to migrate years of paper: it covers from the moment events start being recorded at source. In practice that means the two approaches coexist during the first audit — manual reconstruction for the earlier period and the downloadable pack for the new one — and from the next audit on the first is no longer needed. If bringing in history is of interest, Connect can digitize batches of old documents, but that is a separate project sized by volume.

How is batch ↔ part ↔ sequence traceability closed?

By recording it forwards instead of reconstructing it backwards. The basecoat lot enters the system at receiving with its number and its expiry; the startup sheet and the lab measurements tie it to the process conditions; the Edge inspection associates every part with its rack and that lot; and sequence labeling connects the rack with the position delivered to the customer. Each link is placed by a different case in the matrix, and the evidence pack simply walks the chain. That is why answering "which lot did this part come from and in which shipment did it go?" moves from being an investigation to being a query.

Let's talk

When is your next audit? Arrive with the dossier already done.

We work on your plant's real data, not ours. We review what evidence you generate today and what would be missing to download the pack. Assessment with no commitment.

See how we apply it in your plant — review of your next audit ‹ See all 12 paint & assembly cases See automotive