EU Vehicle Type Approval: Process, CoC and eCoC

EU vehicle type approval is the process through which an approval authority determines whether a vehicle type meets the requirements applicable to it. The approval concerns the defined type; the manufacturer’s Certificate of Conformity links an individual vehicle to that approved specification. Electronic CoC adds structured data preparation and exchange to that vehicle-level record.

This guide focuses on the whole-vehicle approval and conformity workflow for cars, commercial vehicles and trailers within the scope of Regulation (EU) 2018/858. The first project decision is still the approval route. Vehicle category, production scope, manufacturing stage and intended market must be established before the team chooses an application process or builds a document template.

Who does what in the approval process?

The manufacturer prepares the product and supporting information. A designated technical service performs or supervises the relevant testing and inspections. The approval authority assesses the evidence and makes the approval decision. RDW’s certification explanation describes the distinction between a technical service’s test report and the authority’s final assessment.

For project planning, assign a named owner to each handover. Engineering should know which configuration was tested, homologation should know which evidence belongs to the application, and production should know which specification has been released. A shared folder is useful only if the team can identify the current record and explain which earlier versions it replaces.

Prepare a scope and evidence checklist

Start with a short scope statement identifying the manufacturer, vehicle category, type, relevant variants and versions, and state of completion. Then agree the evidence package with the selected authority and technical service. The following is a working preparation checklist, not a substitute for their application requirements:

• A controlled description of the vehicle configuration and the source of its technical values.
• Relevant drawings, system and component approval references, and test evidence.
• A list of differences between the test sample and the configurations proposed for approval.
• Production controls, responsible reviewers and a process for assessing changes.
• A register of open questions with an owner, supporting evidence and a resolution.

Keep the checklist connected to actual files. “Braking report available” is less useful than an identifiable report tied to the correct configuration. If a value is still under review, record that uncertainty before it appears in an application or conformity output. This avoids a later correction being treated as an unexplained overwrite.

Conformity of production continues after approval

Approval work also addresses the manufacturer’s ability to keep production consistent with the approved specification. RDW’s Conformity of Production guidance explains the initial assessment and continuing production controls. A prototype test result and an ongoing production control are different pieces of evidence.

A useful internal exercise is to select one production vehicle and trace its configuration back to the approved record. Check which inspection results support its release and whether any engineering change was assessed before implementation. If the team cannot establish that connection, generating another certificate will not resolve the underlying record gap.

What changes in a multi-stage project?

Consider a chassis-cab completed with a specialist body. As a practical review example, the later-stage team should reconcile the base-vehicle information with the completed vehicle’s dimensions, masses, equipment and approval references. Which values remain applicable, which have changed and which need new evidence? These are questions for the actual configuration, not answers to copy from another vehicle’s certificate.

Maintain the earlier-stage documents alongside the later-stage record. A drawing revision or a different body installation should be assessed for its effect on the approval and conformity data. The multi-stage vehicle approval guide introduces this shared-manufacturer context. The precise responsibilities and evidence must follow the chosen approval route.

Turn the approved record into a vehicle-specific CoC

Before releasing a CoC, compare the VIN, applicable approval reference and vehicle-specific values with the controlled production record. A type-approval number alone does not show that every populated field belongs to that vehicle. The CoC and eCoC comparison explains how the output and delivery checks differ.

For electronic delivery, the work continues through XML generation, IVI validation, the required signing step and the receiving response. Electronic COC Platform creates, validates and signs eCoC XML, submits through the manufacturer’s configured NAP connection and tracks responses. The platform’s output supports that workflow; the approval decision remains with the authority.