US Fixture Data Analysis: Keep Indications, Offers and Agreements Separate

Decide what each record proves before calculating an average

A US chartering dataset should distinguish a planning indication, a specific offer and a supported agreement. These records can all inform commercial work, but they do not provide the same evidence. Combining them under a single fixture label can create an apparent market level that does not represent transactions actually concluded.

USDA's food-assistance ocean-freight page separately identifies tenders and awards in its published listings. USDA FAS ocean freight tenders.

That public-program example illustrates the importance of status without defining every private chartering record. A tender announces or describes a procurement opportunity, while an award record serves a different evidential purpose. The analyst should preserve what the source actually identifies rather than infer a completed shipment or broader market rate from the existence of a listing.

The same discipline applies to internal emails and broker reports. A number mentioned during a discussion is not automatically a fixture. A fixture report may still require confirmation of its source, basis and status before it is suitable for a particular analytical use.

Separate commercial status from the underlying measurement

Create record categories that reflect the information available. A broad market indication can remain useful for early screening if its limitations are retained. An authorized offer can support analysis of the alternatives available at a stated time. A supported agreement can inform a different analysis, subject to the terms and reliability of the record.

Do not use the category field to make legal conclusions beyond the evidence. Where formation or status is disputed, record the uncertainty and seek appropriate review. The dataset should describe the source and known facts rather than settle a disagreement by assigning a convenient label.

Next establish the measurement basis: currency, unit, quantity, route, timing and material service scope. Two records with the same status can still be unsuitable for direct comparison. A per-day figure and a per-tonne figure cannot be averaged together without a justified transformation, and a transformation requires assumptions that should remain visible.

Retain the observation date separately from the shipment period. An offer recorded this week for a later shipment is not necessarily evidence of this week's immediately available freight. The analytical question determines which date matters, so the dataset should preserve both rather than force one field to serve every purpose.

A fictional mixed dataset produces a misleading mean

Assume a hypothetical US cargo team has five records for superficially similar shipments. Two are early indications at $30 and $32 per tonne. Two are offers at $35 and $37. One is a supported agreement at $38. The simple average of all five numbers is $34.40 per tonne.

Calling $34.40 the average agreed freight would be incorrect because only one record is identified as an agreement. The mean of the two offers is $36, while the indications average $31. These separate summaries describe different evidence categories, and the single agreement is too limited to establish a broad transaction average.

Now suppose the $35 offer is a revision of the $37 offer for the same cargo rather than an independent alternative. Treating both as separate market observations would give that negotiation extra weight. The dataset should retain the history but link the versions so the analyst can select the appropriate observation for the question being asked.

Finally, assume the $38 agreement includes a service excluded from the two indications. Even the status-separated values are not yet commercially equivalent. The analyst needs the scope difference and a supported adjustment before comparing them on an all-in basis. These invented records demonstrate classification effects, not actual US freight levels or statistical evidence about a market.

Preserve benchmark definitions instead of treating them as cargo offers

The Baltic Exchange states that dry-bulk assessments use dollar-per-day time-charter or dollar-per-tonne voyage bases. Baltic Exchange indices.

A benchmark series belongs in the dataset with its own definition and source. It should not be relabeled as a quotation for the user's cargo. The analyst can compare a shipment estimate with an appropriately selected reference, but should explain the differences in vessel, route, timing and commercial basis that limit the comparison.

Do not fill missing shipment terms from a benchmark description unless the source explicitly establishes that relationship. A published reference can make an incomplete record look detailed while adding assumptions that were never part of the original transaction. Preserve missingness where information is genuinely unavailable.

If a normalization model is used, keep the original observation alongside the adjusted result. State the assumptions and identify which adjustments are supported and which are illustrative. A normalized number is an analytical output, not a newly discovered fact about the original negotiation.

The team should also be cautious about selection bias. Its internal records may reflect the cargoes it chose to pursue, the brokers it contacted or the offers it retained. A clean dataset can still be unrepresentative of the wider market. Describe the sample before drawing conclusions beyond it.

Match the analysis to the decision it will support

For early budgeting, a range of clearly labeled indications may be adequate. For evaluating procurement performance, the team may need comparable offers and the final selected terms. For reviewing realized economics, it needs additional evidence about actual costs and receipts. These are related datasets, not interchangeable answers to one question.

Choose summary statistics only after defining the population and basis. Explain how revisions, duplicates and incomplete records are treated. A concise statement of those choices makes the result more useful than a precise average whose contents nobody can reproduce.

Zeaclub's proposed freight-data review can help US teams organize evidence according to the decision it supports. Bring a sample of indications, offers and agreement records to Zeaclub for a structured discussion. The objective is an analytical foundation that preserves commercial meaning before turning records into charts, averages or market claims.

Sources

  • USDA FAS: Ocean Freight Tenders, checked October 24, 2026; primary indexed page inspected after direct access returned 403; tender/award labels only.
  • Baltic Exchange: Indices, checked October 24, 2026; assessment-unit distinction only, no current values or route specifications reproduced.

Related articles