How to read certificates, data sheets and DoP

The first check is a character-by-character comparison between the code offered and the code printed on the document. Review letters, numbers, conductor cross-section, number of cores, voltage designation, sheath type and any suffixes separately. Two cables in the same family can have different insulation systems, screen arrangements, flexibility classes or application limits. A family name is useful for navigation, but it is not a substitute for the product code.

If a document applies to a range rather than one code, the range must be stated clearly in the document or its controlled annex. Do not infer inclusion from a similar description or from a product image. The project team can mark the ordered code on the technical table, data sheet, certificate and DoP during review. When the document covers another code, request written scope confirmation or the correct document before approval.

A standard mentioned on a product page is not the same as a document issued against that standard. Read the title, scope, issue date, revision and referenced standard together. IEC, EN, BS, VDE and national references should be compared with the project acceptance criteria instead of being treated as interchangeable by default. Preserve the wording used in the tender or technical specification when requesting evidence.

HFFR, LSZH, halogen-free, flame-retardant and fire-resistant are also not interchangeable labels. HFFR and LSZH are commonly used in markets for halogen-free, low-smoke compounds, but acceptance depends on the actual cable construction and the tests covered by the evidence. Flame-retardant can describe flame-spread behaviour, while fire-resistant may describe circuit integrity for a defined period. Do not assign one term from another without checking the document and the specification.

A document can have several revisions under the same title. Record the issue or revision date, document number, validity period and any statement identifying the superseded version. If a PDF has been renamed, the controlled information inside the document remains decisive. A scan that is unreadable or missing its identification page should not be accepted as final evidence until its number and scope are confirmed.

Selecting the file that looks newest is not enough. Confirm that the current version covers the same product code, scope and required standard. Expired, withdrawn or superseded material should not be presented as current product evidence. A controlled register should also record when the file was received and who checked it. That record makes it possible to explain exactly which version was used in a quotation or project submission.

Quality-management certificates, trade-register records, tax or company information, manufacturer declarations and accreditation details help evaluate the supplier as an organisation. They do not, by themselves, prove the construction or project compliance of a specific cable. They belong in the supplier qualification file, while product-level data sheets, certificates and DoPs remain linked to the ordered code and its stated scope.

A practical document structure keeps company records in a corporate folder and product evidence under the product code or family. The auditor can then assess the quality system, the engineering team can review technical scope, and procurement can check commercial records without mixing their purposes. The presence of an ISO certificate does not automatically establish a particular fire, environmental or performance classification for a cable.

Document review does not end at the quotation stage; it continues at goods receipt against the drum label. The product code, cross-section, standard reference and batch number on the label must identify the same product as the Declaration of Performance and certificate on file. For cables under the Construction Products Regulation (CPR), confirm that the reaction-to-fire class on the label — for example Eca or Cca — matches the class on the DoP exactly; any mismatch requires the delivery record to be reviewed. Record the batch number in the goods-receipt paperwork to preserve traceability between the drum and the relevant declaration if a compliance question arises later. If the label and the document disagree, request written correction from the supplier before the drum is put into use.

Use an evidence matrix rather than relying on file names. Rows can contain product code, cross-section and construction; columns can cover the requested data sheet, certificate, DoP, standard reference, revision and status. Each completed cell should point to a document number or controlled path. If the scope is unclear, mark the item as pending instead of filling the gap with an assumption. This makes missing evidence visible before delivery.

Publishing an unclear file or quietly using evidence for a similar product may look efficient, but it creates a larger approval delay later. Ask the manufacturer for written scope confirmation and retain the response with the document record. The customer pack should contain current files that match the requested product and scope, with any corporate documents labelled separately. A folder full of unexplained PDFs is an archive, not a controlled compliance submission.