Market Intelligence

European Periodic Technical Inspection: National Procedures and Equipment Compliance under Directive 2014/45/EU

2026-08-1013 min readXBW Technical Library

Directive 2014/45/EU and national implementation rules are examined for their impact on inspection intervals, emissions and OBD, brakes, lamps, metrology and data interfaces.

In this article

1. EU law sets a common floor; member states still run the inspection system2. Inspection intervals shape both traffic volume and lane capacity3. Emissions and OBD configuration must match vehicle age and national procedure

1. EU law sets a common floor; member states still run the inspection system

Directive 2014/45/EU establishes minimum common requirements for periodic roadworthiness testing, including test items, defect grading, equipment and personnel. Directive 2014/47/EU covers technical roadside inspection of commercial vehicles. Member states may shorten intervals, add items and use different authorization, fee, reporting and data-platform models. A European project therefore needs a named country, vehicle categories, first-registration rules, competent authority and station operating model rather than a generic claim of EU compliance.

2. Inspection intervals shape both traffic volume and lane capacity

Under the EU minimum framework, M1 and N1 vehicles are generally tested no later than four years after first registration and at least every two years thereafter. Passenger-service vehicles, heavy goods vehicles and certain trailers are generally tested annually from one year after first registration. Member states may apply shorter intervals and special rules for taxis, ambulances, modified vehicles or high-mileage fleets. Capacity planning should use the local mix of vehicles actually presented for inspection, including peak-hour arrivals, retest rates, vehicle changeover and bay occupancy, instead of deriving equipment quantities directly from national fleet size.

3. Emissions and OBD configuration must match vehicle age and national procedure

The annexes to Directive 2014/45/EU include emissions items for positive- and compression-ignition engines and, where applicable, OBD information. Project equipment must still match fuel, emissions class, first-registration year, prescribed operating condition, limit source and the national decision sequence. Gas analyzers, smoke meters, OBD readers, engine-speed and oil-temperature acquisition, chassis dynamometers and environmental sensors are not one mandatory bundle in every market; the current national inspection manual and interface specification determine which modules are required.

4. Brake requirements must be translated into workable bay conditions

The EU framework requires inspection of brake-system condition and braking performance, but the use of roller testers, plate testers or an authorized road-deceleration method still depends on national procedure, vehicle category and station conditions. Selection should verify axle-load range, roller geometry, low-speed control, side-to-side imbalance, parking brake, compatibility with all-wheel-drive and multi-axle vehicles, and the approved route for vehicles that cannot use the tester. Commercial-vehicle projects should also reflect the vehicle categories, load conditions and records used in the roadside-inspection regime.

5. Headlamp accuracy depends on the floor, alignment and vehicle state

Headlamp inspection is not solved by purchasing a tester alone. Floor level, rails, longitudinal vehicle alignment, lamp optical center, tyre pressure, load and automatic levelling all affect the beam result. Matrix and adaptive lighting may also require a prescribed inspection mode or service procedure. Project documents should separately define instrument capability, bay geometry, vehicle preparation and national acceptance values so that workshop adjustment targets, type-approval parameters and in-use limits are not treated as interchangeable.

6. The data interface is part of the inspection process, not final-stage wiring

Implementing Regulation (EU) 2019/621 requires manufacturers to make the vehicle technical information needed for testing available to inspection bodies. Operational systems must also handle vehicle identification, applicable items, raw values, defect grading, retest linkage, reports, access rights and audit records, while exchanging data under the national platform's fields, languages and security rules. Leaving integration until equipment arrival often exposes vehicle-code mapping, time synchronization, version control and responsibility gaps; interface samples, error codes and acceptance datasets should therefore be agreed during procurement.

7. Metrology and acceptance need a country-specific compliance matrix

Directive 2014/32/EU establishes common requirements for measuring instruments within its scope, with MI-010 covering exhaust gas analyzers for motor vehicles. Legal metrology after commissioning, periodic checks, accreditation rules and record retention nevertheless remain influenced by national systems. A procurement matrix should list the legal clause, national implementation, vehicle scope, range and accuracy, software version, type or conformity evidence, initial acceptance, periodic calibration, spares and responsible party. The useful comparison is not between generic EU versions, but between systems able to perform the defined task in the named country.

8. After-sales service must support current rules and a controlled upgrade path

In cross-border inspection projects, downtime often comes from software rules, expired metrology status, interface changes, wear parts and field response, not only from analyzer failure. The service plan should define remote-access controls, version release and rollback, calibration support, critical spares, training language, response time and data backup. In 2025 the European Commission presented COM(2025) 180 to revise the roadworthiness-testing framework. As of this article's date, it remains a legislative proposal and is not a binding current requirement for member states. Projects should be accepted against EU law already in force and the target country's rules, while future software, interface and added-test capabilities are specified as verifiable upgrade options.

Official references

This article is based on the official publications below. Verify the current edition, effective date and local authority requirements before application.