The commissioning report is the proof that the tests were done, by whom, with what equipment, to which procedure and with what result. A client audit does not read everything: it takes a few records at random and follows them to their supports. If each record links to the equipment tested, the test equipment with its valid calibration, the procedure with its revision, the settings with their version, the date and the signature, the report holds up.
Short answer
The commissioning report is the evidence that what was said would be tested was tested. What makes it hold up in a client audit is not its length but that each record can be followed to its supports: the equipment under test with its serial number, the test equipment with a calibration certificate valid on the test date, the procedure with its revision, the settings with their version, and the date and signature of whoever tested and whoever reviewed. What follows is the structure and what is reviewed. The same traceability logic applies to the whole dossier.
Recommended structure
- Identification. Project, location, client, scope, dates, list of equipment tested with serial numbers.
- Summary of results. What was tested, what passed and what remains open (with a link to the punch list).
- Procedures applied, with their number and revision.
- Test equipment, with identification and calibration certificate (number and validity).
- Test records, one per equipment and per test: measured values with unit, criterion and result.
- Settings in the as-found and the as-left states. See settings record.
- Nonconformities and their closure.
- Signatures of whoever tested, whoever reviewed and, if the contract asks, the client.
- Annexes: raw records from the test equipment, photos, marked-up drawings.
What it means for a record to be traceable
A test record answers six questions without asking anyone anything:
- What was tested: equipment uniquely identified (serial number, tag, location).
- With what: test equipment identified, with calibration certificate and validity on the date.
- How: procedure with its number and revision.
- Against what: settings or criteria with their version.
- When: date.
- Who: name and signature of whoever did the test and whoever reviewed it.
A record missing one of the six can be argued; one missing two is usually a finding.
How an audit follows a record
A client audit rarely reads the whole report. It takes a sample of records, for example a percentage of the total or those of the most critical equipment, and follows each:
- It opens the record and reads the equipment tested.
- It goes to the test equipment and checks that the certificate covered the test date.
- It opens the cited procedure and checks that the revision was the one in force on that date.
- It compares the cited settings with those in the file.
- It looks at the date and signature.
If the five links close, the record passes. The report is prepared for that reading: indexes, cross-numbers and a single place for each document, starting with a test plan that sets which record is expected for each piece of equipment. See what to ask for in a protection test report for the buyer’s view.
Frequent errors
- Certificate expired on the day of the test, even if it is renewed today (a criterion worth asking for when choosing a testing company). What counts is validity on the test date.
- Procedure without a cited revision, or with one different from the one used.
- A value without unit or without criterion, which cannot be judged.
- Missing signature, or one from someone who did not test.
- Settings without version, which make it impossible to know what they were compared against.
- Corrections over the original, instead of a new revision.
Worked example
Example data (assumed): report of a commissioning with 48 test records. Each record must have 6 mandatory items (equipment, test equipment with calibration, procedure with revision, settings with version, date and signature). The client audit takes 10 % of the records. In the review before delivery, the client’s signature is found missing on 2 records and the procedure revision on 1.
- Audit sample: 48 × 10 % = 4.8; 5 records are taken.
- Items required: 6 × 48 = 288.
- Items missing: 2 + 1 = 3. Items found: 288 − 3 = 285, which is 285 / 288 = 0.990, or 99.0 %.
- Complete records: 48 − 3 = 45 (each gap is in a different record), which is 45 / 48 = 0.938, or 93.8 %.
- Reading the result: with 3 incomplete records out of 48, a sample of 5 can land on one of them. That is why the sample is not relied on: the 3 are corrected.
The 3 gaps are corrected before delivery, with the date and name of whoever corrects them, in a new revision of the report. With that, the count stands at 288 of 288.
How a delivered report is corrected
A delivered report is not rewritten. A new revision is issued, with its number and date, a short list of what changed and who changed it, and the previous revision is kept. The auditor can then see that the change was deliberate and recorded, not a quiet edit. If the change is to a measured value, the raw record that supports it is attached; if it is to a signature, the signature date is the date it was signed, not the original.
What is delivered and what is kept
The client receives the report with its annexes. The supplier also keeps the original files from the test equipment (the raw data), the settings file in its as-found and final states, and the calibration certificates of each piece of equipment used. The retention period is set by the contract and the client’s management system.
A mock audit before delivery
Before delivery, a person who did not do the tests takes a sample of records, preferably those of the most critical equipment, and follows them as the audit would: equipment, calibration on the date, procedure and revision, settings and version, date and signature. What does not close is corrected before delivery. It is an hour of work that saves a finding.
When it is issued
The report is issued when the tests are finished and the A and B punch items are closed or accepted in writing. If some tests can only be done with the equipment in service, a partial report and a supplementary one are issued, each with its scope stated. Avoid a single report that stays open for months: it is hard to audit, because nobody knows which version is the current one.
What not to do
- Do not deliver a report without a prior check, record by record, of the six items.
- Do not write just “pass”: give the measured value and the criterion.
- Do not overwrite a delivered version: issue a new revision.
- Do not use calibration certificates without checking that they covered the test date.
- Do not leave the raw records out of the dossier.
Checklist
- Equipment under test with unique serial number.
- Test equipment with a certificate valid on the date of each test.
- Procedures with number and revision, and the revision in force on the date.
- Settings in as-found and final state, with version.
- Measured values with unit and criterion in each record.
- Date and signature of whoever tested and whoever reviewed.
- Nonconformities and punch items linked, with their closure.
- Index and cross-references between records, annexes and drawings.
- Report revision with change control.
Related guides
- Commissioning dossier: protocols, reports and as-built
- What to ask for in a protection test report
- Settings record: as-left and as-found
- Relay test plan
- How to choose an electrical testing company
- Commissioning levels
References
- The requirements of each project come from the contract and from the standard for each test.
Need this study?
We design the report structure, the version control and the traceability matrix as part of our engineering design and studies service, for projects in any country. Contact us.
Frequently asked questions
What evidence does an audit look at first?
The usual approach is to take a sample of test records and follow each to its supports: that the equipment under test is identified, that the test equipment had valid calibration on the test date, that the procedure and the settings are of the right version, and that the record has a date and a signature. A broken link at any of these points is usually a finding.
What happens if a missing item is found after the report is delivered?
It is corrected with a new revision of the report, which keeps the previous one, states what changed, who changed it and when, and is delivered again. The original report is not rewritten: traceability requires the change to be visible.
Must the report include the measured values, or are pass and fail enough?
It must include the measured values with their unit and the criterion they were compared against. A pass without a value cannot be reviewed or compared with the next test. The raw records of the test equipment go as an annex.