Moves, Adds and Changes Field Work Order
Small moves and additions can create large documentation and support problems when outlets, switch ports, VLANs, voice settings and asset records drift apart. TechRunz uses a bounded work-order method that distinguishes the requested user outcome from the physical and logical changes needed to deliver it.
Make each dispatch repeatable and recoverable
Define prerequisites, remote ownership, method of procedure, acceptance evidence and rollback before technicians arrive onsite.
Scope validation and change design
Walk the request with the site contact and identify the exact source, destination, endpoint and service. Confirm furniture readiness, access, pathway capacity, outlet count, power and network-port availability. Separate new construction, hazardous access or after-hours requirements from an ordinary MAC ticket.
Trace and document the current outlet, patch-panel position and switch port before disconnecting it. Confirm intended VLAN, voice, PoE, security, authentication and addressing with the network owner. Preserve the original state and approved rollback point.
A one-line ticket can come apart once the technician reaches the floor. Ask the requester for the named user, the desk or room, the service being moved and the date it must work, then confirm onsite that the outlet exists and is reachable. Scope growth beyond that description needs a named approver.
- Authorized request and window
- Exact source/destination
- Physical capacity
- Logical/service dependencies
Cabling, patching and endpoint execution
Install or extend cabling only under the applicable design and pathway requirements. Keep bend radius, support, separation, firestopping and labeling consistent with the site standard. Do not reuse an unknown cable merely because it reaches.
Patch the recorded outlet to the assigned switch port and apply authorized logical changes through the client process. Move the endpoint and peripherals with cable management, ventilation and user ergonomics intact. Remove abandoned temporary patching when included in scope.
On a live floor it helps to prove the new position before releasing the old one, which means a photograph of the patch field, a labeled tail, and the previous jack left patched until the user works. Deviations get written on the work order while the technician is still standing there.
- Trace before disconnect
- Standards-based pathway
- Outlet/patch/port labels
- Authorized configuration
| Stage | Control | Closure evidence |
|---|---|---|
| Discover | Current and target state | Trace/scope record |
| Change | Physical and logical authorization | Work log |
| Validate | Link and business service | Tests/acceptance |
| Close | Records and exceptions | Updated ticket |
Service validation and exception control
Test the installed cabling at the required level, then verify link speed, errors, PoE, DHCP, DNS, authentication, voice, applications and peripherals appropriate to the endpoint. Have the user or application owner confirm the intended business task.
Stop and document mismatches such as occupied ports, failed cables, missing licenses, capacity limits or undocumented security policy. Use an approved exception or follow-on ticket rather than hiding extra work inside the original request.
Closing a MAC on the user’s word alone can leave the desk open to a callback, so keep the cable test file, the switch port name and the moment the endpoint came up. Where the finding is a dead pair or an occupied port, that belongs in its own ticket with the evidence attached.
- Cable and link test
- PoE/addressing/authentication
- User application test
- Exception or rollback decision
Records, capacity and ticket closure
Update outlet, patch-panel, switch-port, VLAN and asset records and attach test files, photographs and user acceptance to the work order. Record unused capacity created or consumed by the change.
Close only after temporary access and settings are removed, exceptions are assigned, and monitoring reflects the new state. Feed repeated MAC failure patterns into standards, spare planning and preventive maintenance.
Small changes are what pull a port map out of alignment with the building, so the updated outlet, panel and port entries matter more here than the photographs. Log the ports freed and consumed as well, because closet capacity is easier to plan from a running count than from a survey ordered after a request is refused.
- Cable/port/asset update
- Evidence attached to ticket
- Temporary changes removed
- Capacity and follow-up recorded
How we plan and deliver the work
The final design depends on site conditions, existing systems, client policies and the selected manufacturer or platform.
Confirm request
Translate the user request into the specific outlet, patch, switch port and profile changes the ticket actually needs.
Trace path
Follow the existing run from outlet to patch panel to switch port and record what is really there.
Make change
Reterminate, repatch or reassign the port, then relabel the outlet, panel position and device to match.
Update records
Test the working outlet, note the before and after state, and hand the ticket back with evidence.
Information to gather before design
A move or add still touches cabling, patch panel positions, switch ports and asset records, so the ticket needs outlet and profile detail up front.
- Requester name and desk location
- Existing outlet and jack labels
- Target VLAN or voice profile
- Building access hours and escort
- Spare patch cable and panel capacity
Frequently asked questions
These are common planning questions. A site-specific answer should be confirmed during discovery and design.
Does moving a PC require cable testing?
Validate the affected permanent link and service to the level required by the work order and site standard.
Can an unused switch port be selected in the field?
Only after the network owner confirms capacity, policy and assignment.
What if the requested outlet does not exist?
Document the condition and route a scoped cabling addition or approved alternative.
Why attach before-and-after records?
They support rollback, troubleshooting, billing and an accurate source of truth.
Manufacturer software, firmware and technical files remain on the manufacturer’s official website. We do not mirror firmware files locally.
Send us your next batch of moves
Tell us how moves, adds and changes reach your team today, which buildings are in scope, the ticket volume you carry in a week, and whether cabling and reterminations sit inside the scope.