FTTH Drop Cable ITP Template and Closeout Records

Use this FTTH drop cable ITP template to control one approved line item from the first inspection point through handover. It includes six linked registers and an editable FTTH drop cable ITP and closeout template that you can copy into the project system.

Quick answer: the FTTH drop cable ITP template

An FTTH drop cable ITP template links an approved cable line item to its inspection points, delivered lot or reel IDs, test evidence, nonconformance and retest history, and final closeout decision. The project owner still has to approve the methods, sampling, limits, and release authority.

For an ISP or telecom EPC package, keep this chain intact:

approved line item -> ITP control point -> lot/reel/assembly ID -> inspection or test record -> NCR/retest -> closeout decision

Procurement summary

For procurement and QA/QC teams, this template begins only after the part number, drawing, datasheet revision, deviations, inspection methods, sample rules, acceptance criteria, and release roles are approved. Use the working package to connect each delivered lot, reel, coil, or assembly to the approved configuration, applicable inspection and test records, any failure, NCR, concession, or retest history, the installed route or final disposition, and the closeout decision. If an identity, criterion, document, or authority is missing, record the gap with an owner and due date. Do not substitute a family brochure, unrelated certificate, or assumed regional practice.

Start after technical approval

Complete the model and evidence review before opening the ITP. The FTTH drop cable technical submittal review guide covers requirements matrices, evidence applicability, model reconciliation, deviations, resubmittals, and pre-purchase approval.

Open the ITP only after the following baseline is controlled:

• project, contract, package, and BOM line;
• exact offered part number and approved document revisions;
• accepted deviations and conditions;
• project-specific inspection, test, sampling, and acceptance requirements;
• buyer, supplier, contractor, inspector, and release authority;
• the record format and repository to be used at closeout.

ITU-T currently lists L.105 (11/2025) as in force and prepublished. The Recommendation addresses cable characteristics, construction, and test methods for drop applications. Its official work-program summary states that required conditions vary with the installation environment and that detailed test conditions should be agreed by the user and supplier. The ITP therefore needs the exact project-invoked requirement, method, sample rule, and criterion; complies with ITU-T L.105 is not a complete record.

Choose the page that owns the decision

How to use the template

1. Assign a document number, revision, project, package, and controlled BOM line to the complete companion template.
2. Replace every bracketed field. Mark an unresolved entry OPEN or TBD with an owner and due date; never let a blank cell imply compliance.
3. Remove starter rows that do not apply and add the inspections, tests, and notices required by the contract.
4. Give each record, lot, reel, coil, assembly, route, and link a stable ID.
5. Link test files, photographs, drawings, and approvals from the register row that uses them.
6. Retain failed, rejected, superseded, and retest records so the acceptance history remains visible.
7. Close the package only when it reaches the project-defined final status or every remaining open item has an authorized conditional disposition.

Four checks before issue

Do not issue the starter structure as an approved model ITP until all four checks are complete:

• the offered part number and every governing document revision match the approved baseline;
• each activity points to an approved method, sample rule, and acceptance-criterion source;
• the record issuer, reviewer, control-point owner, and release authority are named;
• every open field has a visible owner, due date, and route to closure.

If a field is unresolved, record it as open; do not enter an assumed value to make the register look complete.

Template 1: Project and revision control

Before entering a result, establish the exact identity of the line item and the documents that govern it.

For each revision, state which rows changed, why they changed, who approved the change, and which version is superseded. Changing the file name alone is not revision control. ISO 10013:2021 guidance on documented information supports process-specific records, but it neither approves this template nor prescribes a single document hierarchy.

Record the approved technical identity

Record destination-specific procurement and handover controls

Do not turn a regional label into an assumed cable, certification, test, or delivery requirement. North America, Europe, the Middle East, Southeast Asia, Latin America, and Africa each contain multiple codes, operators, climates, routes, languages, and customs processes. Keep the country, site, operator, contract, and approval authority as the decision owners.

Use the same matrix for all six regions at the country, site, operator, and contract level. If an exact requirement or evidence item is unknown, mark it OPEN or TBD with an owner and due date; do not fill the gap with an assumed regional preference.

Template 2: Inspection and test plan register

Give each inspection, test, review, or release decision its own row. The companion file includes starter rows for document review, first article when required, incoming material, in-process control, routine testing, final inspection, shipment release, receiving, and field closeout.

State what happens when a witness is waived or the buyer does not attend. A hold point needs explicit written release; the letters H and W have no meaning until the project defines them.

IEC 60794-1-2:2021 provides general guidance for the cable test methods in the IEC 60794-1 series. If the approved baseline invokes that series, record the exact part, edition, method, sample rule, and acceptance source. IEC 60794 compliant is not enough to identify a test or a limit.

Template 3: Lot, reel, and assembly traceability

A reel, coil, or preterminated assembly should carry the same trace identity from factory release to its installed record or final disposition.

When one factory record covers several reels or assemblies, list every covered ID. If an item is split, reworked, or relabeled, preserve the parent-child relationship.

At receiving, a mismatch in part number, revision, cable print, reel or coil ID, quantity, seal, or package condition should create a controlled discrepancy or hold record. Do not edit the register to match the delivery before the discrepancy is dispositioned.

When an approved U.S. premises submittal depends on a UL optical-fiber cable listing, verify the approved type, manufacturer identity, certification ID, and complete Listing Mark on the reel tag or smallest packaging container. Cable-surface marking alone is not proof that the delivered unit is Listed. The UL wire and cable application guide treats LSHF as an additional smoke and halogen marking, not a replacement for the required placement designation. For other markets, record the adopted code and operator evidence instead of carrying the U.S. designation across jurisdictions.

Template 4: Receiving and test record index

Keep results in their controlled source files. Use the fiber optic cable test record index to show what each file covers, how the result was obtained, and which ITP decision it supports.

FOA outside-plant testing guidance distinguishes end-to-end insertion-loss measurement from OTDR event analysis. IEC 61280-4-3:2022 covers attenuation, optical return loss, and optical power measurements in installed passive optical networks. IEC 61280-4-2:2024 covers attenuation and optical-return-loss measurements for the broader installed single-mode cabling plant. None of these sources defines the project’s pass/fail limit, so the record must cite the invoked method and approved criterion. If OTDR evidence is required, use the FTTH maintenance and OTDR guide for setup and interpretation details.

Escalate a record gap without reopening product selection

An incomplete record index should lead to a scoped evidence request, not a generic sales inquiry. First identify the exact line item, the delivered identities affected, the governing requirement, and the decision that cannot proceed.

For a BWNFiber-supplied line item, ask BWNFiber to confirm the record scope for that exact model, revision, and delivered identity. A family brochure, an unrelated certificate, or a report that does not name the affected IDs does not close the gap. The buyer’s or operator’s designated approval authority still decides whether the response meets the project requirement.

Template 5: NCR, concession, and retest log

Do not replace a failed result with a passing retest. The NCR and retest log should retain both records and the authorized disposition between them.

A concession applies only to the named items and approved scope. It does not change the baseline for later production unless the authorized documents are revised.

Template 6: Closeout document index

The FTTH cable closeout document index should let the operator identify what was accepted, what remains conditional, and where each supporting record is stored.

Network-wide GIS, port, subscriber, maintenance, and asset lifecycle rules belong in the FTTH network documentation and asset management guide. This template passes the drop-cable record into that owner system; it does not replace it.

Release reconciliation: prove the record chain closes

Before the final package is signed, reconcile the records across registers. Apply the review scope defined by the contract or approved quality plan; this starter does not set a sample size.

Record the reconciliation result in the companion template. A complete-looking register is not release evidence when its IDs, revisions, or decision rights do not agree with the source records.

Status and control-point codes

Map each starter status to the project’s actual workflow before use:

If the project uses R, W, and H, define the required record or attendance, notice period, proceed-without-attendance rule, and release authority. The codes have no useful control function without those definitions.

What this template does not decide

Keep the following decisions in their approved owner documents:

• cable types, product recommendations, or a flat-versus-round comparison;
• fiber category selection or universal cable bend limits;
• aerial span, duct, direct-burial, jacket, or building-placement approval;
• universal tensile, crush, attenuation, connector-loss, or OTDR limits;
• a fixed inspection sample size or mandatory factory witness plan;
• a Quick ODN architecture, loss budget, or installation sequence;
• an operator’s GIS, CRM, subscriber, or maintenance data model;
• a substitute for the contract, approved technical submittal, manufacturer instructions, adopted code, or authorized engineering decision.

If one of these decisions remains open, resolve it in the relevant owner document before recording acceptance in the ITP.

FAQ

What is included in the FTTH drop cable ITP template?

It includes project/revision control, an approved-baseline register, ITP rows, lot/reel/assembly traceability, a receiving and test-record index, an NCR/concession/retest log, a closeout index, status codes, and a final package decision.

When should the template be opened?

Open it after the candidate cable and technical submittal are approved and before the first contract-controlled production, inspection, witness, receipt, installation-release, or closeout record is due.

Is this template an approved ITP for every project?

No. It is a starter structure. The project must approve the activities, references, methods, sampling, criteria, control points, notice periods, records, owners, and release authority.

What is the difference between the submittal guide and this template?

The submittal guide decides whether the offered configuration and evidence are approvable. This template records how the approved line item is controlled through production, receipt, field evidence, exceptions, and handover.

Who should own the ITP document?

The contract should name the preparer, reviewer, approval authority, inspector, record issuer, and release authority. Do not infer decision rights from a job title alone.

How should a reel or assembly be tied to test evidence?

Use the same traceability ID in the physical label, packing list, routine-test record, receipt record, installed schedule, and closeout index. List all covered IDs when one report applies to several items.

Can a failed test be replaced by a passing retest?

No. Preserve the failed record, affected IDs, containment, disposition, corrective action, and retest. The passing retest supports closure; it does not erase the failure history.

Does every project need a factory witness or hold point?

No. The project sets control points from risk, contract, specification, and approval needs. Record review may be sufficient for one project and inadequate for another.

Is OTDR required in every closeout package?

No. Record OTDR only when the project requires event, route, splice, baseline, or troubleshooting evidence. Do not use a generic trace requirement as a substitute for the specified end-to-end method.

How should an accepted concession be recorded?

Identify the requirement, affected items, condition, technical impact, approval authority, and incorporated revision. Limit the concession to its approved scope.

When is the closeout package complete?

It is complete when every required record has reached the project-defined final status or has an authorized conditional disposition, each delivered and installed identity is traceable, failures and retests are visible, and the final package revision is signed by the named authority.

Can one FTTH drop cable ITP cover several part numbers?

Only if the contract allows one controlled document and each part number keeps its own approved baseline, criteria, trace IDs, and status. Use separate rows or appendices whenever the construction, test method, acceptance criterion, or release authority differs.

Use the FTTH drop cable ITP template on one controlled line item

Start with one approved BOM line and replace every bracketed field in FTTH_DROP_CABLE_ITP_CLOSEOUT_TEMPLATE.md. Then follow one reel or assembly from its ITP row through record ID, receipt, installed route, exception history, and closeout. If the chain breaks, fix the missing owner, ID, criterion, or record before applying the template to the full order.

If that walk-through exposes a specific product-evidence or record gap, send the details through BWNFiber’s contact page with the controlled line item, approved model and revision, open request, affected quantity, destination, and required decision date. Quotation and release decisions remain separate from this generic project template.

References

• ITU-T L.105 (11/2025, in force and prepublished): Optical fibre cables for drop applications
• IEC 60794-1-2:2021: Basic optical cable test procedures, general guidance
• The Fiber Optic Association: Outside-plant fiber optic testing
• IEC 61280-4-3:2022: Attenuation, optical return loss, and power measurement in installed passive optical networks
• IEC 61280-4-2:2024: Attenuation and optical return loss measurement of installed single-mode fibre cabling
• UL Solutions: Wire and cable application guide
• ISO/TC 176: Release of ISO 10013:2021, guidance for documented information

Source review date: August 25, 2026. Project-specific requirements, control points, sample plans, limits, and decision rights require approval by the authorized project owner.