What happens if a cable ID in the tester file does not match any drop in Demarc?

The result is kept and listed on the project page under Unmatched Test Results. It is not linked to a drop until a drop carries that cable ID.

Will a warranty desk reject a package because the IDs do not match the labels?

The documents we read do not say that in those words. They do require complete, correctly identified results: Hubbell asks for the original tester files with schematic forms, and one owner specification makes the installer retest when an as-built submittal has missing or incorrectly named results.

Does Demarc change the cable IDs in my tester file?

No. The native file is stored as uploaded; Demarc reads the results from the CSV or XML export and matches them to drops by the cable ID the tester saved.

Cable IDs on test results vs labels and as-builts: what gets a job sent back

Demarc › Answers › Do the cable IDs on my test results have to match the labels and the as-built drawings?

Page last updated 2026-11-02. Every quote below links to where it was published.

In their own words

“If on submittal of the As-Built documentation there are any missing test results or incorrectly named files, the test shall be repeated”

Caltech IMSS VDN Specification Section 27 0000 (communications cabling) · source

“Documentation of the installation, including test results, cable management records and as-built documents in native, source or raw electronic format.”

Caltech IMSS VDN Specification Section 27 0000 (communications cabling) · source

“Complete both the Horizontal Schematic and Backbone Schematic forms.”

Hubbell Mission Critical registration steps · source

What it is

A certification result is only useful as proof if someone can tie it to a physical link. The cable ID the tester saved is that tie: it has to equal the label on the outlet and the patch panel port, and the name on the drawing. When the three disagree, the reviewer cannot tell which result belongs to which cable.

Written requirements show what happens then. One university cabling specification says that if the as-built submittal has missing test results or incorrectly named files, the test is repeated at the installer's expense. Hubbell's registration steps ask for horizontal and backbone schematic forms to go in with the test records. These are two documents, not a rule for every owner or program: check the one you are working under.

How Demarc does it

In Demarc you place each drop on the floor plan and name it with its cable ID. When you import the tester export, a result whose cable ID equals a drop's name is linked to that drop, and the drop shows pass, marginal or fail.

A result with no matching drop is not discarded or guessed at: the project page lists it under Unmatched Test Results, so you see the label that disagrees before the package goes out. The as-built closeout package is built from the same project, so its drops and the results come from one set of names.

The bar Demarc is held to

A test imports a result whose cable ID equals a drop's name and checks the drop is linked to it; another imports a result for a cable ID with no drop and checks the project page lists it as unmatched. Both run before every deploy.

Where it stands today

Partly met. Results link to drops by cable ID and unmatched results are listed in the test suite; Demarc does not compare the IDs to the printed labels themselves.

Not built or not measured yet:

Comparing cable IDs to labels printed elsewhere: Demarc knows the names you give the drops and the IDs in the results, and prints labels from that same list, but cannot read a label someone printed by hand.

What the usual tools leave to you

Sending reports by email or a file share leaves the installer to keep the tester's cable IDs, the labels, the drawings and the schematic forms in agreement by hand.

Check that test results match your drops before you send a job

Name every drop on the project with the cable ID printed on its label.
Import the tester export, as a CSV or XML export of the project.
Open the project page and read the Unmatched Test Results list, if there is one.
Correct the drop name or the label that disagrees, then import again, and download the kit.

Questions

What happens if a cable ID in the tester file does not match any drop in Demarc?: The result is kept and listed on the project page under Unmatched Test Results. It is not linked to a drop until a drop carries that cable ID.
Will a warranty desk reject a package because the IDs do not match the labels?: The documents we read do not say that in those words. They do require complete, correctly identified results: Hubbell asks for the original tester files with schematic forms, and one owner specification makes the installer retest when an as-built submittal has missing or incorrectly named results.
Does Demarc change the cable IDs in my tester file?: No. The native file is stored as uploaded; Demarc reads the results from the CSV or XML export and matches them to drops by the cable ID the tester saved.

Do the cable IDs on my test results have to match the labels and the as-built drawings?