Two ledgers for a proposed pause in maritime measures

1. Start with the right record

Transport customers and equipment buyers face different questions. Combining a ship’s voyage and a port’s equipment purchase into one “China cost” conceals the units behind the amounts. Even under the same news assumption, a booking schedule and an equipment plan require different evidence. Establish that distinction before entering amounts.

Suppose a vehicle exporter finds a “vessel-related surcharge” in its next shipping quote. Entering a vessel-wide total directly into its own budget could overstate its cost. Deleting the line on the assumption that freight already includes it could overlook a contractual charge. The first questions concern the ship, voyage and pool of cargo used for allocation. This fictional example provides a starting point; it is not an account of a company’s invoice.

The voyage and allocation tables are static references for matching an existing schedule or quote. Readers supply ship identity, voyage reference, entry timing, counting assumptions and cargo quantity, then retain unanswered items as questions for the operator. Nothing needs to be uploaded. The exercise identifies incompatible numbers placed in the same column; it does not certify vessel eligibility or perform a customs assessment.

2. Separate the existing pause from the next window

The Office of the United States Trade Representative’s Section 301 proposal would prevent liability and required payment for Annex I–III fees and V.A duties from midnight on 10 November 2026 through 23:59 on 9 January 2027, US Eastern time. Comments close at 17:00 on 30 October; adoption is pending.[S1] The current pause ends at 23:59 on 9 November.[S4] Retain both existing terms and an assumed-extension column.

The date table is a version record for explaining the assumptions behind a quote. Keep the date the quote arrived, the planned voyage date and the date a schedule changed. That makes it possible to investigate whether a price difference reflects a discount or altered timing. Including the same voyage reference in a query also helps when a counterparty is answering from an older schedule.

Time zones create another practical trap. A local date on the buyer’s schedule, a different zone on the carrier’s record and a customs timestamp can place a boundary event on different dates. Keep time and zone together, preserving the original display. Establish which event each timestamp describes before converting dates. A planned time and a recorded event also carry different levels of certainty.

3. A ship name does not settle coverage

Annex III covers foreign-built vehicle carriers; the modification uses net tons and caps collections at five per vessel per calendar year.[S2] This is not a rule for every container ship or every Chinese product. Actual coverage, exceptions and the relevant annex require an operator’s assessment. The exercise below starts after that assessment is assumed and examines counting and allocation.

A vessel’s name can change, and a trading brand need not identify the legal operator. Retain the ship identifier and voyage reference used in the underlying record, with commercial names in a supplementary column. Two similarly named rows could describe different voyages or a revision to one schedule. The purpose is to connect documents to the same event, rather than infer a legal conclusion from a name.

Cargo-origin work remains separate. Knowing where a car was made does not establish the unit of a transport surcharge, while a complete vessel file cannot replace equipment-classification documents. Our comparison of ship and cargo conditions in the FMC’s Spain proposal explains that distinction in another regime. The present question goes further: how many events are counted, and what denominator allocates their cost?

4. Match several ports to one voyage

CBP’s guidance, subject to exceptions and special rules, uses the voyage’s first US entry from abroad; the operator assesses applicability.[S3] In the fictional table, ship A visits US ports P, Q and R on voyage V1. Three US port names do not justify entering three fees. The real voyage boundary must nevertheless match the operator’s record, rather than be inferred from a map.

The distinction matters when discharge plans are aggregated. Regional sales teams can list the same ship and voyage in three delivery schedules. If every team copies the same surcharge notice, the group budget may count it repeatedly. Attach a common ship-and-voyage reference before aggregation, and keep port-specific delivery costs separate from the amount associated with the voyage as a whole.

Moving cargo from P to Q may change port-level allocation without changing the number of voyages in the table. Splitting the same volume between ships creates a different comparison. Record the operational change first and rebuild the cost rows afterwards. That sequence avoids updating quantities while leaving vessel costs untouched, or assuming that changing a port name removes a charge.

5. A cap cannot be understood by monthly proration

Where a charge has a collection cap, dividing an annual estimate by twelve does not explain the next voyage’s cost. Let F be the amount per event, n the number of counted events in the same year and C the cap. In a simplified case with unchanged terms and amount, the annual total is F × min(n,C), where min selects the smaller number. This is a planning sensitivity formula, not an automated test of coverage or exceptions.

For illustration, set F at 100 currency units and C at five. Four events produce 400; five produce 500; six still produce 500. Moving from four to five adds 100, whereas moving from five to six adds nothing to this particular line. Fuel and labour do not become free on a sixth voyage. The calculation separates the marginal increase in a capped component from the additional cost of transport as a whole.

That kink means equally long pause windows can produce different comparisons for different schedules. One vessel’s remaining events may lie below a cap; another’s may lie beyond it. Retain each vessel’s schedule and identify the included rows instead of relying on an average ship. The result alone does not estimate a carrier’s profit or the percentage change in global freight rates.

6. Calculate the year-end and new-year rows separately

A table using calendar-year caps needs separate totals for separate years. Suppose fictional year X already has four counted events, with two more planned before year-end and two at the start of year Y. Under the previous assumptions, the addition is one event in X and two in Y, or 300 currency units. Treating the four future rows as one continuous sequence conceals that result. Actual records first require a decision about which events belong in the count.

Now suppose a fictional window W covers one future row in each year. Excluding those rows leaves an additional 100 in X and 100 in Y: 200 against the baseline of 300, a difference of 100. Multiplying the two covered rows by F would instead give 200. The discrepancy arises because the cap also changes how the remaining rows affect the total. Every number is illustrative; the example does not say that voyages made during an actual suspension count towards collections.

The exercise locates sensitive assumptions before a schedule is changed. Weak evidence for the existing count produces a weak incremental calculation. Retain earlier records, reasons for excluded rows and the date a plan became an actual event, then update the table from the operator’s response. A change of year neither creates the same charge for every ship nor ensures that two annual caps will be exhausted.

7. Hold the voyage plan constant between scenarios

If the ship, cargo and entry dates all change between the extension and no-extension cases, the policy difference becomes unidentifiable. Copy one fixed schedule into two columns and change only the window-related assumption. Put an operational substitution in a separate comparison afterwards. The two stages distinguish the policy effect from costs incurred by obtaining another vessel.

Suppose ship A is secured under an existing agreement and substitute B is available only at another price. B could have a smaller vessel-related component but a higher overall quote. Base freight, capacity reservation, transshipment and delivery timing may explain the difference. A lower individual line does not establish a cheaper alternative; return to totals for the same volume and delivery requirement.

Our analysis of the Graham Act waiver and unimplemented tariffs discusses the difficulty of comparing a hypothetical burden with actual payments. The additional task here is to specify that baseline at vessel-and-voyage level. Without showing which events entered the no-extension column, a quote difference has no reproducible basis. Preserve the voyage references included in the comparison, rather than just its conclusion.

8. Allocating a vessel total to cargo

Equal allocation of a vessel cost F over q cargo units gives F ÷ q per unit. This is an assumed planning method, not a statutory charge on one shipper’s unit. Whether an invoice follows that method depends on the agreement and the carrier’s explanation. Capacity, actual load and a selected contract pool also produce different results from the same vessel total.

With F set at 1,000 currency units, allocation over 100 units produces 10 per unit; over 200 units it produces five. The vessel total remains 1,000. A halving of the allocated amount therefore does not establish that the policy charge halved. A changed denominator alone can alter a customer’s quote. These are not observed loads, actual vessel charges or a carrier’s invoicing method.

For a shipper with 20 units, the same assumptions give 200 or 100. Using its own 20 as the denominator and allocating the entire vessel cost to itself is not a valid comparison when other cargo is unknown. If the carrier cannot explain the allocation pool, retain conditional amounts and ask which quantity would change the result. Two traceable estimates can be more useful in a discussion than one falsely precise figure.

9. Equal unit counts can conceal different cargo

Equal allocation assumes cargo can be compared in a common unit. Differences in vehicle size, occupied space or handling can make a simple unit count unsuitable for commercial allocation. When applying the example, keep vehicle counts, area, volume and contractual equivalents distinct, specifying the chosen basis. Adding incompatible units does not create a useful denominator, however tidy the table looks.

Imagine ten small loads and ten large loads on one ship. Splitting cost equally by consignment can produce different customer amounts from allocation using contractual equivalents, while leaving the vessel total unchanged. Before asking which is the correct statutory amount, establish which allocation method the quote uses. Where no contractual equivalent exists, keep illustrative allocation separate from the invoice.

Do not rank quotes by their unit price alone. One may allocate over vessel capacity and another over booked cargo, making the lower figure a difference in scope rather than efficiency. Attach total cost, allocation pool, own quantity and unit to each quote, leaving missing information blank. Only after those scopes align can the price difference be investigated.

For a small test, assign one fictional equivalent to each of ten small loads and two to each of ten large loads. The pool contains 30 equivalents. Allocating a cost of 900 gives the small-load group 300 and the large-load group 600. Equal allocation across the 20 consignments instead gives each group 450. Both totals are 900, yet customer amounts differ. Ranking those unit prices without explaining the denominator is invalid. Check any real equivalence against the agreement.

10. A vessel cap is not a fleet cap

The earlier calculation grouped rows for the same ship. Even when one company operates A and B, do not assume unused space under A’s cap can be transferred to B. Calculating each vessel first and then aggregating can differ from pooling every event before applying a cap. Selecting the correct unit matters before refining the arithmetic. A company table and a vessel table serve different purposes.

Using the illustrative C of five and F of 100, six events for A and two for B give 500 plus 200, or 700. Applying one cap to all eight events gives 500, understating the comparison by 200. Duplicate departmental entries can instead overstate it. Retain vessel subtotals so the aggregate can be traced back to individual rows. Again, this is not an observed fleet or invoice.

A service name can remain unchanged while its vessel changes. If a substitution notice never reaches finance, the old ship’s count may be carried into the new ship’s calculation. Linking the original schedule row to its replacement is more traceable than silently deleting and recreating it. The same link helps identify where a forecast error arose.

11. An equipment import is a separate event

For Annex V.A STS cranes, chassis and related items, the event is consumption entry or warehouse withdrawal for consumption.[S2] Keep the transporting vessel’s row separate from the equipment import. Both may belong to one delivery project, but they require different evidence for assessing the relevant burden.

A port ordering equipment E, transporting it on ship A and installing it after discharge generates separate order, shipment, arrival, import, acceptance and commissioning records. “Delivery this year” could mean arrival or acceptance. Preserve the event named in each document instead of replacing it with that shorthand. In particular, a ship’s scheduled arrival cannot establish the equipment’s import event.

Our comparison of Canadian product tariff changes and customs timing provides a separate example of matching products to customs events. The equipment row here is not a device for multiplying a vessel charge by months or units. It is a distinct record for identifying which cost belongs to which event in an existing purchase. Product coverage and exceptions require checking the underlying documents with the responsible customs specialist.

12. Put the three units side by side

There are now three units: ship-and-voyage, allocated cargo unit and equipment import. The same invoice currency does not align their denominators. Translating a vessel total into cargo-unit cost requires allocation; spreading one equipment purchase over a port’s cargo requires additional assumptions about useful life and utilisation. A common currency alone cannot produce one combined logistics-cost percentage.

Adding a fictional 100 for a voyage to 1,000 for equipment can be appropriate for a cash budget. Dividing that 1,100 by only the current cargo, however, could allocate the entire cost of a long-lived asset to one movement. Label the purpose of the total: this month’s payments or the profitability of this shipment. The same numbers can require different aggregation when the question changes.

Showing a counterparty the column headings can be useful before refining amounts. Asking whether a row represents a ship, voyage or own cargo can expose a misunderstanding early. An amount-only query may receive an answer in another unit. Where logistics, equipment and finance staff share a table, specify the subject and period of each field, as well as its owner, to reduce later rework.

13. SG Group View: count, allocate, then examine equipment

SG Group reads the potential economic effects in three stages: the number of relevant events, the denominator used to allocate their cost, and the conditions connecting equipment to productive use. A wrong event count cannot be repaired by a detailed freight model. Different allocation pools produce different shipper amounts from the same vessel total. At the equipment stage, a changed purchase cost does not immediately create port capacity. The sequence identifies where the result changes.

This framework challenges a uniform global logistics estimate based only on the policy’s duration. Measurement needs the distribution of each ship’s events and the allocation to cargo. Conversely, an event near a cap can be overlooked. Even with a small change in the average, the treatment of a particular voyage or quote may change enough to affect a purchasing comparison.

The interpretation gains support when an operator’s explanation matches the schedule and a comparable quote shows the relevant line changing. It weakens if base freight explains most of the difference, the allocation pool changes, or equipment timing moves beyond the window. Matching this evidence to individual rows makes the reason for a revised assessment traceable.

14. How a vessel-level difference could reach a network

One route from a vessel cost to the wider network is fleet allocation. Different ships have different schedules, agreements and available capacity, changing the economics of assigning cargo. Yet a cheaper option in a spreadsheet may not be available at the required place and time. Turning the cost comparison into transport requires an actual connection between vessel and cargo schedules.

If demand concentrates on some services, capacity could become easier to obtain elsewhere. A lower vessel-related component and a lower customer freight rate need not move together. Base freight on a congested service could offset the component’s decline; a service seeking cargo could show a larger price change. These are conditional supply-and-demand mechanisms, not observations of current freight rates.

Testing a network effect requires quotes for the same lane, cargo terms and similar booking time. Mixing ports or booking lead times confounds the policy effect with ordinary price differences. For a purchasing team, a consistent record on its own lane can inform the next order before any global average becomes available. Those matched observations connect the ship-level comparison to a cargo decision.

15. Where the amount reaching a customer can change

Customers on the same ship can experience different timing because their contracts reset at different dates. A long-term customer may retain an agreed rate, while a late booking reflects current capacity conditions. Compare the event used for costing with the date at which freight was set. A change in the vessel record need not immediately change the shipper’s payment when the price remains contractually fixed.

Consider separate assumptions of full pass-through, half pass-through and inclusion in an unchanged fixed price. With a fictional F of 1,000 and the customer’s allocation share at 10%, the amounts are 100, 50 and no additional price change respectively. Zero here means no change in this customer’s price, not no vessel cost. The agreement determines which comparison is relevant.

Treating a carrier cost reduction as profit growth for every exporter misidentifies who receives the benefit. An unchanged price could leave the difference with the transport provider; competition could transfer more to customers. Linking the issue to business or equity valuation therefore requires evidence across three bridges: the cost unit, allocation and price transmission.

16. The distance from an equipment price to port capacity

A changed equipment quote does not make a port handle cargo faster on the same day. Delivery, installation, connections to power and surrounding facilities, and required testing stand between purchase and use. A single chart combining transport cost and productive capacity can hide that interval. Keep procurement stages separate from the expected commissioning date.

17. Counterargument: available space may matter more

A strong objection is that actual space at the required time matters more than surcharge arithmetic. Where delay interrupts production or sales, paying more for reliable transport can be rational. A precise cap calculation has little value if it includes an unavailable ship. Start with alternatives that can actually be arranged.

Add available quantity, deliverable scope and quote conditions alongside cost. If the cheaper option carries only part of the required volume, compare the combined cost of moving the remainder elsewhere. With only 60 of 100 units on the cheap service, applying its rate to all 100 understates the total. Split the volume first, then aggregate service-specific and common costs.

Prioritising space does not remove the need to establish cost units. Urgent bookings make it particularly useful to know which additional charges remain after contracting. The table does not prescribe the cheapest route; it explains expenditure attached to a feasible transport choice. Cost, quantity and timing on the same row make the trade-off visible.

18. Separate policy and schedule scenarios

Three branches are useful. First, a formal decision matches the assumed window and scope: apply those terms to the existing schedule. Second, the decision changes coverage or timing: reselect the affected rows. Third, policy terms match the assumption but vessel or equipment dates move. Keeping the third branch separate prevents an operational change from being attributed to policy.

If a fixed schedule has two events inside W but one is later delayed, the forecast-to-actual difference includes that delay. Map differences to policy terms, schedule changes, allocation changes and base freight. Do not automatically attribute the unexplained remainder to policy. A large residual is a reason to investigate missing comparison records.

The branches do not assign a single market direction. Even favourable policy assumptions coexist with changes in demand, fuel, currency and available space. The next test concerns evidence identifying the branch and its associated spending requirements. Preserve the earlier table when revising a forecast, showing which changed input changed the conclusion.

19. Blanks that should remain blank

The notice does not establish an individual assessment, actual collection history, a carrier’s allocation denominator or customer price transmission. Filling a blank with zero turns an unknown cost into an absent one. Mark an unresolved amount as such, identifying the document and counterparty needed to resolve it. That makes the next inquiry concrete.

For the annual count, port-entry history and a history of counted charges are different records. The former does not establish the remaining cap without evidence for the latter. The largest leap from illustration to practice would be treating event classification as automatically settled. Distinguish operator-confirmed rows from unresolved ones and make calculations containing the latter conditional.

For equipment, return to specifications and procedural evidence instead of assigning coverage from a generic product name. Do not paste an old rate or exception directly into a current agreement. Classification and individual terms can change the comparison even when the equipment name stays the same. Where evidence is missing, a budget with separate unresolved components is more useful than an average of unsupported estimates.

20. Which column the next document would change

The next formal decision would change the window’s final scope and timing. More comments alone would not settle the application column. What matters is which existing term a formal document changes, rather than the comment count. Retain its version and the specific changed condition. The source list distinguishes filing from Register publication.

An operator’s response changes ship-and-voyage matching, event classification or evidence for prior counts. A revised quote changes the customer amount and allocation method. An equipment procedure record changes that import’s event date. Assigning each source to its column avoids rebuilding the entire table whenever one document arrives and allows the new number to be read against the old assumptions.

Market moves after an announcement do not by themselves establish causation. Retain contemporaneous fuel, currency and booking changes, testing for a difference in the policy-related line. A formal decision, actual operating record and comparable quote together move the assessment beyond expectations. Where one is missing, preserve the remaining assumption when updating the view.

21. Apply the tables to one existing case

Choose one existing transport case, recording quote version and cargo quantity. Add the operator’s ship and voyage references and check for duplicated port rows. Then attach evidence for coverage and the annual count. Where something is missing, retain an inquiry instead of turning an assumption into a final result. Use existing records you are authorised to use; no collection of another party’s confidential data is needed.

Copy the same schedule into the two policy cases and compare by ship and year. Moving from a vessel total to the customer amount requires an allocation denominator and price-transmission terms. Record any equipment purchase separately instead of forcing it into the voyage row. Finally, aggregate funding needs separately from shipment profitability. The sequence shows which subtotal and decision a changed row affects.

The static checklist is a starting point for that comparison, not a saved-input form or automatic vessel-fee service. Copy it to paper or a local spreadsheet, retaining evidence references and unresolved questions. For other regimes or background, browse related subjects in the same-language article index. Check each article’s displayed access conditions.

22. Correct arithmetic can still produce a wrong comparison

Error checking need not begin by recalculating the total. Three ports counted as three voyages can yield correct addition for the wrong grouping. Two ships under one pooled cap use the wrong unit even if the formula runs. Allocating the entire vessel cost to only one customer uses the wrong denominator even if division is correct. A short description of each row’s event exposes errors upstream of arithmetic.

Different observation periods create another error. Comparing a year-end total with one including new-year voyages builds timing differences into the result. The same problem arises when one equipment purchase is compared with several months of transport. Identify start and end, included ships and cargo scope, then construct matched subtotals. Comparing corresponding components first makes the final difference easier to explain.

After a revision, check for obsolete assumptions elsewhere. A changed voyage schedule with an old allocation quantity disconnects vessel cost from the customer amount. Revised equipment timing with an unchanged payment schedule distorts funding expectations. The tables need not be merged; common references can connect them. Linked separate records are more useful than a single blended average.

23. Final assessment: identify the event behind the amount

The practical takeaway is a sequence for questioning a quote, rather than one forecast for logistics costs. Align relevant events, count by ship and year, allocate to the cargo denominator and keep equipment records separate. That identifies which amount changes when the policy assumption changes and which stays. Revising every line proportionally to the window’s length conceals the distinction.

The global economic implications can be assessed by building up those links. A more favourable cost assumption for a ship or purchase reaches freight prices, exporter profits and port capacity only through additional conditions. Following where the benefit remains and when it appears separates supported expectations from unsupported ones. A broad impression of improved trade conditions does not establish a particular company’s profit or a trading decision.