Status is history. By the time a report shows the problem, the money is spent and the date has already moved. The Delivery Hub reads four ways at once: what happened, where you actually are, where this ends up, and what is coming that nobody has thought to look for.
Four fields of view. Most platforms have one.
This is business science applied to delivery. The practice made a science of reading a business. The Delivery Hub makes a science of running the programme that follows. Strategy, execution, delivery: one unbroken chain, and this is its last link.
Every programme on earth adds a percentage for contingency. Ten per cent. Fifteen if the client looks nervous. Twenty if the last one went badly. It is the largest unexamined number in the business, and it is chosen, not computed. The Delivery Hub runs your plan a thousand times: every task carries an optimistic, likely and pessimistic duration; every run respects the real dependency structure; the finish dates form a distribution. The fiftieth percentile is the honest date. The eightieth is the date you commit to. The distance between them is your contingency: measured, from your own work, not borrowed from a rule of thumb.
Contingency you can defend line by line, not a percentage someone chose.
On the record: one thousand simulated runs behind every date. Ask any supplier where their contingency came from. Then ask us.
A change request is raised, by your team or by the client in their own portal. It is triaged, checked against changes already in flight, assessed for impact, priced, and taken to the Design Authority. The Authority decides. The change moves the plan. The record carries every step and every name. Meanwhile the delivery teams run sprints, linked to the programme plan, so finishing work moves the plan; where sprint reality and the programme schedule part company, the platform says so rather than letting the two drift quietly apart for a quarter.
Everywhere else, these are four tools that email each other.
The steering pack is computed through the same path as the dashboards. The steering pack and the screen cannot disagree.
A programme does not slip because one task is late. It slips because that task sat at the head of a chain nobody had followed to the end. Trace any chain of work through every link, upstream or downstream, at task level or across whole workstreams, and across programme boundaries, where the chain leaves your programme and continues in somebody else's. See the whole programme on one canvas, time-true: zoom from the full span to a single week, switch the dependency web on, and watch what is actually holding the date.
Move one item and the consequence is not a matter of opinion.
Built to be presented: the argument that this programme is intricately connected, made in a room, with the evidence on screen.
The platform flags a risk. The programme acts on it. The outcome is recorded: mitigated, materialised, descoped or accepted. That outcome becomes evidence for the next programme. Raise a similar risk a year later and the form tells you what happened last time, the effort it actually took and the cost it actually carried, against the estimate you have just typed. Where the platform has flagged at a given confidence before, it reports how often it was right, and says so plainly when the sample is too small to mean anything.
The same discipline as the science. Predictions tracked, confirmed or falsified, on the record.
Corrections are evidence too: when you overrule the platform, the correction is kept and the platform is measured against it. The platform proposes. You decide. Nothing commits itself.
The practice's position is one sentence: strategy, execution, delivery, one unbroken chain. Elsewhere the chain breaks at every join: the strategy house hands the deck to an integrator, the integrator hands the plan to a delivery team, and every handoff sheds intent. Here, the verdict that read the business becomes the programme that changes it without ever leaving the record. Strategy arrives as concepts, backed by measurement. Execution turns concepts into commitments: scope, sequence, price, dates as distributions. Delivery turns commitments into deliverables, monitored in life, drift caught before the financials show it, governed by the same Design Authority from the first verdict to the last gate. For partners, the whole chain runs under your brand.
Concepts become commitments. Commitments become deliverables. Nothing is shed in a handoff, because there is no handoff.
The same chain drawn on the practice page, arriving at its last star. Run on fact, all the way to the date.