REACH and RoHS Material Compliance Register Inspection

It covers the document trail and traceability for a specific material, component, or packaging item against REACH and RoHS requirements. The register checks whether declarations, test evidence, supplier records, and revision dates are present and current. It is meant for product compliance review, not for a full chemical management program. If you need a broader supplier quality or environmental compliance workflow, you would usually pair it with a separate vendor approval or material declaration template.

Use it when onboarding a new part, reviewing a supplier change, preparing a product for a new market, or refreshing compliance records before an audit. It is also useful after a REACH Candidate List update or when RoHS evidence is nearing expiration. The template works best as a recurring register review, not a one-time filing exercise. If a part has multiple variants or finishes, inspect each compliance-relevant version separately.

Typically a compliance manager, quality engineer, regulatory specialist, or supplier quality representative completes it. In smaller organizations, the buyer or operations lead may gather the records, but someone with compliance authority should review the final outcome. The key is that the person signing off can judge whether the evidence is current, attributable, and applicable to the target market. If supplier data is incomplete, the inspector should log a deficiency rather than guessing.

Review them at onboarding, whenever a supplier changes a formulation or process, and on a scheduled cadence tied to your product risk and market exposure. Many teams also recheck records after regulatory updates, especially when the REACH Candidate List changes or a RoHS exemption is nearing expiry. High-risk or high-volume parts often need more frequent review than low-risk purchased items. The right cadence is the one that keeps the register current before a non-conformance reaches customers.

No. It helps you track whether the right evidence exists and whether it supports the compliance claim, but it does not replace testing or supplier declarations. For some items, a declaration may be enough; for others, analytical test results or a stronger chain of evidence is needed. The template is designed to show what is missing, expired, or not attributable so you can follow up. That makes it useful for both document control and escalation.

The template prompts you to confirm whether SVHC disclosure is documented and whether the Candidate List or restricted substance update is current. That matters because a part that was compliant last quarter may no longer have complete support after a regulatory update. By tying each record to a revision date and supporting evidence, the register makes it easier to spot stale declarations. It also helps you assign corrective action before the gap becomes a market access issue.

Common issues include missing supplier declarations, expired certificates, unclear lot traceability, and evidence that does not match the exact part number or market. Teams also miss packaging or accessory materials that should be included in scope. Another frequent problem is treating a generic statement as proof without checking whether the document is dated, signed, and attributable. This template is built to surface those gaps before they become audit findings.

Yes. You can add market-specific fields, part-family rules, exemption tracking, or supplier approval checkpoints without changing the core inspection flow. Many teams create separate views for EU, UK, and other destination markets so the scope is obvious at a glance. You can also add internal references to material declarations, test reports, or approved supplier lists. The important part is keeping the unique item ID and revision control intact.

This template works well alongside supplier quality audits, ISO 9001 document control, and product compliance release workflows. It can also be linked to corrective action tracking so deficiencies do not disappear after the inspection. If your team uses an ERP, PLM, or document management system, the register can point to the source file rather than duplicating it. That reduces version drift and makes audit retrieval faster.