Acceptance Testing vs Commissioning Testing:
Why the Difference Matters
Two tests that sound similar but serve entirely different purposes — and why confusing them creates real liability at project handover.
On This Page
The Confusion Is Common — and Consequential
The terms acceptance testing and commissioning testing are often used interchangeably on fiber infrastructure projects. They are not the same test. They serve different purposes, are performed by different parties, and produce different legal and contractual outcomes. Confusing the two — or substituting one for the other — leaves clients without the protection they think they have.
Commissioning testing asks: Does this network meet the design specification? Acceptance testing asks: Should this client accept this network from this contractor? These are related but distinct questions, and only one of them protects the client at handover.
Commissioning Testing — What It Is and Who Does It
Commissioning testing is performed at the end of the installation phase, before the network goes live. Its purpose is to verify that the fiber network, as built, meets the design specification — that the loss per span is within the loss budget, that every splice meets the loss threshold, and that every connector passes end-face inspection.
Commissioning testing is typically performed by the installation contractor or by a testing specialist engaged by the contractor. The results are submitted as part of the project close-out documentation.
Commissioning testing answers the contractor's question: is my work done? It does not answer the client's question: Should I accept this work?
What commissioning testing produces:
- ✓ OTDR trace for every fiber run, per the installation specification
- ✓ Insertion loss measurement per fiber at the design wavelength
- ✓ Loss budget calculation showing actual vs. designed margin
- ✓ Pass/fail determination per fiber against the installation specification
- ✓ Commissioning sign-off report — typically submitted by the contractor to close the project
Acceptance Testing — What It Is and Who Does It
Acceptance testing is independent verification — performed by a party engaged by the client, not the contractor. Its purpose is to confirm, using the client's measurements, that the installed fiber meets the performance standard specified in the contract before the client formally accepts the work and assumes ownership of any defects.
This is the critical distinction: acceptance testing is performed by an independent party. The contractor's own commissioning documentation cannot serve as acceptance testing, because the contractor has an interest in passing the test. An acceptance test report produced by Fiber Saber — engaged by the client — is independent evidence that the client can use at handover, in a contractor dispute, or in an insurance claim.
What acceptance testing produces:
- ✓ Independent OTDR characterization — Fiber Saber's own measurements, not the contractor's
- ✓ Splice loss audit — every splice point measured and documented
- ✓ Connector end-face inspection per IEC 61300-3-35 — pass/fail per zone
- ✓ Loss budget verification against the contract specification
- ✓ Acceptance test report — independent, client-owned, suitable for dispute resolution
- ✓ Identified deficiencies with remediation recommendations, before the client formally accepts
An acceptance test report produced by an independent party is a document owned by the client. If the contractor disputes a deficiency, the client has independent evidence. If the network fails six months later, the client has a baseline that proves the condition at the time of handover. The contractor's own commissioning documentation provides neither of these protections.
The Sequence That Protects the Client
The correct sequence is:
The contractor performs commissioning testing and submits the commissioning report.
01The client engages an independent testing firm to perform acceptance testing before formal handover.
02The acceptance test report identifies any deficiencies and specifies remediation requirements.
03The contractor remediates deficiencies.
04The independent firm retests the remediated items.
05The client formally accepts the work.
06In practice, most projects skip steps 2 through 5. The client accepts the contractor's commissioning documentation as sufficient evidence of network performance. When problems surface months later, the contractor is no longer on-site, the deficiencies cannot be attributed to the original installation, and the client has no documented baseline to reference.
When Each Test Is Appropriate
| Commissioning Testing | Acceptance Testing | |
|---|---|---|
| Purpose | Verify contractor's work meets spec | Verify the network before the client accepts it |
| Performed by | Contractor or contractor's tester | Independent party engaged by the client |
| Report ownership | Contractor | Client |
| Suitable for dispute resolution | No | Yes |
| Establishes a baseline that the client owns | No | Yes |
The Bottom Line
If you have only one of these tests, make it the acceptance test — performed by an independent party, before you accept the contractor's work. The commissioning test indicates that the contractor believes the work is complete. The acceptance test tells you whether you should agree.
Put this into practice on your own network.
Talk to a Fiber Saber engineer about your specific infrastructure — no sales layer, direct technical conversation.
