Cable-label and test-result reconciliation sheet

Use it with your own records.

1. Download the workbook and open 27 Test ID matching.
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 27 to complete the checks and record unresolved items.

Before you start

1. Define the approved in-scope cable population and retain its schedule revision, endpoints, and deferred or excluded work.
2. Inventory received result packages independently, preserving original filenames, internal test IDs, source, and session context.
3. Gather installed identification observations, contemporaneous installer maps, naming changes, and applicable technical-review references.
4. Name the identity reviewer and technical acceptance owner, which may be different roles with different decisions.

Complete the register

1. Enter Planned ID and Applied ID independently, preserving any discrepancy in the observed label text.
2. Record Original test ID and Result reference with enough package/session context to retrieve repeated temporary names unambiguously.
3. Enter Endpoints from the actual supporting evidence and mark unconfirmed details rather than inferring them from sequence numbers.
4. Classify Identity status as matched, missing, duplicate, extra, or unresolved as appropriate to the observed relationship.
5. Record accepted alias or retest relationships with Decision evidence and preserve original records when reports are revised.
6. Enter Technical review separately, naming Reviewer and actual identity Verification date without converting a match into a performance pass.

Walk through the example

In fictional DC01 / H1, enter CAB-0043 as both the planned and observed applied cable ID. The original test record is TEST-019 in the EX-Job7 native package. Preserve that name and its exact package location instead of renaming the file to CAB-0043. Enter the proposed endpoint relationship R014/08 to R021/20 and retain its unconfirmed status until supporting evidence is reviewed. Link EX-session-log-7 and any contemporaneous installer mapping that can distinguish this link from neighboring links. The identity reviewer must explain why TEST-019 corresponds to CAB-0043 or leave the alias unresolved. A passing technical result would not settle that identity question. Record the separate test-owner technical review against the actual project requirements. Once correspondence is accepted, verify retrieval from CAB-0043 to the original record and record the identity decision date. Keep any missing technical acceptance or additional evidence obligation open, and retain the original unresolved association in the review history.

Handle common exceptions

Two sessions both contain a result named TEMP-01.

Use session and package context with endpoint evidence; preserve both internal names and resolve each installed-link association separately.

A revised report arrives after an earlier result was disputed.

Retain both versions and record whether the revision changes presentation, identity correspondence, or the underlying test event.

The proposed mapping rests only on similar sequence numbers.

Keep identity unresolved and request distinguishing evidence or the test owner's authorized further-verification decision.

Review and close

1. Give every planned in-scope link a disposition and explain extra received records rather than relying on equal file counts.
2. Check one-to-many and many-to-one associations for documented retests, multiple required results, or unresolved mapping errors.
3. Confirm that each accepted alias has discriminating evidence and an actual reviewer decision.
4. Retrieve original results starting from installed cable IDs, including session context where short names repeat.
5. Keep identity acceptance and technical acceptance distinct, assigning unresolved evidence or further-verification decisions to the test owner.

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

• Fluke Networks: Test and labeling documentation ↗

  Published February 16, 2016; supports label/document correspondence, not current-edition or technical acceptance claims.

  Read scope and linked guides