For vehicle manufacturers, homologation teams and production operations in Europe and the United Kingdom.
Prepare EV eCoC values from the controlled approval and vehicle-specific data applicable to the actual configuration. Keep the meaning of each range or consumption value, its unit, calculation or source reference, and the reviewer’s decision. A catalogue range or dashboard estimate is not a substitute for that evidence chain.
This article concerns WLTP-related data preparation for applicable light-duty battery electric and plug-in hybrid vehicle workflows. It is an operational review guide, not a WLTP calculation manual. Heavy-duty vehicle data, battery capacity information and customer range estimates should not be treated as interchangeable with these certificate particulars.
The WLTP framework in Regulation (EU) 2017/1151 provides the regulatory test context for applicable vehicles. Regulation (EU) 2020/683 sets out CoC templates, while the vehicle-data framework in Regulation (EU) 2019/631 links electric energy consumption and range data to CoC sources. These references establish context; the applicable current template and approval documents determine the actual fields.
Before mapping data, establish the vehicle category, powertrain, approval reference, variant/version and destination. Identify whether a value describes a pure electric vehicle or a particular plug-in hybrid operating condition. The label ‘electric range’ is too broad when the source contains more than one defined measure.
| Data item | Meaning to preserve | Evidence to retain |
|---|---|---|
| Electric range | The applicable defined range measure and test context | Approved source and the configuration to which it applies. |
| City or other separately defined range | A distinct measure where the relevant template requires it | Its own source field; do not copy the combined value by default. |
| Electric energy consumption | The exact consumption concept and unit | Approved result or controlled derivation, unit and rounding decision. |
| Powertrain and vehicle configuration | The approved vehicle to which the values belong | Variant/version, relevant equipment and source-system reference. |
| VIN-level selection | How the correct values reach this certificate | Selection rule, source revision and review outcome. |
Give each dictionary entry a source owner and a reviewer. If values pass through an ERP export, preserve the original meaning in the receiving field rather than relying on a shortened column label. Identify conversions explicitly so that the reviewer can see whether the exported value is a direct source value or a transformed one.
A mathematically valid conversion can still populate the wrong certificate field. Confirm the requested measure before converting units. For a simple unit example, 15.8 kWh per 100 km equals 158 Wh per km: divide by 100 and multiply by 1,000. This arithmetic example does not validate an emissions result, select a WLTP operating condition or establish an authorised rounding rule.
Similarly, keep rated battery capacity, usable battery energy, electricity consumption and electric range separate. Do not calculate the certificate range by dividing an advertised battery capacity by a generic consumption figure. The approved source and applicable calculation context must remain identifiable.
A production option change should trigger a review of the affected certificate data. The reviewer must establish whether it changes the applicable approved configuration or value-selection rule. Do not assume that the highest advertised range for a model applies to every VIN or that a later source extract automatically belongs to an earlier vehicle.
Where a manufacturer uses an approved vehicle-specific derivation or interpolation process, the certificate workflow should consume its controlled result and retain the reference needed to explain it. It should not introduce a second informal calculation that competes with the approved process. Assign disagreements between systems to the homologation or source-data owner before signing.
Illustrative scenario: a model’s brochure shows ‘up to 520 km’. A production spreadsheet places 520 in every certificate record. One build uses a different configuration. The problem is not solved by confirming that 520 is a number or that the XML accepts it. The team needs to prove which controlled range result applies to that VIN.
A useful correction starts by removing the uncontrolled default, tracing the affected records and restoring the correct source-selection rule. Review the affected candidates before release. For records already submitted, use the documented correction procedure for their destination rather than silently replacing the retained source file.
The UK VCA service publishes its own UK IVI requirements. Record the receiving profile alongside the shared approval-data baseline. Data reuse can reduce repeated preparation, but it does not remove the need to review the actual output and receiver response for each route.
For a manufacturer working across markets, keep the same source dictionary available to homologation, IT and certificate operations. Make destination-specific decisions visible and test them with representative vehicles. A schema check, a source-data review and confirmation of the receiver’s outcome answer different questions.
The process is ready to expand when users can explain the selected values and resolve the exceptions without editing a signed output in isolation. Review the evidence chain at the same time as usability: a technically complete mapping that operators cannot verify creates a different kind of operational risk.
Bring a sanitised source record, the applicable approval context and one configuration-change example to an Electronic COC workflow review. Use the XML readiness page and ERP/API integration scope to frame the discussion. For the distinction between vehicle conformity data and battery records, read eCoC versus the battery passport.
Use the controlled value applicable to the actual approved vehicle configuration. A model-level marketing claim, especially an ‘up to’ value, does not establish the correct certificate value for every VIN.
They are different units. For equivalent measures, multiply a kWh/100 km value by ten to express it in Wh/km. First confirm the measure, source and required output unit; conversion alone does not establish applicability.
This guide addresses applicable light-duty WLTP data preparation. Heavy-duty vehicle workflows use their own regulatory and source-data context. Define that scope separately rather than copying light-duty assumptions.
Retain its defined meaning, unit, controlled source and revision, applicable vehicle configuration, any authorised transformation and the review decision. The record should explain why that value belongs to the specific certificate.
Reviewed on 16 October 2026. Authority statements below are distinguished from our suggested operating controls. Receiving-system instructions and the applicable approval scheme govern the actual submission.
Continue with Electronic COC articles that connect eCoC readiness, manufacturer rollout and certificate release control.
Compare vehicle eCoC and battery passport responsibilities, identifiers and data sources. Plan the 2027 EU requirement with separate GB and Northern Ireland checks.
Type Approval Data Checklist for eCoC Preparation: a practical Electronic COC guide for manufacturers planning type approval data for eCoC, Vehicle COC workflow and eCoC preparation.
ERP and API to eCoC Workflow: What Manufacturers Should Plan: a practical Electronic COC guide for manufacturers planning ERP and API eCoC integration, Vehicle COC workflow and eCoC preparation.