NETWORK AND INTERNET · STRUCTURED CABLING
Office Cabling Change Log: Moves, Additions and Port Reassignments
Updated: 14 November 2026. A fictional closure example separating planned and actual port mappings was added.
Recording changes to office wiring; It shows which physical line was changed, for what reason, by whom, and how it is verified after the change. If the tag list in the initial installation is not updated over time, even the correct tag may turn into the wrong port record. The aim is not to write a long report for each operation, but to create a short history that can be reliably traced in maintenance.

office cabling change log: Keep before and after state in the same record
office cabling change log assessment
Desk moving, new printer, patch cable replacement, and permanent line re-termination are not the same process. Clearly state the type of change in the work order. Record the affected outlet, panel and switch port; Do not confuse physical line ID with switch configuration. A VLAN change can affect service without changing the cable label.
Instead of deleting the previous record, link it to the new revision. When a problem notification arrives, it is necessary to be able to see not only today's table but also the previous operation. Do not place a personal password or client secret in this record. Limit access to the need for maintenance; Do not share internal network details via a public document link.
Sample change form
| control | Information to be recorded | decision |
|---|---|---|
| Request | Work order, justification and planned time | Determine the responsible person |
| before/after | Socket, panel and switch ports | Maintain permanent line identity |
| verification | Test and result appropriate to the type of work | Link the file to the line ID |
| Closing | Drawing, label and record revision | Archive old version |
For example, the verification scope for patch cable-only transfer versus permanent cable re-termination may differ. The process performed and the project specification determine which measurement is required. Copying the test report for another line or presenting the old result as a new date does not create a reliable acceptance record.
How do you close the record when the planned and actual ports differ?
Keep the plan, the observed field condition and the acceptance decision in separate fields. If the planned switch port for a socket is unavailable, overwriting the old plan with the actual connection without an explanation loses the change trail. A working service alone does not show that an authorized person has accepted the difference.
The identifiers below are fictional; they describe neither a real Quad project nor a recommended switch configuration. They illustrate that a permanent link identifier and an active device port are separate fields.
| Field | Approved plan | Observed on site | Required for closure |
|---|---|---|---|
| Permanent link | Socket DEMO-12 → Panel DEMO-12 | Link identifier unchanged | Labels and link record must match |
| Switch connection | DEMO-SW / port 08 | DEMO-SW / port 09 | Reason for the difference and authorized decision |
| Record status | Revision A | Candidate revision B | Current record after verification and acceptance |
If the difference has not yet been accepted, leave the record as “pending review”; do not present the actual connection as the approved plan. The organization’s change process should determine correction or rollback. Preserve the previous mapping and the decision; this table alone is not an instruction to unplug cables, change a VLAN or roll back.
NIST SP 800-128 discusses retaining approved configuration versions and updating supporting documentation after verified changes. This table is an original record proposal based on that general principle; it is not a cabling test standard, a legal requirement for Türkiye or NIST certification.
Perform a closing check when the recording job is finished
Verify with the requester that service has been restored; Do not treat this step as the same result as a physical performance test. Opening a business application does not prove that all wiring parameters have been passed. Check that the current tag, correct port matching and required measurement file have the same line ID.
For first naming labeling plan, for report scope test report reading guide use it. structured cabling Agreeing the format of drawings and change records in the cabling proposal makes later maintenance easier. This is an original workflow suggestion, not a claim of manufacturer certification.
Clarify the survey and handover scope
Contact Quad Bilişim; Evaluate the current plan, device list, and expected delivery output together.
Technical resources
- Fluke Networks — Choosing the Test Limit
- NIST SP 800-128 — approved configurations, change records and archiving
Sources reviewed: November 1, 2026. The assessment table, procedure and hypothetical example are original Quad Bilişim working suggestions, without a price or outcome guarantee.