The audit file builds itself

The problem

The nonconformity is almost never for doing it badly.

Ahead of each one, somebody stops operating to reconstruct records out of folders, spreadsheets and memory. And the non-conformity is almost never about having done it wrong: it is about not being able to prove it. The evidence exists, but scattered and in formats that do not cross-reference.

• The health authority looks at hygiene practices, water and labeling. The voluntary food safety standard looks at system and traceability.
• The licensor of a franchised brand looks at whether their product was made exactly to their specification. And the retail customer runs their own, with their own criteria.
• Before each one, somebody stops operating to rebuild files from folders, spreadsheets and memory.
• The nonconformity is almost never for doing it badly: it is for not being able to prove it. The evidence exists, but scattered and in formats that do not cross-reference.

How it fits the IRIS system

Edge and Connect capture; Agents reorganizes by standard.

Every changeover and every batch generates its record as it happens. With Edge and Agents, evidence is built at the moment of the event, not afterwards: before and after photographs of each critical changeover point, the lab parameter series, the washer parameters, the decision log and who signed what and when. None of it asks anyone for extra work. Agents reorganises it by certifying standard. The same evidence serves different audits, but each audit wants it ordered its own way. Agents correlates and generates the dossier by standard and by period, with the index each auditor expects to find. The auditor logs in and downloads the whole period.

Evidence is built when the event happens, not afterwards. That change of timing is what makes the file complete: anything rebuilt after the fact inherits the gaps of whatever nobody wrote down.

See the full IRIS architecture →

Before and after

Today's preparation versus the permanent file

Aspect	Today	With iLEAN Agents
Preparation per audit	Weeks, and stopping operations	Zero
For each additional auditor	The whole job repeats	Same evidence, another view
When it is captured	Rebuilt afterwards	At the moment of the event
Hygiene records and releases	Cross-referenced by hand	Cross-referenced and tied to the batch
The licensor's specification	Justified by searching	Demonstrated from the file
How the auditor accesses it	Somebody prepares folders	They enter, filter and download

Impact estimate

Estimated impact — to validate 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.

• Estimated payback 6-12 months, depending on how many audits you receive a year.
• Quality and production time currently consumed preparing audits several times a year.
• Continuous protection of the certifications and of the relationship with the licensor.
• And the documentation gap stops being discovered on the auditor's day.

The return has two parts: the quality and production time consumed today preparing audits several times a year, and the continuous protection of certifications and of the licensor relationship, whose value is that of the entire franchised portfolio. Estimated payback between six and twelve months depending on audits per year. Estimate to be validated.

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 on its own the instant it happens — before and after photos with time stamps, parameters, signatures — and Agents reorganizes it for whichever standard asks.

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