A customer email lands in your inbox late on Friday. They want confirmation that your product doesn't contain any substance on the Substance of Very High Concern Candidate List above the legal threshold. Sales wants an answer today. Procurement says the supplier declaration is old. Engineering says the formulation changed last quarter. Legal asks whether this is only an information duty or whether the product is now at risk.
That's the moment when the substance of very high concern list stops being abstract.
For companies that make, import, assemble, distribute, or resell products in the EU, the SVHC list is a live compliance trigger. It affects what you ask suppliers, what you tell customers, what you submit to regulators, and how quickly you can respond when a substance is newly listed. Teams get into trouble when they treat it as just another reference list. It isn't. It is a decision point.
In practice, the actual challenge isn't memorizing the legal definition. It's knowing what action follows for your role, your product type, and your place in the supply chain. That's where many internal discussions go off track. One person hears “SVHC” and assumes immediate prohibition. Another hears “candidate” and assumes nothing needs to happen yet. Both can be wrong.
Introduction
A new colleague usually asks the same question after the first urgent SVHC request: “What exactly are we supposed to do when something is on the list?”
That's the right question. Most businesses don't struggle because they've never heard of the list. They struggle because they can't turn list status into a workable next step. The pressure is highest when you import finished goods, buy components from several non-EU suppliers, or sell into customers that expect fast declarations.
The practical answer starts with one mindset shift. The substance of very high concern list is not just a chemicals reference. It is a compliance checkpoint that can trigger communication duties, database reporting, internal escalation, and longer-term substitution or sourcing decisions.
Don't start with “is this substance bad?” Start with “where is it, in what product form, at what level, and what duty attaches to our role?”
Teams that handle SVHC issues well usually do three things consistently. They separate legal triggers from commercial preferences, they keep supplier data current, and they maintain a repeatable review process when the list changes. Teams that struggle often rely on old declarations, blur the difference between articles and mixtures, and answer customer requests before checking whether the underlying data is still reliable.
What the SVHC Candidate List Is and Is Not
The best way to explain the SVHC Candidate List to a new team member is this. Think of it as a watch list, not a ban list.
Under REACH, which entered into force in 2007, the Candidate List identifies substances that meet Article 57 hazard criteria such as carcinogenicity, mutagenicity, reproductive toxicity, PBT or vPvB properties, or another equivalent level of concern. Once a substance is placed on the list, that listing becomes the first step in the REACH authorisation pathway and can trigger downstream communication duties where an article contains the substance above 0.1% weight by weight, as described in ChemSec's explanation of REACH and SVHCs.
What it is
The Candidate List is a formal regulatory status. It tells you that a substance has crossed an important threshold in EU chemicals regulation. That matters because listing is not just informational. It changes how companies must evaluate products, supplier information, and customer communications.
It also signals future regulatory pressure. Some listed substances may later move into the authorisation process. If that happens, the business question changes from “Do we need to communicate this?” to “Can we still use or place this on the market in the same way later on?” That's why regulatory teams often track both the Candidate List and the REACH Annex XIV authorisation list.
What it is not
The Candidate List is not an automatic ban. A substance can be on the list without every use being prohibited. That distinction matters because companies often overreact in one of two ways.
One reaction is panic reformulation without first checking whether the actual legal trigger applies to their product. The other is complacency, where someone says the substance is only on a candidate list and assumes nothing needs to be done. Neither approach is sound.
Here's the practical line:
- Not an immediate ban means you may still have obligations today even if use is not automatically prohibited.
- Not the same as authorisation means a listed substance can create information duties now and stricter controls later.
- Not just for chemical manufacturers means article suppliers, importers, distributors, and assemblers can all be affected.
Practical rule: If your product contains a listed SVHC, the first question isn't whether the substance is “allowed.” The first question is whether your product and role trigger duties now.
Why the 0.1% threshold matters so much
Most day-to-day SVHC work comes back to a single threshold for articles. If the listed substance is present above 0.1% w/w, duties can activate. That's why the list becomes part of routine screening. It isn't enough to know whether the substance appears somewhere in your supply chain. You need to know whether it is present in the relevant product context at the level that triggers action.
A lot of weak compliance programs fail because they collect broad statements like “REACH compliant” or “no hazardous substances intentionally added.” Those statements rarely answer the only question that matters when a customer asks for confirmation.
The Journey Onto the List and Its Constant Evolution
The Candidate List changes because the regulatory assessment changes. That sounds obvious, but many companies still treat SVHC screening as a one-time onboarding task instead of an ongoing process.
A substance reaches the list because authorities conclude it meets the relevant concern criteria. Some substances fit the classic categories that regulatory teams know well, such as carcinogenicity or persistence. Others enter through the broader route of equivalent level of concern. That part is easy to overlook, but it matters because it expands the pipeline beyond the older, narrower view of hazardous chemicals.
Why the list keeps moving
Recent updates show the list is still changing in 2025-2026, with ECHA's Candidate List showing 250 substances of very high concern for authorization, and a January 2024 update added five substances, including 2,4,6-tri-tert-butylphenol and bumetrizole, according to ECHA's Candidate List page.
That single fact should shape your process. If the list changes, a declaration collected from a supplier last year may already be incomplete for today's customer question. This is why static files in shared folders tend to create false confidence.
A useful way to think about list evolution is to split it into two business impacts:
| Change on the list | Practical consequence |
|---|---|
| A new substance is added | Existing product data may need review |
| A known substance gains more attention internally | Purchasing, design, and sales may need aligned messaging |
| “Equivalent level of concern” is used | Borderline cases become more important to monitor |
Equivalent concern changes how you monitor
Many people still associate SVHC status only with the traditional hazard categories. That's too narrow. ECHA's definition also covers equivalent level of concern, which is where newer issues such as endocrine-disrupting properties can enter the process through the SVHC route.
That means monitoring cannot be purely reactive. You should not wait for a customer complaint or a formal nonconformance to start checking borderline substances. Regulatory teams that work well usually watch proposals, dossier developments, and internal material hotspots early, even before the formal listing creates immediate work.
For teams that need to understand the broader regulatory review context, the REACH evaluation framework helps explain why substance status can evolve over time.
What works in practice
The companies that stay out of trouble usually build a recurring review rhythm. Not an occasional web check when a customer asks. A defined process.
That process usually includes:
- A current master list of substances relevant to your own products and materials
- A trigger for reassessment when the Candidate List changes
- A fast route to product impact review for procurement and regulatory teams
- A decision log that records what was checked, when, and against which list version
What doesn't work is treating supplier declarations as permanent truth. They age quickly, especially in categories with many components, frequent sourcing changes, or global contract manufacturers.
Your Core Compliance Obligations for SVHCs
When a listed SVHC is present in an article above the legal threshold, the discussion stops being theoretical. You need to act.
A major milestone came on 5 January 2021, when companies supplying articles containing Candidate List SVHCs at 0.1% w/w or above had to begin notifying information through the SCIP database. The same threshold also ties to supply chain communication duties, and consumers must receive the required information within 45 days on request, as summarized by Yordas on SVHC obligations.
Supply chain communication
If you supply an article containing an SVHC above the threshold, you must provide enough information to allow safe use. That sounds simple, but the simplicity is often undermined by vague declarations. “Contains SVHC” is not enough if the recipient cannot act on the information.
In practice, your internal file should let you answer at least these points:
- Which substance is involved
- Which article contains it
- What safe-use information is needed for the recipient
- Which version of the product data supports that answer
If your sales team is sending broad compliance statements without that backup, you're taking an avoidable risk.
Consumer right to know
Consumer requests often expose weak internal processes because they arrive outside the usual B2B compliance workflow. The legal issue is straightforward. The operational issue is not.
When a consumer asks whether an article contains an SVHC above the threshold, the business must respond with the necessary information for safe use within 45 days. That means someone in the company needs a reliable intake route, a product-data source, and ownership for the reply.
A consumer request is not a special project. It should run through a standard response workflow with named owners and approved wording.
SCIP notification
The SCIP duty forced many businesses to get more disciplined about article-level data. It pushed companies beyond generic declarations toward structured substance information tied to real products.
A workable SCIP process usually includes the following stages:
Identify affected articles
Start with products and components most likely to contain listed SVHCs based on supplier declarations, material composition data, or historical issues.Verify the data source
Check whether the information is current enough to support a filing decision. Old declarations create rework.Prepare product-linked records
Keep article identifiers, composition references, and safe-use information aligned.Submit and retain evidence
Treat submission records as controlled compliance documents, not disposable admin output.
The real operational burden
The legal trigger may be concise, but the business burden spreads across teams. Procurement needs current supplier data. Product stewardship needs to interpret it correctly. IT may support data structure. Customer-facing teams need approved response language. Waste and end-of-life considerations can also surface through SCIP-related expectations.
What usually fails is trying to manage all of this through email. Email is where requests arrive. It should not be where compliance evidence lives.
Navigating the Most Common SVHC Compliance Pitfalls
Most SVHC failures are not dramatic legal misunderstandings. They are ordinary process failures. A buyer accepts a vague declaration. An engineer changes a component and doesn't flag regulatory review. A customer asks about one product family, and someone answers using data from a similar but different bill of materials.
The common thread is scope confusion.
The Candidate List is only the first step toward possible Annex XIV authorisation, and obligations differ by product form and jurisdiction. The same substance can trigger different actions depending on whether it is a substance, mixture, or article, as noted in the overview of SVHC scope and obligations.
Pitfall one: treating all product forms the same
This is the mistake I see most often in mixed portfolios. Someone learns the article threshold rule and then applies the same logic to everything, including bulk substances or formulated mixtures. That leads to bad advice, bad declarations, and wasted time.
A simple internal distinction helps:
| Product form | Main practical question |
|---|---|
| Substance | What obligations apply to the substance itself? |
| Mixture | What communication or composition rules apply to the formulation? |
| Article | Does SVHC content trigger article-specific duties? |
If your internal questionnaire starts with “Does it contain an SVHC?” and stops there, it is too shallow. It should force the reviewer to identify the product form first.
Pitfall two: relying on outdated supplier declarations
This usually looks harmless. You have a supplier letter on file, it says the product is compliant, and everyone moves on. Then the Candidate List changes, the supplier changes a raw material, or the wording in the declaration turns out to be too generic to support the actual question asked by your customer.
What works better is tiered supplier evidence:
- Preferred means a recent full material declaration or product-specific confirmation
- Acceptable with review means a narrower declaration tied to a defined part number and date
- Weak evidence means blanket compliance wording with no product specificity
Reality check: “REACH compliant” is not an answer to an SVHC question unless the statement clearly addresses the relevant listing and threshold.
Pitfall three: confusing list status with prohibition
This produces both over-compliance and under-compliance.
Over-compliance happens when a business assumes every listed substance must be eliminated immediately, even where the immediate issue is communication or reporting rather than a direct ban. Under-compliance happens when someone says the substance is only a candidate and ignores current duties entirely.
The right approach is more disciplined. Separate these decisions:
Current duty
Do we need to communicate, notify, or respond now?Commercial risk
Will customers reject the product anyway, even if use remains legally possible?Strategic sourcing issue
Should we start qualification of alternatives because the regulatory path is tightening?
Those are different questions. Strong teams answer them separately.
Pitfall four: fragmented ownership inside the company
SVHC issues often sit between functions. Procurement owns suppliers. Regulatory owns interpretation. Sales owns customer pressure. Product development owns change control. If no one joins those pieces, gaps appear.
A practical fix is to define a short escalation chain:
- Customer or supplier issue enters one channel
- Regulatory checks product form and duty trigger
- Procurement validates source data
- Commercial team gets approved response wording
- Product team is alerted if substitution risk is rising
That sounds basic, but it's where many businesses gain control. Not by adding more policy, but by removing ambiguity about who decides what.
A Practical Workflow for SVHC Screening and Monitoring
Manual SVHC management usually breaks down in the same places. Teams can't find the latest Candidate List status quickly. They review the same supplier documents repeatedly. Product-specific evidence is scattered across inboxes, shared drives, and ERP notes. Then an urgent request comes in and everyone starts rebuilding the answer from scratch.
A better approach is a simple, repeatable workflow that connects substance checking, document review, and update monitoring.
Start with substance identity, not product labels
The first screening step should always anchor to the actual substance identity. Trade names help commercially, but they are unreliable for compliance screening. Use the identifiers available in your records, typically CAS, EC number, or a precise substance name.
That sounds obvious, yet many internal reviews still begin with product brochures, supplier marketing sheets, or old spreadsheet aliases. Those sources create false negatives.
A solid first-pass review asks:
- Do we know the exact substance identity?
- Is the record tied to the latest supplier or formulation version?
- Are we screening the substance against the current regulatory status, not an old internal list?
For day-to-day work, teams often use a regulatory search platform or an internal approved-substance database. Where documents arrive in mixed formats, a screening tool such as the ReachLex chemical compliance scanner can help flag regulated chemicals and terms in trade, safety, or legal documents so reviewers don't have to read every file line by line.
Build a document triage routine
Most companies already have the raw material for an SVHC process. They just don't control it well. Safety data sheets, declarations of conformity, supplier letters, composition sheets, and contract attachments are sitting in different systems.
The fix is not collecting more documents. The fix is triage.
A practical triage routine looks like this:
| Document type | What to check first | Common weakness |
|---|---|---|
| Supplier declaration | Product scope and date | Too broad to support article-level answers |
| SDS | Substance identity references | May not answer article questions |
| Contract or specification | Change notification clauses | Often disconnected from regulatory review |
| Internal BOM or formulation file | Version control | Engineering changes not linked to compliance updates |
The discipline here is simple. Don't treat every document as equal evidence. Some files support an SVHC answer directly. Others only support part of the analysis.
Set update triggers before you need them
A screening workflow is only as good as its refresh logic. If the Candidate List changes and no one rechecks affected products, your “compliant” file becomes a historical artifact.
Useful triggers usually include:
- List update review tied to Candidate List changes
- Supplier change notifications for raw materials, components, and formulations
- Engineering change control where design or material substitutions occur
- Customer-specific declarations that require periodic confirmation
This is also where companies decide whether they want a spreadsheet-driven process or a system-backed one. Spreadsheets can work for a narrow portfolio with stable suppliers. They become brittle once you have multilingual documents, multiple business units, or repeated customer requests across many SKUs.
Keep one answer file per product family
One practical habit saves a lot of time. Maintain a controlled answer file for each product family or component group. Not a generic REACH folder. A product-linked compliance record.
That record should contain the current supplier evidence, internal review notes, the logic for any threshold assessment, customer-facing wording, and the date of last review. When the next request comes in, the team updates a controlled file instead of rebuilding the reasoning.
The real efficiency gain in SVHC work doesn't come from writing replies faster. It comes from avoiding re-investigation of the same product every time someone asks.
Treat Candidate List monitoring as strategic foresight
The end game of SVHC management is not merely answering today's questionnaire. It is seeing where your product portfolio may face pressure next. Candidate listing can be the first formal sign that a substance may become more problematic from a regulatory or commercial standpoint.
That means your workflow should feed more than compliance. It should inform sourcing strategy, substitution planning, customer communication, and product design review. If a material is likely to create recurring declarations, customer objections, or future authorisation concerns, regulatory should not sit on that knowledge alone.
A good workflow is boring in the best sense. It gives the business a routine way to identify, check, escalate, and update without turning every SVHC issue into a fire drill.
ReachLex can support that routine by giving teams one place to search substances by CAS, EC, or name, review consolidated EU chemical rules, and screen incoming documents for regulated chemicals and terms. If your current SVHC process depends on inbox searches, static spreadsheets, and old supplier PDFs, it's worth looking at how ReachLex fits into a more controlled compliance workflow.