Industry TemplatesFree templatePDF, Excel, Word exportFiber Optics

Fiber Optic Certification Test Acceptance Report Template

Handover is where fiber work becomes a deliverable. This acceptance report packages the test method, criteria and per-link results so the client can sign for what they received.

Fill in

Live preview
Download:

Fiber Optic Certification Test Acceptance Report Template

Fiber Certification Test Report

Project: Plant 2 backbone upgrade Client: Harlow Industrial Components Contractor: Summit Cabling Services Test date: 2026-10-20 Tester: T. Okafor

Test Equipment and Method

Equipment: Power meter and source, S/N PM-3321 Calibration due: 2027-02-15 Method: Tier 1 and Tier 2 (OTDR) Wavelengths: 1310 nm and 1550 nm

Acceptance Criteria

Total link loss at or below the calculated loss budget. No splice event above 0.30 dB. Connector pairs at or below 0.50 dB.

Link Results

Link IDFiber typeLength (m)Loss 1310 (dB)Loss 1550 (dB)Budget (dB)Pass / Fail

Attachments

Raw test files attached: Yes / No OTDR traces attached (both directions): Yes / No End face inspection images attached: Yes / No

Acceptance

Test technician / Date
Contractor representative / Date
Client representative / Date

Tier 1 and Tier 2 follow common industry usage. Use the standard or contract that applies to your project for exact limits. This template is a starting point and not legal advice.

Generate handover packs from tester data

Optional conversation about assembling test reports from tester exports.

Optional. The tool and every export work without this. No spam.

How to use the report

Fill the project, equipment and method fields. State the acceptance criteria explicitly, since a result table without a criterion proves nothing. Export to PDF or Word and add one table row per link tested. Attach the raw files from the tester, because acceptance records usually need the native data and not only a summary.

  • Include calibration due date for the tester
  • State the method used for the reference
  • Attach both directions of any OTDR trace

Tier 1 and Tier 2 testing

Tier 1 certification measures loss with a light source and power meter, and checks length and polarity. Tier 2 adds OTDR traces to characterize events along the link, such as splices, connectors and bends. Many specifications require Tier 1 on all links and Tier 2 on a sample or on all links over a certain length. Record which one you applied in the method field.

Pass criteria and the loss budget

The budget is calculated from fiber attenuation, number of splices and number of connector pairs, plus margin. Compare measured loss to this calculated budget per link. If your contract sets fixed per-event limits, list them in the criteria. Document any link that passes the budget but contains a single event much worse than the rest, since it may become a failure later.

Common mistakes

Reporting loss without stating the reference method, using a tester outside its calibration, testing only one direction on OTDR and omitting the connectors from the budget. Also avoid summarizing failures as passes after rework without retaining the original trace. Keep both the failed and the retested results in the record.

Frequently Asked Questions

What belongs in the acceptance criteria?

State the maximum link loss or the formula used to compute it, any per-event limits for splices and connectors, and the wavelengths covered. Cite the standard or specification clause that your contract references.

Do I need OTDR on every link?

Not always. Many specs require Tier 1 loss testing on every link and OTDR on longer links or a sample. Follow your contract, and note in the report which links received OTDR.

How many copies should the client get?

Provide the signed report plus the native tester files and traces. Keep a copy in your own records for the warranty period or the retention period in your quality system.

What if a link fails?

Record the failure, the corrective action, and the retest. Keep the original result in the file, and list the retest as a new row with a note, so the history is transparent.

If you build the same report for many sites, we can help generate it from tester exports and your project data.