# Product Compliance Program Maturity Assessment > Source: https://netray.co/tools/product-compliance-program-maturity-assessment > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Ten questions that rate how well your manufacturing company manages product regulatory compliance, from ownership and data to change control and records. ## Category compliance-legal ## Audience - Compliance engineer - Quality manager - Operations director ## Tool **Kind:** assessment **Questions:** #### Who owns product compliance in your company? **Options:** ##### Nobody in particular, handled when asked **Score:** 0 ##### Quality or engineering handles it part time **Score:** 1 ##### A named person with a written role **Score:** 2 ##### A team with a defined procedure and backup **Score:** 3 #### How do you know which laws apply to each product? **Options:** ##### Experience, nothing written **Score:** 0 ##### Lists exist for some products **Score:** 1 ##### Applicability matrix for each product family **Score:** 2 ##### Matrix reviewed at each design change and release **Score:** 3 #### Where is component material compliance data stored? **Options:** ##### Email folders and PDFs **Score:** 0 ##### Shared spreadsheets **Score:** 1 ##### A database or portal separate from the ERP **Score:** 2 ##### Linked to ERP items with status and expiry **Score:** 3 #### How do you handle supplier declarations? **Options:** ##### We accept whatever the supplier sends **Score:** 0 ##### We request them at onboarding only **Score:** 1 ##### We request on a schedule and check content **Score:** 2 ##### Scheduled requests, content checks and verification testing **Score:** 3 #### What happens when a design or supplier changes? **Options:** ##### Compliance is not involved **Score:** 0 ##### Compliance is informed after the fact **Score:** 1 ##### Compliance reviews changes flagged by engineering **Score:** 2 ##### Change orders automatically trigger compliance review **Score:** 3 #### How do you track changes to regulations and substance lists? **Options:** ##### We hear about them from customers **Score:** 0 ##### Occasional reading of news **Score:** 1 ##### Subscription or consultant alerts **Score:** 2 ##### Monitored with owners, impact assessment and actions logged **Score:** 3 #### How are technical files and declarations kept? **Options:** ##### Scattered across engineers **Score:** 0 ##### Central folder, inconsistent content **Score:** 1 ##### Controlled documents per product **Score:** 2 ##### Controlled, versioned, retrievable within a day **Score:** 3 #### How do you respond to customer compliance questionnaires? **Options:** ##### Each one is a scramble **Score:** 0 ##### Reuse previous answers when found **Score:** 1 ##### Maintained answer library **Score:** 2 ##### Answers generated from controlled data and reviewed **Score:** 3 #### How do you verify supplier data is true? **Options:** ##### We do not **Score:** 0 ##### Only after a customer complaint **Score:** 1 ##### Periodic XRF or lab tests on risky parts **Score:** 2 ##### Risk based sampling plan with results recorded **Score:** 3 #### Could you recall or notify customers quickly if a part were found non-compliant? **Options:** ##### No, we cannot trace by lot **Score:** 0 ##### Only with manual work over days **Score:** 1 ##### Yes, traceability exists in the ERP **Score:** 2 ##### Yes, tested in a drill with defined communication steps **Score:** 3 **Bands:** #### Reactive **Min:** 0 **Max:** 39 **Verdict:** Compliance depends on individuals and luck, and gaps will surface at audits or customer escalations. **Recommendations:** - Name an owner and write a one page procedure - Build an applicability list for your top products - Start collecting declarations for high volume components #### Developing **Min:** 40 **Max:** 64 **Verdict:** Basics exist but data and change control are inconsistent. **Recommendations:** - Move declarations into a controlled list with expiry dates - Add compliance review to the engineering change process - Create a standard answer library for customer questionnaires #### Managed **Min:** 65 **Max:** 84 **Verdict:** A defined program works for most products, with room to automate and verify. **Recommendations:** - Link status to ERP items and block release when data is missing - Introduce risk based verification testing - Run a traceability drill #### Optimised **Min:** 85 **Max:** 100 **Verdict:** Compliance is built into change control, data and traceability. **Recommendations:** - Keep monitoring regulation changes and test your drills - Automate reporting while keeping human sign-off - Audit the program yearly with an independent reviewer ## Content **Intro:** Product compliance programs often grow by accident. This quick assessment shows where yours stands across ownership, data, supplier management, change control and traceability, and what to fix first. **Sections:** #### How to use the assessment **Body:** Answer for how things work today, not how the procedure says they should work. Ask two or three colleagues from quality, engineering and purchasing to answer independently and compare the results, because differences show where the process is not visible. The score is a percentage of the maximum, and each band comes with practical next steps. #### What the ten questions measure **Body:** The questions follow the life of compliance data: who is accountable, which laws apply, where component data lives, how suppliers are managed and verified, how change is controlled, and how fast you can react to an incident. These are the same areas auditors and large customers probe when they assess a supplier, so a weak area is likely to appear in a questionnaire. #### Reading your result **Body:** A low score is not a verdict on people, it usually reflects missing tools and time. Focus on the lowest scoring questions rather than raising the average. Change control and traceability are often the best investments, because they prevent new gaps while you clean up old ones. Repeat the assessment after six months to see movement. #### Common mistakes **Body:** Companies sometimes buy a compliance tool before defining ownership and process, or treat compliance as a one time project at product launch. Others rely entirely on supplier statements. A modest program with clear ownership, controlled data and a working change process beats a large unused system. **Cta:** If your gaps are mostly data in different systems, Netray can help connect ERP, PLM and supplier data into a read-only compliance view. **Faq:** #### Is this assessment an audit? **Answer:** No. It is a self assessment for planning. It does not replace an audit against a standard or legal advice, but it helps decide where to focus effort and which evidence to prepare. #### How often should we repeat it? **Answer:** Every six to twelve months, and after major events such as a new product line, a new market or an acquisition. Compare scores per question, not only the total. #### What score should we aim for? **Answer:** Most manufacturers do well in the managed band for the regulations that apply to them. The optimised band mainly suits companies with many products, many markets or demanding customers. #### Who should answer? **Answer:** Have compliance, quality, engineering and purchasing each answer, then discuss differences. A single respondent may rate the program higher than it works in daily practice. ## Search terms product compliance maturity assessment, regulatory compliance self assessment manufacturing, product stewardship assessment, supplier declaration management assessment, compliance program gap analysis, rohs reach program audit questions, product compliance scorecard, compliance readiness quiz --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json