Fiber innerduct pre-pull photo record

Direct answer

Before a low-voltage fiber pull in a data center, the pre-pull photo record should identify the room, pathway, conduit or innerduct tag, origin, destination, pathway type, spare duct status, pull-string or pull-tape continuity witness, visible bend-radius support, edge protection, sleeve or pathway seal condition at room entry, fire-rated pathway label where present, open exceptions, reviewer, date, and the release or hold decision.

The record should also say what it does not prove. A clear photo of an orange innerduct, a pull tape, or a fire-rated pathway device does not prove cable pulling tension, sidewall pressure, optical loss, firestop rating compliance, conduit fill, pathway capacity, pulling lubricant choice, test results, manufacturer acceptance, or final cable certification. It proves the observed pre-pull condition and the attached records at one point in time.

Use this as documentation guidance only. The engineer of record, owner standard, low-voltage contractor, cable manufacturer, firestop manufacturer, AHJ, safety plan, approved drawings, and commissioning or IT operations team control the actual pathway release, cable-pull procedure, firestop acceptance, and final fiber test requirements.

What this record covers

This record covers the visible condition of fiber pathways before cable is pulled through innerduct, microduct, conduit, sleeves, cable tray transitions, pull boxes, raised-floor openings, or room-entry pathways. It is meant for data halls, meet-me rooms, entrance rooms, network rooms, carrier rooms, lab rooms, and low-voltage spaces where the pull crew needs a documented starting condition.

The useful record connects four views: the approved route, the physical pathway, the label system, and the hold list. A photo set that only shows a pull string hanging from a conduit leaves the reviewer guessing which route it belongs to. A drawing mark-up with no field photos leaves the pull crew guessing what changed in the room.

The record is strongest when it is prepared before cable reels arrive at the room. That timing gives the project a chance to fix missing labels, crushed ducts, missing caps, sharp edges, unsealed sleeves, mismatched endpoints, and unclear spare conduits before a pull crew has people, reels, tugging equipment, and an outage window waiting.

Keep the scope narrow

Do not turn this photo record into a cable-pull method statement. Pulling speed, pulling tension, lubricant, blowing equipment, jetting method, reel setup, pull grip, swivel, sidewall pressure, bend calculations, cable slack, cable support, and post-installation testing belong in the approved low-voltage work plan and the current cable manufacturer's instructions.

The narrow scope is observed readiness. The field record should say which pathway was found, which labels were visible, whether a pull string or tape was continuous by an approved witness method, whether bend-radius protection was in place at known transitions, whether spare openings were capped, whether sleeves or fire-rated pathways were sealed or held, and what remains open.

That boundary protects the record from becoming overconfident. A pre-pull packet can release a pathway for the low-voltage contractor to proceed under its own approved procedure. It cannot certify that every later cable pull will stay inside the allowed bend radius, tension, fill, cleanliness, firestop, and test limits.

Start with the approved pathway basis

The first page should identify the current drawing, telecom pathway plan, conduit schedule, sleeve schedule, rack elevation or patching basis where relevant, room names, grid references, pathway IDs, firestop details, owner labeling standard, pull plan reference, and any RFI or field change that changed the route. Use the latest accepted record, not an old bid drawing.

TIA's pathway and spaces standard page frames telecommunications pathways and spaces as a building infrastructure topic across rooms, enclosures, racks, cabinets, access floor, above-ceiling routes, and building pathways. TIA's administration standard page frames labeling and administration across building and data center premises. Those public pages support the need for route identity and administration without replacing the project documents.

If the drawings, labels, and field condition disagree, hold the route. A conduit tag saying F-12, a drawing saying FC-12, and a room note saying spare carrier path may describe the same route, or they may not. The record should preserve that conflict until the responsible design or owner representative resolves it.

Identify rooms and endpoints

Start each route with the room name, room number, row or grid reference, source rack or wall, destination rack or wall, pathway ID, and owner route name. Add wide photos of both endpoints before close photos of labels and openings. The wide view prevents a later reviewer from applying a clean label photo to the wrong room.

For data center work, endpoint names matter as much as pathway names. A route from ER-101 to MMR-1 is not the same as a route from ER-101 to data hall row C, cabinet C14, or a splice cabinet in the same room. If the endpoint is future or reserved, call it future or reserved instead of pretending a rack is already assigned.

When the pathway enters a room through a sleeve, pathway device, floor penetration, wall box, cable tray transition, or stub-up, show the entry point and the endpoint label in the same photo set. The goal is not artistic photography. The goal is that a foreman can stand in the room and find the exact pathway without a memory tour.

Pathway label evidence

Pathway label photos should show the tag text, mounting location, direction, nearby room or grid context, and whether the label is permanent, temporary, handwritten, printed, missing, damaged, duplicated, or inconsistent. Capture the label at both ends of the route and at intermediate pull points where the owner standard requires them.

TIA's administration standard page supports the idea that telecom infrastructure needs an administration system, including data center premises. The photo record should follow the owner's accepted naming convention instead of inventing a cleaner field shorthand. If the project uses pathway numbers, keep pathway numbers. If it uses route names, keep route names.

Do not accept a label just because it is legible. Check whether the label matches the drawing, the conduit schedule, the sleeve schedule, and the destination. A crisp wrong label is still a hold item because it can send cable into the wrong route during a crowded pull window.

Innerduct and microduct identity

Innerduct and microduct evidence should identify duct color, duct count, bundle ID, pathway ID, duct size where labeled, unused ducts, occupied ducts, owner designation, and the route relationship to the parent conduit or tray. A photo should show enough surrounding context to prove which bundle or duct is being documented.

Dura-Line's FuturePath page describes bundled MicroDucts under one sheath and lists common installation contexts such as open trench, aerial, directional drilling, plowing, or pulling into existing conduit. It also describes HDPE conduits used as innerducts in existing conduits. That supports documenting the duct system as its own pathway, not as a nameless sleeve inside another pathway.

If several microducts exit the same sleeve, number or name them using the accepted field standard before release. A route photo that says blue microduct ready is weak if three blue ducts are present. The record should make the exact duct obvious to the pull crew and the owner.

Pull-string or pull-tape continuity evidence

Continuity evidence should identify the route, the pull string or pull tape type where visible, the witness, the method allowed by the contractor's procedure, the endpoint confirmation, and whether the string or tape is tied off, bagged, protected, and labeled. The photo should show the string or tape at both ends, not just one neat coil.

Dura-Line's Bull-Line Pull Tape page describes pull tape in several tensile strengths and notes that pull tape can be pre-installed into conduit. That supports recording whether the pathway has a usable pull tape or pull line present before the fiber crew starts work. It does not make the tape approved for every cable pull.

Write the result carefully. Use phrases such as pull tape present at both endpoints, continuity witnessed by low-voltage foreman, route not released because tape is missing at destination, or tape present but tied to unidentified route. Avoid broad phrases such as pull path good because the record must separate continuity from pull readiness.

Do not turn continuity into cable-pull approval

A continuous pull string or tape is a useful starting fact, not a full cable-pull approval. It does not prove the conduit is clean, dry, unblocked, correctly sized, below fill limits, inside bend limits, compatible with the cable jacket, or ready for the selected pulling method.

FOA's installation guidance warns that fiber installation must stay within cable specifications for pulling tension, minimum bend radius, and crush loads, and that manufacturer recommendations and route assessment matter. Corning's duct and indoor installation procedures also point readers back to cable specification sheets and minimum bend radius limits. Those sources support caution, not a generic release.

The pre-pull record should therefore say continuity verified for documentation only, cable pull still controlled by approved pull plan. That wording prevents a clean continuity photo from being treated as permission to skip bend, tension, route, and safety planning.

Bend-radius saddle and trumpet evidence

Bend-radius evidence should show saddles, radius drops, trumpets, sweeps, flexible conduit, sheaves, quadrant blocks, pathway outlets, rounded entry fittings, or manufacturer radius-control components at known transition points. Capture the component, the direction of cable travel, the route label, and nearby edges that could contact the cable.

FOA's bend-radius guidance distinguishes bend radius under pulling tension from installed bend radius, gives typical ratios while telling readers to check the cable specifications, and emphasizes that pulleys and capstans must be sized for the cable radius limit. Panduit's FiberRunner material describes bend-radius control surfaces and directional fittings. Leviton's Fiber Raceway selection guide also describes a raceway system that maintains a minimum bend radius.

The pre-pull photo should not state that the radius is compliant unless the responsible reviewer measured it against the actual cable's requirement. Better wording is visible bend-radius support installed at tray drop, cable-specific bend radius not verified by this photo record.

Pull path and edge protection evidence

Document sharp edges, saw-cut sleeve edges, metal tray lips, floor penetrations, threaded conduit ends, pull-box knockouts, wall openings, and rack-entry points. The record should show whether bushings, grommets, sleeves, rollers, flexible conduit, radius modules, or other edge protection are present where the approved plan requires them.

Corning's indoor installation procedure highlights protection in raceway transitions, sharp bends, congested ceilings and floors, cable trays, ladder racks, raised floors, and equipment entries. FOA's installation guidance also points to protecting cable at conduit ends and transitions with appropriate supports. Those sources support a pre-pull check for contact points.

If the pathway has a visible edge risk, hold the route or write a limited release that excludes cable pull. Do not let a pull crew discover a sharp sleeve edge after the reel is mounted and the route is staffed.

Spare conduit cap and plug evidence

Spare conduit and unused innerduct evidence should show caps, plugs, end caps, temporary seals, labels, and whether the spare is reserved, future, blocked, unknown, or available for a later route. Photograph both ends when the spare is part of the same turnover package.

Dura-Line lists Micro End Caps for sealing microduct ends. The Carlon PVC conduit transition fitting instructions describe inserting plugs to keep conduit clean and dry during rough-in and removing plugs when the rough-in stage is complete. Those product sources support documenting caps and plugs as pathway protection evidence.

A missing cap is not a cosmetic issue in a data center pathway record. An open spare can collect dust, water, debris, labels, cable scraps, or construction material. The pre-pull record should show which spares are capped and which spares are held for correction.

Room-entry sleeve seal evidence

Room-entry evidence should identify the wall or floor penetration, sleeve ID, route ID, room side, opposite side where accessible, seal type, fire-rated pathway device where present, smoke seal status where visible, cable load condition, empty opening condition, and label. Include wide context so the reviewer knows which wall or floor boundary is being shown.

STI's EZ-Path product page and product data sheet describe fire-rated pathway devices for cables through fire-rated walls and floors, with built-in sealing systems and product labeling or accessories. Those sources support documenting the device and visible status. They do not let the photo record approve the rating for a specific installation.

The record should use cautious wording: sleeve seal visible, pathway device labeled, empty sleeve capped, firestop inspection pending, smoke seal damaged, or rating not verified by this record. The final firestop acceptance belongs to the responsible inspection process.

Fire-rated pathway boundary

When the pathway crosses a rated wall or floor, separate pathway readiness from firestop acceptance. The low-voltage crew may need the route released for cable pull while the firestop contractor and inspector own the final seal condition after cable installation. The pre-pull note should say which boundary is being released.

A fire-rated pathway device can make moves and adds easier, but it still has product limits, listing conditions, cable capacity, installation details, and inspection requirements. The photo record should not override those requirements by writing firestop passed from a visual photo.

Use a status ladder: not in scope, pre-pull sleeve condition recorded, pathway device present, existing seal intact, cable load to be updated after pull, firestop inspection required after cable installation, or turnover held for damaged or missing seal. That gives the owner a practical status without overclaiming.

Wall or floor rating evidence

Where the rating is relevant, the record should attach the approved life-safety drawing, penetration detail, firestop submittal, rated-wall mark-up, sleeve schedule, inspection tag, or commissioning requirement. A field photo of a sleeve cannot identify a wall rating by itself unless the approved record ties that sleeve to the rated assembly.

The room side matters. A pathway can pass from a nonrated corridor into a rated data hall wall, through a floor slab into an equipment room, or through a carrier room boundary with owner security and smoke-control requirements. The photo packet should state the boundary it is documenting.

If the rating basis is not available, write rating basis not attached and hold the firestop release. The route may still be physically identified, but it should not be released as firestop-complete from a photo-only review.

Cable tray and rack entry context

Many fiber routes leave conduit or innerduct and enter tray, basket, ladder rack, FiberRunner-type systems, overhead raceway, or rack pathways. Photograph the transition, the support, the route label, the rack or row label, and the protection used where the cable leaves one pathway type for another.

Panduit, Leviton, Chatsworth, and Corning materials all point to bend-radius management and pathway support as real fiber-route concerns. The field record should show the supports that are supposed to protect the route at tray drops, ladder rack turns, equipment entries, and room transitions.

Do not write tray route approved if the photo only shows the first foot of transition. Say transition to overhead tray photographed, downstream tray route not included, or tray route included from grid C4 to rack row D. The boundary should be obvious.

Access floor and ceiling pathway context

Raised-floor and above-ceiling routes need clear boundary notes. Record the panel or ceiling grid location, accessible opening, protective sleeve or flexible conduit, nearby supports, existing cable congestion, and whether the pathway can be inspected without disrupting other systems.

Corning's indoor installation procedure discusses raised floors, suspended ceilings, flexible conduit for protection, and maintaining bend radius at entries and exits. TIA's pathway and spaces page also includes access-floor and above-ceiling pathway context. Those sources support documenting these areas as pathway spaces, not as hidden assumptions.

If the route disappears under a raised floor or above a ceiling, state how far the photo record follows it. The record may cover room-entry and first accessible pull point only. It should not imply that hidden sections were inspected unless the reviewer actually inspected and documented them.

Conduit and innerduct condition evidence

Condition photos should show cracked duct, flattened duct, crushed innerduct, sharp bends, pulled-out bushings, missing supports, loose connectors, unlabeled conduits, open ends, water, dust, debris, mud, kinked microduct, damaged pathway device, or field-cut edges. Record both normal and defective conditions.

The point is not to diagnose every cause. The point is to preserve the pre-pull condition before cable work starts. If a duct is already crushed or a sleeve is already full of debris, the route should not become the cable installer's problem after the cable pull fails.

Use plain status words: intact, damaged, dirty, wet, blocked, unlabeled, capped, uncapped, crushed, unsupported, label mismatch, or hidden. If the condition cannot be seen, say not visible and attach the record that supports it.

Fill and capacity boundary

The pre-pull photo record can document visible occupancy, spare ducts, empty sleeves, installed cable groups, and reserved route names. It should not calculate conduit fill, microduct capacity, jamming risk, or sidewall pressure unless the accepted engineering record includes those calculations.

Corning's duct source and FOA guidance both treat cable specifications, pulling tension, bend radius, and route assessment as cable-installation controls. Those controls belong in the pull plan, not in a photo caption. The caption can point to the pull plan and say whether the visible pathway matches the planned route.

If capacity is uncertain, hold the release for engineering or low-voltage contractor review. The route should not move from uncertain to accepted because the pathway looks large in a photo.

Existing cable protection

Pre-pull records are especially useful when new fiber will pass near existing production cable. Photograph existing cable groups, warning labels, separation points, protective sleeves, tray dividers, high-traffic areas, and any temporary protection the approved plan requires before the pull starts.

Corning's indoor procedure warns against damaging existing cable and describes protection at transitions, raised floors, ceiling spaces, and trays. CommScope's patch-cord management guidance also warns that bend radius and excessive force can affect fiber performance. Those ideas support careful documentation around existing cable.

Do not use the photo record to approve contact with live production cable or to relax the owner change-control process. If a route runs through a live network area, the release should identify the operations witness, change window, and no-touch boundaries.

Label naming convention

A useful naming convention ties route, room, endpoint, pathway type, and direction together. Examples include MMR1-to-DH2-FP-014, ER101-R03-innerduct-blue, carrier-spare-S2, or the owner's existing route format. Use the project convention even if it is less elegant than a new field system.

The label should be readable at the point of work. A label hidden behind a cabinet, under a floor tile, or inside a crowded pull box may satisfy no one during a pull. Photograph whether the label can be found from the normal work position.

When the label is temporary, write temporary label and assign permanent label follow-up. A temporary tag may be enough for a supervised pull, but it should not silently become the permanent administration record.

Photo sequence

Take wide photos first: room entrance, wall or floor boundary, pathway bank, tray or rack row, and endpoint context. These photos orient the reviewer before close-ups of labels, caps, strings, and sleeves.

Take mid-range photos next: the route label at each endpoint, the duct or conduit bank, pull box, cable tray transition, radius support, sleeve seal, spare caps, and pathway device. Include enough surrounding detail to locate the condition.

Finish with close photos and screenshots: label text, pull tape or string tie-off, cap or plug, bend-radius saddle, trumpet, bushing, room-entry seal, inspection label, hold tag, drawing mark-up, and release decision. Keep file names tied to route IDs so photos do not detach from the route.

Minimum pre-pull packet

Use the owner's required form first. Add this packet when the existing form does not connect the route, label, physical condition, and pre-pull hold decision.

Before low-voltage cable pull checklist

Use this checklist after the approved route and pull plan exist. It is a documentation pass, not a substitute for the cable manufacturer's installation requirements.

• Room, route ID, origin, destination, reviewer, date, and pre-pull scope recorded.
• Current telecom pathway drawing, conduit schedule, sleeve schedule, firestop detail, and approved changes attached or referenced.
• Wide photos show room context, pathway bank, tray or rack row, floor or wall boundary, and both endpoints.
• Labels at both endpoints match the approved route name, drawing, and owner administration standard.
• Innerduct, microduct, conduit, or sleeve identity is visible and tied to the route record.
• Pull string or pull tape is visible at both ends or continuity is held for correction.
• Pull tape or string condition is recorded without approving cable pulling tension, fill, or method.
• Bend-radius saddles, trumpets, bushings, flexible conduit, or radius-control components are photographed where visible.
• Sharp edges, threaded ends, saw-cut sleeves, tray lips, or rack-entry risks are corrected or listed as holds.
• Spare conduits, spare microducts, and unused openings are capped, plugged, labeled, or assigned for correction.
• Room-entry sleeve seals, pathway devices, firestop tags, smoke seals, or inspection status are recorded.
• Hidden pathway sections are marked hidden and supported by accepted records rather than guessed from nearby photos.
• Existing production cable, change-control boundaries, and no-touch areas are recorded where the route passes live spaces.
• Open exceptions identify the responsible party, due date, and evidence needed before release.
• Final decision states released, held, limited release, pull-plan review required, label correction required, or firestop review required.
• Limitations state that the photo record does not replace cable pull planning, manufacturer instructions, optical testing, firestop inspection, or AHJ approval.

Normal condition wording

Use exact, restrained language. A useful release note might say: Route MMR1-to-DH2-FP-014 photographed from MMR-1 wall sleeve S-14 to data hall row D overhead tray entry. Innerduct label FP-014 visible at both ends. Pull tape visible and continuity witnessed by low-voltage foreman. Radius trumpet installed at room-entry sleeve. Spare microducts capped and labeled future. Fire-rated pathway label visible; final firestop inspection after cable pull remains outside this release.

That wording gives the pull crew and owner enough information to find the route and understand the boundary. It does not claim the cable can be pulled at any tension, that the firestop rating is complete, or that the final link will pass optical testing.

Avoid phrases such as path good or ready for fiber unless the project standard defines those phrases. Plain evidence is easier to defend months later.

Exception wording

If the route is not ready, write it plainly. Example: Turnover held. Route ER101-to-MMR2-FP-006 label visible at source only. Destination duct not identified in MMR-2. Pull string present at source but not found at destination. Wall sleeve has open annular space and no firestop inspection tag. Low-voltage contractor to identify destination, install approved temporary route label, confirm continuity, and request firestop review before release.

Good exception wording names the route, the observed defect, the missing evidence, the responsible party, and the next record needed. It does not blame a trade without facts, and it does not hide a hold inside vague status words.

If the owner accepts a limited release, write the limitation. Released for route identification only is different from released for cable pull. Released for pull before final firestop is different from final turnover acceptance.

Pre-pull hold criteria

Hold the route when labels do not match, an endpoint is unknown, pull string or pull tape is missing where required, continuity is not witnessed, a duct is crushed, a spare is uncapped, the path has a sharp edge, bend support is missing at a required transition, the sleeve seal is damaged, the firestop status is unclear, or the route crosses an unapproved area.

Also hold when the photo record contradicts the drawing. If the drawing shows four spare microducts and the field photo shows three, the record is not ready. The correction might be an RFI, a revised drawing, a field label update, a missing duct investigation, or owner acceptance of the difference.

A hold is not a claim that the installation is failed. It means the pre-pull record is not clear enough to release the route without creating avoidable risk for the pull crew, the owner, or existing network operations.

Multiple pathways and redundant routes

Data centers often have A and B routes, carrier routes, diverse building entries, meet-me room routes, protected network paths, and future spares. The record should not collapse those into one generic fiber path. Name each route, side, room, endpoint, and pathway family.

If two routes share a sleeve bank or tray for part of the run, record the shared segment and the split point. If diversity is a design requirement, the photo packet should not certify diversity from visible photos alone. It can only document the segments observed and the drawings attached.

When route identity matters to operations, require separate release decisions for each pathway. Route A released and route B held is clearer than fiber pathways mostly ready.

Future spare pathway record

Future pathways deserve the same identity discipline as active routes. Record the spare ID, endpoint, cap or plug condition, pull string or tape state, sleeve or duct label, owner reservation, and whether the spare is available, blocked, reserved, unknown, or not part of this release.

Dura-Line's microduct and end-cap context supports treating small spare ducts as managed assets. A capped spare with a clear route name is useful later. An uncapped spare with no label becomes a troubleshooting task during the next project phase.

If a spare is intentionally left without a pull tape, say so and cite the owner or contractor direction. Do not let a missing pull line look like an oversight if it was an accepted scope decision.

Handoff to low-voltage contractor

The handoff should state which routes are released for the low-voltage contractor to use under its approved pull plan. Include the route list, hold list, drawing references, photo folder, witness names, change-control requirements, access limits, and any owner operations constraints.

The low-voltage contractor still owns the cable installation work assigned to it. That includes selecting the proper equipment, protecting the cable, observing cable specifications, controlling the pull, labeling installed cable, testing fiber, and correcting damage under the contract and approved procedures.

This separation keeps the pathway record useful. The general contractor, commissioning team, or owner representative can release the route condition without pretending to supervise every technical detail of the cable pull.

Safety boundary for photos

The photo task should stay outside hazardous or restricted work. Do not remove covers, open live electrical equipment, enter confined spaces, climb above ceilings without authorization, disturb firestop, pull on existing cable, or move production fiber to improve a photo.

Many pathway records can be completed with exterior photos, approved drawings, field labels, owner screenshots, and qualified inspection records. If evidence is hidden behind a controlled boundary, mark it hidden and attach the responsible party's record.

The release form should never pressure an unqualified person to reach into a crowded sleeve, pull box, tray, or energized space. A missing photo is a documentation issue. It is not a reason to create a safety issue.

What not to claim

Do not claim that a photo record proves optical loss, certification, continuity of installed fibers, cable cleanliness, connector quality, end-face condition, channel performance, final labeling, as-built accuracy, firestop rating, conduit fill, sidewall pressure, or cable warranty acceptance.

Do not claim that a bend-radius saddle photo proves the pull will stay inside the cable's loaded bend radius. The route may still include hidden bends, pull-box handling, reel setup, or equipment contact points outside the photo.

Do not claim that an empty sleeve seal photo proves final firestop acceptance after cable is pulled. The seal condition may change when cable is installed. The final inspection must follow the firestop system, project documents, and inspection authority.

Pull-box and handhole evidence

Where pull boxes, handholes, vaults, or intermediate boxes are part of the pre-pull route, document the box ID, route labels, entry and exit ducts, pull string or tape condition, cover condition, water or debris, bend support, edge protection, and safe access status. Photograph the box only from an approved safe position.

FOA and Corning guidance both treat cable protection at conduit ends, pull boxes, manholes, handholes, and bends as important. The pre-pull record should therefore show whether intermediate points are ready for cable handling, not just whether the two room endpoints look clean.

If a handhole is wet, blocked, missing route labels, or unsafe to access, hold the route for the responsible team. Do not write endpoint continuity verified as if intermediate conditions no longer matter.

Source-specific limitations

The sources used here support documentation concepts: telecom pathway identity, administration and labeling, optical fiber cable handling constraints, bend-radius protection, pull tape presence, innerduct and microduct identity, pathway caps, fire-rated pathway devices, and transition protection.

They do not support applying one product's installation details to another product, approving a specific cable pull from a photo, certifying a fire-rated assembly, proving code compliance, or replacing the exact project drawings and cable manufacturer's current instructions.

For a real project, the controlling source is the approved pathway drawing, owner standard, firestop submittal, cable submittal, manufacturer installation procedure, low-voltage pull plan, AHJ requirement, commissioning plan, and owner operations rule.

Reviewer questions

Ask whether the route can be found from the record without the person who took the photos. If the answer depends on memory, add wider photos, endpoint labels, drawing mark-ups, or room references.

Ask whether the evidence separates identity, continuity, bend protection, caps, seals, and release decision. If one photo caption says route ready, split the statement into observed facts and remaining limits.

Ask whether the packet could be misread as a cable-pull procedure or firestop approval. If it could, add a limitation: documentation only, pull plan controls cable installation, firestop inspection controls rated penetrations, and final fiber testing remains separate.

Release wording

Use one of a few clear release states: released for cable pull under approved pull plan, released for route identification only, held for label correction, held for continuity confirmation, held for bend or edge protection, held for cap or plug correction, held for sleeve seal review, held for firestop inspection, held for route conflict, or owner review required.

Attach the route list to the release. A single release note for ten routes should identify each route and each exception. Do not make the pull crew infer that unlisted routes are approved because nearby routes were accepted.

If the release is temporary, state the expiration or next condition. For example: released for scheduled 2026-06-12 pull only, final sleeve seal inspection required after cable installation. That wording avoids a temporary field release becoming permanent closeout.

Final decision record

The final decision should name the route, evidence reviewed, open exceptions, release boundary, and next action. Good decisions are released for cable pull under approved plan, held for missing destination label, held for pull tape continuity, held for damaged innerduct, held for edge protection, held for spare cap correction, held for firestop review, limited to route identification, or owner review required.

Keep the final note short but exact. The owner and pull crew need to know which route was documented, what labels matched, whether continuity was witnessed, whether visible bend support was present, whether spares were capped, whether room-entry seals were recorded, and which claims remain outside the photo packet.

A clean pre-pull record prevents avoidable confusion at the start of low-voltage work. It ties the approved route, physical pathway, label system, pull-string or pull-tape status, bend protection, spare protection, sleeve seal status, and release decision into one usable field record before cable installation starts.

Sources checked

• TIA FOTC, ANSI/TIA-569-E Telecommunications Pathways and SpacesUsed for telecommunications pathway and space context including rooms, access-floor areas, above-ceiling routes, racks, cabinets, and building pathways.
• TIA FOTC, ANSI/TIA-606-D Administration StandardUsed for telecom infrastructure administration and labeling context across buildings and data center premises.
• TIA FOTC, ANSI/TIA-568.3-E Optical Fiber Cabling and Components StandardUsed for optical fiber cabling and component context without making project-specific performance claims.
• Fiber Optic Association, General Guidelines For Installing Fiber Optic CableUsed for cable handling boundaries, manufacturer recommendations, pulling tension, minimum bend radius, crush load, lubricant, swivel, and route assessment context.
• Fiber Optic Association, Fiber Optic Cable Bend Radius or DiameterUsed for bend-radius framing, loaded versus installed bend-radius context, pulley or capstan sizing context, and transition protection caution.
• Dura-Line, FuturePathUsed for bundled MicroDuct, innerduct, FuturePath, HDPE conduit, installation context, product markings, rip cord, locate wire, and microduct end-cap context.
• Dura-Line, Bull-Line Pull TapeUsed for pull-tape presence, pre-installed pull tape, tensile strength range, and cable or conduit installation context.
• Panduit, FiberRunner Cable Routing System BrochureUsed for fiber routing, bend-radius control surfaces, directional fittings, trumpets, and cable management transition context.
• Leviton, Fiber Raceway System Selection GuideUsed for fiber raceway and minimum bend-radius management context in data center and telecom spaces.
• Chatsworth Products, Cable RunwayUsed for cable runway, radius-drop, pathway support, and bend-radius support context.
• Specified Technologies, EZ-Path Series 44+ Fire-Rated PathwayUsed for fire-rated pathway device context, wall and floor cable penetrations, and visible pathway-device documentation.
• Specified Technologies, EZ-Path Series 44+ Product Data SheetUsed for fire-rated pathway device construction, sealing system, cable-loading context, labels, accessories, and inspection boundary language.
• Carlon, PVC Conduit Transition Fittings Installation InstructionsUsed for conduit plug and rough-in protection context, including keeping conduits clean and dry before later work.
• Corning, Indoor Installation of Corning Optical Communications Fiber Optic CableUsed for indoor fiber installation context, raceway transitions, conduit or innerduct, raised floors, suspended ceilings, warning signs, bend radius, and cable protection boundaries.

Related guides