Note

A quiet link is a working link

A standby service that stays quiet is doing what it was bought for. Here is the rule we build to and the six gates that enforce it.

Type: Note
Updated: 10 September 2026
Reading time: 5 min

A telecom expense tool that reads utilisation will eventually find a link running at three per cent of its contracted capacity. The tempting move is to call that waste and put a number on it. It is usually the wrong call.

Backup and DR circuits are supposed to be quiet, because that is the product being delivered. A contractual minimum commits you to capacity whether or not you use it. Burst headroom exists so that the ninety-ninth percentile costs money rather than an outage. Seasonal capacity is idle for ten months by design, and an out-of-band management link carries almost nothing until the day it carries everything.

So a candidate finding has to earn its place. Six gates stand between an observation and a claim we would put in front of a carrier.

The six gates

Every gate is a question with a recorded answer. A failed gate keeps the candidate, marks it suppressed, and stores the reason, so the estate learns something either way.

Billing history: the charge appears on at least three consecutive invoices, with no credit or dispute already in flight
Coverage: high enough to support a waste claim, with no counter discontinuities, and idle hours distinguished from hours where the poll returned nothing
Window: at least thirty days, including one complete billing period
Role: not backup, DR, burst, seasonal, test, out-of-band management or a diverse pair, and not unknown
Contract: no minimum commitment this service helps meet, and an early-termination exposure smaller than the projected saving
Identity: the invoice line, the service and the monitored interface joined with a recorded method and a high confidence

So what is waste

Two things clear all six gates, and we keep the word for those two alone. A confirmed billing error, where the carrier has charged for something the contract does not support. And a cleared ghost: a service disconnected at the site that is still on the invoice, evidenced by a disconnect acknowledgement and a recurring charge that outlived it.

Both are recoverable, both are arguable in front of the carrier, and both carry a snapshot of the role, the contract and the coverage as they stood when the verdict was reached. That snapshot is what survives a carrier's pushback four months later, which is the only test that matters.

Everything else stays an observation. That is exactly what a utilisation figure is.

Utilisation is a question

A utilisation figure becomes a verdict only when three other facts sit beside it: what the circuit is for, what the contract obliges you to, and how much of the period was actually observed. On its own it is a prompt to go and look.

So the product renders utilisation neutrally. Subscribed capacity and delivered traffic are drawn in colours that stay quiet, with the circuit's role as a badge and the coverage as a chip. A design token waits for the evidence rather than pre-empting it.

The role badge is doing most of that work, which is why the role gate treats a blank as seriously as a backup.

Unknown is a task

An unroled circuit is an onboarding task: somebody has to say what it is for. Suppressing on an unknown role turns it into a data-quality item that makes the inventory better, rather than a false positive that costs the tool its credibility.

This is also how the system learns your group. A dismissal is data, kept with its reason. Over a few months the suppression reasons describe your estate: which sites hold diverse pairs, which contracts carry minimums, and which circuits still need an owner.

The utilisation figures themselves, the coverage rules behind them and the read that produces them are on the bandwidth page.

Bandwidth utilisation

A woman at a crossing in warm evening glow

Send three invoices. A person replies with what they show.

Request a pilot