The package, item by item
| Item | What good looks like |
|---|---|
| Project header | Project, building, room, contractor, tester model and serial, calibration date |
| Test limits | The loss budget or limit set used, stated per link type |
| Reference method | e.g. one-cord reference for Tier 1, with reference values |
| Tier 1 results | Every link, both wavelengths (850/1300 nm MM, 1310/1550 nm SM), length, pass/fail |
| OTDR results | Where specified; bi-directional on backbone; launch and receive cables used |
| Inspection | End-face inspection result per connector, to IEC 61300-3-35 |
| Polarity | Confirmed per link, especially on MPO trunks |
| Summary | Count of links tested, passed, failed, retested |
| Retest log | What failed, what was done, the new result, date |
| Native files | The tester's own file format, not just PDFs |
| Naming | Every result named exactly to the labeling schedule |
The five most common reasons a package is rejected
- Names do not match labels. If a result is named
Link_0443and 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. - 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.
- One-directional OTDR. A single-direction reading can show splice "gainers" or exaggerated losses. Bi-directional averaging gives the true value.
- No launch or receive cable. The first and last connectors are invisible without them.
- 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
- SERVICEOTDR testing and fiber certification crewsHardline test crews certify fiber with Tier 1 (light source and power meter) and Tier 2 (bi-directional OTDR) testing, then deliver results …
- SERVICEPunch list and QA/QC crews for cabling closeoutHardline QA/QC crews close out cabling phases: they audit labels against the schedule, retest failed and marginal links, rework terminations…
- FIELD GUIDEFiber loss budgets: splice, connector and cable limitsA fiber loss budget adds up the maximum allowed loss of every component in a link: cable attenuation (loss per kilometre times length), each…
- FIELD GUIDETIA-606 labeling in the data center: what inspectors checkANSI/TIA-606 is the administration standard for telecommunications infrastructure. In a data center it means every space, rack, panel, port …
- COMPANYHow our crew rates workHardline prices crews two ways: a blended hourly rate per technician and foreman, or a per-unit rate (per splice, per drop, per link). Trave…