A new location fails or succeeds on the things nobody sees. The furniture arrives, the signage goes up, the team shows up on day one — and then someone discovers the conference room has no data drop, the point-of-sale terminal can’t reach the network, and the circuit the carrier promised is still three weeks out. None of that is a technology problem in the moment it surfaces. It is a sequencing problem that started months earlier, when the build schedule moved forward without a technology plan attached to it.
The fix is unglamorous: a new location IT setup checklist that runs in parallel with construction, not after it. The order below reflects how long each item takes to deliver, not how visible it is. Circuits and cabling take the longest and get scheduled first. Devices take the least and get scheduled last.
Start with a site assessment, not an equipment list
Before anyone specifies a switch or a firewall, walk the space against the floor plan. You are looking for the physical constraints that dictate everything downstream: where the demarcation point is, whether there is a room that can serve as an IDF or MDF, how far the furthest drop will be from that room, what the ceiling and wall construction will allow, and whether the electrical plan includes dedicated circuits and adequate cooling for the equipment you intend to put there.
Two questions decide most of the budget. First, how many people and devices will this site support at full occupancy, not at opening? Second, what does the lease allow you to change, and what has to be coordinated with the landlord or the base building? A site that looks straightforward on paper often has a riser you cannot access or a ceiling you cannot open without a permit. Finding that out during the assessment costs a conversation; finding it out during installation costs a schedule.
Lock in connectivity early — it has the longest lead time
Carrier circuits are the single most common reason a location opens without working technology. Provisioning a business fiber circuit can take anywhere from a few weeks to several months depending on whether the building is already lit, whether construction is required to reach it, and how busy the carrier’s local queue is. That timeline is largely outside your control, which is exactly why the order goes in first.
Plan for a primary circuit and a secondary path that does not share the same physical route or the same provider — fixed wireless or cellular failover is often enough for a smaller site. Confirm the demarcation location in writing, since carriers will terminate somewhere that makes sense to them and nowhere near your equipment room. And build in time for the circuit to be tested before opening rather than on opening day.
Design the cabling to the space, then to the standard
Structured cabling is the layer you will live with longest and change least. Getting it wrong is expensive to correct once walls are closed and ceilings are finished. Design to where the work actually happens — desks, conference rooms, reception, back of house, wireless access point locations, camera and access control positions, and any equipment that needs a wired connection for reliability.
A few decisions worth making deliberately:
- Cable category — match the media to the horizon you are planning for, not just to today’s switch capability.
- Drop count per position — a second drop at a desk or AP location costs very little during construction and a great deal afterward.
- Pathways and capacity — leave room in conduit, tray, and sleeves for the cables you have not thought of yet.
- Labeling and documentation — every drop labeled at both ends, with a record that outlives whoever installed it.
- Testing and certification — every run tested to standard and the results handed over, not assumed.
Coordinate this with the general contractor’s schedule. Cable pulls happen after framing and before ceilings close, and that window is narrower than most people expect.
Standardize the network stack across locations
The temptation at a new site is to specify whatever is convenient, available, or already sitting in a closet. Resist it. The value of a standard is that the tenth location behaves like the first: the same switch platform, the same firewall model tier, the same wireless controller approach, the same VLAN and addressing scheme, the same naming convention, the same monitoring agent, the same backup and patching policy.
Standardization is what makes remote support viable. When configurations are consistent, a problem at one site is diagnosable by someone who has never physically been there, and a fix that works at one site works everywhere. When every location is bespoke, every issue becomes an investigation. This is the discipline at the core of managing technology operations across multiple sites, and it is far easier to establish at a new location than to retrofit into an existing one.
Provision devices and prove it works before day one
Endpoints come last because they take the least time and depend on everything above. Build the device list from the roles the site will actually staff — laptops, desk phones or softphones, printers, displays, room systems, tablets, point-of-sale hardware, badge readers, cameras. Image and enroll them centrally before they ship, so they arrive already joined to your management platform with policy applied.
Then test the way the site will be used. Place a call from a conference room. Badge in at the door. Pull the primary circuit and confirm failover actually carries traffic. Check wireless coverage where people will sit rather than where the access point is mounted. Confirm backups are running and that a restore works.
Finally, hand over documentation: the as-built cabling record, the network diagram, credentials in a managed vault, vendor and carrier contacts with account numbers, and a support escalation path the local team can actually use. A site that opens with working technology and no documentation is a site that will be difficult to support six months from now.
Opening a new location in the next two quarters? A Built Environment Performance Assessment maps your existing sites and gives you a repeatable technology standard to build the next one against. Request a BEPA →