August 24, 2026
A multi-location business internet requirement that starts with a provider list usually fails at the first unowned workflow, not at the first logo. A shortlist is a channel map. It is not the brief. If you do not write what has to work at each location, what happens when it does not, who owns the outcome, and which dates would make a delay disruptive, the next familiar carrier still controls the conversation.
That is why the live multi-location business internet requirements page starts with the decision, then a location inventory, then the workflows the network carries, then resilience, ownership, and timing : not a roster. This note does not replace that page. It is a supporting reminder that a quote packet is a screening input, not the requirement.
What the public briefing is actually about
A Telarus HITT session dated 28 May 2024 records a mid-market networking conversation about demand that has already moved past "one circuit, one site." Speakers define an advanced network as anything beyond a single connection at a single location: multiple sites, multiple products, and often more than one access type. They list four buyer requirements that keep showing up: the path has to perform the work it was bought for; it has to stay available, which usually means more than one path; the team wants visibility into who is on the network and what they are doing; and spend and tools have to be optimized instead of stacked.
The same session later uses an eighty-location example and an SLA written as the ability to pass and receive traffic at the location, not as a credit on one circuit. Treat those notes as industry calendar, not as a finished design. Do not import partner process notes, supplier SKUs, incentive talk, or a named-provider rescue story onto a public buyer page. It is not a Data Partner engagement, not a win story, and not a recommendation of any firm named on that call.
What to add to the multi-location business internet requirements brief
Before anyone treats a provider list as the answer, fill these rows:
- Decision identity: what is changing, why now, who owns the outcome, and whether the problem is still being defined or a bounded option is being compared.
- Location inventory: current and planned sites, the role each site plays, current connectivity and known reliability issues, contract or renewal dates, whether the site is opening, moving, or changing how it operates, and who can validate that location. Addresses are not required for the first conversation.
- Workflows the network carries: cloud and SaaS, voice and video, payments or warehouse work, remote access and identity, and guest or device traffic that must stay separate. Record what users notice when the path degrades.
- Resilience: which locations need a backup path, what traffic must continue, how teams will know a failure happened, who escalates, and how the plan will be tested.
- Ownership: who owns policy, monitoring, vendor responsibility, and incident process : including security and finance, not only the network team.
- Timing: decision date, existing contract milestones, approvals, construction or lease dates, and the operational date that cannot move.
The multi-location connectivity assessment is the companion when the inventory has to become a next-step brief. It is not a substitute for writing the requirements. The redundancy and failover worksheet is the companion when one site still needs a failure-domain design.
Questions that belong in the first meeting
Ask the incumbent or a challenger to show, not describe:
- Which locations and workflows they believe are in scope now, and which they would refuse to bid without writing down first : not a logo wall.
- What continues at a transaction site versus a back-office site when the primary path fails, and who owns that failover.
- How they keep the same comparison criteria if two carriers and an overlay provider all receive the same brief.
- What evidence you get after a location cannot pass traffic, and who tests that before the prior service is disconnected.
If those answers are a provider list and a promised install week, you do not have a multi-location business internet requirement. You have a shortlist.
What this post is not
This is not a HITT reprint, not a carrier ranking, and not a claim that The Data Partner already designed anyone's branch fabric after a Tuesday call. Skip incentive talk, skip branded OEM menus, and skip any suggestion that "who is on-net" replaces owners and dates. Use the live multi-location business internet requirements checklist, write the locations and the work, then request the next conversation.