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.
The remote team should supply the site identifier, approved design, equipment list, configuration status, contacts, access window and success criteria. The field technician verifies serials, labels, damage, accessories and prerequisites before changing production service.
- 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.
Use a written method of procedure with hold points for configuration-sensitive actions. Photograph and label the before state, preserve known-good cabling or configuration, and keep a practical rollback path. Record deviations as they occur instead of reconstructing them after the visit.
- 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.
Validation must cover physical status, management visibility, addressing, uplinks, power, policies and representative user traffic. When redundancy is expected, test the approved failure and restoration scenarios. Escalations should include timestamps, identifiers and reproducible evidence.
- 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.
Closeout combines annotated photographs, serials, port and cable records, software versions, test output, exceptions and ownership. Credentials and private configurations belong in the client-controlled repository, while public pages should point only to official manufacturer support resources.
- 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.
Prepare
Confirm access, equipment, remote readiness and rollback.
Execute
Install through the approved method and document deviations.
Test
Validate management, service, resilience and user workflows.
Close
Deliver evidence, inventory, exceptions and support ownership.
Information to gather before design
Good decisions are easier when the project team starts with complete operational and technical information. The following items help reduce assumptions, change orders and avoidable return visits.
- Site access and remote contacts
- Staging, inventory and prerequisites
- Method, maintenance window and rollback
- Acceptance tests and escalation
- Evidence and operational ownership
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.
Build a repeatable field-deployment plan
Provide the site list, target schedule, equipment responsibility, change-window constraints and acceptance criteria. We will help turn them into a practical rollout and closeout workflow.