Pathway and penetration identification schedule

Use it with your own records.

1. Download the workbook and open 19 Pathway IDs.
2. Enter your site and room scope and the project or policy reference.
3. Use the blank amber table for actual records. The fictional example below it is a reference.
4. Insert table rows when needed. Keep identifiers as text, including leading zeros.
5. Follow guide 19 to complete the checks and record unresolved items.

Before you start

1. Define the full site and room scope, included pathway object types, survey boundary, and any excluded or inaccessible continuation.
2. Collect the approved route plan and schedule by sheet, revision, grid, and detail, along with penetration and linked cable records where relevant.
3. Confirm the local meaning of a complete run ID, segment ID, branch reference, and penetration identity before proposing new names.
4. Identify the drawing owner and prepare observations with fixed landmarks that will let another reviewer locate each bounded segment again.

Complete the register

1. Enter the Pathway ID exactly as observed or mark a temporary survey reference clearly when the permanent identity is unresolved.
2. Record Object type separately and define Segment/location through stable start and end landmarks with full room context.
3. Enter Previous segment and Next segment as explicit relationships, using additional rows or a branch reference when more than one continuation exists.
4. Cite the exact Drawing/grid reference and preserve any competing field and drawing names as a specific finding.
5. Link cable IDs only where accepted records or permitted observations establish that association; distinguish documented continuity from observed continuity.
6. Record the owner decision and identify which label, drawing, or relationship changes, retaining specialist penetration references separately.
7. Review the accepted chain forward and backward and attach final evidence for the bounded objects included in the correction.

Walk through the example

For the fictional branch at JCT-G19-301 in DC01 / H1, record TRY-G19-301 as the approach and TRY-G19-302 as its main continuation. Create a separate conduit-branch entry from that junction to PEN-G19-301 at wall W3, grid D4. Preserve the branch's observed TRY-G19-301 text and cite PATH-G19-301 revision 4, which names CON-G19-301. DEC-G19-301 accepts the branch identity without changing the main tray names. Enter the corrected conduit face and retain the two successor relationships explicitly. After the authorized identification correction, link EV-G19-303 and follow the branch forward to the penetration and backward to the junction. Keep the penetration's specialist references separate, review only supported cable links, and state any concealed continuation outside scope. Record the actual identity-review date and retain the original copied label as finding history rather than treating the naming correction as a broader route inspection. Confirm the schedule still names the main continuation separately so the corrected branch does not absorb its identity.

Handle common exceptions

One run name has been copied onto several branches.

Preserve the observed faces and map the actual junction relationships; have the drawing owner establish distinct accepted branch references before issuing labels.

The continuation passes into an unobserved room or concealed section.

Record the documented relationship and explicit observation boundary, leaving unsupported continuity or cable links unresolved.

The penetration has a separate specialist label or inspection issue.

Retain its identity and specialist reference, and route that issue to its responsible owner rather than replacing or closing it through the pathway schedule.

Review and close

1. Check that each corrected identity can be located again using the recorded landmarks and matches the accepted drawing reference.
2. Confirm branch and predecessor/successor relationships remain explicit in both directions after the correction.
3. Retain cross-room scope and any shared penetration relationship without creating unexplained duplicate physical objects.
4. Keep unobserved concealed sections and unsupported cable associations visibly unresolved.
5. Record the actual review date, included objects, and specialist-record boundaries without implying route diversity or treatment acceptance.

Fields and filled example

Fictional values only. Scope: DC01 / H1 unless another location is shown. The downloadable register is blank for your actual observations.

Sources and scope

• TIA FOTC: TIA-606-D scope ↗

  Public overview of infrastructure administration, not full normative text or a claim that D is the latest edition.

  Read scope and linked guides
• Smithsonian: Design standards, volume 2 ↗

  October 2021 owner specification; communications as-built requirements at printed section 27 15 00-4. Not a universal mandate.

  Read scope and linked guides