How to record a correction to a technical source
When a technical source is corrected, update the affected reference field and keep the earlier document in the record as superseded evidence. Record the replacement document’s identifier and issue date, the date your entry changed, and what changed in the record. Do not imply that a technical value changed unless comparison of both documents confirms it. EOTA’s ETA register distinguishes assessments described as currently valid from former versions held in a separate superseded database, which makes status and version part of the source trail. [1] [4]
- EOTA says its ETA database contains currently valid assessments, while its separate Superseded ETAs database represents former versions; newly issued assessments may not yet appear in the current database. [1] [4]
- The 01.09.2025 ETA-24/0676 identifies itself as replacing the same-numbered assessment issued on 11.02.2025. [2]
- A Danish certification-body listing independently records ETA-24/0676 dated 11.02.2025, supporting the earlier source date but not explaining the technical changes. [3]
What should the record show?
Keep the technical field separate from its evidence. A useful entry has the declared value or scope, the source identifier and issue date, the source status, and the date checked. When a replacement appears, preserve the old source row and mark it superseded; add the replacement as the current source. Link the two records by the shared assessment number or another stable identifier. This lets a reader see which document supported each version of the field. [1] [2] [4]
A documented revision: ETA-24/0676
The 01.09.2025 European Technical Assessment ETA-24/0676 for Nordsten Brick states that it replaces and supersedes the same-numbered ETA issued on 11.02.2025. The revised document identifies the product as recycled clay masonry units and gives, among other declared fields, dimensions of 228 × 108 × 55 mm and gross dry density of 1,650 kg/m³ with a ±30% tolerance class. A Danish certification-body listing also records the earlier ETA date of 11.02.2025. [2] [3]
What changed, and what remains unverified?
The verified field-level change is the source record: the current evidence is the 01.09.2025 edition, while the 11.02.2025 edition is its superseded predecessor. The available current assessment names the earlier edition but does not describe the technical amendments, and the earlier assessment text was not available for a direct comparison. The dimensions and density above are therefore values in the replacement document, not verified differences from the earlier document. Preserve that uncertainty instead of labelling a technical value as corrected. [2] [3]
How to update a supplier entry
For this example, the entry can show “Assessment: ETA-24/0676; issue date: 01.09.2025; status: latest edition located in issuer’s assessment PDF; EOTA register status not confirmed as of 26.09.2026.” Its source history should retain “ETA-24/0676; issued 11.02.2025; status: superseded by the 01.09.2025 edition.” Keep the stated dimensions and density attached to the replacement document. If a project decision depends on the exact revision, request both editions or a change summary from the issuing Technical Assessment Body, then record the affected fields and page references. EOTA says its ETA database contains currently valid assessments but newly issued assessments may not yet appear. Record the date and location of each status check; locating a document does not by itself confirm its current register status. [1] [2] [3]