GHT: Glass House Technologies
GHT service / Physical infrastructure

Cabling changes, audits, and repair

When the drawings stopped matching the walls

Moves, additions, repairs, tracing, testing, abandoned-cable review, network-room cleanup, and records updates for existing cabling.

What you should have at closeoutA verified before-and-after record, tested affected links, corrected labels, and an exception list for work that remains.
References3 reviewed
Last updated2026-08-20
Overview

What Cabling changes, audits, and repair includes

A MAC request is small only when dependencies are known. Port capacity, VLAN or voice assignment, cable route, furniture, work hours and endpoint readiness can turn a simple move into a service-risk event.

An audit records observed state and evidence. It does not certify concealed conditions or convert assumptions into as-builts. Remediation priorities should separate immediate defects, operational risks and orderly cleanup.

Question to answer before designWhat is active now, what needs to change, what may be removed, and how will the finished state be tested?
Common situations

This service may fit when:

  • Ports, outlets or patching cannot be traced
  • A move or refresh depends on undocumented services
  • Abandoned cable or failed links obstruct active infrastructure
  • Multiple sites need the same audit and closeout format
System components

What the system includes

A complete scope covers each part below and the connections between them.

01

Observed state

What can be traced and evidenced before change

02

Disposition

Retain, repair, relocate, remove or investigate

03

Controlled change

Sequenced work with impact and rollback notes

04

Updated record

Final labels, tests, photos and remaining exceptions

Project record

How site information becomes a tested project

A complete project record connects the conditions found on site, the design decisions made from them, and the tests and closeout documents delivered afterward.

Site information

What we confirm before design

  • Affected users, devices and business window
  • Known port, circuit and application dependencies
  • Available drawings, schedules and prior test files
Design decisions

What those findings determine

  • Audit depth: Match evidence depth to the decision the audit must support.
  • Remediation: Separate required repairs from optional standardization.
  • Removal: Verify ownership, service state and restoration scope first.
Closeout records

What you should receive

  • Current-state audit table
  • Before-and-after photo set
  • Disposition and exception register

The exact inputs, decisions, and acceptance records depend on the site and signed scope.

Project stagesSurvey through closeoutView details
Project stages

How the work moves from survey to closeout

Each stage should produce the records and test results needed before the next stage begins.

  1. 01

    Establish current state

    Trace affected endpoints, ports, pathways, services and visible condition.

    EvidenceBefore photos, trace table and unknowns list
  2. 02

    Classify change

    Separate retain, relocate, add, repair, remove and owner-decision items.

    EvidenceDisposition schedule and impact notes
  3. 03

    Execute controls

    Stage labels, patching, testing and rollback around the approved work window.

    EvidenceChange log and tested affected-link results
  4. 04

    Reconcile record

    Confirm service, close exceptions and update schedules and photos.

    EvidenceAfter-state schedule, photos and signed exception list
Design choicesCompare the available approachesView details
Options

How to choose the right approach

The right choice depends on the site, application, operating risk, and acceptance requirements. More equipment does not automatically improve the system.

FactorTypical approachMore demanding conditionsWhat determines the choice
Audit depthTypical approach: Visual room and endpoint surveyMore demanding conditions: Trace, test and configuration correlationWhat determines the choice: Match evidence depth to the decision the audit must support.
RemediationTypical approach: Correct identified physical defectsMore demanding conditions: Normalize labels, patching, records and spare capacityWhat determines the choice: Separate required repairs from optional standardization.
RemovalTypical approach: Clearly abandoned accessible materialMore demanding conditions: Route-wide removal with ceiling and penetration restorationWhat determines the choice: Verify ownership, service state and restoration scope first.
Change windowTypical approach: Normal-hours low-impact workMore demanding conditions: Staged after-hours cutover with rollbackWhat determines the choice: Use business consequence and dependency confidence.
Before design

What we need to know

  • Affected users, devices and business window
  • Known port, circuit and application dependencies
  • Available drawings, schedules and prior test files
  • Definition of defect and acceptance criteria
  • Removal, disposal and restoration responsibilities
At closeout

What you should receive

  • Current-state audit table
  • Before-and-after photo set
  • Disposition and exception register
  • Affected-link test results
  • Updated port, cable and asset schedule
Equipment examplesSee relevant hardwareView details
Best fit

When this service makes sense

  • Office restacks and tenant changes
  • Retail or branch device refreshes
  • Pre-renovation discovery
  • Network-room cleanup with a defined service window
Before we commit

What we verify first

  • Incomplete records and concealed routes
  • Live-service impact during tracing
  • Unverified ownership of abandoned material
  • Ceiling, furniture, tenant and security access
Site contextSee where this work is usedView details
Where it is used

How site conditions change the design

Occupancy, operating hours, user activity, regulation, weather, construction, and access can change the design.

Common questions

What people usually ask

Is an audit the same as certification testing?

No. An audit describes the agreed observed scope. Certification testing is a specific instrumented evaluation of a link against a selected performance limit.

Can abandoned cable always be removed?

Only after ownership and service state are established and the route, access, firestop and disposal requirements are understood.

What makes a move low risk?

Known dependencies, staged materials and configuration, a defined work window, an observable acceptance test and a practical rollback path.

Standards and referencesReview the source materialView details