Skip to main content
EV Evidence

Regulation · UK

What the public chargepoint open-data duty covers

The open-data duty applies to non-micro public chargepoint operators. Since 24 November 2024, they must hold accurate prescribed data for each public chargepoint and publish reference and availability data free, in machine-readable form and without use terms. They must update EVSE status within 30 seconds. The duty does not open every internal or historical record, guarantee a third-party display is current, or guarantee access on arrival.

The National Archives: The Public Charge Point Regulations 2023, Regulation 10

Reviewed

Key facts and evidence

Across the UK, as checked on 12 August 2026, the open-data duty has applied since 24 November 2024 to operators that are not micro businesses. Prescribed reference and availability data must be free, machine-readable and without use terms, with EVSE status updated within 30 seconds. This does not require every internal or historical record or guarantee access on arrival.

The National Archives: The Public Charge Point Regulations 2023, Regulation 10

Understand the non-micro-operator boundary, 30-second EVSE source update and limits of the public charging open-data duty.

Defined data, not every record

A covered operator must hold accurate prescribed data for each public point and make reference and availability data public free of charge, machine-readable and without use terms. The duty does not expose every internal or historical dataset.

Thirty seconds is a source-update rule

The operator must update an EVSE status within 30 seconds after its status changes. Transmission, caching or display latency may occur after the operator feed, so the rule does not guarantee a third-party screen or physical availability on arrival.

What to do next

Use open data to check location, connectors, payment methods, price, unavailable hours and current availability while allowing for downstream delay.

Immediate action: Record the chargepoint, timestamp, source and observed mismatch if required data appears inaccurate or inaccessible.

  • Do not treat a third-party app timestamp as proof of when the operator feed changed.
  • Do not infer that an open available status guarantees access or a successful charging session.

Checks that stay with this vehicle

  1. Record the point identifier, timestamp, data source and observed reference or availability mismatch.

    The report distinguishes the operator data claim from the condition observed at that time.

    Stop the compliance conclusion if operator size, source timestamp or required-data scope is unknown.

Do not infer from missing evidence

  • Do not claim that every internal record must be public or that a 30-second source update guarantees a third-party display.

Professional hand-off

  • Report materially inaccurate, inaccessible or non-machine-readable required data to the operator and then OPSS with the recorded evidence.

Questions this record can answer

What does the sourced evidence say about defined data, not every record?

A covered operator must hold accurate prescribed data for each public point and make reference and availability data public free of charge, machine-readable and without use terms. The duty does not expose every internal or historical dataset.

What does the sourced evidence say about thirty seconds is a source-update rule?

The operator must update an EVSE status within 30 seconds after its status changes. Transmission, caching or display latency may occur after the operator feed, so the rule does not guarantee a third-party screen or physical availability on arrival.

Sources