One View, Many Systems

"Single connected view" is one of those phrases that sounds like a dashboard and gets sold like one. But for anyone who coordinates work across other companies — a broker with shippers on one side and carriers on the other, and a stack of paperwork in between — the phrase means something more specific, and more useful, than a prettier screen. It's worth being precise about, because the version most software offers isn't the version that solves the problem.

What it is not

The common interpretation is a big central database everyone logs into. Pull every party's data into one system, put a screen on top, and call that the single view. It demos well. It also fails in practice for the same reason consolidation always does: it asks everyone to abandon the systems they already run and hand their commercial records to software a counterparty controls. Nobody outside your own company signs up for that, so the "single view" ends up showing only the slice of the operation you already owned — which was never the part you were blind to.

A view built by collecting everyone's data into one pool isn't connected. It's consolidated, partially, and stale the moment the other party updates their own system without re-keying into yours.

What it actually means

A genuine single connected view is a live read across systems you don't own — assembled from facts that still live where they were created. The shipper's ERP keeps the order. The carrier's system keeps the movement. The warehouse keeps the receipt. Nothing moves house. What you get is one place that answers where is this, and what's true about it right now, drawn from all of them at once.

The distinction isn't academic. It changes what the view is made of:

• It's a read, not a copy. The view reflects each party's current state instead of a snapshot someone imported last Tuesday. When the carrier marks a pickup, the fact surfaces in your view because it's connected to their system, not because a person retyped it into yours.
• It's facts, not filings. The view carries status, milestones, and document references — the small structured signals that say booked, in transit, delivered, proof-of-delivery ready. It doesn't try to become the master copy of anyone's documents; each party keeps its own archive.
• It's shared without being owned. Every party sees the same connected facts, and no party has to surrender its system of record to get them. The view is neutral ground, not one company's database with guests invited in.

Why it matters for a broker

A broker's entire job is coordination across parties who can't see each other's screens. The status calls, the "did the paperwork come through," the reconciling of a date that reads one way in the shipper's system and another in the carrier's — that's not overhead around the work, it is the work, and almost all of it exists because there's no shared, current view of facts everyone already agreed on. A connected view doesn't add a feature to that job. It removes the reason the job is so manual.

And it does it without a rip-and-replace. That's the part that makes it adoptable. Asking a broker to migrate to a new platform — and asking every shipper and carrier they work with to do the same — is a non-starter, which is why so many "single view" initiatives stall before they connect anything worth connecting. A connective layer inverts the ask: keep your system, keep your counterparties on theirs, and let the facts move between them.

How Veritas builds the view

This is the specific thing Veritas by ATG does. It sits between the parties as a connective layer — not a replacement for anyone's software — and moves structured facts along the paths that were missing, so each party's screen can show the same live state without merging anyone's books. The broker gets a single connected view because the systems are connected, not because everyone was herded into one system. The archive stays home; the facts travel; the view assembles itself from what's already true.

The same shape holds well beyond freight. A clinic coordinating a referral, a general contractor coordinating subs and suppliers, an adjuster coordinating a claim across parties — each wants one current view of a process that lives in several systems at once. Different paperwork, identical need.

The line to hold

A single connected view is not a place you put everyone's data. It's a live read of facts that stay where they belong. Get that distinction right and the phrase stops being a dashboard feature and becomes what it should have meant all along: the coordinator finally seeing the whole operation without asking anyone to give up their own.