Bonding identification register

Use it with your own records.

1. Download the workbook and open 14 Bonding 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 14 to complete the checks and record unresolved items.

Before you start

1. Define the included conductors, equipment, busbars, and full location scope, identifying any endpoint outside the permitted survey area.
2. Collect the bonding drawing by sheet, revision, and detail, plus the equipment and busbar identity registers and naming dictionary.
3. Establish whether local identifiers follow physical conductors, connection positions, or both, so replacements and aliases can be recorded without conflating their meanings.
4. Identify the electrical drawing owner and prepare observation references that distinguish conductor text from evidence of each specific endpoint.

Complete the register

1. Enter the conductor identity exactly as observed, preserving missing or unreadable characters as a finding rather than reconstructing them.
2. Record the equipment parent and its specific attachment reference from the approved record, keeping asset identity and rack location distinct where applicable.
3. Enter Busbar ID separately from Busbar endpoint; retain the exact connection or drawing-detail reference needed to distinguish the attachment.
4. Cite the drawing sheet, revision, and detail and compare each field with its corresponding visible evidence.
5. Classify findings separately as unreadable text, missing identity, alias conflict, endpoint conflict, or an unobserved endpoint.
6. Record the electrical owner's accepted disposition and identify exactly which labels, aliases, or records change while preserving the original observations.

Walk through the example

For BND-G14-301 in DC01 / H1, enter CAB-G14-301 / BS1 as the documented equipment endpoint and BAR-G14-301 / POSITION 04 as the destination in BDR-G14-301 revision 5. Preserve the observed conductor destination GB-OLD-G14-301 / POSITION 04 in the finding evidence. The initial row therefore shows an alias conflict rather than silently translating the old name. Link DEC-G14-301 when the drawing owner confirms the historical rename and identifies the affected records. Update the accepted destination wording while keeping the old alias in history. After the identification correction, compare the conductor face and busbar identity evidence with the accepted current record. Record any endpoint-access limitation separately, even if the alias issue is resolved. Enter the real review date only for the completed identity comparison and make no claim that the labeling check established electrical integrity. Include the busbar's fixed location reference so the accepted alias resolves to one physical bar within the hall.

Handle common exceptions

The bar identity is known but its attachment reference is ambiguous.

Cite the available drawing detail and ask the electrical owner to establish the accepted endpoint reference; do not invent a position number.

A conductor label uses a former busbar name.

Preserve the observed alias and verify the rename history before updating the destination text and its linked records.

The label is repaired while the far endpoint remains inaccessible.

Close only the supported text correction and retain the endpoint limitation and responsible follow-up as a separate unresolved item.

Review and close

1. Confirm the current conductor and endpoint identities agree with the accepted decision and referenced drawing.
2. Check that any busbar rename has been reflected in the affected conductor records and label text, with the historical alias retained appropriately.
3. Require final evidence for the specific corrected field and keep any still-unobserved endpoint explicitly unconfirmed.
4. Retain original observation, accepted correction, and final comparison references together under the finding.
5. Enter the actual identity-review date and keep continuity, condition, or suitability conclusions in their separate responsible records.

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

• Panduit: Infrastructure identification guide (July 2014) ↗

  Historical grounding and bonding identification examples, page 10; older cited standards are not current-edition evidence.

  Read scope and linked guides
• TIA: ANSI/TIA-607-E publication announcement ↗

  Primary May 17, 2024 publication announcement. Establishes E publication, not project adoption or detailed clause changes. Checked September 12, 2026.

  Read scope and linked guides