Move · the first
Re-route in time
A score moving from 30 to 65 on the 4-week horizon, with port queue and inland haulage named as the contributors, is the cue to convert a marginal volume to an alternate lane while the conversion is still cheap.
Live lane-level disruption forecasts, one decision-ready number per lane per week, with the contributing factors named explicitly. Calibration is published. The methodology is versioned and signed. The number is the product, not the dashboard.
For thirty years, operators of cross-border lanes have lived with two kinds of disruption forecast. The first is the trade press headline: a Suez incident, a Red Sea attack, a Panama drought. By the time the headline lands, the operational decision — the routing, the buffer stock, the freight contract — is already three weeks late. The second is the carrier dashboard: a wall of indicators, mostly correlated, mostly trailing, mostly impossible to translate into a number an underwriter can price against. Both fail in the same direction. They produce too much information, too late, in a form that cannot be used.
The Signal Routes premise is that the operator does not need more data; they need fewer numbers. Eight inputs, fused into one score per lane per week, with the contributors named so that the operator can see why the score moved. A score that moved because the inland-haulage segment of the lane is being disrupted is a different decision from a score that moved because the originating port is. We say which it is.
A disruption score that is not calibrated is decoration. A score of 70 needs to mean a 70 % probability of a disruption event of declared magnitude within the declared horizon, and it needs to mean that consistently across lanes, across weeks, across the cycles in the underlying inputs. Signal Routes calibrates against a rolling 52-week window. Calibration plots are published; the data behind them is published; the version of the methodology that produced any historical score is signed and held in the Library against the date that score was issued.
When the calibration drifts beyond the published tolerance — twice in the life of the product so far — we suspend new scores on the affected lane class, post a notice in the Library, and do not resume until the calibration is within tolerance. We have not, and will not, ship an out-of-calibration score and let the operator find out from the disruption.
A score moving from 30 to 65 on the 4-week horizon, with port queue and inland haulage named as the contributors, is the cue to convert a marginal volume to an alternate lane while the conversion is still cheap.
An underwriter pricing a trade-finance facility against a lane can read the score and the contributors directly into the pricing model. The contributors are stable across releases — the operator does not have to re-fit the model when the score moves.
A sourcing team reading the same score against the lanes their suppliers ship through can buffer the lanes that matter rather than buffering on the headline. The contributors tell the team which suppliers, on which lane segments, against which weather and port conditions.
When the disruption arrives — or, as is common, does not — the signed methodology and the calibrated score together form the defensible audit trail. The operator can show what the number was, what the contributors were, and what they did about it.
The most useful first conversation about Signal Routes is held against the lanes you actually operate. Name the five or ten lanes that carry most of your volume; we will run the scores against them, name the contributors, walk through how the score has moved over the last twelve months, and put the calibration plots on screen. The session is 45 minutes; the output is a written report you keep whether or not the engagement continues.