Reading a Type Test Report: What Cable Buyers Should Verify
Quick Answer: A type test report proves that a particular design was tested once, to a particular standard, in a particular size. It is evidence only if that design, standard and size are the ones you are buying. Most report disputes come from a document that is genuine but does not cover the cable delivered, so the buyer’s job is to read the scope, the standard and the sample size before accepting it as proof of anything.
Introduction
A type test report arrives as a stack of paper with test names, graphs and signatures. It looks like proof, and on many orders it is the only technical evidence the buyer ever sees. Whether it proves the cable is a separate question that the report itself has to answer.
This guide is written for the buyer who has to sign the report off. It sets out what a type test is and is not, which sections matter, how to cross-check the report against the cable delivered, and when a routine factory test is the more appropriate evidence. The wider testing picture is in our note on cable factory testing, and the certification that the report supports is in our note on the power cable certifications checklist.
What a Type Test Report Is and Is Not
A type test proves a design once. It is carried out on a sample to show that a construction meets a standard, and it is not repeated on every drum. That is normal, and it is exactly why the buyer has to check that the sample represents the cable ordered.
A type test is not a factory test. The tests done on the actual lengths delivered are the factory or routine tests, and they are the ones that show the cable that shipped meets its specification. Our note on factory versus site acceptance testing sets out how the two fit together, and the routine test matters as much as the type test when the question is what was delivered.
A report is only as strong as its scope. A report for one size does not cover another size, a report to one standard does not satisfy a different standard, and a report from one factory does not automatically describe the cable from another. The scope section is where the honest report states its limits.
A report is not a guarantee of workmanship. The best type test says the design is capable. Whether the cable delivered was made to that design is a question of consistency and of the factory tests, not of the type test. That is the gap a factory audit closes, as set out in our note on cable factory audit.
Read the report the way an engineer reads a drawing: for what it covers, and just as carefully for what it leaves out. The second reading is where the value is.
Report Types and What Each One Proves
The table sets out the documents a buyer commonly receives, what each actually proves, what to check and how each one fails to support the purchase when it is misread.
| Document | What it proves | What to Verify | Evidence to Demand | Cost and Lead-Time Driver | How It Fails |
|---|---|---|---|---|---|
| Type test report | That a design passed a defined test to a named standard | Scope, standard, sample size and factory named | The full report, not a summary page | Carried on many designs; the cost is the test programme once | A report for another size or standard accepted as covering the order |
| Routine or factory test | That the lengths delivered meet their specification | The cable reference on the results and the acceptance figures | Results per drum or per batch, keyed to the delivery | Small, done as part of normal production | Routine results accepted without being linked to the drums delivered |
| Third-party report | That an independent body tested the sample or the factory | The body's scope, the sample identity and the date | The report with the laboratory and accreditation named | Independent testing costs time and money | A third-party report that tested a sample nobody can match to the order |
| Certification certificate | That the product holds a listing under a scheme | The certificate scope, the sizes listed and its validity | The certificate with its schedule of covered products | Certificate maintenance sits with the maker | A certificate that lists a product family but not the size ordered |
| Declaration of conformity | That the maker declares a product meets a standard | Who signed it, to which standard, and on what evidence | The declaration and the test reports it refers to | Low cost, but it rests on the reports behind it | A declaration treated as evidence when the reports do not exist or do not cover the size |
Reading a Report: The Sections That Matter
The scope and the sample. Start here. The report should state the construction, the size and the standard it covers, and identify the sample. If the sample size differs from the ordered size, ask what covers the ordered size, even where the standard permits extension to other sizes.
The standard and its edition. A report to an out-of-date edition of a standard may not satisfy a specification that names the current one. Check the edition and the year, and check that it is the standard your specification asks for rather than a family one.
The test list and the results. Each test should have its method, its conditions and its acceptance criterion, and the result should be readable against that criterion. A page of numbers with no acceptance figure is not evidence the buyer can use. Where a mechanical test is claimed, the method is set out in our note on the IEC 60811 mechanical test family, and abrasion claims follow our note on the cable abrasion test standard.
The laboratory and the signature. Note who carried out the test and whether the report is from the maker’s own laboratory or an independent body. Both are legitimate, but they answer different questions, and our note on third-party cable inspection sets out when an independent view is worth paying for.
The date and the validity. A report has a date, and where a scheme requires periodic re-testing that date matters. A report that is several editions of a standard old may describe a design the factory no longer makes, which is worth knowing before it is quoted as current evidence.
What to Freeze Before the Order Goes Out
Six clauses make the test evidence checkable rather than decorative.
| Decision | What to State | Evidence to Attach | Cost of Leaving It Open |
|---|---|---|---|
| Standard and edition | The exact standard and edition the type test must be to | The report naming that standard and edition | A report to an old edition accepted as current compliance |
| Size coverage | The sizes and constructions the evidence has to cover | The report's scope and sample, or an extension statement | A report for one size relied on for a size it never covered |
| Routine test results | The factory tests to be supplied with the delivery, and their acceptance figures | Results keyed to the drums or batches delivered | Type evidence with nothing to show the delivered cable matches it |
| Independent testing | Whether a third-party report is required, and for which tests | The independent report with the body named | Paying for independence that was never actually obtained |
| Report currency | How recent the evidence must be, and whether re-testing applies | The report date and any scheme re-test requirement | Evidence describing a design or standard that has since changed |
| Submission timing | When the evidence must be submitted for approval, before despatch | A document schedule tied to the order | Reports appearing after the cable, with no chance to act on them |
Matching the Report to the Cable Delivered
The most common failure is not a forged report but a genuine one that describes something else. The discipline is to take the four things a report identifies, the construction, the size, the standard and the factory, and check each against the order and the delivery.
Then check the link to the actual lengths. The routine test results should name the drums or the batches delivered, so the type evidence and the delivered cable are connected by a reference rather than by hope. Where the factory offers a sample approval step, it is worth using it to fix the construction and its evidence together, which is the sequence in our note on the cable sample approval process.
Where a switchgear or protection interface depends on the cable’s behaviour, the report has to cover the condition that interface assumes, and the reasoning is close to the one behind our note on why factory acceptance testing matters for switchgear. The point is the same in both cases: the test has to measure the condition the design actually relies on.
Cost and Lead Time
Test evidence is rarely a line item, but it moves two things. A design tested to a standard the buyer needs usually exists already and costs nothing extra; a design that has to be tested to a new standard or a new size adds weeks to the lead time and belongs in the programme rather than in the week before delivery. Where independent testing is required, that time has to be planned as well.
Existing type test evidence is the fastest case and covers most standard constructions. Extension or additional testing for a size or a standard the factory has not covered adds both cost and time, and should be identified at the enquiry. Independent testing and certification is the longest line of the three and, where a project or a country requires it, it is a programme item rather than a purchase detail.
Incoming Inspection and What to Record
Compare the delivery to the report. Read the construction and size off the delivered drums and the drum marking, and check that they are the ones the report covers.
Collect the routine results. Get the factory test results for the lengths delivered and check that they carry the drum or batch reference, so the type evidence and the delivery are linked.
File the evidence together. Keep the type report, the routine results, the certificates and the drum markings in one file at handover, so a future question can be answered from documents rather than from memory.
Note the acceptance. Record who accepted the evidence, on what date and against which specification clause. That note is what turns a bundle of paper into a decision that can be defended later.
When a Type Test Report Is Not Enough
When the question is consistency, not capability. A type test says the design can meet the standard. Whether every drum is made to that design is a factory test and audit question, and no type report answers it.
When the report covers a different size. Where the ordered size is not the tested size, the report is evidence about a related product rather than about the purchase. Ask what covers the size ordered rather than accepting the nearest report.
When the standard does not match the specification. A report to a standard nobody asked for is not compliance with the specification, however impressive the test list. Check the standard before the results.
When the report is there instead of a routine test. Some suppliers present the type report as the whole evidence package and never supply routine results. That leaves the delivered cable unlinked to any evidence, which is the opposite of what the report is for.
RFQ Checklist
- The exact standard and edition the type evidence must be to
- The constructions and sizes the evidence has to cover
- Whether the factory has current evidence for the size ordered, or any extension applies
- Whether a third-party report is required, and for which tests
- The routine or factory tests to be supplied with the delivery
- How routine results are keyed to the drums or batches delivered
- How recent the evidence must be, and any re-test requirement
- When the evidence must be submitted, and whether it gates despatch
- Who accepts the evidence, and against which specification clause
- How the evidence will be filed with the handover records
Conclusion
A type test report is one link in a chain of evidence, and it is only useful when the construction, size, standard and factory it names are the ones you are buying and the delivered cable is tied to the factory results that go with it. Read the scope and the sample first, check the standard before the results, and connect the report to the drums on the delivery note. Most report disputes come from a document that was genuine and simply described something else, and a buyer who reads for coverage rather than for test names rarely has one.
Kexingyu Cable Group (KXYE) has manufactured cable in Quanzhou since 1996, with type test and routine test evidence across its power, control and special constructions, and a testing routine that keys results to the drums delivered. Send us the specification clause and the standard you are working to, and we will send the evidence that covers the size and construction on the order, with any gap stated plainly. A request for quotation is the fastest route.
