# FTTH Testing: Construction and Turn-Up Checks for Acceptance **Author:** Omar Molina **Published:** October 22, 2026 **Last updated:** October 22, 2026 **Category:** FTTH Design **URL:** https://draftech.com/blog/ftth-testing **Title tag:** FTTH Testing: Construction and Turn-Up Guide 2026 **Meta description:** FTTH testing explained: OTDR traces, optical loss tests, ONT power readings and connector inspection, with construction, turn-up and acceptance handoffs. **Primary keyword:** ftth testing **Plan reference:** plan-2026-10-08-4 **Visible word count:** 2670 --- A connected subscriber can make a fiber build look finished while construction records still leave questions unanswered. The service may work, yet the owner may have no usable baseline for the feeder or no way to associate a trace with the installed drop. Those gaps need to be resolved at handoff, before the owner accepts the work. This guide follows the optical checks from construction through subscriber turn-up. It explains what each instrument establishes, when to schedule the work and how the results support the owner's decision. The emphasis is on selecting and documenting the right test, with acceptance thresholds kept in the project's approved specification. ## What FTTH testing establishes FTTH testing verifies the installed fiber path and its readiness for service. It combines 4 complementary checks: connector inspection, OTDR characterization, optical loss testing and ONT power readings. Construction tests establish the passive plant's condition; turn-up measurements establish operating power at the subscriber endpoint, with both sets of results supporting acceptance. **Construction and activation have different boundaries.** A feeder can be tested before subscriber drops exist. A completed drop can be tested before an ONT is provisioned. These are separate milestones because a result only describes the path connected during that measurement. The acceptance record needs to say which portion of the network it covers. The owner should be able to follow a result from its filename back to a physical fiber. A trace labeled only with a street description leaves room for confusion when several cables share the route. Using the same asset identifiers in the test records and splice documentation lets the reviewer locate the tested connection without interpreting a technician's shorthand. **Service readiness also includes work beyond optics.** An ONT may receive acceptable light while registration or provisioning prevents service. Conversely, a successful service check does not explain every splice event in the passive path. Optical acceptance and the operator's service verification procedure each need their own evidence where the turnover scope calls for both. ## Set the test boundaries before construction The test plan starts with the intended optical path. Identify whether a measurement covers a cable segment, passes through the splitter or reaches the customer connection. We put that boundary on the test schedule before field work begins. Otherwise, a contractor can submit a valid feeder result that the owner mistakenly reads as evidence for the entire subscriber path. **Splitters change the measurement problem.** A passive optical network branches, so a test taken from the common side may not isolate an individual output. The approved method must account for the topology and the instrument's capabilities. Our [GPON network design guide](https://draftech.com/blog/gpon-network-design-guide) provides the architecture context for deciding which branches and endpoints belong in the test plan. Access planning matters just as much as instrument selection. An end-to-end loss test needs coordinated access to the defined endpoints, while an OTDR can collect a trace from its launch end. Our access planning includes coordination with construction supervision and any receive cable placement. Including the test arrangement in the work package avoids reopening closures just to carry out an overlooked test. In our test plans, the specification names the required wavelengths and test directions. It should also define how the reference is established and which connectors fall inside the measurement boundary. Those choices determine what a reported loss represents. An instrument's factory pass setting may differ from the owner's requirements; its automatic result is only meaningful under the selected configuration. **Design documents need a testable connection plan.** If a splitter port or splice assignment changes during installation, the test schedule must follow the approved field change. This is where our [FTTH design and construction packages](https://draftech.com/services/ftth-design) connect to acceptance: the network described on the drawing has to be the network identified in the field results. **Unused fibers need an explicit disposition.** A construction contract may require testing spare fibers even though no subscriber is being connected to them yet. Our recommendation is to include those obligations in the test schedule so the activation list does not end up defining construction completion. The owner can then distinguish an intentionally unprovisioned fiber from an installed fiber whose required test is still missing. | Check | When it happens | What it establishes | Acceptance record | | --- | --- | --- | --- | | Connector inspection | Before test connections and final mating | Endface condition at the inspected interface | Inspection result tied to the connector | | OTDR characterization | After installation or splicing, and during fault investigation | Event locations and trace characteristics | Native trace with test settings and endpoints | | Optical loss test | After the defined passive path is complete | Measured insertion loss across that path | Loss result with reference method and wavelength | | ONT power reading | At turn-up and during live-service troubleshooting | Operating optical power at the identified interface | Power reading tied to the ONT and service state | ## Match each test to its construction or turn-up task ### Connector inspection before mating **Inspect the connection before trusting the measurement.** Contamination at a test lead can create a problem that appears to belong to the installed plant. The Fiber Optic Association's Installation Guide calls for connector inspection and cleaning before testing. Before mating, follow a documented procedure: inspect, clean when needed, and reinspect. Include the interfaces on the test cords. Use equipment and procedures suitable for the fiber's live or dark condition. Never look into a fiber end to check for light. A video inspection probe gives the technician a view of the endface without direct viewing through an optical microscope, but the probe still needs to be used within its manufacturer's instructions. An inspection pass addresses the endface; it does not establish the loss of the assembled path. The inspection record belongs to a particular connector at a particular time. If that interface is disconnected during later work, inspect it again before reconnecting it. File the required inspection evidence under the same asset naming scheme as the optical results. That makes a later contamination investigation traceable without claiming the original inspection guarantees permanent cleanliness. ### OTDR traces after installation and splicing An optical time domain reflectometer uses returned light to characterize events along the fiber. The FOA's reference chapter on OTDRs explains how the trace helps locate connections and faults. When reviewing a test package, use the trace to investigate events along the route and the separate loss measurement to assess transmission through the defined path. **The setup controls what the trace reveals.** Launch and receive fibers help assess the end connections when the test method calls for them. Pulse settings and measurement range affect the ability to distinguish nearby events. Our recommendation is to keep the original trace file with its settings. With only a screenshot, the reviewer may be unable to examine an event or check the test configuration. A PON trace requires particular care around splitters and branches. Do not assume that a trace acquired through a splitter identifies every downstream drop. Use the instrument manufacturer's supported PON method and the owner's approved test arrangement. For numerical event limits and their interpretation, use our [OTDR testing acceptance criteria and fiber splice loss guide](https://draftech.com/blog/otdr-testing-acceptance-criteria-fiber-splice-loss); those criteria remain separate from this workflow. ### Optical loss testing on the completed passive path An optical loss test uses a light source and power meter, or an optical loss test set, to measure insertion loss between defined endpoints. The FOA's Testing Cables reference explains that the source and meter simulate transmission through the installed cable plant. Before comparing the measured result with the approved path budget, confirm that both describe the same connections. **The reference method belongs in the report.** Reference cords and the way they are connected determine which connector losses are included in the measurement. A result without that information can be difficult to compare with another test of the same fiber. Record the selected method and verify the reference arrangement before testing, following the equipment procedure and project specification. We ask reviewers to confirm whether the documented test path includes the splitter and customer drop. A loss result for a distribution cable cannot be carried forward unchanged as the result for a completed subscriber circuit. Loss is expressed in dB, while received optical power is expressed in dBm. They answer different questions even when the same handheld instrument can display both. ### ONT power readings during turn-up The ONT reading describes optical power at an operating endpoint. Check it against the requirements for the installed equipment and PON system, with the measurement direction clearly identified. VIAVI's Test and Monitoring Solutions for Fiber to the Home selection guide distinguishes downstream power verification from selective upstream and downstream measurement. The meter must support the signals the technician intends to measure. **Identify the source of the reading.** An ONT's reported receive power and a reading from an external PON power meter come from different measurement arrangements. In our view, that distinction belongs in the record. On networks carrying multiple PON technologies, use a wavelength-selective instrument suited to the deployed system; a combined power reading can hide which optical channel produced the result. Upstream transmission needs its own supported measurement method because ONTs transmit in bursts. A downstream reading alone does not verify the upstream signal at the OLT. Record the ONT identity and operational state with the result, and keep registration or service verification evidence beside it. That allows the owner to distinguish an optical fault from a provisioning issue. **Keep live testing deliberate.** Confirm whether the fiber carries service before connecting a source or OTDR. Use the operator's approved live-network procedure and suitable filtered equipment where required, so a diagnostic action does not disrupt subscribers or expose an instrument to an unsupported signal. ## Turn measurements into an acceptance package **Acceptance requires traceable evidence.** A test register can associate each required measurement with the installed asset and the governing requirement. The reviewer should be able to open the original result from that register. Missing tests need a visible disposition rather than an empty cell that could mean either unfinished work or an excluded scope. Preserve enough context to reproduce the setup. Record the instrument identification and calibration status with the measurement configuration. Keep the technician and test date attached to the exported result. For an end-to-end test, identify both endpoints explicitly; a report organized only by the technician's working location leaves the far end uncertain when assignments change. The final connection records must agree with the test files. If an installation change moves a subscriber onto another splitter output, the closeout needs to show that assignment and the result for the final path. Our recommendation is to check the asset mapping before acceptance review starts. A technically sound measurement attached to the wrong fiber still leaves the owner without evidence for that fiber. **Record requirements also need to work in the field.** Requiring an export that nobody can open, or a naming scheme that field equipment cannot produce reliably, adds clerical work without improving the decision. A limitation of our emphasis on detailed records is the extra clerical work when the format does not suit field equipment. We recommend agreeing on a sample deliverable before production testing. The owner can confirm that the native files and readable report are usable while changes to the workflow are still straightforward. ## Resolve failures without losing the test history A failed result should trigger a defined investigation. Check the test setup and reference leads before assigning the defect to the plant, then use the appropriate measurement to narrow the location. We would keep the original failure attached to the asset record. Deleting it after a passing retest removes the explanation for the repair and makes the final package harder to audit. **Retest the scope affected by the repair.** Cleaning a test connection calls for repeating the measurement that depended on it. Reworking a shared feeder splice can affect paths beyond the subscriber that first reported trouble. The responsible reviewer should identify those affected paths from the connection records and require the applicable tests, rather than treating the first recovered service as evidence for every branch. Separate technical resolution from acceptance authority. A technician can record the corrective action and demonstrate the result; the designated owner representative decides whether the contract's evidence is complete. If an exception remains, state its affected scope and who accepted it. Leave that decision visible in the turnover record so operations does not inherit an unexplained qualification. ## Recommended next steps for FTTH testing **For network owners:** specify the test boundary and required evidence before awarding the work. **For construction managers:** schedule testing while the necessary endpoints remain accessible. **For operations teams:** require asset-linked files that can serve as a troubleshooting baseline. These responsibilities meet at acceptance, but each needs an accountable person before the field work starts. Draftech International delivers turnkey telecom and power infrastructure from field survey and planning through construction drawings, permits and agency coordination, followed by construction, as-builts and closeout. Engineering is 100% in-house; full turnkey construction is delivered by Draftech-managed subcontract crews. Our [partner and delivery team information](https://draftech.com/about) identifies the organization behind that scope. Active in 24 states. Available across all 50 U.S. states. Unclear test boundaries and mismatched connection records are problems to resolve while the package is being designed. Through the [free-design offer](https://draftech.com/free-design), Draftech engineers the first 20,000 linear feet of a qualifying route at no cost, from feasibility and field survey through permit approval; the owner reviews each request before Draftech commits the package. That early design work is the place to establish how the planned fiber paths will be identified. For an existing build, bring the test specification and connection records to a [project scope discussion](https://draftech.com/contact) so we can define the engineering and closeout work needed to resolve the gaps. You can also reach us at [info@draftech.com](mailto:info@draftech.com). Agree on what the owner must receive before the next field test, and make that agreement part of the delivery scope. ## Frequently Asked Questions ### What does FTTH testing include? It covers connector condition, OTDR characterization, insertion loss and operating optical power, with the required scope set by the owner. These 4 checks address different parts of the acceptance decision. Before testing begins, define which fibers and endpoints each result covers. Retain the evidence under the same asset identifiers used in the final connection records. ### Can an OTDR replace an optical loss test? Retain both where the specification requires them. An OTDR helps locate events along the fiber, while a source and power meter measure loss across 2 defined endpoints. The results complement each other, but their measurement methods differ. Use the approved test plan to decide the required evidence rather than substituting an instrument's automatic pass label. ### When should connectors be inspected? Inspect connectors before test connections and final mating, and inspect again after an interface has been disconnected for further work. The 2 sides of the mating pair need attention, including the test cord. A clean inspection image does not establish end-to-end optical loss. Retain the inspection result for the identified connector and follow the approved cleaning and reinspection procedure when contamination is present. ### Does acceptable ONT power mean construction is accepted? An acceptable ONT power reading supports turn-up of 1 endpoint, but the owner still needs the construction evidence required by the contract. The reading cannot identify every event along the path or establish that untested fibers meet their requirements. Tie the operating power record to the ONT and review it beside the passive-plant results before closing the optical acceptance scope. ### What should happen after a failed fiber test? Keep the failed result and its passing retest as 2 linked records, with the corrective action documented between them. Verify the setup before assigning the fault to the plant, and retest the affected scope after repair. If work changes a shared feeder, identify which downstream paths need testing; the owner's designated reviewer should close the exception only when the required evidence is complete.