An SD-WAN assessment 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 a drawing of locations and last miles. It is not an SD-WAN assessment.
An assessment answers whether overlay, policy, and a written degraded state are even the job in front of you. It names the work that must stay usable, the failure each option is meant to survive, who changes policy after hours, and which underlays a later bake-off will hold constant. A map can prove that sites exist and that circuits have names. It cannot prove steering, ownership, or a security boundary that travels with the session.
The usual shortcut treats the drawing as finished homework. Someone pins every office, colors the primary and the backup, and calls that “the SD-WAN assessment.” The next meeting then becomes 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.
That is why the live SD-WAN providers brief treats a circuit map as an underlay drawing, not a shortlist. This note does not replace that page. It is the assessment reminder that sits in front of it. If a faster last mile is being used as the architecture choice, stop and use the SD-WAN versus MPLS page before anyone treats a capacity quote as the assessment.
What the assessment must hold
- Decision identity: add an overlay, replace a private WAN, dual-run for a term, or set a multi-site standard — plus who approves.
- Application register: the workflows 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 held constant: which circuits, wireless paths, and cloud handoffs sit under every option you will later test.
- Failure domains: last mile, building entrance, provider core, edge gear, power, and policy. Name the failure the assessment is meant to survive, and what it still shares.
- Operating model: who changes policy after hours, who opens the carrier case, and what internal IT still owns.
Questions that belong in the first meeting
Ask the incumbent or a challenger to show, not describe:
- Which applications they will not assess without, and how those paths are proven on the same underlays a later option will use.
- What continues, pauses, or is blocked on purpose 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 security inspection and logging stay with the session, and which stay on the site or a separate service.
If those answers are a circuit map and a promised overlay SKU, you do not have an SD-WAN assessment. 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. It is not a reprint of the live providers brief or the live SD-WAN versus MPLS comparison. Skip incentive talk, skip site pins as a substitute for a written degraded state, and skip any suggestion that a drawing replaces an assessment. Write the rows. Then use the live providers page when a shortlist is actually the next job, or contact The Data Partner on that packet. Planning questions that are not WAN-specific sit on the FAQs page.