Safe-to-Gate Monthly
June 2026
June 2026 kept the shape March, April, and May established: paired mid-horizon revision, concentrated at Garden City, not a late-stage collapse at the boundary.
Published July 3, 2026 · Framework TradeLanes Safe-to-Gate Monthly v1.1 · Data baseline 2026-07-13 (100%-coverage mart, voyage-keyed) · Status Operator-facing
Q2 archive edition. This closes the Safe-to-Gate Q2 archive - March, April, May, and June 2026 monthly summaries - each linking to that month's weekly editions.
Data-baseline note (2026-07-13). Computed on the 100%-coverage mart (production U.S. export observations) and keyed on distinct vessel-voyages - normalized vessel name plus terminal - rather than booking/schedule-version rows, so a voyage published under two alliance carriers, or revised across many schedule versions, is counted once. The co-movement diagnosis is built on the operational cohort - the 641 June voyages that carry an Earliest Return Date. A further 52 voyages carry a CY Cut but no ERD; these are excluded from the co-movement analysis, since a voyage with no ERD cannot show paired movement.
This month's Safe-to-Gate weekly editions: Week of 7-13 Jun · Week of 14-20 Jun · Week of 21-27 Jun · Week of 28 Jun-4 Jul
1. Opening
Layer 1 · Headline · Opening Frame
June 2026 carried 4,602 CRW revision events across 693 distinct vessel-voyages at ten U.S. export gateways. Of those, 641 carried an Earliest Return Date - the operational cohort where the receiving window can actually move. Just under half of the month's revision mass, 49.6%, arrived beyond T-7. The movement that mattered sat inside the planning horizon, not at the late-stage boundary the system is built to catch.
2. The Mechanism
Layer 2 · Diagnosis
The three-element read
Contradiction. The network median window barely moved across June's planning horizon - and 641 operational voyages still generated thousands of revision events. Both readings are true because the aggregate hides where the mechanism operates: not in the median, but in the concentration.
Operator implication. The plan committed at T-4w met a wall of revision between T-14 and T-7 - 24.6% of the month's events - exactly the window where rail is committed and drayage dispatch is finalized. The commit was made against a shape that was still being redrawn.
Failure mode. Paired revisions arrive mid-horizon. The window reshapes as a unit - Earliest Return Date and CY Cut moving together. Stability never sets. The commit deadline arrives, the exporter commits against the latest shape, and the next revision overtakes it before the container reaches the gate.
3. Bridge to Evidence
Layer 2 to Layer 3
June did not break the Q2 pattern; it extended it. The same signature that ran through March, April, and May - paired ERD-and-CY-Cut movement, clustered mid-horizon, concentrated at a single Savannah terminal - is the story again. What follows is the evidence.
4. Quantified Proof
Layer 3 · Evidence
Half of June's revision mass arrived beyond T-7. 25.0% of events landed beyond T-14 and a further 24.6% between T-14 and T-7. Only 10.4% arrived inside T-3. The mechanism sits outside the 72-hour boundary and inside the planning horizon.
Paired ERD and CY Cut activity is the dominant signature. Among the 641 operational voyages, 42.0% showed both fields revising together - the largest class in the dual-signal breakdown - against 18.9% moving on CY Cut alone. The mode is sustained and paired, not divergent.
Volume held near May's level. 4,602 events across 693 distinct vessel-voyages, roughly 6.6 revisions per voyage - broad-based across carriers and ports, not isolated to one alliance. June's intensity matched May's without easing back toward the calmer months earlier in the year.
5. The Illustrative Case
Layer 3 · Named Evidence
ONE MAGNIFICENCE 0084W at USSAV Garden City (carrier ONEY, departing in June 2026). 15 Earliest Return Date revisions and 15 CY Cut revisions across the same voyage - 30 paired moves, roughly 3,600 hours of total absolute magnitude. The terminal moved the whole receiving window as a single unit, over and over, through the planning horizon. This is Sustained Churn in one voyage: not one large late shift, but a window that never stopped being redrawn.
6. Concentration and Repeat Offenders
Layer 3 · Where it concentrates
Part A - Concentration
USSAV Garden City - the mechanism in detail. Savannah carried the month's most active vessels (152 distinct vessels with revision activity) and its heaviest revision load by a wide margin: 1,853 events, more than three times the next port's. Los Angeles - the largest U.S. gateway by throughput - showed far lighter churn: 46 active vessels and 563 events. The contrast locates June's instability at Savannah, not at the largest gateway. (Vessel counts are reconciled and deduped on distinct vessel identity - a sailing published under two alliance carriers is counted once, per the 2026-07-13 carrier-attribution fix; the June events counts are unchanged.)
USORF - deferred pending methodology review. Several MAEU vessels at Norfolk again show heavy CY Cut activity with little or no paired ERD movement - the same pattern noted in Safe-to-Gate Monthly Dec 2025, where the recorded CY Cut moved back and forth without a matching change at the terminal. Until that pattern is confirmed against the terminal's own record, these voyages are left out of June's concentration finding.
Part B - Repeat Offenders
The heaviest paired-activity voyages in June cluster at Garden City across multiple carriers - ONEY, MSCU, and others - the same cross-carrier, single-terminal signature seen through the quarter. The churn is a property of the terminal's window management, not of one carrier's schedule.
7. Decision and Cost
Layer 4 · What to do
Part A - The Decision Shift
The commit horizon is wrong. Committing at T-4w means committing before half the month's revision activity has arrived. The window an exporter plans against in the fourth week out is not the window they will gate against.
The decision shift: where operational constraints allow, move the commit inward - toward T-7 to T-3, where the schedule carries the most information - even at the cost of a tighter planning horizon. Waiting is not passivity; it is buying a more reliable shape.
Part B - Operational Cost Chain
An early commit against a mid-horizon-unstable window cascades: rail is booked to a receiving date that moves, drayage is dispatched against a CY Cut that shifts, and the container either sits or misses. The cost is not the revision itself - it is the commitment made before the revision arrived.
8. System Statement + Forward Hook
Layer 5 · Close
Through all of Q2 2026, the operator's problem was not too many vessels at once. It was no stable point at which to act. June closed the quarter the way it opened: the window moves as a unit, mid-horizon, at Garden City, and the exporter who commits early commits against a shape already being overtaken.
The question July carries forward is whether the Savannah concentration holds, and whether the mid-horizon mass moves earlier or later in the window.
Methodology
Operational cohort. The co-movement diagnosis is computed on the 641 June voyages that carry an Earliest Return Date. The 2026-07-13 data baseline additionally carries 52 voyages with a CY Cut but no ERD; these cannot exhibit paired movement and are excluded from the co-movement analysis. Raw event counts reflect the full cohort.
Sustained Churn cohort definition. Voyages with paired ERD and CY Cut activity (co-moving) form the umbrella cohort under the voyage-level pattern taxonomy. Sub-modes are named in the framework appendix. Classification thresholds are maintained internally and not published.
Carrier-terminal exclusion. Maersk vessels at Norfolk's primary container terminal continue to show CY Cut revisions that are not matched by terminal activity - first noted in Safe-to-Gate Monthly Dec 2025 and still present in June 2026. MAEU/USORF voyages appearing in residual top-activity lists with CY Cut activity that does not reflect underlying terminal behavior are excluded from concentration findings until the pattern is confirmed against the terminal's record.
Cohort window. June 2026 U.S. departures with observable schedule revisions. 4,602 events across 693 distinct vessel-voyages. The full cohort definition and classification thresholds are maintained internally and held consistent across publications.
Editorial update, Nov 2026: wording of the Norfolk methodology note clarified; no figures changed.