A bodybuilder’s eCoC process must explain what changed at its manufacturing stage and which evidence supports those changes. For motorhomes, minibuses, ambulances and other completed vehicles, a single VIN can sit within a chain of manufacturers and approvals. The operating task is to keep that chain understandable when data is received, reviewed, signed or corrected.
Sources checked: 16 October 2026. The handover model below is an implementation recommendation; complete the mandatory fields required by the applicable approval and destination.
What is different about multi-stage eCoC?
A VIN identifies the vehicle, but it does not explain the full conformity history. Your working record should also identify the manufacturing stage, responsible manufacturer, relevant approval and issued version. Otherwise, a later-stage record can be mistaken for a duplicate or an earlier-stage correction can be applied to the wrong data.
The EUCARIS guidance describes retrieval of the highest version for each stage. Design your archive so that staff can see both stage relationships and revision history, without treating the two as interchangeable.
Which information should be requested from the previous manufacturer?
Agree a handover pack before the first vehicle arrives. Ask for an identifiable previous-stage conformity record and the technical evidence needed for your stage. Record the source and issue date of every file. A manually copied value should retain a reference to the document it came from.
Scroll the table horizontally to view all columns.
| Information | Check at receipt | Action owner |
|---|---|---|
| VIN and previous-stage record | Same vehicle, correct manufacturer and current issued version | Incoming-vehicle coordinator |
| Approval and stage references | Relevant approval, extension and stage are identifiable | Homologation team |
| Masses, dimensions and body information | Source values are distinguished from final measured or calculated values | Engineering |
| Emissions or energy-related inputs where applicable | Value applies to the actual configuration and has an identified method/source | Designated technical specialist |
| Changes or corrections from the base manufacturer | Affected vehicle list and downstream impact are recorded | Quality and release teams |
Do not silently fill a missing value from a neighbouring vehicle. A similar commercial model can have a different approval extension, variant or permitted configuration. Put incomplete handovers into a visible exception queue with an accountable contact.
How do you distinguish inherited data from changed values?
Use a field-level register containing the source value, your stage’s value, the reason for change and the supporting evidence. Mark a field as unchanged only after confirming that the source remains applicable. This does not remove the need to populate mandatory fields in the final output.
A practical review asks three questions for each material value: was it altered by the build, does the approved configuration permit it and who has verified the result? The answer should be available from the record, rather than reconstructed from emails at dispatch.
- Import or register the previous-stage evidence without overwriting it.
- Associate the vehicle with your stage’s approval and configuration.
- Enter changes with units, provenance and supporting calculations or measurements.
- Run schema checks and cross-field technical checks.
- Release, sign and submit the correct stage record.
- Retain destination evidence and provide the agreed handover to the next party.
Worked example: converting an incomplete chassis into a motorhome
Illustrative workflow: a motorhome manufacturer receives a chassis and previous-stage evidence. The completed build changes body characteristics, overall dimensions and vehicle masses. Engineering records the final configuration, while homologation confirms the connection to the relevant completed-vehicle approval.
The release reviewer should be able to open the source record, inspect the changes and follow each consequential value to its evidence. A system that merely copies the chassis file and replaces the manufacturer’s name does not demonstrate this review. Equally, deleting unchanged data without checking mandatory requirements creates a different failure.
For a pilot, deliberately include a missing handover field and an upstream correction. The team should demonstrate how release is blocked, who resolves the issue and how the corrected source is assessed against work already completed.
What changes for a UK VCA programme?
The VCA’s multi-stage FAQs state that incomplete vehicles are included and explain previous-stage data access. They also distinguish mandatory or stage-applicable IVI sections from unnecessary consolidation of unchanged, non-mandatory earlier-stage data. Apply that guidance to the UK route rather than assuming an EU workflow is identical.
Agree who obtains missing previous-stage evidence and how the team verifies access before delivery. Do not build a production dependency on a future retrieval feature without checking that it is available for your actual records. Keep the manufacturer's account responsibility separate from a software supplier’s technical role.
How should upstream corrections be handled?
Subscribe to, or contract for, a clear notification process with the preceding manufacturer. An upstream correction may affect an unchanged reference, a final technical value or a conformity decision. Assess the impact before issuing a later-stage revision; a new source file does not automatically determine what must change downstream.
Keep a change log showing the affected VINs, stage, old evidence, new evidence, technical assessment and release decision. For XML corrections, consult the EReg IVI guidance and the receiving system’s current rules. Version control cannot replace the engineering assessment.
Frequently asked questions
Does the chassis manufacturer’s eCoC automatically cover the completed vehicle?
It is evidence for its own stage. Review the completed vehicle, the later-stage approval and the applicable submission requirements; do not assume that a chassis record describes changes made by the bodybuilder.
Should every field from the earlier stage be copied?
Use the relevant schema, mandatory fields and destination guidance. Keep the complete source evidence in your archive, but distinguish that archive from the fields required in the submitted stage record.
Can a supplier prepare the file on our behalf?
Define the permitted technical role, account access and release authority. Outsourcing preparation does not remove the need for the responsible manufacturer to verify its data and approval context.
What is the most useful first test?
Follow one completed vehicle through receipt, changed-field review, signing, submission and an upstream correction. Include the people who will resolve missing information during normal production.
Review your stage handover
Use the EU and UK scope guide to confirm the route and the correction guide to design revision handling. Ask Anemon Engineering to review a representative multi-stage case, including the previous-stage evidence and your final approval.
Summary
A reliable stage handover connects the VIN, previous-stage evidence, approved changes and the responsible manufacturer. Check mandatory fields and market-specific rules, retain the source records and test a complete vehicle before expanding production.
