OSP Fiber Optic OTDR Bidirectional Test Report
Use this bidirectional OTDR test report to document outside plant fiber acceptance, trace-by-trace, with splice loss, connector reflectance, and end-to-end attenuation recorded for each span.
Trusted by frontline teams 15 years of frontline software AI customization in seconds
Built for: Telecommunications · Data Centers · Utilities · Construction
Overview
This template is an outside plant fiber optic OTDR bidirectional test report for documenting acceptance of a fiber span from end to end. It captures the project and route details, safety readiness, OTDR setup, bidirectional trace evidence, splice-by-splice loss, connector reflectance, end-to-end attenuation, and the final closeout record in one place.
Use it when a fiber route needs acceptance testing, repair verification, or turnover documentation and the owner wants traceable evidence rather than a simple pass/fail note. The report is especially useful for single-mode outside plant links where launch and receive fibers are needed to resolve the first and last events, and where bidirectional averaging is required to judge splice loss fairly. It also works well when a customer, AHJ, or internal quality team expects the trace files, event tables, and supporting photos to be attached.
Do not use this template as a casual field checklist for a quick continuity test or for jobs where no OTDR evidence is required. It is not a substitute for a construction punch list, and it should not be used without matching the acceptance criteria to the project specification, wavelength plan, and fiber type. If the span has unresolved damage, missing reference jumpers, or a test setup that cannot produce valid bidirectional results, the report should document the deficiency rather than forcing a false pass.
Standards & compliance context
- This template supports quality records commonly expected under ISO 9001:2015 by preserving objective evidence of inspection, measurement, and disposition.
- For outside plant work, the safety section helps document controlled work practices consistent with applicable OSHA requirements and site-specific traffic or utility corridor controls.
- If the project is part of a telecommunications build, the acceptance criteria should align with the owner’s specifications and recognized fiber testing practices used in the industry.
- Where the work occurs in a construction environment, the report can be paired with contractor safety documentation and competent-person oversight as required by the job plan.
- If an AHJ, customer, or utility owner requires witness signoff, the closeout section provides a place to capture that approval without altering the test record.
General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.
What's inside this template
Test Identification and Route Details
This section anchors the report to a specific span, wavelength plan, and acceptance standard so the rest of the measurements can be tied to the correct route.
- Project name, route ID, and fiber span identified
- Test date and time recorded
- Cable type, fiber count, and wavelength(s) documented
- Test endpoints and direction of travel identified
-
Reference standard and acceptance criteria noted
Document project acceptance criteria and applicable standard references, such as TIA-568 requirements and project specifications.
Safety and Test Readiness
This section confirms the crew can test safely and that the OTDR setup is valid before any trace is captured.
-
Work area controlled and traffic/public exposure managed
Verify the test area is safe for OSP field work, including traffic control, access control, and site-specific hazards.
-
PPE appropriate for OSP fiber work in use
Confirm required PPE is worn, including eye protection and any site-specific PPE for the work location.
-
Fiber ends cleaned, capped, and laser safety precautions followed
Confirm connector endfaces are clean and optical safety practices are followed before connecting test equipment.
- OTDR, launch fiber, receive fiber, and adapters available and verified
-
Test equipment calibration status valid
Verify the OTDR and any power meter or light source used are within calibration or verification interval.
Bidirectional OTDR Trace Capture
This section preserves the raw evidence from both directions, which is essential for resolving event location and validating splice loss.
-
Trace captured from end A to end B
Upload the OTDR trace image or file reference for the A-to-B direction.
-
Trace captured from end B to end A
Upload the OTDR trace image or file reference for the B-to-A direction.
-
Launch fiber length sufficient to resolve first event
Record launch fiber length used for the test. It must be long enough to separate the first connector or splice event from the OTDR dead zone.
- Receive fiber length sufficient to resolve end event
- OTDR pulse width, range, and averaging settings documented
-
Event table exported or attached
Attach the OTDR event table or file export used to support splice and connector analysis.
Splice-by-Splice and Connector Measurements
This section turns the trace into actionable measurements by documenting loss, reflectance, and any non-conforming events at each point in the link.
-
Splice loss values recorded for each event
Document splice-by-splice loss for all identified fusion or mechanical splice events.
- Connector insertion loss recorded for each end connection
-
Reflectance measured for connector events
Record reflectance or return loss values for connector events where applicable.
-
Bidirectional average loss calculated for each splice
Confirm splice loss is averaged from both directions where required by the test method.
- Non-conforming events identified and explained
End-to-End Attenuation and Acceptance
This section states whether the full span meets the project’s attenuation and reflectance limits and whether continuity is confirmed.
-
End-to-end attenuation recorded for each wavelength
Document total link attenuation for each tested wavelength and direction as applicable.
- Measured attenuation within project acceptance limit
- Reflectance or ORL within project acceptance limit
- Fiber continuity verified end to end
Closeout and Documentation
This section locks the record by attaching files, noting corrective actions, and capturing the required signatures for turnover.
- All trace files, event tables, and supporting photos attached
- Deficiencies and corrective actions documented
- Inspector signature
-
Customer or AHJ witness signature
Use when required by project specifications, customer handoff, or Authority Having Jurisdiction.
How to use this template
- 1. Enter the project name, route ID, fiber span, cable type, fiber count, test wavelengths, endpoints, and acceptance criteria before the field test begins.
- 2. Confirm the work area is controlled, PPE is in use, fiber ends are cleaned and capped, and the OTDR, launch fiber, receive fiber, adapters, and calibration status are ready.
- 3. Capture OTDR traces from end A to end B and from end B to end A using documented pulse width, range, and averaging settings, then export the event table.
- 4. Record splice loss, connector insertion loss, and reflectance for each event, and calculate the bidirectional average loss for every splice that appears in both directions.
- 5. Compare end-to-end attenuation and reflectance or ORL against the project limits, mark any non-conforming events with an explanation, and attach all files and photos before obtaining signatures.
Best practices
- Use the same reference standard and acceptance criteria for every span in the project so results can be compared consistently.
- Make the launch and receive fiber lengths long enough to separate the first and last events from the dead zones of the OTDR.
- Clean and inspect every connector before each trace, because contamination can create false loss and reflectance readings.
- Document the exact OTDR settings used for each wavelength, including pulse width, range, and averaging, so the trace can be reproduced later.
- Photograph the labeled endpoints, test setup, and any visible defects at the time of testing, not after the crew has moved on.
- Flag any splice or connector that fails the project limit as a non-conformance and describe the likely cause instead of leaving it as an unexplained note.
- Keep bidirectional results paired by event location so the average loss reflects the same physical splice in both directions.
- Attach the raw trace files and event tables, not just screenshots, so the acceptance record can survive audit or dispute review.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What does this OTDR bidirectional test report cover?
This template captures the full acceptance record for an outside plant fiber span, including project and route details, safety readiness, bidirectional OTDR traces, splice-by-splice loss, connector reflectance, and end-to-end attenuation. It is designed to show whether the installed link meets the project’s acceptance criteria at the tested wavelengths. Use it as the closeout record for new builds, repairs, or restoration work where trace evidence matters.
When should I use a bidirectional OTDR report instead of a simple continuity check?
Use this template when the job requires acceptance-level evidence, not just proof that light passes end to end. Bidirectional OTDR testing is appropriate when you need to locate events, verify splice loss, compare both directions, and document reflectance or ORL concerns. A continuity check alone will not show whether a splice, connector, or bend is within tolerance.
Who should complete this inspection?
A qualified fiber technician, test engineer, or field inspector should complete it, ideally someone trained to interpret OTDR traces and event tables. The person running the test should understand launch and receive fiber setup, wavelength selection, and how to identify non-conforming events. If the project has a customer, owner, or AHJ witness requirement, their signoff can be captured in the closeout section.
How often is this report used?
It is typically used at commissioning, after construction, after splice repairs, and during acceptance testing before a fiber segment is turned over. It can also be reused for troubleshooting when a span shows excessive loss, poor reflectance, or intermittent service. For recurring maintenance programs, teams often keep the same structure and update the project-specific acceptance criteria each time.
What standards or regulations does this template support?
The template supports documentation practices commonly expected under telecom and construction quality programs, and it can be aligned to project specs, manufacturer requirements, and industry standards such as TIA/EIA fiber testing practices and ISO 9001 quality records. If the work is performed in an active roadway, utility corridor, or construction zone, the safety portion also helps document compliance with applicable OSHA and traffic-control requirements. Final acceptance limits should always follow the contract, design documents, or owner specifications.
What are the most common mistakes this report helps catch?
Common issues include missing bidirectional results, launch fiber that is too short to resolve the first event, incorrect wavelength selection, and event tables that do not match the trace files. Teams also miss dirty connectors, undocumented non-conforming splices, and reflectance values that exceed the project limit. This template forces those items into the record before closeout.
Can I customize the acceptance criteria and wavelengths?
Yes. The template is meant to be cloned and adapted to the project’s fiber type, operating wavelengths, and acceptance thresholds. You can add fields for single-mode or multimode builds, specific connector types, ORL targets, or owner-required pass/fail rules without changing the overall inspection flow.
What files should be attached with the report?
Attach the OTDR trace files from both directions, the exported event table, and any supporting photos of the test setup or labeled endpoints. If the project requires it, include calibration evidence for the OTDR and any reference jumpers or launch/receive fibers used during the test. Keeping those attachments with the report makes later dispute resolution much easier.
How does this compare with ad hoc field notes or screenshots?
Ad hoc notes usually miss one or more of the items needed to prove acceptance, such as directionality, wavelength, reference standard, or the exact event table used for review. This template creates a repeatable record that is easier to audit, easier to hand off, and easier to compare across spans or crews. It also reduces the chance that a trace is rejected because the setup details were not documented.
Related templates
Go deeper on the topic
-
A daily huddle is a brief (10–15 minute) standing meeting held at the start of a shift or workday to align the team on priorities, surface issues, and...
-
A deskless worker is any employee whose job happens without a desk, a company laptop, or a fixed workstation. They're roughly 80% of the global workforce —...
-
A frontline employee app is a phone-first application that gives hourly, field, and deskless workers access to their schedule, pay, announcements, training,...
-
A frontline worker is any employee whose job happens away from a desk — on a production floor, in a patient room, behind a store counter, in a customer's...
-
See how bank branch managers use MangoApps scheduling to fill shifts, communicate policy updates, and eliminate last-minute coverage chaos.
-
Roadmap to AI-first employee experiences with phased AI experts, apps, intranet, and workflows to boost productivity and engagement.
-
MangoApps AI now creates surveys, quizzes, and team structures in minutes, helping Ops, HR, and IT teams launch faster.
-
Sync ADP Workforce Now with MangoApps to auto-update employee data, permissions, and HR info in one place—no IT effort required.
Ready to use this template?
Get started with MangoApps and use OSP Fiber Optic OTDR Bidirectional Test Report with your team — pricing built for small business.
