A transformer test record should contain enough information for another engineer to repeat the test, understand the result and compare it with the correct baseline years later. That means more than the measured value: it requires transformer identification, test conditions, instrument and calibration details, raw data, the calculation method, the verdict and the people responsible.
A complete record is what turns a set of readings into evidence that supports an acceptance, a maintenance decision or a fault investigation.
What a Test Record Must Identify
The record must identify the object of the test without ambiguity: manufacturer, type, serial number, year of manufacture, rated voltage, rated power, vector group and the tap position relevant to the test. On multi-winding transformers, the winding tested and the terminals used must be named. A record that cannot be tied to a specific unit and a specific terminal arrangement loses most of its value the moment it leaves the test site.
Identification also includes the reason for the test: factory acceptance, site commissioning, routine maintenance, post-transport verification or post-fault investigation. The reason sets the context for the acceptable comparison, because a post-fault record is compared with the pre-event baseline, while a commissioning record becomes the new baseline for the unit’s life.
Conditions, Instruments and Calibration That Belong in the Record
Test results change with conditions. Ambient temperature, winding temperature, humidity and weather all belong in the record because they affect insulation measurements and resistance readings. Winding temperature is especially important for resistance tests, where the result is corrected to a reference temperature before comparison with the factory baseline. Record the temperature measurement method as well as the value, so the correction can be reproduced.
Every reading should be traceable to an instrument: the instrument model, serial number and calibration date. A result that cannot be connected to a calibrated instrument is difficult to defend in an acceptance dispute. Where the test method affects the result, name the method and the settings, including test voltage, test current, frequency where relevant and the measuring time at which the reading was taken.
Raw Data, Calculations and the Verdict
Record the raw readings, not only the final corrected values. A later reviewer may need to check the calculation, apply a different correction or investigate an anomaly, and that is impossible if only the conclusion was written down. For a winding resistance measurement, the raw value, the temperature and the corrected value belong together. For an insulation test, the timed readings and the calculated ratios belong together.
The verdict should state what was compared and why the result is acceptable or not: the measured value against the factory baseline, the phase-to-phase spread, the pattern across tap positions, or the criterion in the applicable standard or specification. A verdict without its basis is an opinion; a verdict with its basis is a decision that another engineer can review.
Factory Reports vs Site Records
Factory reports and site records serve different purposes and should not be confused. The factory report proves what the unit achieved before dispatch: routine tests on the unit itself, type tests on the design, and any special tests agreed in the contract. The site record proves what was verified after transport, installation and commissioning, and it becomes the operating baseline. The two sets of data are compared, not merged.
Site records should reference the factory report so that the comparison is easy to reproduce: the factory ratio deviation and the site ratio deviation, both corrected to the same conditions, are the evidence that transport did not change the winding relationships. Where the factory report uses a different reference temperature or test method, the site record should say so rather than silently comparing unlike values.
Baselines, Trends and Retention
The purpose of a record is comparison over time. A single measurement is a snapshot; the same measurement repeated on the same unit under the same conditions is a trend. Trends reveal gradual deterioration that no single value can show, which is why the record format should make repeat comparison easy: fixed fields, fixed units, fixed tap positions and fixed correction conventions from year to year.
Retention policy should reflect the life of the evidence. Acceptance records may need to survive the warranty period and the life of the unit; trend records need to be accessible whenever the next test is scheduled. Store records where the test team can actually retrieve them, with the unit serial number as the primary key, and protect them against loss when systems change.
Digital records make comparison easier but introduce their own discipline. A spreadsheet full of readings without headers, units or dates is no better than a paper record left in a drawer. Define the record template once, including the field names and units, and use the same template for every test and every tester. Add a review step before the record is filed: a second engineer checks that the identification matches the unit, the readings are internally consistent, the temperature and calibration fields are complete, and the verdict follows from the stated comparison. A worked example shows the value: a winding resistance result of 1.240 Ω at 28 °C, corrected to 1.312 Ω at 75 °C using the copper constant, is only meaningful when the record also shows the factory baseline of 1.305 Ω at 75 °C and the phase spread across the other windings. Without those three reference points, the single corrected value cannot support an acceptance decision.
Name the people behind the record. The test record should identify who performed the test, who reviewed it and who approved the verdict, with their roles rather than initials alone. Responsibility gives a record its weight: an acceptance decision signed by the responsible engineer is an action, while an unsigned set of readings is only data.
A Transformer Test Record Checklist
| Field group | What to include |
|---|---|
| Object identity | Manufacturer, serial number, type, ratings, vector group, winding and terminals tested. |
| Context | Reason for test, tap position, date, location and the responsible organisation. |
| Conditions | Ambient and winding temperature, humidity and measurement method. |
| Instrument | Model, serial number, calibration date and test settings. |
| Data | Raw readings, timed values, calculations and corrected results. |
| Verdict | Comparison basis, criterion, conclusion and the name and role of the person signing. |
Frequently Asked Questions
What fields must a transformer test record include?
At minimum: transformer identification, the reason for the test, the tap position and terminals tested, ambient and winding temperature, instrument and calibration data, raw readings, the calculation or correction used, the comparison basis and the signed verdict. Include everything needed to repeat the test and reproduce the comparison.
How do I identify the transformer in the report?
Use the manufacturer, serial number, type and ratings, together with the winding and terminal arrangement tested. The record should point to one specific unit and one specific test point, so that it can be matched to the factory report and to earlier and later site records.
Why keep a baseline record?
A baseline is the reference against which all later results are judged. Without a baseline, a change caused by transport, a fault or gradual deterioration cannot be distinguished from normal variation. The commissioning record usually becomes the baseline for the operating life of the unit.
For the instruments used in commissioning tests, see the transformer commissioning test equipment range, and for the complete test programme read What Tests Are Required for a Power Transformer.