The situation
You keep redrawing a diagram that is wrong before you save it.
Somebody owns the network documentation as a second job nobody funded. It is accurate on the day it is published and drifting by the end of that week, and everybody has quietly learned not to trust it.
Why documenting harder has never worked.
Every attempt to fix this has been a discipline problem dressed as a tooling problem: a better template, a stricter change process, a reminder in the ticket. They fail for the same reason, which is that the record is maintained by hand and the network is not changed by hand alone.
The gap that matters is not between the diagram and perfection. It is between what you meant to build and what is actually on the wire, and a hand-maintained picture cannot show you that gap because it only ever holds one of the two.
What to do about it
Stop maintaining the picture. Keep the record instead.
- Install it inside your walls. One command on a Linux machine. Docker, PostgreSQL that the install brings with it, and about 4 GB of RAM.
- Give it read-only credentials for one site. It starts discovering immediately and never writes to a device.
- It holds two records apart. What you intended, and what it found. The difference between them is the part worth looking at.
- Ask it in plain English. And every answer cites the record underneath it, so it can be checked rather than believed.
The tool for it
CrossConnect is the one for this.
It is the only one of the six that keeps running after you walk away, which is exactly why it should start on one site.
You will never update a network diagram again.
Start with one site, read-only, and see what the gap actually looks like.