Skip to content
Board advisory and board seats: full for 2H FY26 and 1H FY27. 1 of 3 positions open from 2H FY27 onward.
See details →
Writing

27 Locations, One IT Team: The Build-Out Checklist

The kit I'd hand a new site lead: circuits first, a closet with a spec, 911 that reports the right floor, and Wi-Fi, AV and doors built once for every site.

By Michael YorkNovember 5, 2026 9 min read 2,117 words All postsTable of contents

Twenty-seven locations stay manageable only when every one of them is built from the same kit. Here's the kit I'd hand a new site lead, in the order I'd work it, including the 911 rules that are easy to leave to the phone vendor.

A new or moved office is ready when four things are true: the internet runs on two paths, every cable is labeled to a drawing, a 911 call from any phone reports the right address and floor, and nobody had to invent anything to get there. Everything else is furniture.

From 2014 to 2016 I was Head of Infrastructure & Security at Starwood Waypoint Residential Trust, a publicly traded REIT with 600+ employees across 27 locations. The fleet I managed ran past 10,000 devices, spanning end-user systems, servers, networks, telecom, and branch IT buildouts. At that count, a site that's built differently from the others isn't a quirk. It's a second support model, and you pay for it every time something breaks there and the person on the phone has never seen the room.

So the checklist below is ordered by lead time, not by what's fun to buy, and every external rule in it is cited to the body that wrote it.

Order the circuits the week the lease is signed

The internet circuit is the one item on the list whose date you don't control. The carrier sets it, and if the building has never had that carrier's fiber, the order can turn into a small construction project with its own permits. I'd treat the circuit order as the start of the project rather than a task inside it. It goes in the week the lease is signed, before the floor plan is final.

Two paths from two providers is the standard I'd hold every site to. Ask the landlord which carriers are already lit in the building, since a provider that's already there has less to build to reach you. Then pick a second path that doesn't share the first one's entry where the building allows it: a second wired carrier if there is one, cellular if there isn't.

Two details get missed. The carrier's handoff point, the demarc, can sit in a ground-floor or basement room nowhere near your suite, so someone has to own the cable run from there to your closet. Put it in the cabling contract by name. And the circuit term should match the lease. A 36-month circuit in a 24-month lease is a year of paying for a building you've already left, which is why I'd negotiate the exit terms at signing instead of at the move.

Treat the network closet as a room with a spec

Every cable on the floor ends in the closet, so where it goes is a design decision. I'd put it near the middle of the space instead of in whatever corner is left over, give it a lock the cleaning crew doesn't share, put the switches on a UPS, and keep the rack layout identical from site to site. When the rack looks the same in every office, a remote tech can work it from a photo.

Specify the cabling to published standards so you aren't arguing with an installer about what good means. TIA-568 is the Telecommunications Industry Association's family of cabling standards, and TIA-568.1 is the part for commercial buildings. Its addendum TIA-568.1-E-1, which TIA announced in March 2023, added what TIA calls "a requirement for 2 category 6A cables for WAPs," meaning two runs to every wireless access point location. Pull them while the walls are open. A drop added after the drywall is up costs more than a spare pulled on day one.

Label to TIA-606-D, TIA's administration standard from October 2021, which assigns identifiers to infrastructure components and specifies the records that go with them. The acceptance test I'd use is that someone who wasn't on the install crew can find any port from the drawing alone.

Then heat and power. TIA's 2022 addendum TIA-569-E-1 revised the temperature and humidity recommendations for telecommunications spaces and harmonized them with ASHRAE's thermal guidelines for data processing environments. NIST SP 800-53 Rev. 5 makes it a control: PE-14 asks you to maintain and monitor environmental levels where the systems live, and PE-9 asks you to protect power equipment and power cabling from damage. In practice that's a temperature sensor that alerts a person, a dedicated circuit, and a closet that isn't also the supply room.

Make 911 report the right floor before the phones go live

This is the item with federal rules behind it, and it's easy to miss because the phones work fine without it.

The FCC's 2019 Report and Order implementing Kari's Law and Section 506 of RAY BAUM'S Act set the rules for multi-line telephone systems, which is the FCC's term for business phone systems, PBX, VoIP, and hosted alike. The rules live in 47 CFR Part 9, Subpart F, sections 9.15 through 9.17. Under 9.15 they apply to any such system installed after February 16, 2020, which covers any build-out you're doing today. The on-site duties fall on whoever installs, manages, or operates the system, and 47 CFR 9.3 defines the manager as the entity controlling it after installation, including adding and moving lines. If your team adds and moves the lines, read that definition closely. The same order says an enterprise owner has an obligation to hold its third-party providers responsible, and that a passive owner generally shouldn't face liability if it contracts with a responsible third party and writes the compliance requirements into the provider agreement.

  • Direct dial. A user has to reach 911 from any phone without dialing an extra digit or prefix, "including any trunk-access code such as the digit 9." The FCC's order records why. Kari Hunt was killed in a motel room in Marshall, Texas in 2013. Her 9-year-old daughter tried four times to call 911 for help from the room phone, and the call never went through because the motel's system required a 9 for an outside line first.
  • Notification. Where the system can be configured to do it without a hardware or software upgrade, it has to alert a central location at the facility, or another person or organization wherever they sit, when someone dials 911. The definition in 47 CFR 9.3 says the alert carries the fact of the call and, where technically feasible, a callback number and the caller's location, and 9.16 says it must go "to a location where someone is likely to see or hear it."
  • Dispatchable location. The call has to carry the validated street address plus the suite, floor, or similar detail a responder needs to find the caller. Fixed on-premises phones had to do this automatically by January 6, 2021. Non-fixed devices on premises, and devices used off premises, followed on January 6, 2022: automatically where technically feasible, otherwise through the user's manual update or a fallback location the rule defines.

On a build-out, that turns into five lines on the checklist. Write the three requirements into the phone vendor's contract. Enter the site's validated address and floor in the phone platform before the first handset is plugged in. Point the notification at someone who's physically at that site during business hours, not a shared inbox at headquarters. Confirm that no dial plan anywhere still needs a 9 to reach 911. And when a site moves, the location records move first, because a phone reporting the old address works perfectly right up until someone needs it.

Whether a specific configuration complies is a question for counsel and the vendor. The checklist's job is to make sure someone asked.

Design Wi-Fi from the floor plan, then copy the settings

Coverage comes from a survey against the floor plan, and the access point count comes out of that survey. The cabling section already assumed this: the two Category 6A runs go where the survey says, so the survey happens before the cabling bid.

New builds should buy for 6 GHz. In its April 2020 Report and Order, FCC 20-51, the FCC made 1,200 megahertz in the 6 GHz band (5.925 to 7.125 GHz) available for unlicensed use, including low-power indoor access points across the entire band, and said it was doing so to ease existing and anticipated Wi-Fi congestion. Access points stay on the ceiling for years, and hardware that can't use that spectrum locks the site out of it for the life of the gear.

What has to be identical everywhere is the configuration. Same network names, same authentication, same guest network walled off from corporate traffic, same VLAN plan. A laptop that works in one office should join in every office without a ticket. And size each closet switch's Power over Ethernet budget for everything you'll plug into it, because access points, phones, cameras, and door controllers all draw from the same box.

Conference rooms and doors come from a kit too

Conference-room AV is where sites drift, because every room gets designed by whoever is standing in it. The standard I'd set is a short list of room kits, a huddle room, a mid-size room, and the boardroom, each with a fixed bill of materials, one meeting platform, and the same controls on the table. The power and data drops for the display and the table belong in the cabling package so they're pulled with everything else. The room devices get enrolled in central management and placed on their own network segment, since a room system is a computer with a camera and a microphone in your most sensitive meetings.

Door access is identity with a lock on the end. Pick one platform for every site, so a badge behaves the same way at every location and every door's log lands in one place. Then tie badges to the same joiner and leaver process as accounts, so the badge and the laptop login stop working on the same day.

The hardware on the door isn't IT's call alone. Egress, and whether a lock releases or holds when the power drops, are life-safety questions for local code and the building owner, so bring the landlord and the fire alarm vendor into the door spec early. Across the AV and physical-security work I've done at a federal-facing ML company, a multi-site nonprofit, a healthcare services firm, and in private consulting, I've held one position: a room or a door that needs its own instructions is a one-off, and the support desk ends up owning every one-off.

Keep 27 sites on one version of the kit

Standardization fails when the standard lives in someone's head. Write the site kit down as one versioned document: the bill of materials, the rack elevation, the VLAN and network-name plan, the phone template with its 911 settings, the room kits, the door hardware spec, and the labeling scheme. Every new or moved site gets built to the current version.

Deviations get a written exception with an owner and an expiry date, because a site that was allowed to differ once will keep differing. When the kit changes, it changes as a new version, and older sites catch up on their refresh cycle instead of each one drifting on its own schedule. It's the same logic as treating architecture as guardrails a pipeline checks: the standard has to be cheaper to follow than to skip.

The kit also decides who does the work. Low-voltage cabling, AV installs, and door hardware are commodity labor, and renting them is fine. The standard, the acceptance test, and the sign-off stay in-house, which is the split I'd make between commodity and judgment anywhere. A standard kit is also what makes national vendor agreements possible, since you can't consolidate suppliers across sites that each bought differently.

Monday: audit three sites against the list

Pick three sites, including your newest one and the one that moved most recently, and check five things.

  1. Confirm the dial plan routes 911 with no prefix, then confirm the location record shows the current street address and floor. Coordinate any live test with your vendor and the local 911 authority first.
  2. Find out who receives the 911 notification, and whether that person is actually at the site.
  3. Open the closet. Look for a lock, a UPS, a temperature alert, and labels that match a drawing.
  4. Confirm the site has a second internet path that doesn't share the first one's way into the building.
  5. List every way the site differs from your best site. That list is the first draft of your kit.

Anything that fails item one goes to the top of the queue this week. The rest can wait for version one of the kit.

InfrastructureBranch ITNetworkingPhysical SecurityIT Operations