WIRETRACE UK

Editorial & testing methodology

A useful answer needs a visible evidence trail.

Four labels, kept separate

What an original test must record

Record the sample ID, wiring and fault location, reference length, cable material and screening, instrument model and firmware, mode and adapters, calibration where relevant, far-end state, date, repeat count and original readings. Keep expected behaviour separate from observed behaviour. An empty value means unmeasured, not zero.

For PoE, state where voltage and power were measured, the PSE and PD models, allocated budget, actual loads and operating modes. For tracing, record the cable bundle, shielding, connected state and confirmation method.

Limits stay with the result

A successful test on one unit does not establish all production revisions. Continuity is not certification. A negotiated Ethernet rate is not an entire performance test. PoE detection is not a load test. Any claim must remain within the method that produced it.

Sources and revisions

Guides name their references and display an update date. Manufacturer documents establish model-specific specifications; formal standards and project requirements establish acceptance limits. Secondary tutorials can help explain a subject, but their figures and terminology need checking. We do not reproduce paywalled standards or imply that a public summary is the full standard.

Corrections

Our correction policy is to revise the affected statement and conclusion, explain a material change, and record the revision date. This applies equally to products sold by associated retailers.

Download our blank test-record template →