What is test documentation?

The written record of commissioning — what was tested, how, with what, the result, and who signed it.

TEST DOCUMENTATION · THE WRITTEN EVIDENCE PLANNED · RECORDED · CHECKED · SIGNED · FILED 1 PLAN Test plan agreed Limits stated Sheets prepared RECORD: test plan 2 RECORD Values written live Date, time, tester Instrument noted RECORD: test sheets 3 VERIFY Within the limits Calibration current Nothing left blank RECORD: check 4 SIGN Tester signs Witness signs Engineer signs RECORD: sign-offs 5 FILE Report compiled Indexed, traceable In handover pack RECORD: test report RECORD COMPLETE? TRACEABLE · SIGNED · WITHIN LIMITS 6 INCOMPLETE OR UNCLEAR CORRECT · RE-TEST · RE-FILE COMPLETE READY FOR HANDOVER SCHEMATIC · STEPS SHORTENED · NOT TO SCALE
documentation step
record kept
incomplete
complete
The Fact Commissioning practice

Test documentation is the written evidence that the system was tested and passed. Results are recorded at the time on test sheets that show the circuit, the method, the limit, the measured value, the date, the tester and the instrument used.

Each record is checked against its limit, then signed by the tester and the witness. A mistake is fixed by a dated correction, never by erasing. Complete records are compiled into the test report, indexed and delivered in the handover pack, so the system has a traceable baseline for later maintenance.

  1. Plan. Agree the test plan, the limits and the test sheets before testing starts.
  2. Record. Write each value as it is measured, with date, tester and instrument.
  3. Verify. Compare every result with its limit and confirm the instrument calibration is current.
  4. Sign. The tester, the witness and the responsible engineer sign each record.
  5. File. Compile and index the test report and include it in the handover pack.
  6. Correct. Fix any gap or error by a dated entry and re-test where the result is in doubt.
Purpose Prove what was tested, how, and that it passed
Record shows Item, method, limit, value, result, date, tester, instrument
Rule Record at the time; correct by dated entry, never erase
Signed by Tester, witness and responsible engineer
Output Indexed test report in the handover pack
Reference ICAO Doc 9157 Pt 5; project contract and test plan
Schematic — steps shortened for clarity. Record formats, required signatures, retention and the content of the test report are set by the contract, the project test plan and the applicable standard. Live work follows your site’s permit-to-work procedure.
Entry 30 · Commissioning sequence Full Index · Division 13

Frequently Asked Questions

Q1What is test documentation in airfield ground lighting?

The written record of everything tested during commissioning: the test plan, the completed test sheets, the instruments used, the results against the limits, and the signatures. It is the evidence that the system was tested and that it passed.

Q2Why must test results be recorded at the time?

Values written down as they are measured are reliable and traceable. Results filled in later from memory can be wrong and cannot be defended. Each entry should show the value, the date, who tested and the instrument used.

Q3What should a test sheet show?

The circuit or item tested, the test method, the limit that applies, the measured value, the pass or fail result, the date, the instrument and its calibration reference, and the signatures of the tester and the witness where required.

Q4Why does instrument calibration matter?

A reading is only as good as the instrument behind it. Recording the instrument and its calibration certificate shows the results can be trusted, and lets a reading be checked or repeated later with the same confidence.

Q5How is a mistake in a test record corrected?

By a dated and initialled correction, with the original entry left readable. If the result is in doubt the test is repeated and the new result is recorded. Erasing or overwriting an entry removes the evidence and should not be done.

Q6What happens to the test documentation after commissioning?

It is compiled into a test report, indexed so each record can be traced to its circuit, and delivered in the handover pack. It becomes the baseline for later maintenance, so future readings can be compared with the commissioning values.

Precision AGL Academy

See It. Understand It. Then Learn How to Engineer It.

Recognising an AGL system visually is the first step. The next step is knowing how to design, install, test, commission and maintain them correctly.

Build Practical AGL Engineering Skills

Go deeper with structured training from Precision AGL Academy, covering:

AGL Fundamentals Design & Electrical Engineering Approach Lighting Photometry Installation & Commissioning Maintenance & Troubleshooting

Learn how each light, sign and circuit works as part of a complete airport lighting system, not just as an isolated diagram.

See. Understand. Apply. Engineer.