REACH SCIP — the Candidate List changes twice a year, your SCIP cannot lag behind it.

The problem

“The Candidate List has just added three substances and I don't know which SKU they are in.”

REACH is a system that works, but the daily job of keeping SCIP up to date is where almost every industrial manufacturer breaks. The regulatory manager knows the mechanics:

1. ECHA updates the SVHC Candidate List twice a year (typically January and June). Every update adds substances.
2. You have to check whether those substances are present in any of your articles — and the answer lives in the SDS and technical datasheets the supplier sent months ago.
3. If an SVHC is present at a concentration >0.1 % by weight per article, you must notify SCIP, and also inform the B2B customer under article 33 of REACH.
4. The deadline for SCIP runs from the moment the article is placed on the market, not “whenever you have time”.

The problem is not the logic — it is that the real composition lives scattered: SDS as PDF per component, the supplier datasheet in the quality folder, the BOM in the PLM with generic material, shop-floor additives that the quality technician writes down in a notebook. When the Candidate List adds a substance, re-reading two hundred SDS by hand is not viable, and SCIP is left with articles that were never notified.

How it fits the IRIS system

iLEAN does not replace the regulatory function — it re-reads the SDS for you when ECHA updates the list.

SCIP does not fail for lack of tools — the IUCLID/ECHA portal does its part. It fails because the real composition of each article and the updated Candidate List never meet in time. iLEAN acts as the filler that keeps that cross-check alive, without the regulatory manager having to re-read two hundred SDS every six months.

Tracer anchors the exact composition to the SKU. Connect captures SDS and certificates through whatever channel they arrive. The agent re-reads and cross-references with the Candidate List when ECHA updates. The person signs.

The three iLEAN pieces applied to REACH SCIP:

• Tracer — anchors to each SKU its real composition: additives, coatings, engineering plastics, alloys, inks. The concentration per substance is recorded with its source (SDS, certificate, supplier declaration) and the date — so you know which source backs which declaration.
• Connect — captures the SDS and technical datasheets through whatever channel they arrive: supplier email with a PDF, chemical distributor portal, scanned certificate, a call with the technical manager. Every document is anchored to the corresponding article and stays searchable.
• Agent — keeps the ECHA Candidate List live with its CAS and EC numbers. When ECHA publishes the twice-yearly update, the agent automatically re-reads the archived SDS and the PDF certificates to detect whether the new SVHC was already present — and therefore whether there are overdue SCIP notifications. It prepares the notification in IUCLID format, and the customer communication under article 33. The regulatory manager signs.

And all of it under the three safety rings: capture and re-reading happen in ring 3, the cross-validation (is the concentration declared by the supplier consistent with the use of that additive?) in ring 2, and the signed notification lives in ring 1. What is submitted to ECHA is what the person approved. Never the other way round.

See the full IRIS architecture →

Before and after

SCIP by hand vs. SCIP cross-referenced with iLEAN

Aspect	SCIP with a spreadsheet + SDS in a folder	With iLEAN Tracer + Connect + Agent
Composition per article	Scattered SDS, BOM with generic material	Real composition anchored to the SKU, with its source
Candidate List update	Email alert, re-read the SDS by hand	Automatic cross-check against every archived SDS
New SVHC in an existing BOM	Late detection — days or weeks	Detected as soon as ECHA publishes
SCIP notification	IUCLID template filled in by hand	Dossier ready for signature with evidence
Article 33 to the customer	Generic email whenever someone remembers	Communication per SKU in the B2B customer format
National authority audit	Rebuild the history of declarations	Traceability per article with its source SDS

Impact estimate

Impact estimate for your plant — to be validated with your numbers.

The block below is an estimate to be validated with the concrete data of your operation. We put it forward so the committee has an order of magnitude; we refine it during the diagnostic.

• Mid-sized manufacturer (chemicals, metalworking, electronics, furniture, construction) with 50-500 active SKUs on the EU market, tens to hundreds of archived SDS.
• Tracer + Connect + Agent pilot on one product family and the latest Candidate List update. First expected value within a few weeks: detection of overdue SCIP notifications and preparation of notifications for signature.
• Indicative payback between 4 and 9 months, depending on the number of exposed SKUs and the current cost of maintaining SCIP by hand (regulatory FTE + quality hours + delays).
• Reduction of manual hours spent re-reading SDS after each ECHA update: ≥ 30 %, with room for more as more articles enter the loop.
• The hard lever is avoiding a fine from ECHA or the national authority for a SCIP notification that was never filed, and shielding yourself from a B2B customer claim for breaching article 33.

And the regulatory manager's reasonable doubt

“What if the agent misreads an SDS and lets an SVHC through without notifying it?” — hallucination is a problem of free generation, not of anchored tasks. In tasks where the AI is limited to recontextualising a data point (read the SDS, extract the composition, look up the CAS in the Candidate List), the best models brought the error below 1.5 % ^[1]. And even so, the notification does not go out on its own: the agent prepares it, the responsible person reviews and signs it. The three rings are there for exactly this.

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

Keep reading: Conflict minerals 3TG · CBAM carbon border · CSDDD due diligence