The evidence pack
Your 14 January report, with its evidence already in order.
Every rapid network reports its reliability to the regulator by 14 January. The figure is the easy part. The work is the evidence behind it: every charge point, every minute of the year, every outage and why it happened. We build that for you from the data you already publish, and keep it so that it can be checked.
Ask for your network's pack Download a sample (all UK networks, anonymised)
What the regulations ask of you
Under the Public Charge Point Regulations, a network of rapid charge points (50 kW and above) must be reliable 99% of the time across the calendar year, and must report it. By 14 January you send the regulator a workbook with:
- One row per charge point: the minutes of the year it spent available, charging, reserved, inoperative, out of order, blocked, and so on. Each row has to add up to every minute of the year.
- Your network's figure, worked out from those rows by the regulator's formula.
- An evidence record: for each period of downtime you want treated as outside your control, when it was, why, and what shows it.
What is in the pack
The workbook, filled in
The regulator's own template, as an OpenDocument spreadsheet: every charge point's minutes in every column, each row adding up to the year, and the network figure by the regulator's formula.
Every downtime period, listed
The evidence record arrives with each outage of each charge point already on its own line, with its start and end. You add the reason and attach what proves it. Nobody has to find the outages first.
Where every number came from
A stamp that names each source file the pack was built from and the sealed daily record behind each day, by fingerprint. A figure can be followed to the charge point, the day, and the file your feed gave us.
What your data says about itself
Time your feed reported as unknown, charge points that dropped out of it, hours it stopped updating. These count in your report whether or not anyone has looked at them.
How the workbook is built, step by step
- Collect. Your open data feed is read every one to two minutes, as the regulations require you to publish it: each charge point's location, power and live status.
- Keep. Every response is stored exactly as it arrived, with a fingerprint, before anything else happens to it. If a figure is ever questioned, the original is there.
- Decide what counts. Only rapid charge points (50 kW and up) are in the report, and only once your own location data has shown a charge point's power. Slower ones in the same feed are kept but left out, exactly as the report expects.
- Count every minute. Each status your feed gives holds until the next one, minute by minute, for every charge point. A gap in your feed is recorded as time with no data, never guessed.
- Apply your opening hours. Time outside a site's published opening hours is exempt, as the regulator's guidance says, so a car park that shuts at night isn't counted as down.
- Seal each day. A day after it ends, every charge point's day is sealed in storage that can't be changed, and its fingerprint is published.
- Fill in the workbook. The year's sealed days become the regulator's own template, column by column: minutes available, charging, reserved, inoperative, out of order, blocked, planned, removed and unknown for every charge point, each row adding up to the year. The network figure follows the regulator's formula, and the evidence record lists every downtime period.
Two ways in
We measure you
If your feed is public, or you give us read access to it, we measure your network from now on and your pack builds itself from the record. Nothing to send, nothing to install.
You bring your own data
Already hold the year's status history in your own systems? The filing helper in the portal takes your charge points and status periods as CSV or JSON and gives you the regulator's template, filled in, as a spreadsheet. What you upload stays yours: it's never published, counted or added to anyone's figures.
Many networks use both: their own history for the months before we started, our record from then on, and the two side by side to see where they differ.
The care taken with the evidence
A reliability figure is only worth something if it can't be quietly improved afterwards, by you or by us. So the record is kept the way accounts are kept.
- Kept as received. Every response from your feed is stored exactly as it arrived, before anything is done with it, with a fingerprint of the file. Nothing is edited, ever.
- Closed every day. Twenty-four hours after a day ends, each charge point's record of that day is sealed. Its fingerprint, and the network's, are published.
- Corrected in the open. If a day turns out to be wrong (late data, a mistake of ours, evidence from you), the correction is a dated note beside the sealed day, saying what changed and why. The original stays readable.
- Checked again, daily. A sample of sealed days is rebuilt from the stored files and compared with the record. A difference raises an alarm and is investigated by a person.
- The same method for everyone. One published method, the regulator's columns and formula. No network is counted differently.
- Honest about its limits. We read your feed every one to two minutes, so a change shorter than that can be missed. Time we hold no data for is shown as no data, never filled in. The pack says both.
The time it saves
Done by hand, the evidence is the slow part. Someone exports a year of status history from the charge point system, works out each charger's minutes in each state, finds every outage, and matches each one to a ticket, an engineer's visit or a grid fault, charge point by charge point. For a network of a few hundred rapid chargers that is thousands of lines to assemble before the first reason can be written.
The pack does the assembling. What is left for your team is the part only you can do:
- Say why. Against each outage that was outside your control, the reason and the evidence you hold.
- Compare. Where our figure differs from the one in your own systems, you see it in January, with the days it comes from, before anyone else asks.
- Sign and send. The declaration and the submission stay yours.
And the linking is already done: each line of the evidence record points to the charge point's sealed day, and that day to the files behind it. If the regulator asks how a number was reached, the answer is a link, not a search.
What signing up gets you
- A portal account for your company, for the people who prepare the report, signed in with a work address at your company's domain.
- The pack for any period, whenever you want it: a week, a month, a quarter, the year so far. January holds no surprises.
- Your downtime as it happens: each charge point's outages listed as they're sealed, so reasons can be gathered through the year rather than in a January rush.
- Feed health: we watch for your feed going quiet, reporting charge points as unknown or dropping them, and tell you, before it shows in your figures.
- The filing helper, for your own data, as above.
- Periodic reliability reports for your landlords and partners: one site or the whole network, numbered and checkable by them.
Ask us about signing your network up.
Ready on 2 January
- 31 December, midnight. The year ends.
- 2 January. The last day of the year is sealed a day after it ends, and the year's record closes with it. Your pack for the full year is ready to download that morning.
- 2 to 14 January. Twelve days for the part that needs you: reasons, evidence, review, signature.
- 14 January. The report is due.
During the year you can take the same pack for any week, month or quarter, so January holds no surprises.
What it is, and isn't
The pack is an independent reconstruction from the data you publish: what the regulator and your drivers can see. It is not your submission, and it is labelled as such. It covers the period we have been collecting your feed and states exactly which hours that is. Data can't be collected afterwards, which is the reason to start before January rather than in it.