You can see the cargo receiving window weeks before you have to act on it. That is not the same as the window holding when you do.
This article is part of the TradeLanes decision-timing series.
The assumption
Most export teams have solved visibility.
The ERD is published. The CY Cut is published. The booking is confirmed. The cargo receiving window is on the screen, and it is on the screen early.
So the working assumption is reasonable: if you can see the window weeks out, you have time to plan against it.
You can see it. That part is true.
The question is whether what you saw is still there when the truck is dispatched.
Figure 1 - The Assumption
Seeing the window and controlling it are treated as the same thing. They are not.
Visibility is not the failure
Across 3,309 U.S. container export voyages departing between November and the end of March, the cargo receiving window was fully visible - both ERD and CY Cut published - at least two weeks before the final ERD for 87.4% of voyages.
That number does not change at one week. It is still 87.4%.
The reason it does not change is the finding most teams do not expect:
- 59.1% of voyages became fully visible more than four weeks out
- 28.3% became visible between four and two weeks out
- 0% became visible in the last two weeks
- 12.6% never became fully visible before the final ERD
Visibility in this window was binary. A voyage either showed its full window early, or it stayed opaque to the end. Almost nothing became visible late.
So early visibility is not the problem. By the time you are planning, the window is already on the screen.
Figure 2 - Visibility Is Not the Failure
The window is on the screen long before you have to act on it.
Control is the failure
Here is what happened after the window became visible.
Across the same cohort, the system produced 17,829 valid receiving-window revisions - real ERD and CY Cut changes, after filtering out initial publications and zero-change noise.
Of those revisions:
- 89.9% arrived after the voyage's window had already become visible
- 42.7% arrived inside the final 7 days
- 22.5% arrived inside the final 72 hours
Read that first number again. Nearly nine in ten revisions landed after the window was already on the screen.
The window did not stay where you first saw it. It kept moving, and most of the moving happened after you had already planned against it.
Figure 3 - Control Is the Failure
Seeing the window early did not stop it from moving late.
The gap between visibility and control
This is the shape of the problem.
Visibility arrives early. Motion arrives late. The two are not the same event, and they are not synchronized.
You see the window four weeks out. You build the plan: the drayage, the warehouse release, the appointment, the rail connection. The plan is built against the window you saw.
Then the window moves - in the last seven days, in the last seventy-two hours, inside the time when the plan is already committed and the truck is already scheduled.
The window you saw early and the window you executed against were not the same window.
Figure 4 - Early Visibility Is Not Early Control
Visibility tells you the window exists. It does not tell you it will still be there when you commit.
Why more monitoring does not close the gap
The instinct is to watch harder. Check the carrier site again. Check the terminal site again.
But the gap here is not a visibility gap. The window was visible. Checking it a second time confirms what you already saw.
The gap is between the moment you commit and the moment the window stops moving. More monitoring tells you the window changed. It does not tell you, at the point of commitment, whether the window is stable enough to commit against.
That is a different question, and it is the one that decides whether the truck rolls clean or rolls twice.
Figure 5 - More Monitoring Does Not Close the Gap
This is not a visibility gap. It is a timing gap.
The shift
The old question is a visibility question:
"Can we see the window?"
Almost always, now, the answer is yes. You can see it weeks out.
The better question is a timing question:
"Is the window still real when we act on it?"
That is the shift the data forces.
Early visibility tells you the window exists. It does not tell you whether the window will still hold when you commit. And once the truck is dispatched against a window that has not finished moving, the difference becomes cost.
The plan did not fail because no one was watching.
It failed because it was built on a window that was visible early and settled late.
Figure 6 - The Shift
The problem is not visibility. The problem is timing.
The problem is not visibility. The problem is timing. The signal arrives after the decision has already been made.
Part of the TradeLanes decision-timing series.
Leave a Comment