Audit-ready evidence pack

The problem

On inspection day, the plant shows scattered paper.

The waste-management authorization inspection and construction-client audits demand evidence that's rebuilt manually today, risking findings from documentation gaps. The inspector asks for proof, the plant shows scattered papers.

• The inspection under the waste-management authorization asks for proof: what entered, how it was sorted, where every ton went. The answer has to hold for every truck in the period, not just for a sample.
• Construction clients audit too, often with their own checklist, because their own compliance depends on the certificate you issue them. Each audit asks for the same evidence cut a different way.
• Today that proof is rebuilt by hand from intake forms, scale tickets, sorting notes, hopper sign-offs and memory. Someone spends days on it before every visit. Usually the same person who should be running the plant.
• And whatever was never written down shows up as a documentation gap — a finding against the license to operate. The plant may have done everything right and still be unable to prove it.

How it fits the IRIS system

Edge captures each critical change; Agents organizes the dossier by case file.

Edge (captures photo and data per critical change: hopper, sorting, incidents) plus Agents (organizes by case file, generates a structured dossier per inspection period). Zero human post-hoc work.

Every hopper change, sorting incident and batch closes its own case file at the moment it happens. The inspector or the contractor's auditor is handed a structured dossier for the period, not a box of paper — and nobody spends a minute assembling it afterwards. The work that used to take days before a visit simply disappears, because it was done at the moment each event happened.

See the full IRIS architecture →

Before and after

Evidence rebuilt for the visit versus evidence closed in the moment

Aspect	Today	With iLEAN Edge + Agents
Pre-inspection preparation	Days of rebuilding	Zero: the dossier exists
Proof of a hopper changeover	A signature	Before and after images
Sorting incidents	In someone's notebook	In the batch case file
Findings for missing records	A real risk	Gaps detected when they occur
Contractor audit	Another round of assembling	Same evidence, filtered by client
Human post-hoc work	Most of the effort	None

Days of pre-inspection prep rebuilding evidence → zero. Risk of findings from incomplete documentation → eliminated.

Impact estimate

Impact estimate — measured as a protected authorization.

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 inspection frequency and the yearly volume of certificates issued to construction clients.
• Days of pre-inspection preparation go to zero, for the authority and for every contractor that audits.
• The risk of findings from incomplete documentation is eliminated at source, because gaps are detected the day they occur, while the people involved still remember what happened.
• And the waste-management authorization — the license to operate — is protected continuously, not in a rush before each visit. That is the difference between preparing for an inspection and simply receiving it.

Continuous protection of the waste-management authorization (the license to operate), estimated payback 6-12 months depending on inspection frequency and yearly certificate volume. *Estimate to validate*.

And the fair question from the production manager

“Isn't this a document manager with another name?” — a document manager stores what someone uploads afterwards and inherits every gap. Here the evidence is captured at the critical change itself, by the camera or the tablet that was already there, and assigning each photo and record to its case file is an anchored task where the best models drop below 1.5% error [1]. The supervisor still reviews the period's dossier before it goes to the inspector. What changes is that review takes hours, not the days of assembling it took before.

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