Document an inherited
client network.

Taking responsibility for an existing environment is different from documenting a new installation. Services are already running, labels may conflict and every assumption can affect a support decision. The goal is not to make the rack look perfect on day one; it is to separate verified facts from unknowns and create a record that can improve safely.

1. Define the first useful scope

Start with the sites, cabinets and services that matter most to support delivery. Agree what will be inspected, what can be traced without disruption and what requires a later maintenance window.

2. Preserve evidence before changing anything

Capture overall cabinet photographs, existing labels, supplied schedules and visible connection state before remediation. Do not tidy, repatch or relabel until the initial condition is recorded and the effect on live services is understood.

3. Build the physical hierarchy

Create the client, sites, rooms and racks using names the service team can recognise. Record the installed hardware at its actual rack-unit positions, including passive equipment and shelf-mounted devices that influence connection paths.

4. Verify connections progressively

Map clear paths first, then work through conflicting and unknown connections. Record patch-panel ports, switch ports, outlets, endpoint information, uplinks, fibre and carrier handoffs. Mark each uncertain path as unknown or unverified rather than copying an unreliable schedule into the new record.

5. Prioritise operational context

Identify connections supporting critical, essential or managed services where the customer authorises those classifications. Record PoE, patch-lead colour and service notes where they materially help future field work.

6. Separate discovery from remediation

Create a clear list of missing labels, damaged leads, unsupported equipment, congestion and documentation conflicts. Plan corrections through an approved change process. This prevents documentation work from becoming an uncontrolled production change.

7. Make the baseline part of service delivery

Review the completed baseline with the customer and internal support team. Assign responsibility for updating records during moves, additions and changes. Use history, reports and controlled contractor access so the record remains useful beyond the onboarding project.

MSP onboarding baseline

• Priority sites and cabinets are identified.
• Initial condition and supplied records are preserved.
• Installed hardware and rack positions are captured.
• Verified and unverified paths are clearly separated.
• Important outlets, uplinks and carrier services are represented.
• Documentation gaps and remediation items are listed.
• The customer understands the current record and remaining unknowns.
• Future physical changes include a documentation update.