A conversation that starts with a circuit map — “here are the sites,” “these are the underlays,” “overlay the broadband” — usually fails at the first unowned application path, not at the first site pin. A circuit map is inventory. It is not what SD-WAN means.
SD-WAN is a policy-driven overlay that steers application traffic across underlays. The word names a delivery model: how sessions are classified, which path they take on a normal day and a degraded day, who changes that policy, and what inspection travels with the session. It does not name a drawing of last miles. It does not name MPLS. It does not name a faster DIA. It does not name an overlay vendor logo. Pins and colors can prove that sites exist and that circuits have names. They cannot prove steering, a written degraded state, or an owner after 5 p.m.
The usual shortcut treats the map as the category. Someone pins every office, colors the primary and the backup, and calls that “SD-WAN.” The next meeting is a product tour on a lab path that is not the production underlay. You still do not know whether voice, payments, or identity survive a degraded hop, or who opens the carrier ticket when they do not. Drawing another circuit does not create meaning. It creates another slide unless you write the overlay, the policy, and the work that must stay usable.
That is why the live SD-WAN assessment treats a circuit map as an underlay drawing, not the job. This note does not replace that page. It is the meaning reminder that sits in front of it. The assessment answers whether overlay and policy are even the work in front of you. This page names the category those questions assume. If a private WAN is being compared to an overlay as if they were the same object, use the SD-WAN versus MPLS page before anyone treats a capacity quote as the architecture. When the next job is which names belong on a list, use the SD-WAN providers brief after the category is written. If a faster last mile is being used as a substitute for steering, stop and use the business internet assessment rather than renaming a circuit map as SD-WAN.
What SD-WAN is not
- It is not a circuit map. Inventory of sites and last miles is an input. It is not the overlay, the policy, or the degraded state.
- It is not MPLS. A private WAN is a different underlay and a different operating bargain. Comparing them starts with the work that must stay usable, not with a logo or a pin.
- It is not a faster DIA. More megabits on one underlay do not classify sessions or steer them when that underlay degrades.
- It is not an overlay vendor logo. A brand can sell edge gear, a controller, and a security add-on under one word. The word still has to be unpacked.
What to write before the map
- Decision: add an overlay, replace a private WAN, dual-run for a term, or set a multi-site standard, plus who approves.
- Work: the applications that must stay usable, including voice and any payment or identity hop. Write the degraded state, not a copy of the primary megabit number.
- Underlays: which circuits, wireless paths, and cloud handoffs the overlay will steer across. The map belongs here as inventory, not as the category.
- Policy and ownership: who changes steering after hours, who opens the carrier case, and what internal IT still owns.
- Boundary: which inspection and logging travel with the session, and which stay on the site or a separate service.
Questions that belong in the first meeting
Ask the incumbent or a challenger to show, not describe:
- What they treated as SD-WAN, and what they treated as underlay, MPLS, or a security add-on sitting beside the overlay.
- How an application is classified and steered when a path degrades, not only when a link light goes out.
- Who owns a policy change after 5 p.m., and what evidence exists after it.
- Which inspection stays with the session, and which they will not discuss without a different product brief.
If those answers are a circuit map and a promised overlay SKU, you do not have an SD-WAN meaning. You have a drawing.
What this page is not
This is not a provider ranking, not an overlay product sheet, and not a claim that The Data Partner already replaced anyone’s WAN after a map review. The Data Partner is the advisor on the decision frame, not the overlay operator and not the carrier. It is not a reprint of the live assessment, the live SD-WAN versus MPLS comparison, or the live providers brief. Skip incentive talk, skip site pins as a substitute for a written overlay, and skip any suggestion that a drawing defines the category. Write what SD-WAN must mean for this organization. Then use the live companions, or contact The Data Partner on that packet. Broader buying questions sit on the FAQs page.