# OTDR Test Report Template

> Source: https://netray.co/tools/otdr-test-report-template
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

Generate a clean OTDR test report with instrument settings, event table, total loss and sign-off, ready to export as PDF or Word.

## Category

industry-templates

## Industry

Fiber Optics

## Audience

- Test technician
- Fiber optic engineer
- Project manager

## Tool

**Kind:** template

**Output:** document

**Fields:**

#### Contractor / company

**Key:** company

**Type:** text

**Default:** Northline Fiber Services

#### Project

**Key:** project

**Type:** text

**Default:** Plant 2 backbone upgrade

#### Link / cable ID

**Key:** link_id

**Type:** text

**Default:** BB-02-A

#### End A location

**Key:** end_a

**Type:** text

**Default:** MDF Rack 3, Panel 1

#### End B location

**Key:** end_b

**Type:** text

**Default:** Building B IDF, Panel 2

#### Test date

**Key:** date

**Type:** date

**Default:** 2026-10-19

#### Technician

**Key:** tech

**Type:** text

**Default:** A. Singh

#### OTDR model and serial

**Key:** instrument

**Type:** text

**Default:** Model OTDR-X / SN 000123

#### Calibration due date

**Key:** cal_date

**Type:** date

**Default:** 2027-03-01

#### Fiber type

**Key:** fiber_type

**Type:** select

**Options:**

- OS2 single-mode
- OM3 multimode
- OM4 multimode
- OM5 multimode
- OS1 single-mode

**Default:** OS2 single-mode

#### Test wavelengths (nm)

**Key:** wavelengths

**Type:** text

**Default:** 1310, 1550

#### Pulse width

**Key:** pulse

**Type:** text

**Default:** 100 ns

#### Distance range

**Key:** range

**Type:** text

**Default:** 5 km

#### Index of refraction

**Key:** ior

**Type:** text

**Default:** 1.4682

#### Averaging time

**Key:** avg_time

**Type:** text

**Default:** 30 s

#### Launch / receive cable length

**Key:** launch

**Type:** text

**Default:** 150 m each

#### Measured link length

**Key:** length

**Type:** text

**Default:** 2,418 m

#### Total link loss (dB)

**Key:** total_loss

**Type:** text

**Default:** 1.62 at 1310 nm, 1.31 at 1550 nm

#### Optical return loss (dB)

**Key:** orl

**Type:** text

**Default:** 38.4 at 1550 nm

#### Acceptance limit

**Key:** limit

**Type:** text

**Default:** Splice 0.1 dB avg, connector 0.5 dB, link 2.5 dB

#### Overall result

**Key:** result

**Type:** select

**Options:**

- Pass
- Fail
- Pass with comments

**Default:** Pass

#### Comments

**Key:** comments

**Type:** textarea

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

**Blocks:**

#### OTDR Test Report

**Body:** Contractor: {{company}}
Project: {{project}}
Link ID: {{link_id}}
Test date: {{date}}
Technician: {{tech}}

#### Link Details

**Body:** End A: {{end_a}}
End B: {{end_b}}
Fiber type: {{fiber_type}}
Measured length: {{length}}
Launch and receive cables: {{launch}}

#### Instrument and Settings

**Body:** OTDR: {{instrument}}
Calibration due: {{cal_date}}
Wavelengths: {{wavelengths}}
Pulse width: {{pulse}}
Range: {{range}}
IOR: {{ior}}
Averaging: {{avg_time}}

#### Event Table

**Table:**

**Columns:**

- Event #
- Type
- Distance (m)
- Loss (dB)
- Reflectance (dB)
- Result

**Rows:**

**0:** 1

**1:** Connector (launch)

**0:** 2

**1:** Splice

**0:** 3

**1:** Splice

**0:** 4

**1:** Connector (end)

#### Results

**Body:** Total link loss: {{total_loss}}
Optical return loss: {{orl}}
Acceptance limits: {{limit}}
Overall result: {{result}}

#### Comments

**Body:** {{comments}}

#### Sign-off

**Signatures:**

- Test technician
- Contractor supervisor
- Customer representative

**Notes:** 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.

## Content

**Intro:** 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.

**Sections:**

#### How to use the template

**Body:** 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.

**Bullets:**

- 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

**Body:** 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

**Body:** 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

**Body:** 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.

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

**Faq:**

#### What should an OTDR test report include?

**Answer:** 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?

**Answer:** 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?

**Answer:** 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?

**Answer:** 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.

## Search terms

OTDR test report template, OTDR report format, fiber optic test report sample, OTDR trace report, fiber certification report template, OTDR test record word, fiber optic acceptance report, OTDR event table template

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json