Common COP preparation failures and how to control them

01

Direct answer

Direct answer

COP should not be treated as a last-minute exercise in collecting records before an assessment. Major risks arise when the approved configuration can no longer be traced clearly to the BOM, suppliers, production process, inspection, measuring equipment and nonconformity records. A robust COP system must demonstrate that series-produced products continue to conform to the approved type.

Search intent

Informational + commercial investigation

02

The practical issue

A business may hold ISO 9001 certification and maintain many forms, yet still struggle to demonstrate continuity between the certified product and the product currently being released. COP requires operating evidence, not only system documentation.

03

What to check

  • The approved configuration/type/family and current BOM.
  • Change control for design, material, supplier, tooling, process and factory.
  • Incoming, in-process and final inspection and release records.
  • Traceability from finished product to the relevant lots, components and processes.
  • Calibration/verification of inspection equipment.
  • NCRs, concessions, CAPA and effectiveness checks.
  • Control records for characteristics directly related to certification requirements.
04

Regulatory basis

LEGAL REQUIREMENT: COP requirements must be established from the applicable QCVN, TT54/2024 or TT55/2024 and effective amendments for the relevant product and procedural route. Do not infer one inspection frequency for all products.

FACT: The UNECE 1958 Agreement uses Conformity of Production within the type-approval system; the specific requirements depend on the applicable Regulation and approval.

05

Expert analysis

EXPERT INTERPRETATION: An effective COP audit should follow the chain approved configuration → production control → inspection evidence → release → traceability, rather than only following an ISO procedure list.

EXPERIENCE-BASED INSIGHT: LotusTSE prioritizes change control, traceability and evidence of actual production control. Three recurring finding groups deserve close review: changes made without impact assessment, breaks in the traceability chain and control records that do not demonstrate the certified characteristics.

06

Common risks

  • Supplier or material changes without an impact assessment.
  • Drawing/BOM revisions that do not match the certification dossier.
  • Overdue measuring equipment or an unsuitable calibration scope.
  • NCR/CAPA records without evidence of effectiveness.
  • Records generated shortly before the audit without evidence of historical operation.
07

Recommended approach

1. Build a COP evidence matrix for each type/family.

2. Map the approved characteristics to the control plan and records.

3. Review the change log since the most recent assessment or certification.

4. Select backward and forward traceability samples to test the system.

5. Close gaps before the formal assessment.

08

How LotusTSE may support the project

COP readiness review; gap assessment; evidence matrix; mock audit; change-impact review. LotusTSE does not guarantee an external decision or decision timeline.

09

Knowledge Graph

Service: COP assessment / certification support.

QCVN: product-specific, including QCVN 09, 28, 32, 33, 34, 36, 78, 113 and 125 where applicable.

Circulars: TT54/2024, TT55/2024 and effective amendments.

UNECE: the applicable Regulation and the 1958 Agreement/COP framework.

Related Knowledge: Product Changes; Factory Changes; Representative Samples.

10

NEEDS VERIFICATION

Inspection frequency, retention period, sample plan and specific COP requirements must be verified against the product, QCVN/Regulation, approval and applicable procedure.

11
KG

This content does not replace a case-specific legal or technical assessment.

LotusTSE

Need to apply this guidance to a specific configuration or project?

Discuss the assessment scope