Multi-Stage Vehicle Approval: Bodybuilder eCoC Checklist

Multi-stage vehicle approval covers a vehicle built or completed in successive stages. A common example is a chassis-cab supplied by one manufacturer and completed with a specialist body by another. For the bodybuilder, the practical task is to connect the earlier-stage evidence with the changes made to the finished vehicle, then prepare conformity data that describes the correct configuration.

This guide focuses on preparation for an EU vehicle approval and eCoC workflow. It is a working checklist for the manufacturer’s team, not a complete authority application form. Agree the actual approval route, vehicle scope and evidence requirements with the responsible authority and technical service before releasing documents.

Establish the scope and each manufacturer’s responsibility

The multi-stage framework in Regulation (EU) 2018/858 addresses responsibility for additions and modifications and the exchange of information between manufacturers. Earlier-stage approval is not blanket coverage for later changes. Identify the systems affected by your work and the evidence needed to assess them.

Begin with the intended market, vehicle category, manufacturing stage and proposed configuration. Confirm who holds the relevant approval, who supplies the base data and who reviews the completed vehicle record. The EU type-approval guide explains how manufacturer preparation, technical-service evidence and the authority’s decision fit together.

What should the previous-stage handover contain?

Request a traceable package for the vehicle and approval scope you actually use. A practical handover can be organised around the following records and review questions:

• Approval reference and applicable revision: can the reviewer connect the supplied vehicle configuration to the relevant approval documents, including extensions where applicable?
• Vehicle identity and conformity record: do the VIN and vehicle details agree across the delivery record, available previous-stage CoC and your production order?
• Technical source data: are the units, definitions and configuration limits clear enough to distinguish a permitted limit from an actual measured value?
• Bodybuilding information: which drawings, installation instructions and restrictions apply to your proposed body or equipment?
• System and component evidence: can you identify the references relevant to the work, rather than relying on an unlabelled collection of certificates?
• Change notification contact: who will tell your team when a base-vehicle revision affects the documents or data already used in production?

Do not mark a handover complete because the files are present. Open a sample, check its revision and record what it supports. If a source is missing, assign a named owner and a question that can be answered. “Confirm applicability to this configuration” is more useful than leaving an unexplained red cell in a spreadsheet.

Example: a chassis-cab completed with a box body

The following example is illustrative; it contains no approved dimensions or engineering limits. A manufacturer receives a chassis-cab, installs a box body and prepares the completed vehicle record. The review should connect each changed characteristic to evidence and a release decision.

For example, a drawing may be revised after an initial inspection. Before using the inspection result, establish whether it still represents the vehicle being released. Do not invent a new value to make the certificate look consistent. Resolve the source difference, retain the decision and regenerate the affected output.

Prepare one coherent vehicle file before issuing the CoC

A useful internal folder structure has five parts: received base documents, configuration and change records, inspection evidence, released conformity output, and submission records. Give each file an identifiable version and responsible reviewer. The structure is an operating suggestion; the authority may require a different application package.

Compare the VIN, applicable approval references and vehicle-specific fields across these parts. Where more than one person enters data, decide which source controls each field. RDW’s Conformity of Production guidance explains the continuing production-control context. Your internal record should make it possible to show why the selected vehicle was released.

Move the reviewed data into the electronic workflow

Prepare the dataset required by the receiving route, retaining the necessary stage information instead of flattening every reference into a single generic record. IVI XML validation checks the selected structure and rules. It does not decide whether a physical modification is covered by an approval.

Electronic COC Platform creates, validates and signs eCoC XML, submits through the manufacturer’s configured NAP connection and tracks responses. Establish the submission account, test context and response handling for that manufacturer. The NAP submission workflow explains the handover; the CoC and eCoC comparison distinguishes the document from the electronic delivery evidence.