Working with your product

REACH / SVHC / SCIP: trace the evidence behind a substance assessment

Connect supplier declarations with the product data version and selected Candidate List source. The result is not an isolated answer: you can trace the inputs, substance information and outstanding evidence needed for the next decision.

Workflow illustration: REACH / SVHC / SCIP: trace the evidence behind a substance assessment
Illustration of the workflow area.

What you gain

You retain an assessment with its source context and history, ready to revisit after product or material information changes.

When this module helps in daily work

A substance declaration is useful only when its component, material and scope are clear. Begin with supplier material and product identification, not the result you hope to obtain. Check concentration units and whether the statement concerns the whole article or one part.

When a corrected declaration arrives, another assessment can retain the earlier basis. Saved source context helps distinguish a product-data change from a change in the reference list, making the reason for another review easier to explain.

What to prepare

  • Product version and substance declarations
  • Supplier information and concentrations
  • Reviewed Candidate List source

How the workflow works

  1. Establish the source

    Check the origin and version of the substance list. Retain the mapping-review reference rather than assuming any downloaded file is current. Check the source identity and review status before assessment. A file found in an email thread is not automatically the appropriate reference.

  2. Record substance information

    Link declarations to the product and relevant materials. Missing supplier information remains a visible task for completion and review. Compare substance names, identifiers, units and declaration scope. Clarify which component a value describes before using it in an assessment.

  3. Inspect results and history

    Run the assessment for the saved version, then inspect its inputs and result. Earlier runs retain their own source context. Read results alongside their inputs. Establish whether the declaration, product or source changed before attributing a difference to a new obligation.

What you retain after the workflow

  • Substance inputs linked to the product version.
  • An assessment result with its Candidate List reference context.
  • Earlier assessment history and a basis for investigating evidence gaps.

At the next review, start with the saved version and check whether new information changes earlier findings.

Fictional example

An updated supplier declaration

A Terra component supplier provides a completed substance declaration. Save the information and another assessment, then check what changed compared with the earlier result and the selected reference source.

Follow the step-by-step example: LED desk lamp →

Official sources for further reading

Choose a plan for your workflow

Compare the module scope and available platform plans.

View plans