Control tower mandates and decision rights

Visibility without authority changes nothing

The value comes from the intervention, not the screen. That means writing down what the function may do without asking: rebook a missed collection, authorise a partial despatch, switch a consignment to a faster service, hold a delivery pending stock, or instruct a site to reprioritise. Each of those spends money or disappoints somebody, so each needs an explicit permission. Where no permission exists, the tower can only observe and report, and it should be priced accordingly.

The data belongs to several parties at once

Feeds arrive from carriers, sites, customers and the client's own systems, and each source has its own owner, format and reluctance. Securing the right to receive and use that data, particularly from providers who may be under review, is a contracting task rather than a technical one. Agree who obtains each feed, who fixes it when it breaks, what the tower may share with other parties, and what happens to the accumulated data at the end of the mandate.

Escalation that ends in a decision

Escalation paths fail when they route to a role rather than to a decision. Useful design names the trigger, the person contacted, the time within which a response is expected, and the default action if nobody responds. That last element is what makes a path work outside office hours, and agreeing the defaults in advance is far easier than agreeing them during an incident with a customer waiting.

Measuring a function that never touches the goods

Delivery performance measures the network, not the tower. Sensible measures cover detection: how many exceptions were identified before the affected party reported them, how quickly interventions were made, how many escalations were resolved at the level they entered, and whether corrective actions from previous incidents were closed. Reporting the network alongside those measures shows whether the function is improving anything or simply narrating.

Frequently asked questions

Does a control tower need to be provided by a logistics company?

No. The function can sit with an orchestration provider, with an incumbent operator, or in-house with bought-in tooling. What matters is independence from the parties being monitored and enough authority to act, not who employs the team.

What is the most common reason these mandates disappoint?

Authority was never granted. The team detects problems accurately and then waits for a client decision that arrives after the moment for intervention has passed, which makes the function look expensive and slow when it is simply constrained.

Should the tower monitor the provider that operates it?

It can, provided the reporting on that provider is produced from data the client can verify independently and reviewed by someone outside the provider's account team. Otherwise the arrangement asks a supplier to mark its own work.