Industry TemplatesFree templatePDF, Excel, Word exportFiber Optics

OTDR Test Report Template

An OTDR report is the evidence that a fiber link was built and tested to specification. Use this template to record instrument settings, the event table, total loss and sign-off, then export a clean PDF or Word file.

Fill in

Live preview
Download:

OTDR Test Report Template

OTDR Test Report

Contractor: Northline Fiber Services Project: Plant 2 backbone upgrade Link ID: BB-02-A Test date: 2026-10-19 Technician: A. Singh

Link Details

End A: MDF Rack 3, Panel 1 End B: Building B IDF, Panel 2 Fiber type: OS2 single-mode Measured length: 2,418 m Launch and receive cables: 150 m each

Instrument and Settings

OTDR: Model OTDR-X / SN 000123 Calibration due: 2027-03-01 Wavelengths: 1310, 1550 Pulse width: 100 ns Range: 5 km IOR: 1.4682 Averaging: 30 s

Event Table

Event #TypeDistance (m)Loss (dB)Reflectance (dB)Result
1Connector (launch)
2Splice
3Splice
4Connector (end)

Results

Total link loss: 1.62 at 1310 nm, 1.31 at 1550 nm Optical return loss: 38.4 at 1550 nm Acceptance limits: Splice 0.1 dB avg, connector 0.5 dB, link 2.5 dB Overall result: Pass

Comments

All events within limits. Trace files saved with the link ID in the file name.

Sign-off

Test technician / Date
Contractor supervisor / Date
Customer representative / Date

Attach the native OTDR trace files (for example SOR) with the report. Confirm the acceptance limits and the required test standard in your contract. This template is a starting point and should be adapted to project requirements.

Want a test report library inside your system?

We can talk about storing and searching test reports against assets or work orders in your ERP, on-prem.

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

How to use the template

Fill the link details, instrument and calibration information, and test settings in the form fields. Enter the total loss and return loss from your trace and choose the overall result. The document includes a blank event table for you to complete or edit after export, plus a comments area and signature lines. Create one report per link, or per fiber if your contract requires it, and attach the native trace files so the customer can verify the numbers independently.

  • Record the instrument serial and calibration due date
  • Use launch and receive cables so the first and last connectors can be measured
  • Keep pulse width and IOR consistent between directions
  • Name trace files with the link ID, fiber number and wavelength

What a good report contains

At minimum an OTDR report should identify the link, the technician and the date, then list the instrument, wavelengths, pulse width, range, IOR and averaging time so the test can be repeated. It should list each event with distance, loss and reflectance, the total link length and loss, and a pass or fail against stated limits. Many specifications also require bidirectional measurements and a power meter test for total insertion loss, because an OTDR is less accurate for end-to-end loss than a light source and power meter.

Reading the event table

Events are points where the trace changes. Non-reflective events are splices or bends and show only loss. Reflective events such as connectors show loss and a reflectance value in negative dB, where a more negative value is better. A sudden large loss without a connector may indicate a macrobend or a damaged fiber. Compare the distance of events with the as-built drawing and investigate any event that has no matching physical component.

Common mistakes

Frequent report errors are an incorrect IOR that skews the length, a pulse width too long to resolve closely spaced connectors, forgetting launch cables, and testing in only one direction. Reports that say pass without showing limits are weak evidence. Also confirm the calibration is current: a test with an expired instrument calibration can be rejected at handover.

Frequently Asked Questions

What should an OTDR test report include?

Link identification, technician and date, instrument and calibration details, test settings, event table with distances and losses, total loss and length, acceptance limits, a pass or fail result, and the trace files. Signatures are usually required.

Do I need both directions on an OTDR report?

For splice loss acceptance, yes. Bidirectional averaging removes backscatter differences that can make one direction look like a gain or an exaggerated loss. Many contracts require both directions for every fiber.

Is an OTDR enough for total link loss?

Often not. Contracts commonly require a light source and power meter test for end-to-end insertion loss because it is more accurate, and an OTDR for event detail and fault location.

What file format should trace files be in?

The standard exchange format is SOR (Telcordia SR-4731). Provide native trace files alongside the PDF so the customer can open them in any compatible viewer and check the events.

If you want test reports, inspection records and cable assets connected inside your own ERP or quality system, we can discuss a private deployment.