What to Ask About Provisioning New Sites
1. Does the platform support zero-touch provisioning out of the box?
A new device should be able to arrive at a site, get connected, and receive its full configuration automatically, without a network engineer on site or a technician manually applying a template. Cisco Catalyst Center built its plug-and-play model around exactly this, letting a Catalyst switch call home and pull its configuration the moment it powers on. Ask any platform you evaluate to demonstrate this end to end, not just describe it.
2. Can it template a site once and replicate that template across every new location?
The difference between a platform that scales and one that doesn't shows up at site 50, not site 2. Look for a design model where you define a site type once, including IP pools, VLANs, DHCP, and DNS settings, and every new site of that type inherits the template automatically. Cisco's site hierarchy model, where child sites inherit parent settings but can override specific details, is a useful reference point for what this should look like.
3. Does it work across the vendors you actually deploy, or only within one ecosystem?
Many platforms provision deeply within a single vendor's hardware and treat everything else as an afterthought. If your build projects mix hardware, from different switch vendors to different access point suppliers across regions or contractors, confirm the platform orchestrates all of it consistently rather than only the primary vendor's equipment.
4. How does it handle IP addressing, VLANs, and DHCP automatically at each new site?
Manually assigning address space and VLANs at every new site does not scale past a handful of locations. The platform should pull from a defined addressing scheme and apply it automatically as part of site provisioning, so a network engineer is not manually carving out address ranges for site 80.
5. Does it validate that a site is ready before going live?
Construction and build timelines are unpredictable, and a network provisioning platform should be able to confirm a site is physically and technically ready, cabling in place, power available, uplink connectivity confirmed, before attempting full provisioning. A platform that only discovers problems after go-live pushes that risk onto the go-live date itself.
What to Ask About Standardization and Governance
6. Does it enforce configuration standardization, or does every site drift over time?
The point of a platform is that site 200 ends up configured the same way as site 2, unless there is a defined reason for it to differ. Ask how the platform prevents configuration drift after go-live, not just how it handles day-zero setup. A platform with no ongoing compliance checking will look standardized at launch and drift within a year.
7. Can it represent legitimate differences between sites without breaking standardization?
Not every site is identical. A flagship retail location might need more access points than a standard store. A manufacturing site might need OT segmentation a corporate office does not. The platform should let you define these as intentional variations on a standard template, rather than forcing every site into one rigid configuration or, at the other extreme, treating every site as a one-off build.
8. How does it integrate with your existing change governance and ITSM processes?
New site provisioning does not happen in isolation from the rest of your IT operations. Confirm the platform can trigger from, or report back into, your existing ITSM and change management tooling, so a new site rollout produces the same audit trail as any other governed network change.
9. What audit trail does it produce for each site rollout?
When a compliance review or an internal audit asks how a site was configured and by what authority, the answer should already exist in the platform rather than requiring reconstruction from memory or scattered documentation. Confirm what gets logged automatically: what was configured, when, by which workflow, and under whose approval.
What to Ask About Scale and Operations
10. Does it maintain accurate inventory automatically as new sites come online?
Every new site adds devices, IP addresses, and configuration details to your network inventory. Confirm the platform updates this record automatically as sites go live, rather than depending on someone updating a separate inventory system after the fact.
11. Does it handle your target scale, not just your current scale?
A platform that works cleanly for 10 sites can behave very differently at 500. Ask specifically how the platform has performed at a scale close to your rollout plan, not just your current site count, and ask what happens to provisioning speed and reliability as site count grows.
12. What happens when something goes wrong during provisioning?
Failed provisioning at a new site should not leave that site in an undefined or partially configured state. Confirm the platform can roll back cleanly to a known state, alert the right team automatically, and provide enough detail to diagnose the failure without a technician needing to be on site.
