A BESS performance scorecard is a dated record artefact. It collects identity, basis, source, tier, and review entries for performance evidence about a stationary battery system. It applies to a stationary system within the passport record for industrial batteries under Regulation (EU) 2023/1542. It is governed by its version date and by the dates of its source entries. It does not create a measurement. It states what evidence exists, where each item sits, its basis, and its last check date.
A performance scorecard means the index and summary record for performance evidence. It is distinct from the performance evidence itself. It names the system, version, source entries, basis, tier, and gaps. The scope of this guide is the scorecard as a record artefact. This guide does not cover how to run a capacity test, how to set a charge rate, how to judge fitness for a grid service, or how to score a system against a commercial benchmark. The scorecard points to test methods, site records, and service records rather than repeating them.
What is the difference between a scorecard and a performance record?
A performance record holds a measurement with its conditions. A scorecard holds the trace back to that measurement. The distinction matters at handover, at transfer, and at audit. A reader needs to know whether a figure came from a factory report, a site report, a periodic check, or a maintenance entry. A reader also needs to know whether the figure is still current. A scorecard that copies a figure without its source, method name, and date breaks that trace. A scorecard that keeps the trace intact lets a later reader re-check the figure against the source entry.
What fields belong in the scorecard header?
The header fixes identity and version. Two scorecards for the same system at different dates must not be confused. An empty header field is recorded as a gap. A configuration change after the version date requires a new version entry or a dated amendment, with the earlier version preserved.
| Field | Entry | Check |
|---|---|---|
| Identifier | Identifier matching passport and site records | Identity match |
| Version | Version label and date on the scorecard | Version control |
| Configuration | Configuration as installed, changes noted and dated | Match with installed system |
| Owner role | Role responsible for the scorecard, named by role | Ownership of gaps |
| Review date | Date of next scheduled review | Currency |
| Status | Current, superseded, or under review | Whether current |
What does the basis statement record?
The basis statement records the kind of evidence behind each source entry. It also records the conditions under which the evidence was produced. Basis is a factual statement about origin. It is not a judgement of quality. A factory report, a site report, a periodic check, and a maintenance observation have different bases. The scorecard must keep those bases separate, even when entries concern the same system. A site report does not become a factory report because the two reports agree. For each source entry, the basis statement names the report type, report date, method named in the report, and configuration to which the report applies. Where a report states a condition, the scorecard points to the source entry for that condition. It does not copy the condition as a scorecard claim.
How are source entries listed?
A source list is an ordered list of linked entries. Each entry carries a title, a date, a holder, and a location or identifier. The location must let a reader find the entry. The list should cover factory, site, periodic, and maintenance evidence that bears on performance, where such evidence exists. Where a category does not exist, the scorecard records the absence as a gap entry. The gap entry carries an owner role and a review date. The category is not omitted silently. A superseded entry keeps its place on the list. It carries a superseded marker and a pointer to the replacing entry.
How does a worked scorecard read?
The worked scorecard below uses placeholder values, labelled illustrative, for a single stationary system. The placeholders are not measurements from a real battery. The worked scorecard is not a claim about any real system. It shows the shape of a complete file. A gap in a real file can be recognised by comparison with that shape.
| Section | Illustrative entry |
|---|---|
| Identifier | Illustrative identifier matching the passport record |
| Version | Illustrative version dated 2026-10-30, marked current on that date |
| Factory report | Illustrative factory report dated 2026-10-30, method named in the linked report |
| Site report | Illustrative site report dated 2026-10-30, method named in the linked report |
| Periodic check | Illustrative periodic check dated 2026-10-30, method named in the linked report |
| Basis | Illustrative basis entry stating report type, date, and method name |
| Tier | Illustrative tier entry for each field group |
| Gap | Illustrative gap for a missing periodic check, with owner role and review date |
| Review | Illustrative review date, with reviewing role named by role |
An illustrative figure may appear only with a unit, a method, and a date attached to the same entry. For example, an illustrative entry of 100 kilowatt-hours, measured by the method named in the linked site report dated 2026-10-30, meets that rule. Unit, method reference, and date travel together. A figure without a unit, method reference, or date should not appear, even as a placeholder.
How are access tiers recorded?
An access tier records who may see a field group. The tier applies under the access rules for the passport record at the date of the scorecard. The scorecard should state the tier for each field group in plain terms. A reader can then see, without opening a separate access file, which groups are openly accessible and which groups are restricted. Where access rules change through a delegated act or an implementing act, the tier assignment requires a new version entry. The earlier assignment is preserved and the change is dated. No fixed scorecard template is published in the Regulation text consulted, so tiers are recorded from the current texts, with source and date, or treated as a gap.
What does a scorecard not prove?
A scorecard does not prove that a system performs at a stated level. It does not prove that a system is safe for a stated application. It does not prove that a system meets a stated grid service requirement. It does not prove that a system will perform at the same level in future. A scorecard proves only that certain evidence entries exist. It proves that each entry has a stated basis, source, tier, and date. It proves that gaps are recorded with owners and review dates. Performance, safety, and service fitness are proved, where they are proved at all, by the source entries themselves. Those entries must be read with their methods and conditions. A complete scorecard is not a rating, warranty, or purchase recommendation. A scorecard with no gaps is a complete index, not a high-performing system. A scorecard with gaps is an incomplete index, not a poorly performing system.
How are gaps, reviews, and maintenance links recorded?
A gap entry names the missing item. It names the reason where a reason is known. It names the owner role and a review date. A gap without an owner role and without a review date is an observation. It is not a managed gap. A review entry records the reviewing role, review date, version reviewed, and outcome. The outcome may be confirmed current, amended with a new version, or held pending a named source entry. A review that changes a tier, adds a source entry, or closes a gap produces a new version entry. The earlier version is preserved. A maintenance record describes work at a stated date. A scorecard entry pointing to it states its date, basis, and effect on configuration. The scorecard does not repeat the maintenance narrative.
This guide is general educational information only, not individual legal advice, and a scorecard for a specific battery should be checked against the current Regulation text and any applicable delegated or implementing act before acting on it.
Sources & further reading
Source links point to primary materials and further reading, including commercial implementation resources where cited. This introductory guide does not replace the legislation.