Start a merger network review with a circuit inventory

A merger deadline often turns a network conversation into a request for an immediate installation commitment. An enterprise account executive earns trust by turning urgency into an inventory workshop with named owners. The early goal involves a shared view of sites, contracts, traffic, and decisions before anyone reviews a migration path. A close date matters, yet a close date does not replace current connectivity records.

Start with the business event. Ask which warehouse functions need service on the first day after close, which offices or facilities are changing hands, and who holds carrier records. A finance spreadsheet might list monthly charges. A network team might hold service details. Warehouse operations might know which tasks stop during an outage. Keep each source separate until participants compare records. A charge record does not prove a circuit type, and a service label does not explain business impact.

Set a purpose for the workshop in one sentence. For example, “We will create a reviewable inventory of connectivity records, operational dependencies, contract dates, and unanswered questions for every changing location.” Send this purpose before invitations go out. Procurement sees why agreements belong in the room. Operations sees why shift patterns matter. Network staff sees why a service identifier without site context needs follow up.

Invite people who own information, not only people with senior titles. A network architect often interprets current connection details. A procurement lead brings agreements and supplier contacts. A warehouse operations manager explains receiving, picking, shipping, and support needs. A facilities contact often knows who grants access to communications rooms. Finance helps match charges to legal entities. At a smaller organization, one person might cover several roles, so ask which records each participant controls.

Prepare a basic inventory sheet before the meeting. Give every location one row with separate fields for location name, street address, current service label, contract holder, renewal or end date, business activity, record source, and unresolved dependency. Leave unknown fields blank or mark them unknown. Do not fill a gap with a guess from a monthly invoice. A visible unknown prompts assignment. A hidden guess creates false confidence and returns later as a surprise.

In a fictional call, Maya, an account executive, hears, “We close in eight weeks. Please have every site on your network by then.” She responds, “I understand why the date matters. I cannot confirm delivery timing before we review site records and readiness work. Let us build an inventory with your network architect, procurement lead, and warehouse operations manager. We will identify current circuits, contract dates, traffic needs, and unknowns for each site.” The director says an acquired warehouse has a carrier agreement through March, while nobody knows its uplink requirements. Maya records both facts in separate fields.

Maya asks, “Who holds the agreement, and who has network documentation for the warehouse?” The director names procurement for the agreement and an acquired company engineer for network records. Maya requests a short workshop rather than a large planning meeting. She asks for the agreement, a recent service record if available, address confirmation, and a list of warehouse activities during receiving and shipping windows. Nobody needs to solve a future design during this first session. Their job involves making current facts visible.

Open the workshop by confirming scope. Read the location list slowly and ask which sites belong in the review. A merger team sometimes uses different names for a facility after close. Record alternate names beside one address so participants do not create duplicate rows. Ask whether a location will close, remain active, move, or change legal ownership. These business changes affect which inventory questions deserve attention, yet nobody should infer a service decision from a label alone.

Review records source by source. Start with the finance list and ask who recognizes each charge. Move to network records and compare site identifiers. Then ask operations what happens during an outage at each facility. A warehouse manager might say receiving stops for fifteen minutes while shipping labels continue through a separate process. Record those words as an operational dependency, not as a technical conclusion. The network architect later explains whether current records connect to those workflows.

Use plain questions when information conflicts. “Does this circuit identifier appear on the finance record?” “Which building entrance leads to the equipment room?” “Who speaks with the carrier during a service issue?” “Which shift needs service first after a close weekend?” Each question produces a fact or an owner. Avoid asking whether everyone has everything. A broad question invites a quick yes and leaves no path for checking individual gaps.

Separate contract facts from migration preferences. An agreement through March does not automatically determine a later choice. A monthly charge does not identify a termination choice. Record contract holder, end date, notice terms when supplied, and the person who understands the agreement. Procurement or legal counsel retains interpretation of contract obligations. The workshop record shows where a decision needs review without stating a requirement beyond supplied information.

Site access deserves its own field. A location might need a local escort, a facility badge, a property manager appointment, or a safety orientation before anyone examines equipment. The facilities contact should explain local process. Access affects when facts become available. In the fictional warehouse example, Maya asks who controls Saturday entry. The operations manager says an acquired company supervisor has keys and works weekday mornings only. Maya records, “Confirm access contact and review window.” The team now sees a practical issue before scheduling a visit.

Near the end, sort open questions by owner and date. Give every question one responsible person. Maya asks the procurement lead for the March agreement by Wednesday. The acquired engineer confirms service labels by Friday. The operations manager lists priority warehouse activities before the next meeting. Avoid assigning a vague team. A named person receives a clear request and has a chance to identify a better owner.

The decision point involves treating a deadline as a promise request or a planning trigger. Use a date as a trigger for organized fact gathering. A carrier change often depends on site access, design review, and contract choices held by different people. An inventory workshop does not slow a project. An undocumented circuit or unavailable facility contact often causes more delay than a focused early session.

For a fictional practice, draw four columns named site, current circuit, business critical traffic, and unresolved dependency. Place an acquired warehouse in the first row. Write “unknown” for current circuit, “shipping labels during evening shift” for traffic, and “agreement holder plus equipment room access” for dependency. Roleplay the director asking for an eight week commitment. Maya names the inventory workshop, asks procurement for an agreement, asks operations for evening shift details, and schedules a Thursday review. At 3 PM on Thursday, she opens the sheet, marks every reply received or outstanding, and assigns a named owner before moving to the second site.