An always-current IATF 16949 audit dossier

The problem

Weeks go into proving things that already happened correctly.

IATF 16949 audits and PPAP/8D requests require evidence that's manually reconstructed today, risking nonconformities from documentation gaps.

• Before an IATF 16949 audit or an OEM's PPAP or 8D request, someone spends weeks rebuilding traceability for lots that were machined correctly months ago. That work is usually done by the same quality team that should be improving the process.
• The evidence exists, but it is spread across setup sheets, heat certificates, SPC charts, emails and people's memory. Each source has its own owner and its own filing logic.
• Every gap found during that rebuild is a potential documentation nonconformity, even when the part itself was right. Auditors write findings on missing evidence, not only on bad parts.
• And with several OEMs, the same work is repeated for each customer that asks, in each customer's own format, by the same small team. Each OEM also has customer-specific requirements on top of IATF 16949.

How it fits the IRIS system

Edge captures at the moment; Agents files it by standard and period.

Edge captures before/after photos of every critical change linked to the heat certificate and a timestamped decision log; Agents structures the dossier by certification standard and period.

A dossier rebuilt afterwards inherits every gap nobody wrote down. One captured as each changeover happens has nothing to rebuild, and that is the whole difference on audit day: the quality lead reviews instead of searching. It also frees the quality team for improvement work instead of document hunting. The auditor gets a structured download; the plant gets its weeks back.

See the full IRIS architecture →

Before and after

Audit preparation today versus the dossier always ready

Aspect	Today	With iLEAN Edge + Agents
Pre-audit reconstruction	Weeks	Zero
Critical changeover evidence	A signed checklist	Before/after photos, timestamped
Heat certificate link	Searched in binders	Attached to the changeover
Decision log	Emails and memory	Who decided what, and why
PPAP or 8D request	A project	A filtered download
Documentation-gap nonconformity	Found by the auditor	Eliminated

weeks of pre-audit reconstruction → zero. Documentation-gap nonconformity risk → eliminated.

Impact estimate

Impact estimate — to be validated with your audit calendar.

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 audit frequency and the number of PPAP/8D requests per year. The more OEMs audit you, the faster it pays.
• Continuous protection of the IATF 16949 certification, which is the license to keep supplying the OEM. Losing it would mean losing the right to quote new programs.
• Pre-audit reconstruction goes from weeks to zero. The quality team stops preparing audits and starts reviewing them.
• And the documentation-gap nonconformity risk is eliminated at the source, not patched before the auditor arrives. Gaps are flagged when the evidence should have been generated, while they can still be fixed.

continuous protection of IATF 16949 certification, estimated payback 6-12 months depending on audit frequency and PPAP/8D requests. *Estimate to be validated*.

And the fair question from the production manager

“Isn't this just another document management system?” — the direction is reversed: a document system stores what someone uploads afterwards, this one captures as the changeover happens. Filing a timestamped photo against a known clause is an anchored task, where the best models drop below 1.5% error [1], and the quality lead reviews the pack before any auditor sees it, so nothing leaves the plant unchecked.

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