A fiber installation and test record should connect each installed fiber to its endpoints, test setup, measured results, acceptance criteria, and supporting files. Use the blank forms below as one coordinated acceptance package: a project record, installation checklist, test setup record, per-fiber results sheet, and attachment register.
Keep traceability intact from the label on the patch panel to the original instrument file. A loss value without a fiber ID, wavelength, direction, reference method, and applicable limit is not enough to support acceptance or a meaningful comparison during later troubleshooting. FOA recommends preparing cable and fiber records before testing and comparing measured insertion loss with the calculated loss budget.
The tables can be printed or copied into an editable document or spreadsheet. They are blank recording forms; they do not calculate loss budgets or automatically determine pass or fail.
Establish the Acceptance Basis Before Testing
Complete the acceptance basis before collecting final results. Use the contract, approved test plan, equipment requirements, and applicable standard editions—not an unexplained default limit in the tester.
| Acceptance basis | Project entry |
|---|---|
| Project name and location | |
| Owner / client | |
| Installing contractor | |
| Test plan ID and revision | |
| Contract specification and applicable section | |
| Applicable test standard(s), edition(s), and method(s) | |
| Approved loss-budget document and revision | |
| Required fibers, including spare fibers | |
| Required wavelengths by fiber type | |
| Required test directions | |
| Required tests: continuity, polarity, insertion loss, OTDR, other | |
| Required length, event-loss, reflectance, or other limits | |
| Measurement uncertainty / borderline-result decision rule | |
| Required deliverables and file formats | |
| Authorized acceptance reviewer |
Identify whether each criterion applies to the installed cable plant, a channel that includes equipment patch cords, an individual event, or a particular transmission application. These boundaries are not interchangeable.
An optical loss test set (OLTS), or a suitable light source and power meter (LSPM), measures end-to-end insertion loss. An optical time-domain reflectometer (OTDR) characterizes events and their locations using backscattered and reflected light. Do not substitute an OTDR’s inferred total loss for a required OLTS/LSPM measurement. Whether OTDR characterization is also required depends on the project specification and test plan.
Blank Project and Installation Record
Use one project record for the handover package and one link record for each separately identified test path. For a path crossing several cable sections or closures, reference the splice schedule or as-built drawing that defines the complete path.
Project Record
| Field | Entry |
|---|---|
| Project / work order ID | |
| Record package ID and revision | |
| Installation date(s) | |
| Test date(s) | |
| Installer / company | |
| Test technician / company | |
| Site or building | |
| As-built drawing reference and revision | |
| Cable schedule / splice schedule reference | |
| Approved deviations / change references |
Link Identification and Installed Configuration
| Field | Entry |
|---|---|
| Link ID | |
| Cable / segment ID(s) | |
| Endpoint A: site, room, rack, panel, port | |
| Endpoint B: site, room, rack, panel, port | |
| Fiber number / buffer tube / ribbon position | |
| Fiber type and manufacturer designation | |
| Cable manufacturer, part number, and fiber count | |
| Connector type and polish at A | |
| Connector type and polish at B | |
| Intermediate panels, closures, and splice references | |
| Mated connection count within the test boundary | |
| Splice count within the test boundary | |
| Splitters or other passive devices, if present | |
| Test boundary and included / excluded patch cords | |
| Route length and source, if recorded | |
| Installed cable length and source | |
| Measured optical length, method, and units | |
| Service-loop / slack locations and drawing reference | |
| Installation observations / approved exceptions |
Keep route length, installed cable length, and measured optical length in separate fields. Record whether a length came from drawings, sheath markings, installation records, or an instrument. For an OTDR-derived length, retain the refractive-index setting with the test setup; the instrument derives distance from propagation time rather than measuring the physical route directly.
For multifiber connectors, identify the connector position and individual fiber mapping. A connector-level label alone does not identify every tested optical path.
Installation and Acceptance Checklist
Mark each item Complete, Open, or Not applicable. Explain every Open or Not applicable entry and identify its supporting record. A completed checklist records the review; it does not replace the underlying inspection or test evidence.
| Check | Status | Evidence / exception reference |
|---|---|---|
| Cable IDs and endpoint labels match the as-built records | ||
| Fiber assignments, splice schedules, and port mappings are complete | ||
| Installed route, closures, slack storage, and deviations are documented | ||
| Applicable cable handling and installation requirements have been reviewed against installation records | ||
| Connector end faces were inspected and cleaned as needed before mating | ||
| Continuity and endpoint mapping were verified for the required fibers | ||
| Duplex or multifiber polarity matches the approved mapping | ||
| Instruments and reference cords are identified and suitable for the test | ||
| Reference setup and verification records are complete | ||
| All required wavelength and direction combinations have results | ||
| Insertion-loss results were reviewed against the approved limits | ||
| Required OTDR traces and event results were reviewed | ||
| Failed, suspect, or incomplete results have a documented disposition | ||
| Repairs and retests are linked to the original records | ||
| Native test files, readable reports, and as-built records are indexed | ||
| Final package has been reviewed by the authorized recipient |
FOA identifies continuity, polarity, and end-to-end insertion loss as core installed-fiber checks. Connector inspection should follow an inspect–clean–inspect process when cleaning is needed. Before any direct-view optical inspection, establish that hazardous optical power is absent using the applicable safety procedure.
Test Setup and Reference Record
Assign a setup ID to each documented instrument and reference configuration. Reference that ID in every measurement row. Create a new setup record when the reference is reset or a configuration change affects the measurement.
OLTS / LSPM Setup
| Field | Entry |
|---|---|
| Setup ID | |
| Technician | |
| Source / OLTS make, model, serial number | |
| Power meter / remote make, model, serial number | |
| Firmware / reporting software version | |
| Calibration certificate reference and due date, as applicable | |
| Fiber type and selected wavelength(s), nm | |
| Reference method: one-, two-, three-cord, or specified method | |
| Reference connection diagram / procedure reference | |
| Launch and receive reference-cord IDs | |
| Reference-cord fiber type, connector types, and polish | |
| Adapter IDs / types, where relevant | |
| Multimode launch condition / encircled-flux evidence, if required | |
| Reference set date, time, and time zone | |
| Reference power at each wavelength, dBm, if available | |
| Reference-cord verification method and result | |
| Subsequent reference checks and results | |
| Instrument limit profile name and revision | |
| Conditions or changes affecting the setup |
Record the actual reference method, not simply “zeroed.” The one-, two-, and three-cord methods can produce different results because connections included during referencing affect the subsequent loss measurement. FOA’s mathematical treatment shows that two- and three-cord references subtract the losses of the connections present in the reference setup; those losses are not necessarily equal to the endpoint connection losses of the installed link. Do not compare measurements made with different reference arrangements as though they were equivalent.
For multimode testing, record the launch-condition requirements and how the selected source and reference-cord arrangement satisfy the approved procedure. Fiber type and wavelength alone do not fully describe the test setup.
OTDR Setup, When Required
| Field | Entry |
|---|---|
| OTDR setup ID | |
| Make, model, serial number, and firmware | |
| Calibration record / status | |
| Wavelength, nm | |
| Direction and endpoint reference | |
| Launch fiber ID and length, m | |
| Receive / tail fiber ID and length, m | |
| Refractive index / group index setting | |
| Range, pulse width, and acquisition / averaging time | |
| Event-detection and acceptance thresholds | |
| Link start / end markers and reference-plane treatment | |
| Trace-analysis software and version | |
| Native trace filename(s) |
Select launch and receive fibers appropriate to the instrument settings and link so the endpoint connections can be evaluated. Do not assume that an automatic event table has resolved every closely spaced event or dead-zone limitation. Retain the trace for review.
Per-Fiber Test Results
Use one row for each fiber, wavelength, direction, and test attempt. Do not place two wavelengths in one cell or overwrite an earlier failed result with a later passing result.
Repeat the table as needed for printing, or use its column headings in a spreadsheet.
| Result ID | Link / fiber ID | Wavelength, nm | Direction | Setup ID | Test date / time |
|---|---|---|---|---|---|
| Result ID | Continuity / polarity | Measured length and unit | Insertion loss, dB | Limit, dB | Limit source / revision | Instrument file |
|---|---|---|---|---|---|---|
| Result ID | Instrument verdict | Reviewer disposition | Exception / retest reference | Reviewer / date |
|---|---|---|---|---|
The result ID joins these three table sections. In a spreadsheet, keep all columns on the same row.
Preserve leading zeros in cable, fiber, and port IDs by formatting those fields as text. For CSV exports, use separate columns for values and units, and include the setup ID and original file reference. A flat CSV should not be the only copy of information stored in the instrument’s native format.
Compare Loss With the Correct Limit
For a source-and-meter measurement expressed as positive insertion loss:
Here, (IL_{\lambda}) is insertion loss in dB, while both power readings are in dBm at the same wavelength and under the documented reference procedure. If the instrument already reports insertion loss, retain that result and its sign convention rather than recalculating it from unrelated power readings. FOA distinguishes absolute optical power in dBm from relative loss in dB.
Where the approved acceptance basis uses a component loss budget, document it as:
=
\alpha_{\lambda}L
+
\sum_i C_{i,\lambda}
+
\sum_j S_{j,\lambda}
+
\sum_k D_{k,\lambda}
- (\alpha_{\lambda}): specified fiber attenuation allowance, in dB/km.
- (L): installed fiber length within the test boundary, in km.
- (C_{i,\lambda}): allowance for each mated connection, in dB.
- (S_{j,\lambda}): allowance for each splice, in dB.
- (D_{k,\lambda}): allowance for each other included passive device, in dB.
Use approved project values or identified manufacturer/specification limits—not unlabeled typical values. Match the budget’s reference planes and included components to the measurement method. FOA describes comparing measured loss with a budget built from fiber, connection, and splice losses.
Do not automatically add future repair or operating margin to the installation acceptance allowance. Record such reserves separately unless the approved acceptance method explicitly includes them.
If useful, record the arithmetic difference:
A positive difference indicates that the recorded measurement is below the stated limit. It does not, by itself, establish acceptance: the setup must be valid, all required tests must be complete, and the project’s decision rule must be applied. Do not turn a borderline reading into a definite pass by rounding it down.
Keep the instrument’s verdict separate from the reviewer’s disposition. A tester can apply the wrong limit profile correctly; recording “PASS” without the profile and acceptance reference hides that distinction.
OTDR Event Record and Bidirectional Results
When event characterization is required, retain both the trace files and an event record.
| Event ID / location | Event type | Wavelength, nm | A→B loss, dB | B→A loss, dB | Bidirectional loss, dB | Applicable limit / source | Disposition |
|---|---|---|---|---|---|---|---|
Add event reflectance or overall optical return loss as separately labeled fields when required by the test plan. Do not label either simply “loss,” because it would be ambiguous with insertion loss.
Where the procedure calls for bidirectional OTDR event-loss analysis, match the same physical event in both traces and calculate:
=
\frac{IL_{\mathrm{event,A\to B}}+IL_{\mathrm{event,B\to A}}}{2}
Differences in backscatter characteristics can make an event appear as a “gainer” in one direction and show excessive apparent loss in the other. Bidirectional averaging addresses that directional effect; retain both original readings, including their signs. Fluke’s procedure also emphasizes preserving the launch and receive connections to the link during the paired measurements.
Do not automatically apply this OTDR averaging rule to bidirectional OLTS results. Preserve each OLTS direction separately and use the acceptance rule specified for that test.
Attachment Register, Retests, and Handover
Supporting Files
| Attachment ID | Link / fiber / result IDs | Description | Filename or repository reference | Revision / date |
|---|---|---|---|---|
| Native OLTS / LSPM result | ||||
| Native OTDR trace(s), if required | ||||
| Readable test report | ||||
| As-built drawings / splice schedule | ||||
| Inspection / calibration / exception evidence |
Use filenames that identify the link, fiber, wavelength, direction, and test attempt. Keep a readable report for review and native files for later analysis. Baseline loss records and traces help maintenance teams distinguish an original condition from a subsequent change.
Repair and Retest Record
| Original result ID | Issue / suspected location | Corrective action | Retest result ID(s) | Final disposition / reviewer |
|---|---|---|---|---|
After corrective work, repeat the affected acceptance measurements under a documented setup. An OTDR trace showing an improved event does not replace a required final insertion-loss retest.
Handover Approval
| Field | Entry |
|---|---|
| Package ID and revision reviewed | |
| Required fiber / wavelength / direction records complete | |
| Missing records or approved exclusions | |
| Outstanding defects / punch-list reference | |
| Final disposition: Accepted / Accepted with listed exceptions / Rejected / Pending | |
| Submitted by / company / date | |
| Reviewed by / company / date | |
| Authorized acceptance / date |
State what the acceptance covers and list any exceptions explicitly. A completed test package documents the installed configuration and results under the recorded conditions; it does not establish support for every transmission application or replace the project’s authorized approval process.