HARDLINEFIELD SERVICESHardline Field Services home

FIELD GUIDE

What a fiber test closeout package should contain

UPDATED SEP 2026 · 2 MIN READ

SHORT ANSWER

A complete fiber closeout package contains native tester files and a PDF report for every link, Tier 1 loss results at both wavelengths, OTDR traces where specified (bi-directional on backbone), connector inspection results, a pass/fail summary against the stated loss budget, and a record of every retest. Every result must be named to the labeling schedule so a reviewer can match it to a physical port.

The package, item by item

ItemWhat good looks like
Project headerProject, building, room, contractor, tester model and serial, calibration date
Test limitsThe loss budget or limit set used, stated per link type
Reference methode.g. one-cord reference for Tier 1, with reference values
Tier 1 resultsEvery link, both wavelengths (850/1300 nm MM, 1310/1550 nm SM), length, pass/fail
OTDR resultsWhere specified; bi-directional on backbone; launch and receive cables used
InspectionEnd-face inspection result per connector, to IEC 61300-3-35
PolarityConfirmed per link, especially on MPO trunks
SummaryCount of links tested, passed, failed, retested
Retest logWhat failed, what was done, the new result, date
Native filesThe tester's own file format, not just PDFs
NamingEvery result named exactly to the labeling schedule

The five most common reasons a package is rejected

  1. Names do not match labels. If a result is named Link_0443 and the port is labeled to a TIA-606 identifier, the reviewer cannot match them. Build the tester's job file from the labeling schedule before testing starts.
  2. One wavelength only. Multimode needs both 850 nm and 1300 nm; single-mode needs both 1310 nm and 1550 nm unless the spec says otherwise. Bends show up at the longer wavelength.
  3. One-directional OTDR. A single-direction reading can show splice "gainers" or exaggerated losses. Bi-directional averaging gives the true value.
  4. No launch or receive cable. The first and last connectors are invisible without them.
  5. Retests with no history. A failed link that suddenly passes, with no note of what changed, looks like a re-shot result. Log the fix.

How to specify it up front

Put this in the scope before work starts, not at closeout:

  • The limit set or loss budget for each link type — see the loss budget guide
  • Which links need OTDR, and whether bi-directional
  • Reference method
  • Naming convention (from the labeling schedule)
  • File formats required: native plus PDF
  • Who reviews, and the turnaround time for review comments

If you are already at closeout and it is failing

A small independent QA/QC crew can audit labels, retest, rework and rebuild the package while the installation crew moves to the next phase.

NEED A CREW? GET A RATE IN 24 HOURS.

REQUEST CREWS →

FREQUENTLY ASKED

Why do closeout packages get rejected?
The usual reasons are results that cannot be matched to labels, missing wavelengths, OTDR traces shot in one direction only, wrong reference method, missing launch or receive cables on OTDR, and retests with no record of what was fixed.
Should the reference method be written in the package?
Yes. Loss results only mean something if the reviewer knows how the tester was referenced — for example, the one-cord reference method most specifications require for Tier 1. State the method and the reference values.
Do OTDR traces need launch and receive cables?
Yes. Without a launch cable the OTDR cannot measure the first connector, and without a receive cable it cannot measure the last. A trace without them is incomplete.

RELATED

TELL US THE SCOPE. GET A RATE IN 24 HOURS.

No account manager. No discovery deck. Send the scope and the start date and we will tell you what a crew costs and when it lands.

CALL DISPATCHREQUEST CREWS