Why REACH compliance fails: it's a process problem wearing a data disguise

When a REACH submission doesn't hold up, the instinct is to blame the data. A substance was missing from the registration. A tonnage figure didn't match what the site actually used. A container couldn't be traced back to when it entered the business. It's easy to stop there and call it a data problem.

But poor data is the tip of the iceberg. It's a byproduct, not the root cause. REACH doesn't ask for a single accurate figure at a single point in time. It asks organizations to know the cumulative quantity of a substance manufactured or imported across a full year, in order to determine which registration threshold applies and which SVHC obligations follow. That's a lifecycle question, not a snapshot question. And when there's no process connecting procurement, storage, use and disposal, nothing tracks a substance's full journey through the business well enough to answer it.

So the data issue is really a process issue. And the most effective way to fix a broken process at scale is better software: a system that connects every lifecycle stage automatically, so the figures feeding a REACH registration are accurate because the process behind them never lost sight of the chemical in the first place.

The registration threshold is a lifecycle calculation, not a lookup

REACH registration obligations are triggered at 1 tonne per year, per substance, per legal entity. That sounds like a simple number to track. In practice, it requires visibility into every point a substance entered the business, every site it was used at, and every quantity consumed, wasted or disposed of along the way, aggregated accurately across a twelve-month window.

Most organizations don't have a single system that does this. They have a purchasing record that shows what was ordered, a site-level spreadsheet that shows what was logged as received, and a usage estimate that gets reconstructed at reporting time from whatever records are still available. None of these three things update each other. A substance can cross the 1 tonne threshold mid-year and go unnoticed for months, because no process was connecting procurement data to usage data in real time.

This is why threshold miscalculation is one of the most common REACH compliance failures. It isn't a data entry error. It's the predictable result of trying to answer a lifecycle-wide question using disconnected, point-in-time records.

The SVHC Candidate List doesn't wait for your next audit

ECHA updates the Substances of Very High Concern Candidate List twice a year, and it currently runs past 253 substances. Every addition creates an immediate obligation: organizations using an affected substance above 0.1% concentration in an article must be able to notify ECHA and communicate down the supply chain, in some cases within six months of the substance being listed.

That obligation lands on whatever chemical inventory an organization has at the moment of the update, not the inventory as it existed during the last full audit. If chemical records are only reconciled once a year, ahead of a filing deadline, a new SVHC addition can sit unrecognized against the live inventory for months. The gap isn't a failure to check the Candidate List. It's a failure to have inventory data current enough for a Candidate List check to mean anything the day it happens.

An automated, continuously updated inventory closes that gap by design: when ECHA adds a substance, the system can flag every affected container against the current inventory immediately, not at the next scheduled review.

Registration, evaluation, authorization: three stages, one continuous record

REACH is structured around registration, evaluation and authorization, or restriction, for substances that pose a higher risk. Each stage depends on the information gathered at the one before it. An organization can't respond confidently to an ECHA evaluation request, or prepare an authorization application for a restricted substance, if the underlying registration data was built from estimates rather than tracked quantities.

This is where the cost of a broken process compounds. A registration built on incomplete lifecycle data doesn't just create risk at the point of filing. It weakens every subsequent interaction with ECHA that depends on that data being accurate, because REACH treats these stages as connected, not as separate one-off events.

From chemical custody to chemical strategy

Chemical custody means knowing what was ordered. Chemical strategy means having a live, connected record of a substance from the moment it's procured to the moment it's disposed of, so that when a REACH threshold, an SVHC update or an ECHA evaluation request lands, the organization already has the answer rather than needing to reconstruct one.

Organizations that manage this well don't rely on periodic data calls. They run a single system where procurement, storage, usage and disposal all feed the same live record, so a REACH registration reflects what's actually happening in the business rather than a best estimate assembled after the fact.

REACH isn't getting simpler. The Candidate List keeps growing, CLP classification requirements continue to evolve, and enforcement consistency across member states is increasing. None of that is solved by adding another review step at the reporting stage. It's solved by fixing the process that generates the data in the first place, at the point where the chemical enters the business, not the point where the report is due.

Ask the expert: a live look inside Ideagen Chemical Management

See how Ideagen Chemical Management connects every stage of the chemical lifecycle for accurate, audit-ready data

Watch the webinar